- Users - libvirt List Archives

[libvirt-users] Libvirt Qemu compatibility
by Shawn Furrow 21 Aug '12

21 Aug '12

Hi all, I am using Ubuntu 10.04 Server and I am trying to figure out which versions of qemu-kvm and libvirt are known to work well together and if there is anything special that needs to be done during their installs. I am trying to work with the latest version of libvirt possible that will be stable with qemu-kvm. Right now, the only configuration I've been able to get working are the "libvirt-bin" and "qemu-kvm" distribution packages. However, I would like to at least install libvirt from source because I want to have access to the source code and make minor changes. Thanks, Shawn -- Virginia Tech Bradley Department of Electrical and Computer Engineering B.S. Electrical Engineering B.S. Computer Engineering

2 1

[libvirt-users] IP over IB support.
by Eric J Nelson 21 Aug '12

21 Aug '12

Hello, I'm trying to set up a lxc container with access to a Infiniband card with IP over IB. I have scripts written to create the device in the container and add all the proper cgroup permissions on the host. I can access the card from the container, but there is no Infiniband network device present. I can't create the ib0 and ib1, and I have come to believe this is because they are made on the host when the modules are inserted. Is inserting modules possible with lxc and libvirt? Is it currently possible to use IP over IB in any of the virtualization technologies that libvirt supports? I'm not bound to lxc. Eric Nelson

1 0

[libvirt-users] capabilities mismatch
by Sean Abbott 21 Aug '12

21 Aug '12

So I have two instances of opennebula running libvirst/kvm. They were both installed using identical methods (a bit of a black box, frankly) on slightly different hardware. (one is "nephalem" intel, the other is "westmere". That's the only difference.) in fact, an architecture check from a kernel standpoint seems to come back identical. (unless my understanding of uname -a is incomplete, which seems likely) Old machine: Linux my.old.machine.com 2.6.38-7.2.0.2-amd64-8993020 #1 SMP Fri Dec 16 23:01:26 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux New machine: Linux my.new.machine.com 2.6.38-7.2.0.2-amd64-8993020 #1 SMP Fri Dec 16 23:01:26 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux However, the capabilities in virsh are very different. The new machine has i686 instead of x86_64,and it is missing the guest KVM domain type. Old capabilities: http://pastebin.com/EptdUYiG New capabilities: http://pastebin.com/pke4MGFJ Two questions: First, any idea why it might've come down differently. Second, can it be fixed? Can I try just copying the capabilities from old to new? Or something equally straightforward?

1 0

[libvirt-users] storage pool does not support volume creation
by zhijun liu 21 Aug '12

21 Aug '12

hi,all I use iscsi create stroage pool,now i want create a volume on the pool,but encouner a error: error: Failed to create vol from volume.xml error: this function is not supported by the connection driver: storage pool does not support volume creation else replacing way to resolve this problem?? thanks

2 1

[libvirt-users] libvirtd crashes after guest migration with attached console
by Andrey Korolyov 21 Aug '12

21 Aug '12

Hi, please see following backtrace. How to reproduce: start qemu guest w/attached console, execute migration, get a crash at the end. Program received signal SIGSEGV, Segmentation fault. virHashRemoveEntry (table=0x7fa0e0003e90, name=0x7fa0ec00ca60) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/util/virhash.c:463 bt #0 virHashRemoveEntry (table=0x7fa0e0003e90, name=0x7fa0ec00ca60) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/util/virhash.c:463 #1 0x00007fa0ffa5efcc in virConsoleFDStreamCloseCb (st=<optimized out>, opaque=0x7fa0ec00cad0) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/conf/virconsole.c:259 #2 0x00007fa0ffa7a303 in virFDStreamCloseInt (st=0x7fa0ec00c900, streamAbort=<optimized out>) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/fdstream.c:325 #3 0x00007fa0ffaa0503 in virStreamAbort (stream=0x7fa0ec00c900) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/libvirt.c:15289 #4 0x00000000004290c0 in daemonStreamEvent (st=<optimized out>, events=12, opaque=0x18869f0) at /var/tmp/build/libvirt/libvirt-0.9.13/./daemon/stream.c:234 #5 0x00007fa0ffa7a4ac in virFDStreamEvent (watch=<optimized out>, fd=<optimized out>, events=13, opaque=0x7fa0ec00c900) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/fdstream.c:171 #6 0x00007fa0ff9fb07f in virEventPollDispatchHandles (fds=<optimized out>, nfds=11) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/util/event_poll.c:489 #7 virEventPollRunOnce () at /var/tmp/build/libvirt/libvirt-0.9.13/./src/util/event_poll.c:636 #8 0x00007fa0ff9f99b7 in virEventRunDefaultImpl () at /var/tmp/build/libvirt/libvirt-0.9.13/./src/util/event.c:247 #9 0x00007fa0ffad930d in virNetServerRun (srv=0x186f0b0) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/rpc/virnetserver.c:712 #10 0x000000000040c9fc in main (argc=<optimized out>, argv=<optimized out>) at /var/tmp/build/libvirt/libvirt-0.9.13/./daemon/libvirtd.c:1299

2 2

[libvirt-users] Using Libvirt Java Bindings on Windows 7 64bit
by Frank Wilson 21 Aug '12

21 Aug '12

Hi All, Has anybody had any managed to use the libvirt java bindings on Windows 7 64bit (or similar configuration)? I am using Java 6. When I try to use the Test.class delivered with the bindings it always fails with the following error: C:\Users\fwilson\Desktop\libvirt-java-0.4.7>java "-Djna.library.path=C:/Program Files (x86)/Libvirt/lib/" -classpath .;target/classes;jars/* Test Exception in thread "main" java.lang.UnsatisfiedLinkError: Unable to load librar y 'virt': The specified module could not be found. at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:169) at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:242) at com.sun.jna.Library$Handler.<init>(Library.java:140) at com.sun.jna.Native.loadLibrary(Native.java:368) at com.sun.jna.Native.loadLibrary(Native.java:353) at org.libvirt.jna.Libvirt.<clinit>(Unknown Source) at org.libvirt.Connect.<clinit>(Unknown Source) at Test.main(Test.java:17) I installed libvirt using the experimental package: http://libvirt.org/windows.html Is this a 32bit build? Does that mean I should use a 32bit JVM? In any case the above test program fails whether I use a 32 or 64 bit JVM. I tried pointing jna.library.path to the libvirt bin directory instead of the lib directory but that also failed. Thanks for any help you can offer, Frank

1 0

[libvirt-users] Failed to use virDomainDefineXML
by 何鑫 21 Aug '12

21 Aug '12

Hi， When I use virDomainDefineXML(conn, xml), there is a message - "libvir: Domain Config error : at line 1: Opening and ending tag mismatch: domian line 1 and domain"- that I cannot continue to define my domain. I search a lot of website, but failed to find correct answer. I guess the value of const char *xml might be the point. I set "<domain>....</domain>" or "<domain type='qemu'>....</domain>", but both are not successful. My content of xml is "<domain type='qemu'> <name>qemu-test</name> ......</domain>" Also I am confused that the API of virDomainDefineXML don't tell me input any filepath of XML, so how do the API find out correct filename? Thanks a lot! Regard, Cory

2 1

[libvirt-users] getCPUStats of a domain by a non-root user - libvirtError: Requested operation is not valid: cgroup CPUACCT controller is not mounted
by Anton Beloglazov 21 Aug '12

21 Aug '12

Hello, I'm trying to use libvirt as a non-root user to obtain statistics on the CPU usage by VMs using the Python API. I'm performing basically the following steps: import libvirt conn = libvirt.openReadOnly(None) dom = conn.lookupByUUIDString('268e38ea-1bc7-41e4-c19e-8eff682e58e4') dom.getCPUStats(True, 0) However, they result in the following error: libvir: QEMU Driver error : Requested operation is not valid: cgroup CPUACCT controller is not mounted --------------------------------------------------------------------------- libvirtError Traceback (most recent call last) <ipython-input-23-9317cf967f6d> in <module>() ----> 1 dom.getCPUStats(True, 0) /usr/lib/python2.7/site-packages/libvirt.pyc in getCPUStats(self, total, flags) 1733 [{cpu_time:xxx, user_time:xxx, system_time:xxx}] """ 1734 ret = libvirtmod.virDomainGetCPUStats(self._o, total, flags) -> 1735 if ret is None: raise libvirtError ('virDomainGetCPUStats() failed', dom=self) 1736 return ret 1737 libvirtError: Requested operation is not valid: cgroup CPUACCT controller is not mounted However, CPUACCT is actually started and mounted to /mnt/cgroups/cpuacct, and the following steps actually work for the root user: import libvirt conn = libvirt.open(None) dom = conn.lookupByUUIDString('e06c6b11-d655-5a98-fd90-724d106066f9') dom.getCPUStats(True, 0) Output: [{'cpu_time': 10245430984L, 'system_time': 5350000000L, 'user_time': 1870000000L}] The domains referenced above are started for the non-root and root users respectively. I would be very grateful for any pointers to possible solutions of my problem. Thanks, Anton Beloglazov

2 4

Re: [libvirt-users] automatically detaching PCI host devices from guest for SRIOV usage.
by Rajesh Kumar Mallah 21 Aug '12

21 Aug '12

Dear Alex , Thanks Once again for responding. I tried to replicate your steps. in our case readlink always reveals that the pci device is being handled by the pci-stub driver (as in our case ixgbevf is absent in the host) Below is an annotaded sequence of events. Check status : # readlink -f /sys/bus/pci/devices/0000\:04\:10.0/driver /sys/bus/pci/drivers/pci-stub Content of the nic.xml: root@debian-squeeze:/usr/local/libvirt/etc/libvirt/qemu# cat /root/nic.xml <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x04' slot='0x10' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </hostdev> # readlink -f /sys/bus/pci/devices/0000\:04\:10.0/driver /sys/bus/pci/drivers/pci-stub corrent connectivity is OK # ping 192.168.101.10 PING 192.168.101.10 (192.168.101.10) 56(84) bytes of data. 64 bytes from 192.168.101.10: icmp_req=1 ttl=64 time=0.491 ms 64 bytes from 192.168.101.10: icmp_req=2 ttl=64 time=0.384 ms 64 bytes from 192.168.101.10: icmp_req=3 ttl=64 time=0.310 ms ^C --- 192.168.101.10 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.310/0.395/0.491/0.074 ms # readlink -f /sys/bus/pci/devices/0000\:04\:10.0/driver /sys/bus/pci/drivers/pci-stub Detach and reattach and check connectivity in running guest. note: the guest has pci hotplug support , the ethernet interfaces are configured to allow hotplug and IP is statically assigned. # virsh detach-device new-installed /root/nic.xml Device detached successfully # readlink -f /sys/bus/pci/devices/0000\:04\:10.0/driver /sys/bus/pci/drivers/pci-stub root@debian-squeeze:/usr/local/libvirt/etc/libvirt/qemu# ping 192.168.101.10 PING 192.168.101.10 (192.168.101.10) 56(84) bytes of data. >From 192.168.100.6 icmp_seq=9 Destination Host Unreachable >From 192.168.100.6 icmp_seq=10 Destination Host Unreachable >From 192.168.100.6 icmp_seq=11 Destination Host Unreachable ^C --- 192.168.101.10 ping statistics --- 14 packets transmitted, 0 received, +3 errors, 100% packet loss, time 13096ms pipe 3 # virsh attach-device new-installed /root/nic.xml Device attached successfully # ping 192.168.101.10 PING 192.168.101.10 (192.168.101.10) 56(84) bytes of data. 64 bytes from 192.168.101.10: icmp_req=1 ttl=64 time=0.507 ms 64 bytes from 192.168.101.10: icmp_req=2 ttl=64 time=0.388 ms 64 bytes from 192.168.101.10: icmp_req=3 ttl=64 time=0.314 ms 64 bytes from 192.168.101.10: icmp_req=4 ttl=64 time=0.315 ms 64 bytes from 192.168.101.10: icmp_req=5 ttl=64 time=0.335 ms ^C --- 192.168.101.10 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3998ms rtt min/avg/max/mdev = 0.314/0.371/0.507/0.076 ms # readlink -f /sys/bus/pci/devices/0000\:04\:10.0/driver /sys/bus/pci/drivers/pci-stub Above proves that detach-attach cycle was successful. # virsh detach-device new-installed /root/nic.xml Device detached successfully Please note that guest is being shutdown with nic detached. # virsh shutdown new-installed Domain new-installed is being shutdown Guest being started again : # virsh start new-installed Domain new-installed started # ping 192.168.101.10 PING 192.168.101.10 (192.168.101.10) 56(84) bytes of data. 64 bytes from 192.168.101.10: icmp_req=1 ttl=64 time=0.583 ms 64 bytes from 192.168.101.10: icmp_req=2 ttl=64 time=0.402 ms 64 bytes from 192.168.101.10: icmp_req=3 ttl=64 time=0.308 ms 64 bytes from 192.168.101.10: icmp_req=4 ttl=64 time=0.316 ms 64 bytes from 192.168.101.10: icmp_req=5 ttl=64 time=0.318 ms 64 bytes from 192.168.101.10: icmp_req=6 ttl=64 time=0.247 ms ^C --- 192.168.101.10 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 4997ms rtt min/avg/max/mdev = 0.247/0.362/0.583/0.109 ms Please note on starting the guest the PCI device came up and connectivity was established. The device was also defined inside the guest XML. Now shutting down the Guest without detaching. # virsh shutdown new-installed Domain new-installed is being shutdown # virsh start new-installed Domain new-installed started # ping 192.168.101.10 PING 192.168.101.10 (192.168.101.10) 56(84) bytes of data. >From 192.168.100.6 icmp_seq=9 Destination Host Unreachable >From 192.168.100.6 icmp_seq=10 Destination Host Unreachable >From 192.168.100.6 icmp_seq=11 Destination Host Unreachable ^C --- 192.168.101.10 ping statistics --- 14 packets transmitted, 0 received, +3 errors, 100% packet loss, time 13095ms pipe 3 CONNECTION IS LOST We are using latest libvirtd (0.9.13) , lastest ixgbe/ixgbevf (from sf) , lastest stable kernel (3.5.1) Regards, Rajesh Kumar Mallah Tel. 91-11-46710500 (Ext:303) Cell +919811255597 Website: http://www.tradeindia.com/ \|/ \|/ \|/ stop printing \|/ \|/ \|/ | | | start planting | | | ----- "Alex Jia" <ajia(a)redhat.com> wrote: | From: "Alex Jia" <ajia(a)redhat.com> | To: "Rajesh Kumar Mallah" <mallah(a)tradeindia.com> | Cc: libvirt-users(a)redhat.com | Sent: Tuesday, August 21, 2012 9:34:24 AM | Subject: Re: [libvirt-users] automatically detaching PCI host devices from guest for SRIOV usage. | | On 08/21/2012 11:22 AM, Rajesh Kumar Mallah wrote: | | Dear Alex / List , | | Thanks for the response. | | The problem is regarding detaching from the guest not host. | | I see, if you attach a PCI device into guest with 'managed' mode(managed='yes') then the device is automatically detached from guest and returned to host after guest exiting, for example. | | # lspci | grep Eth | 00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02) | | # readlink /sys/bus/pci/devices/0000\:00\:19.0/driver/ -f | /sys/bus/pci/drivers/e1000e | | # virsh start foo | Domain foo started | | # ping -c 3 xx.xx.xx.xx | PING xx.xx.xx.xx (xx.xx.xx.xx) 56(84) bytes of data. | 64 bytes from nx-in-f160.1e100.net (xx.xx.xx.xx): icmp_seq=1 ttl=49 time=87.8 ms | 64 bytes from nx-in-f160.1e100.net (xx.xx.xx.xx): icmp_seq=2 ttl=49 time=85.2 ms | 64 bytes from nx-in-f160.1e100.net (xx.xx.xx.xx): icmp_seq=3 ttl=49 time=91.8 ms | --- xx.xx.xx.xx ping statistics --- | 3 packets transmitted, 3 received, 0% packet loss, time 2093ms | rtt min/avg/max/mdev = 85.240/88.327/91.881/2.731 ms | | # cat hostdev.xml | <hostdev mode='subsystem' type='pci' managed='yes'> | <source> | <address domain='0x0000' bus='0x00' slot='0x19' function='0x0'/> | </source> | </hostdev> | | # virsh attach-device foo hostdev.xml | Device attached successfully | | # readlink /sys/bus/pci/devices/0000\:00\:19.0/driver/ -f | /sys/bus/pci/drivers/pci-stub | | # ping -c 3 xx.xx.xx.xx | connect: Network is unreachable | | # virsh destroy foo | Domain foo destroyed | | # readlink /sys/bus/pci/devices/0000\:00\:19.0/driver/ -f | /sys/bus/pci/drivers/e1000e | | # ping -c 3 xx.xx.xx.xx | PING xx.xx.xx.xx (xx.xx.xx.xx) 56(84) bytes of data. | 64 bytes from xx.xx.xx.xx: icmp_seq=1 ttl=49 time=79.7 ms | 64 bytes from xx.xx.xx.xx: icmp_seq=2 ttl=49 time=83.2 ms | 64 bytes from xx.xx.xx.xx: icmp_seq=3 ttl=49 time=84.5 ms | | --- xx.xx.xx.xx ping statistics --- | 3 packets transmitted, 3 received, 0% packet loss, time 2087ms | rtt min/avg/max/mdev = 79.714/82.480/84.513/2.040 ms | | Notes, need to wait for local network recovery again then check network connectivity. | | If your network still is disconnect, it may be a bug IMHO, please show your libvirt | and qemu-kvm version, or my example is not what you want, please let me know. | | Thanks, | Alex | | | In our case since ixgbevf driver is NOT present in the host hence the virtual | interfaces never really attach themselves to the host. | | Regards, | Rajesh Kumar Mallah | Tel. 91-11-46710500 (Ext:303) | Cell +919811255597 | Website: http://www.tradeindia.com/ | \|/ \|/ \|/ stop printing \|/ \|/ \|/ | | | | start planting | | | | | | ----- "Alex Jia" <ajia(a)redhat.com> wrote: | | From: "Alex Jia" <ajia(a)redhat.com> | | To: "Rajesh Kumar Mallah" <mallah(a)tradeindia.com> | | Cc: libvirt-users(a)redhat.com | | Sent: Tuesday, August 21, 2012 8:31:21 AM | | Subject: Re: [libvirt-users] automatically detaching PCI host devices from guest for SRIOV usage. | | | | On 08/20/2012 08:34 PM, Rajesh Kumar Mallah wrote: Dear List , We are using intel 82599EB based SRIOV capable 10GbE cards on the host machine.The VFs are being assigned to the guest in pass through mode and are providing the network connectivity as expected. However when we shutdown the guest the connectivity does not comes back via the VFs on the guest in next boot unless the VFs are detached from the *guest* *before* initiating a shutdown of the guests. Dear Rajesh, | | | | Please see the following comments. | | | | ( the detach is explicitly done via virsh command /usr/local/libvirt/bin/virsh detach-device guest01 ~/nic.xml nic.xml contained <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x04' slot='0x10' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </hostdev> ) The question is anyone else facing similar problem and if so what solution was used? Secondly , is there anyway to automate the detaching of the VFs from the guest when the guest is put in the shutdown sequence ? (or for that matter destroyed). | | When managed is "yes" for a PCI device, it is automatically detached from the host before being passed on to the guest, and automatically reattached to the host after the guest exits such as shutdown a guest. | | | | Regards, | | Alex | | | | Regards, Rajesh Kumar Mallah Tel. 91-11-46710500 (Ext:303) Cell +919811255597 Website: http://www.tradeindia.com/ \|/ \|/ \|/ stop printing \|/ \|/ \|/ | | | start planting | | | _______________________________________________ libvirt-users mailing list libvirt-users(a)redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users | | |

1 0

[libvirt-users] automatically detaching PCI host devices from guest for SRIOV usage.
by Rajesh Kumar Mallah 21 Aug '12

21 Aug '12

Dear List , We are using intel 82599EB based SRIOV capable 10GbE cards on the host machine.The VFs are being assigned to the guest in pass through mode and are providing the network connectivity as expected. However when we shutdown the guest the connectivity does not comes back via the VFs on the guest in next boot unless the VFs are detached from the *guest* *before* initiating a shutdown of the guests. ( the detach is explicitly done via virsh command /usr/local/libvirt/bin/virsh detach-device guest01 ~/nic.xml nic.xml contained <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x04' slot='0x10' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </hostdev> ) The question is anyone else facing similar problem and if so what solution was used? Secondly , is there anyway to automate the detaching of the VFs from the guest when the guest is put in the shutdown sequence ? (or for that matter destroyed). Regards, Rajesh Kumar Mallah Tel. 91-11-46710500 (Ext:303) Cell +919811255597 Website: http://www.tradeindia.com/ \|/ \|/ \|/ stop printing \|/ \|/ \|/ | | | start planting | | |

2 3