- Users - libvirt List Archives

[libvirt-users] libvir: Domain Config error : internal error incorrect root element
by 何鑫 22 Aug '12

22 Aug '12

hi, When I use dom = virDomainDefineXML(conn, xml) to define xml, I countered a problem that " libvir: Domain Config error : internal error incorrect root element". Could you please tell me what's wrong with it? I tend to debug such problem above by gdb to step into virDomainDefineXML. When I press "step" in gdb, the console just shows the wrong messages, so I fail to access to the internal function of virDomainDefineXML. My libvirt's version is 0.98 allowing debug with the command "CFLAGS = -g -O2" in libvirt's Makefile. I installed libvirt-bin by "sudo apt-get install libvirt-bin"in ubuntu. Is there something wrong in my installing steps? Thanks a lot! Best Regards, Corey

1 0

[libvirt-users] virsh command vol-upload purpose question
by Li, Chun Wen 22 Aug '12

22 Aug '12

I use virsh vol-upload to upload some data in a volume and use vol-download to download these data from the same volume, both these two commands work well. However, when I first use these two commands, I thought I can use vol-upload to upload some file, then attach this volume to a vm, and access the upload file in this vm. I did this experiment, bud it not success. Once I upload a file into a volume, attach it to a vm, then the vm can not recognize the file type of this vm, if I mkfs to the volume, the file I upload disappear. So, my question is the purpose of the vol-upload is just to save some data in the volume outside vm? And at this point do we have method to access the data upload to the volume from vm? Thanks Bests Kimi Li

1 0

[libvirt-users] What can cause "libvirtd dead but pid file exists."
by xuanmao_001 22 Aug '12

22 Aug '12

Hi, Eric: I noticed that: # service libvirtd status libvirtd dead but pid file exists. I operated VMs(like create, edit, delte) normally for a second, but the libvirtd on host was dead. I checked the libvirtd.log but didn't find any useful information. so I want to know what can cause the problem? another question: I found the message in /var/log/message like "libvirtd: Could not find keytab file: /etc/libvirt/krb5.tab: Permission denied." what is going wrong? my libvirt version: 0.9.8. thanks. xuanmao_001

2 1

[libvirt-users] Finding cause when "virsh list" hangs
by Whit Blauvelt 22 Aug '12

22 Aug '12

Hi, Did something dumb - had two VM hosts with DRBD mirroring of VMs on the same UPS, which failed and crashed them both. While I've got VMs running now on both, "virsh list" and "virsh start" and so on are just hanging. I'm not seeing it log anything in these instances - just hanging. Both systems are Ubuntu 10.10, one with the stock libvirtd 0.8.3 and one with 0.9.12 compiled from source. They each brought up their autostart VMs okay. But I've got no working virsh shell on either now. The 0.9.12 host was, to complicate this report, okay with virsh initially, or "virsh list" anyway. But it hung with a "virsh start," and now "virsh list" fails too. So ... what should I look for to have been left where by the crash that's making virsh hang? Is there any way to get virsh to provide debugging info in a coffee-addled-friendly way? I've of course Googled "virsh list" hanging, but without finding anything that seems to directly apply to my case, although it's been seen before. Thanks, Whit

2 3

[libvirt-users] disappeared VM in virsh
by Akendo 21 Aug '12

21 Aug '12

Hi guys, one of my VM has disappeared in libvirtd. I still can see the process with ps and the configuration file is as well there. But it is not displayed or found with virt-manger/virsh. virsh list shows only 4 of 5, but there is no real error message. I restarted the daemon without solving the problem. Any idea what to do? Here some info: Compiled against library: libvir 0.9.13 Using library: libvir 0.9.13 Using API: QEMU 0.9.13 Running hypervisor: QEMU 0.12.1 uname -a Linux 2.6.32-220.17.1.el6.x86_64 #1 SMP Wed May 16 00:01:37 BST 2012 x86_64 x86_64 x86_64 GNU/Linux It's a CentOS 6 so far Akendo

2 3

[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

[libvirt-users] Failed to change the content of tag- <emulator>
by 何鑫 21 Aug '12

21 Aug '12

Hi, I tend to change the qualified path to run other emulator binary, which is besides libvirt supporting but based on qemu, so I set the tag as "<emulator>/usr/bin/emulator<emulator>".(I have set the emulator binary to env.). As a result, the messages shown as below: ....(ignoring much xml contents) </devices></domain>, flags=011:00:27.110: 2263: debug : remoteIO:5824 : Do proc=10 serial=3 length=2144 wait=(nil)11:00:27.110: 2263: debug : remoteIO:5896 : We have the buck 10 0x993b9e0 0x993b9e011:00:27.110: 2263: debug : virEventPollUpdateHandle:144 : Update handle w=2 e=011:00:27.111: 2263: debug : virEventPollInterruptLocked:686 : Skip interrupt, 0 011:00:27.136: 2263: debug : remoteIODecodeMessageLength:5214 : Got length, now need 416 total (412 more)11:00:27.136: 2263: debug : remoteIOEventLoop:5750 : Giving up the buck 10 0x993b9e0 (nil)11:00:27.136: 2263: debug : virEventPollUpdateHandle:144 : Update handle w=2 e=111:00:27.136: 2263: debug : virEventPollInterruptLocked:686 : Skip interrupt, 0 011:00:27.136: 2263: debug : remoteIO:5924 : All done with our call 10 (nil) 0x993b9e0 error: Failed to create domain from fedora-qemu.xmlerror: internal error Child process (LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin /usr/bin/emulator -help) status unexpected: exit status 1 11:00:27.137: 2263: debug : virConnectClose:1354 : conn=0x99374a811:00:27.137: 2263: debug : virUnrefConnect:145 : unref connection 0x99374a8 111:00:27.137: 2263: debug : virReleaseConnect:94 : release connection 0x99374a811:00:27.137: 2263: debug : virEventPollRemoveTimeout:278 : Remove timer 111:00:27.137: 2263: debug : virEventPollInterruptLocked:686 : Skip interrupt, 0 011:00:27.137: 2263: debug : virEventPollRemoveHandle:171 : Remove handle w=211:00:27.137: 2263: debug : virEventPollRemoveHandle:184 : mark delete 1 511:00:27.137: 2263: debug : virEventPollInterruptLocked:686 : Skip interrupt, 0 011:00:27.137: 2263: debug : remoteIO:5824 : Do proc=2 serial=4 length=28 wait=(nil)11:00:27.137: 2263: debug : remoteIO:5896 : We have the buck 2 0x993ba78 0x993ba7811:00:27.138: 2263: debug : remoteIODecodeMessageLength:5214 : Got length, now need 56 total (52 more)11:00:27.138: 2263: debug : remoteIOEventLoop:5750 : Giving up the buck 2 0x993ba78 (nil)11:00:27.138: 2263: debug : remoteIO:5924 : All done with our call 2 (nil) 0x993ba78 Could you please tell me what's wrong in the source code? If so, where should I modify? Thanks a lot! Regard,Corey

1 0

[libvirt-users] Live Snapshot and Rebasing using blockpull
by Andrew Martin 20 Aug '12

20 Aug '12

Hello, I am looking for a solution for live backups of running KVM hosts. I recently read this article which highlights the following method: http://www.linux-kvm.com/content/first-look-virtual-machine-online-disk-sna… 1. virsh snapshot-create-as to create the snapshot 2. cp myvm.qcow2 myvm-backup.qcow2 to copy off the now read-only backing image file 3. virsh blockpull to merge the base and snapshot images together into a single image again Is this functionality only available in qemu 1.1? I am using Ubuntu 12.04 LTS on production servers which only includes qemu 1.0.x. Is there a safe alternative for accomplishing live backups like this on qemu 1.0.x? Is there a minimum version of libvirt that supports this behavior? Thanks, Andrew

2 2

[libvirt-users] IVSHMEM support
by Shawn Furrow 20 Aug '12

20 Aug '12

Hi all, Does anyone know if Libvirt supports shared memory devices such as IVSHMEM. I know it didn't at one point but I didn't know if support for it had been recently added. Thanks, Shawn -- Virginia Tech Bradley Department of Electrical and Computer Engineering B.S. Electrical Engineering B.S. Computer Engineering

1 0

[libvirt-users] ANNOUNCE: Oz 0.9.0 Release
by Chris Lalancette 20 Aug '12

20 Aug '12

All, I'm pleased to announce release 0.9.0 of Oz. Oz is a program for doing automated installation of guest operating systems with limited input from the user. Release 0.9.0 is a (long overdue) bugfix and feature release for Oz. Some of the highlights between Oz 0.8.0 and 0.9.0 are: - Easier to create Debian/Ubuntu packages - Ability to specify the disk size in the TDL - Ability to specify the number of CPUs and amount of memory used for the installation VM - Cleanup and bugfixes to oz-cleanup-cache - Ability to install Fedora-17 disk images - Ability to install guests as a non-root user. This has several caveats; please see the documentation on http://github.com/clalancette/oz for more information. - Ability to install RHEL-6.3 disk images - Ability to install ScientificLinuxCERN disk images - Ability to install Mandrake 8.2 disk images - Ability to install OpenSUSE 10.3 disk images - Ability to install Ubuntu 12.04 disk images A tarball of this release is available, as well as packages for Fedora-16. Instructions on how to get and use Oz are available at http://github.com/clalancette/oz . If you have any questions or comments about Oz, please feel free to contact aeolus-devel(a)lists.fedorahosted.org or me (clalancette(a)gmail.com) directly. Thanks to everyone who contributed to this release through bug reports, patches, and suggestions for improvement. Chris Lalancette

2 2

[libvirt-users] Where does "cmd" initailize in qemu_command.c?
by He Xin 17 Aug '12

17 Aug '12

Hi, Excuse me, I have a question when I reading the libvirt source codes. I have known the process of how libvirt start/manage qemu, since I need to write a driver based on libvirt. But one thing also confused, please give me some tips. 1. In qemu_command.c, there is a function call "cmd = virCommandNewArgList(emulator, "-S", NULL);", which initializes pointer "cmd". However, I don't find the initial value of "cmd->args", which represents the input of virFindFileInPath in Util.c. Through virFindFileInPath, one could find a requested executable file in the PATH env to start specified hypervisors. So could you please tell me what the value of args[0] is? Or where does cmd->args initialize? 2. In qemu_driver.c, there is a function call "vm = virDomainFindByUUID(&driver->domains, dom->uuid);", whose returned value "vm" is important in the next functions. Then we could get the "vm"'s value in hash.c which is the end part to lookup domains saved in hashtable. May I know where does HashTable initialize? I mean where can I set the hashtable's values in detail, if I want to modify some values? 3. This might be the same as question 1. In command.c, "execve(cmd->args[0], cmd->args, cmd->env)" is a way to exec command. About qemu_driver, what is the value of those three inputs? Thanks a lot! Regard, Corey

2 2

[libvirt-users] Fwd: vm pxe fail
by Alex Jia 17 Aug '12

17 Aug '12

----- Forwarded Message ----- From: "Andrew Holway" <a.holway(a)syseleven.de> To: "Alex Jia" <ajia(a)redhat.com> Cc: kvm(a)vger.kernel.org Sent: Friday, August 17, 2012 4:24:33 PM Subject: Re: [libvirt-users] vm pxe fail Hello, On Aug 17, 2012, at 4:34 AM, Alex Jia wrote: > Hi Andrew, > I can't confirm a root reason based on your information, perhaps you may > try to find a reason by yourself via the following docs: > > http://wiki.libvirt.org/page/PXE_boot_%28or_dhcp%29_on_guest_failed (Troubleshooting) > http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/sec… (User Guide) Everything seems quite normal. > > If can't, please provide your version of kvm, libvirt, tftp, etc, and run 'virsh net-dumpxml br0' to dump your > network bridge XML configuration, and run 'cat pxelinux.cfg' to show your pxelinux configuration, thanks. default is my pxelinux configuration but I'm not sure is this is what your after. dhcp is a protocol decode of the DHCP traffic. You see that the VM is sending each request twice which is a bit odd. [root@node002 ~]# yum list | grep qemu gpxe-roms-qemu.noarch 0.9.7-6.9.el6 @base qemu-img.x86_64 2:0.12.1.2-2.295.el6_3.1 @updates qemu-kvm.x86_64 2:0.12.1.2-2.295.el6_3.1 @updates qemu-guest-agent.x86_64 2:0.12.1.2-2.295.el6_3.1 updates qemu-kvm-tools.x86_64 2:0.12.1.2-2.295.el6_3.1 updates br0 is created by brctl. There is not XML config as far as I am aware. [root@node002 ~]# ifconfig br0 br0 Link encap:Ethernet HWaddr 00:9C:02:24:1A:E0 inet addr:10.141.80.2 Bcast:10.141.255.255 Mask:255.255.0.0 inet6 addr: fe80::29c:2ff:fe24:1ae0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:185129 errors:0 dropped:0 overruns:0 frame:0 TX packets:2094 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:8820359 (8.4 MiB) TX bytes:123842 (120.9 KiB) [root@node002 ~]# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:02:C9:36:21:A1 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) [root@node002 ~]# brctl show bridge name bridge id STP enabled interfaces br0 8000.009c02241ae0 no eth1 vnet0 virbr0 8000.525400a6d5aa yes virbr0-nic > > -- > Regards, > Alex > > > ----- Original Message ----- > From: "Andrew Holway" <a.holway(a)syseleven.de> > To: kvm(a)vger.kernel.org > Sent: Thursday, August 16, 2012 8:25:35 PM > Subject: [libvirt-users] vm pxe fail > > Hallo > > I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips. on the physical host I can get the pxelinux.0 file from the pxe server via tftp and can clearly see that traffic with tcpdump. > > Ive tried using various virtual interfaces. > > I can pxe boot my physical hosts with no problems. > > I can tftp fine from the physical host and see the traffic with ethdump > > Here is the terminal output from the VM: https://dl.dropbox.com/u/98200887/Screen%20Shot%202012-08-15%20at%206.41.12… > > Thanks, > > Andrew > > [root@node002 ~]# yum list | grep qemu > gpxe-roms-qemu.noarch 0.9.7-6.9.el6 @base > qemu-img.x86_64 2:0.12.1.2-2.295.el6_3.1 @updates > qemu-kvm.x86_64 2:0.12.1.2-2.295.el6_3.1 @updates > qemu-guest-agent.x86_64 2:0.12.1.2-2.295.el6_3.1 updates > qemu-kvm-tools.x86_64 2:0.12.1.2-2.295.el6_3.1 updates > > [root@node002 ~]# ethtool eth0 > Settings for eth0: > Supported ports: [ TP ] > Supported link modes: 10000baseT/Full > Supports auto-negotiation: No > Advertised link modes: 10000baseT/Full > Advertised pause frame use: No > Advertised auto-negotiation: No > Speed: Unknown! > Duplex: Unknown! (255) > Port: Twisted Pair > PHYAD: 0 > Transceiver: internal > Auto-negotiation: off > MDI-X: Unknown > Supports Wake-on: g > Wake-on: g > Current message level: 0x00000014 (20) > Link detected: no > > [root@node002 ~]# brctl show > bridge name bridge id STP enabled interfaces > br0 8000.009c02241ae0 no eth1 > vnet0 > virbr0 8000.525400a6d5aa yes virbr0-nic > > [root@node002 ~]# ethtool vnet0 > Settings for vnet0: > Supported ports: [ ] > Supported link modes: > Supports auto-negotiation: No > Advertised link modes: Not reported > Advertised pause frame use: No > Advertised auto-negotiation: No > Speed: 10Mb/s > Duplex: Full > Port: Twisted Pair > PHYAD: 0 > Transceiver: internal > Auto-negotiation: off > MDI-X: Unknown > Current message level: 0xffffffa1 (-95) > Link detected: yes > > <domain type='kvm'> > <name>vm004</name> > <uuid>4f03b09b-e834-bbf3-a6c2-1689f3156ef2</uuid> > <memory unit='KiB'>2097152</memory> > <currentMemory unit='KiB'>2097152</currentMemory> > <vcpu placement='static'>2</vcpu> > <os> > <type arch='x86_64' machine='rhel6.3.0'>hvm</type> > <boot dev='hd'/> > </os> > <features> > <acpi/> > <apic/> > <pae/> > </features> > <clock offset='utc'/> > <on_poweroff>destroy</on_poweroff> > <on_reboot>restart</on_reboot> > <on_crash>restart</on_crash> > <devices> > <emulator>/usr/libexec/qemu-kvm</emulator> > <disk type='file' device='disk'> > <driver name='qemu' type='raw' cache='none'/> > <source file='/cm/shared/vm/vm004.img'/> > <target dev='hda' bus='ide'/> > <address type='drive' controller='0' bus='0' target='0' unit='0'/> > </disk> > <disk type='block' device='cdrom'> > <driver name='qemu' type='raw'/> > <target dev='hdc' bus='ide'/> > <readonly/> > <address type='drive' controller='0' bus='1' target='0' unit='0'/> > </disk> > <controller type='usb' index='0'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> > </controller> > <controller type='ide' index='0'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> > </controller> > <interface type='bridge'> > <mac address='00:00:00:00:00:0d'/> > <source bridge='br0'/> > <model type='rtl8139'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> > </interface> > <serial type='pty'> > <target port='0'/> > </serial> > <console type='pty'> > <target type='serial' port='0'/> > </console> > <input type='mouse' bus='ps2'/> > <graphics type='vnc' port='-1' autoport='yes'/> > <video> > <model type='cirrus' vram='9216' heads='1'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> > </video> > <memballoon model='virtio'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> > </memballoon> > </devices> > </domain> > > > > _______________________________________________ > libvirt-users mailing list > libvirt-users(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users

1 0

[libvirt-users] vm pxe fail
by Andrew Holway 16 Aug '12

16 Aug '12

Hallo I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips. on the physical host I can get the pxelinux.0 file from the pxe server via tftp and can clearly see that traffic with tcpdump. Ive tried using various virtual interfaces. I can pxe boot my physical hosts with no problems. I can tftp fine from the physical host and see the traffic with ethdump Here is the terminal output from the VM: https://dl.dropbox.com/u/98200887/Screen%20Shot%202012-08-15%20at%206.41.12… Thanks, Andrew [root@node002 ~]# yum list | grep qemu gpxe-roms-qemu.noarch 0.9.7-6.9.el6 @base qemu-img.x86_64 2:0.12.1.2-2.295.el6_3.1 @updates qemu-kvm.x86_64 2:0.12.1.2-2.295.el6_3.1 @updates qemu-guest-agent.x86_64 2:0.12.1.2-2.295.el6_3.1 updates qemu-kvm-tools.x86_64 2:0.12.1.2-2.295.el6_3.1 updates [root@node002 ~]# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10000baseT/Full Supports auto-negotiation: No Advertised link modes: 10000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: No Speed: Unknown! Duplex: Unknown! (255) Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: off MDI-X: Unknown Supports Wake-on: g Wake-on: g Current message level: 0x00000014 (20) Link detected: no [root@node002 ~]# brctl show bridge name bridge id STP enabled interfaces br0 8000.009c02241ae0 no eth1 vnet0 virbr0 8000.525400a6d5aa yes virbr0-nic [root@node002 ~]# ethtool vnet0 Settings for vnet0: Supported ports: [ ] Supported link modes: Supports auto-negotiation: No Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Speed: 10Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: off MDI-X: Unknown Current message level: 0xffffffa1 (-95) Link detected: yes <domain type='kvm'> <name>vm004</name> <uuid>4f03b09b-e834-bbf3-a6c2-1689f3156ef2</uuid> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>2</vcpu> <os> <type arch='x86_64' machine='rhel6.3.0'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none'/> <source file='/cm/shared/vm/vm004.img'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='block' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hdc' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='bridge'> <mac address='00:00:00:00:00:0d'/> <source bridge='br0'/> <model type='rtl8139'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes'/> <video> <model type='cirrus' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </memballoon> </devices> </domain>

1 0

[libvirt-users] error: virsh not could create bridge interface
by Gao Yongwei 16 Aug '12

16 Aug '12

hello, virsh iface-bridge to build bridge interface does not work for me,i've searched in google but got nothing ,please give some help,thanks. # VIRSH_DEBUG=0 VIRSH_LOG_FILE=bridge.log virsh iface-bridge eth0 br0 iface-bridge: found option <interface>: eth0 iface-bridge: <interface> trying as interface NAME libvir: Interface error : Interface not found: couldn't find interface named 'br0' libvir: Interface error : internal error could not get interface XML description: XSLT transformation failed - runtime error: file /usr/share/netcf/xml/initscripts-get.xsl line 196 element node error: Failed to define new bridge interface br0 error: internal error could not get interface XML description: XSLT transformation failed - runtime error: file /usr/share/netcf/xml/initscripts-get.xsl line 196 element node # virsh version Compiled against library: libvir 0.9.10 Using library: libvir 0.9.10 Using API: QEMU 0.9.10 Running hypervisor: QEMU 0.12.1 # cat bridge.log [2012.08.16 16:16:50 virsh 10895] INFO iface-bridge: found option <interface>: eth0 [2012.08.16 16:16:50 virsh 10895] DEBUG iface-bridge: <interface> trying as interface NAME [2012.08.16 16:16:50 virsh 10895] ERROR Failed to define new bridge interface br0 [2012.08.16 16:16:50 virsh 10895] ERROR internal error could not get interface XML description: XSLT transformation failed - runtime error: file /usr/share/netcf/xml/initscripts-get.xsl line 196 element node this is some debug log from /var/log/libvirt/libvirtd.log: 2012-08-16 08:54:25.724+0000: 11526: debug : virInterfaceDefineXML:10794 : conn=0x7f963c0009c0, xml=<?xml version="1.0"?> <interface type="bridge" name="br0"> <start mode="onboot"/> <protocol family="ipv4"> <ip address="118.123.12.65" prefix="25"/> <route gateway="118.123.12.1"/> </protocol> <bridge stp="on" delay="0"><interface type="ethernet" name="eth0"><mac address="00:30:48:D9:F7:EE"/></interface></bridge></interface> , flags=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollCleanupTimeouts:506 : Cleanup 3 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollCleanupHandles:554 : Cleanup 8 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollMakePollFDs:383 : Prepare n=0 w=1, f=7 e=1 d=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollMakePollFDs:383 : Prepare n=1 w=2, f=9 e=1 d=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollMakePollFDs:383 : Prepare n=2 w=3, f=12 e=1 d=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollMakePollFDs:383 : Prepare n=3 w=4, f=13 e=1 d=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollMakePollFDs:383 : Prepare n=4 w=5, f=6 e=1 d=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollMakePollFDs:383 : Prepare n=5 w=6, f=16 e=1 d=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollMakePollFDs:383 : Prepare n=6 w=7, f=15 e=1 d=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollMakePollFDs:383 : Prepare n=7 w=8, f=17 e=1 d=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollCalculateTimeout:325 : Calculate expiry of 3 timers 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollCalculateTimeout:351 : Timeout at 0 due in -1 ms 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollRunOnce:619 : EVENT_POLL_RUN: nhandles=8 imeout=-1 2012-08-16 08:54:25.730+0000: 11526: error : interfaceDefineXML:425 : internal error could not get interface XML description: XSLT transformation failed - runtime error: file /usr/share/netcf/xml/initscripts-get.xsl line 196 element node thanks.

1 0

[libvirt-users] What can cause "libvirtd dead but pid file exists."
by xuanmao_001 16 Aug '12

16 Aug '12

Hi, # service libvirtd status libvirtd dead but pid file exists. I operated VMs(like create, edit, delte) normally for a second, but the libvirtd on host was dead. I checked the libvirtd.log but didn't find any useful information. so I want to know what can cause the problem? another question: I found the message in /var/log/message like "libvirtd: Could not find keytab file: /etc/libvirt/krb5.tab: Permission denied." what is going wrong? my libvirt version: 0.9.8. xuanmao_001

1 0

[libvirt-users] Source of Qcow2 Image Corruption
by Andrew Martin 14 Aug '12

14 Aug '12

Hello, I have two KVM virtual machine nodes in a high-availability cluster using Pacemaker + Heartbeat on Ubuntu 10.04 Server amd64. This cluster hosts a single Ubuntu 10.04 VM which uses a qcow2 image file, myvm.qcow2, with a backing file, backingfile.qcow2. This morning, the VM suddenly powered off. I attempted to start it again with virsh start domain, but it would only start briefly and then power off again. I checked the qcow2 disk image and found countless corruption errors: root@vmhost:/mnt/storage/vmstore/disks# qemu-img info myvm.qcow2 image: myvm.qcow2 file format: qcow2 virtual size: 9.8G (10485760000 bytes) disk size: 13G cluster_size: 65536 backing file: backingfile.qcow2 (actual path: backingfile.qcow2) Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1.5G 2056-05-05 21:01:212795663:45:42.642 /archive/1006/20100627000/2il_root/save/archive/1002/20100204005/1 743M 1995-08-16 12:47:352289751:06:20.183 root@vmhost:/mnt/storage/vmstore/disks# qemu-img check myvm.qcow2 2>&1 | head ERROR OFLAG_COPIED: offset=80000002047d0000 refcount=0 ERROR OFLAG_COPIED: offset=8000000212e50000 refcount=0 ERROR OFLAG_COPIED: offset=80000001ffde0000 refcount=0 ERROR OFLAG_COPIED: offset=80000001ff710000 refcount=0 ERROR OFLAG_COPIED: offset=8000000216ec0000 refcount=0 ERROR OFLAG_COPIED: offset=8000000206db0000 refcount=0 ERROR OFLAG_COPIED: offset=80000001ff720000 refcount=0 ERROR OFLAG_COPIED: offset=80000001ffdf0000 refcount=0 ERROR OFLAG_COPIED: offset=8000000212e60000 refcount=0 ERROR OFLAG_COPIED: offset=8000000212e70000 refcount=0 root@vmhost:/mnt/storage/vmstore/disks# qemu-img info backingfile.qcow2 image: backingfile.qcow2 file format: qcow2 virtual size: 9.8G (10485760000 bytes) disk size: 4.8G cluster_size: 65536 root@vmhost:/mnt/storage/vmstore/disks# qemu-img check backingfile.qcow2 No errors were found on the image. If I use qemu-img to convert the image, the resulting image is "clean": # convert myvm.qcow2 -O qcow2 /tmp/test.qcow2 # qemu-img check /tmp/test.qcow2 No errors were found on the image. I had this corruption happen a month ago to a different VM on the same machine but a different physical drive, so I do not believe it to be a physical disk failure. I can find nothing in /var/log that gives any more information related to this corruption. What other debug information can I provide to diagnose why these images are getting corrupted and taking these running VMs offline? Thanks, Andrew Martin

1 1