Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot find qemu.json. #23

Open
navhos opened this issue Nov 6, 2017 · 2 comments
Open

Cannot find qemu.json. #23

navhos opened this issue Nov 6, 2017 · 2 comments

Comments

@navhos
Copy link

navhos commented Nov 6, 2017

The qemu.json file cannot be found in /etc/libvirt/hooks/.
However, hooks.json is located there. These are the contents of hooks.json:

{
    "cloud-admin": {
        "interface": "virbr1",            // you can use comments
        "private_ip": "192.168.124.10",   /* both styles */
        "source_ip": "8.8.8.8",
        "port_map": {
            "tcp": [[1100, 3000], 443]
        }
    },
    "cloud-node1": {
        "private_ip": "192.168.126.2",
        "port_map": {
            "tcp": [[1101, 80],
                    [1102, 443]]
        }
    }
}

Could anyone advise on how I can edit this file to suit my network configuration settings?
I am using an ethernet connection on the host machine(Ubuntu 16.04LTS), and a NAT configuration on Cent OS 7 VMs.

@oscziryak
Copy link

The name has to be the name of the VM as known to libvirt. The private IP has to be the one known to the host. And for the host map, the first number is the port on the host. The second number is the port on the VM.

@claes
Copy link

claes commented Jul 30, 2018

The documentation could be clearer about the filename. I suspect that qemu.json is a reference to what it was called previously and the documentation is not updated? Or vice versa? In any case, the installation does not create the qemu.json file so either the user is expected to create it themselves, or they should edit hooks.json. But from what I can tell, hooks.json is the file that is read

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants