René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Autodetect IPs used inside the VM","articleBody":"With regards to IP info reporting, Cloudstack relies entirely on it's DHCP data bases and so on. When this is not available (L2 networks etc) no IP information is shown for a given VM.\r\n\r\nI propose we introduce a mechanism for \"IP autodetection\" and try to discover the IPs used inside the machines by means of querying the hypervisors. For example with KVM/libvirt we can simply do something like this:\r\n\r\n```\r\nroot@fedora35 ~]# virsh domifaddr win2k22 --source agent\r\n Name       MAC address          Protocol     Address\r\n-------------------------------------------------------------------------------\r\n Ethernet   52:54:00:7b:23:6a    ipv4         192.168.0.68/24\r\n Loopback Pseudo-Interface 1                      ipv6         ::1/128\r\n -          -                    ipv4         127.0.0.1/8\r\n```\r\n\r\nThe above command queries the qemu-guest-agent inside the Windows VM. The VM needs to have the qemu-guest-agent installed and running as well as the virtio serial drivers (easily done in this case with [virtio-win-guest-tools.exe](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.215-2/virtio-win-guest-tools.exe) ) as well as a guest-agent socket channel defined in libvirt.\r\n\r\nOnce we have this information we could display it in the UI/API as \"Autodetected VM IPs\" or something like that.\r\n\r\nI imagine it's very similar for VMWare and XCP-ng.\r\n\r\nThank you","author":{"url":"https://github.com/NuxRo","@type":"Person","name":"NuxRo"},"datePublished":"2023-01-30T09:39:30.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/7142/cloudstack/issues/7142"}