[GH-ISSUE #387] libvirt: QEMU Driver error : argument unsupported: Unknown IP address data source 3 #239

New issue

Open

opened 2026-02-27 15:57:55 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 15:57:55 +03:00

Owner

Originally created by @xujianhua1974 on GitHub (Nov 9, 2020).
Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/387

When I open an instance view page, I can see a libvirt error message in the project running window (in pyCharm IDE) as following:
libvirt: QEMU Driver error : argument unsupported: Unknown IP address data source 3
I don't know which function code produces the error. Although the instance view page is shown properly

Originally created by @xujianhua1974 on GitHub (Nov 9, 2020). Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/387 When I open an instance view page, I can see a libvirt error message in the project running window (in pyCharm IDE) as following: `libvirt: QEMU Driver error : argument unsupported: Unknown IP address data source 3` I don't know which function code produces the error. Although the instance view page is shown properly ![screenshot](https://user-images.githubusercontent.com/68722846/98523695-2af22480-22b1-11eb-8848-a5193ee294fa.png)

kerem commented

2026-02-27 15:57:56 +03:00

Author

Owner

@catborise commented on GitHub (Nov 9, 2020):

It is related with ip address query. It checks two way. One of them is qemu-guest-agent other one is arp query.
One of them produces this error. But it is harmless.

@catborise commented on GitHub (Nov 9, 2020): It is related with ip address query. It checks two way. One of them is qemu-guest-agent other one is arp query. One of them produces this error. But it is harmless.

kerem commented

2026-02-27 15:57:56 +03:00

Author

Owner

@xujianhua1974 commented on GitHub (Nov 10, 2020):

@catborise Thank you very much

@xujianhua1974 commented on GitHub (Nov 10, 2020): @catborise Thank you very much

kerem commented

2026-02-27 15:57:56 +03:00

Author

Owner

@xujianhua1974 commented on GitHub (Nov 10, 2020):

@catborise , I found another problem, I had pacemaker cluster to manage HA vm instances, and I wrote a script to disable the cluster resource related vm instance, and changed the instances views:poweroff function code just call the script if the vm instance is managed by pacemaker cluster. When I shutdown a vm Instance from the instance view page by clicking the Poweroff button, and I saw the VM was shutdown indeed from the host terminal through virsh list --all, but the instance view page kept wrong #power tabpanel from changed, and I saw the page kept runnging the interval get_status javascript of the instance.html as the same with other vm instances through the project running window (in pyCharm IDE), the page kept frequently flashing a hint "waiting http://127.0.0.1" at the bottom of the broswer. Even if I refreshed the page by clicking the refresh icon of the vm instance page or through F5 (browser refresh button), no change occured. The instance view page was shown properly only if I closed the page, and reopened the vm intance page. Aslo, the intance view page was shown properly when I clicked poweron button (changed the instance status from shutdown to startup). I saw no change occured on the vm instance database during the VM shutdown and startup, and the HA VM running on the same host in the pacemake cluster every time when it startup. What may be the root cause?

The instance view page was shown properly as following only if I closed the page, and reopened the vm intance page or clicked other links to change the page and return the vm instance view page .

@xujianhua1974 commented on GitHub (Nov 10, 2020): @catborise , I found another problem, I had pacemaker cluster to manage HA vm instances, and I wrote a script to disable the cluster resource related vm instance, and changed the instances views:poweroff function code just call the script if the vm instance is managed by pacemaker cluster. When I shutdown a vm Instance from the instance view page by clicking the Poweroff button, and I saw the VM was shutdown indeed from the host terminal through virsh list --all, but the instance view page kept wrong #power tabpanel from changed, and I saw the page kept runnging the interval get_status javascript of the instance.html as the same with other vm instances through the project running window (in pyCharm IDE), the page kept frequently flashing a hint "waiting http://127.0.0.1" at the bottom of the broswer. Even if I refreshed the page by clicking the refresh icon of the vm instance page or through F5 (browser refresh button), no change occured. The instance view page was shown properly only if I closed the page, and reopened the vm intance page. Aslo, the intance view page was shown properly when I clicked poweron button (changed the instance status from shutdown to startup). I saw no change occured on the vm instance database during the VM shutdown and startup, and the HA VM running on the same host in the pacemake cluster every time when it startup. What may be the root cause? ![4](https://user-images.githubusercontent.com/68722846/98626021-be783380-234b-11eb-962b-10131c6576fa.png) ![3](https://user-images.githubusercontent.com/68722846/98626024-c0da8d80-234b-11eb-9b83-63d83b999c58.png) ![2](https://user-images.githubusercontent.com/68722846/98626027-c0da8d80-234b-11eb-960e-960bbfad669a.png) ![1](https://user-images.githubusercontent.com/68722846/98626030-c1732400-234b-11eb-8bc1-5754744c020b.png) The instance view page was shown properly as following only if I closed the page, and reopened the vm intance page or clicked other links to change the page and return the vm instance view page . ![5](https://user-images.githubusercontent.com/68722846/98626220-2b8bc900-234c-11eb-92f5-bbcddc63a12e.png)