Getting IP Address of QEMU Guest

[prologic]

So I did a bit of research and found what I believe is a viable and reliable way of getting the IP Address of a QEMU Guest.

$ qm agent 302 network-get-interfaces | jq -r '.[] | select(."hardware-address" == "42:24:09:dd:1c:73") | ."ip-addresses" | .[] | ."ip-address"'

Basically this requires that the qemu-guest-agent is installed on the guest and qemu-ga daemon is running. You can then either run qm agent <vmid> <command> or probably talk tot he UNIX sokcet directly on the PRmoxox VE host.

[prologic]

A fallback mechanisms would be to run arp -a on the host. This gives you an output like this:

root@vz1:~# arp -a
? (10.0.0.14) at 36:32:31:61:32:66 [ether] on vmbr0
? (10.0.0.1) at 4c:5e:0c:a0:a6:25 [ether] on vmbr0

[lnxbil]

Both are viable, yet I do not know if the qemu-agent gets installed in the boot2docker iso

[prologic]

I'm actually more interested in RancherOS myself and filed rancher/os#2267 for this very reason.

I think using qemu-guest-agent is going to be more reliable; so I would almost make this a hard requirement that if you want to use this driver, your guest better have this agent installed and running.

[lnxbil]

Yes, I agree. I've never tried something else besides the default docker machine OS, so I'm open to this.

[prologic]

Yeah no worries. RancherOS is what I run everywhere in production. I deploy clusters of 3-5 nodes running with Docker Swarm mode (builtin/native to Docker engine). James Mills / prologic E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au

…

On Mon, Mar 5, 2018 at 7:11 AM, Andreas Steinel ***@***.***> wrote: Yes, I agree. I've never tried something else besides the default docker machine OS, so I'm open to this. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABOv-o9xxmNkupEK4EQ1164xt9VYRujrks5tbVWMgaJpZM4Sbh3I> .

[lnxbil]

I just stumbled over your entry in RancherOS by chance .. Good to know that we're going to have support in RancherOS. I haven't found any entry in the boot2docker issue tracker about this. Are so few people using KVM/QEMU and docker?

[lnxbil]

You idea with RancherOS works perfectly. We're going to make this the default:

root@proxmox4 ~ > pvesh create nodes/proxmox4/qemu/7321/agent -command network-get-interfaces
200 OK
{
...
     {
         "hardware-address" : ....
         "ip-addresses" : [
            {
               "ip-address" : "1.2.3.4",
               "ip-address-type" : "ipv4",
               "prefix" : 16
            },
            ....
      },
...
}

[prologic]

Coool :) That is awesome! James Mills / prologic E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au

…

On Mon, Apr 16, 2018 at 5:19 AM, Andreas Steinel ***@***.***> wrote: You idea with RancherOS works perfectly. We're going to make this the default: ***@***.*** ~ > pvesh create nodes/proxmox4/qemu/7321/agent -command network-get-interfaces 200 OK { ... { "hardware-address" : .... "ip-addresses" : [ { "ip-address" : "1.2.3.4", "ip-address-type" : "ipv4", "prefix" : 16 }, .... }, ... } — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABOv-vg6lIFL6vee6EHUdQyeVMf_cF0aks5tpIw6gaJpZM4Sbh3I> .

[lnxbil]

In addtion, I just build Boot2Docker with support for QEMU Guest Agent and created a pull request in boot2docker/boot2docker#1319. This actually works right now!

[prologic]

Niiiiccee! James Mills / prologic E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au

…

On Mon, Apr 16, 2018 at 11:54 AM, Andreas Steinel ***@***.***> wrote: In addtion, I just build Boot2Docker with support for QEMU Guest Agent and created a pull request in boot2docker/boot2docker#1319 <boot2docker/boot2docker#1319>. This actually works right now! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABOv-tTLKws2WgbmA4s0FyL4mUhj9UvXks5tpOjlgaJpZM4Sbh3I> .

[lnxbil]

So, we can close this, because the detection works now.

[prologic]

Cool (y) James Mills / prologic E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au

…

On Wed, Apr 18, 2018 at 2:43 PM, Andreas Steinel ***@***.***> wrote: So, we can close this, because the detection works now. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABOv-pDfdOWEmj2wHj0k72d1U0T88Omcks5tp7OAgaJpZM4Sbh3I> .