- Users - libvirt List Archives

[libvirt-users] failure creating a snapshot volume within a lvm-based pool
by Edoardo Comar 23 Apr '13

23 Apr '13

Hi I have defined a logical pool and a volume within it # virsh vol-create-as images_lvm myvol 2G Vol myvol created # virsh vol-list images_lvm Name Path ----------------------------------------- myvol /dev/libvirt_images_vg/myvol if I try to create another volume using the previous one as backing-vol, the creation fails with what looks like an incorrect commandline for lvcreate: # virsh vol-create-as images_lvm myvol-instance 2G --backing-vol myvol error: Failed to create vol myvol-instance error: internal error Child process (/usr/sbin/lvcreate --name myvol-instance -L 2097152K -s=/dev/libvirt_images_vg/myvol) unexpected exit status 3: /usr/sbin/lvcreate: invalid option -- '=' Error during parsing of command line. Exactly the same happens if I specify a qcow2 format (the doc however says that The logical volume pool does not use the volume format type element). is this a known bug? I'm running Fedora 18 # virsh version Compiled against library: libvirt 0.10.2 Using library: libvirt 0.10.2 Using API: QEMU 0.10.2 Running hypervisor: QEMU 1.2.2 -------------------------------------------------- regards, Edoardo Comar WebSphere Application Service Platform for Networks (ASPN) ecomar(a)uk.ibm.com Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

2 2

Re: [libvirt-users] Fwd: kvm
by Stefan Hajnoczi 23 Apr '13

23 Apr '13

On Mon, Apr 22, 2013 at 10:59:25AM +0100, Gary Lloyd wrote: > I was wondering if anyone could help me with an issue with KVM and ISCSI. > > If we restart a controller on our EqualLogic SAN or there are any > network interruptions on the storage network, KVM guests throw a > wobbler and their files systems go into read only(centos 5.9 guest > with virtio driver). > > I have read a few forums that indicate you can set disk timeout values > on the guests themselves but this is not possible using the virtio > driver, which is what we are currently using. > > Is there any way we can instruct KVM to pause the vm's if there is a > storage failure and resume them when the storage comes back online ? > > We are currently running Centos 6.4. There seems to be a werror='stop' > and rerror='stop' options to achieve this but if I try to put these in > options in the libvirt xml file for a vm, libvirt appears to be > removing them. Please email libvirt-users(a)redhat.com for questions about libvirt in the future. This is a question about libvirt domain XML. The documentation is here: http://libvirt.org/formatdomain.html#elementsDisks The attribute is called "error_policy". The documentation says: The optional error_policy attribute controls how the hypervisor will behave on a disk read or write error, possible values are "stop", "report", "ignore", and "enospace".Since 0.8.0, "report" since 0.9.7 The default setting of error_policy is "report". There is also an optional rerror_policy that controls behavior for read errors only. Since 0.9.7. If no rerror_policy is given, error_policy is used for both read and write errors. If rerror_policy is given, it overrides the error_policy for read errors. Also note that "enospace" is not a valid policy for read errors, so if error_policy is set to "enospace" and no rerror_policy is given, the read error policy will be left at its default, which is "report". Stefan

1 0

[libvirt-users] Libvirt profiling
by Jon Martin Sigvaldsen 23 Apr '13

23 Apr '13

Hi For a school project I am researching performance issues when using libvirt to run very large numbers of virtual machines. My experiments indicate that having more CPU cores negatively impacts the performance. A simple desktop with an Intel Core 2 Duo E6550 performs better than a server with a 48 core AMD CPU. Limiting the cores used through 'cputune' improves performance on the server. If anyone has got any explanations for this, it would be greatly appreciated. Further on I would like to profile the slowdowns, but I am not sure how to approach this problem. Any recommendations on how to do this? Best regards Jon

2 1

[libvirt-users] Sanlock - what are my options?
by Russell Jones 23 Apr '13

23 Apr '13

Hi all, I have an RHCS 2 node cluster utilizing SAN storage with GFS2 for the VM images. I am looking into configuring Sanlock, however am running into some architecture questions with it. The documentation for Sanlock states: "The sanlock plugin needs to create leases in a directory that is on a filesystem shared between all hosts running virtual machines. Obvious choices for this include NFS or GFS2." I do not have a highly available NFS mount where I can store the disk leases, and I cannot store the lockspace on the same GFS2 mount as the disk images as during fencing/journal recovery disk I/O can become blocked, which causes Sanlock to log warnings/errors about renewals. Is there another option for configuration?

1 0

[libvirt-users] problem when get the vm cpu stat
by Wangkai (Kevin,C) 20 Apr '13

20 Apr '13

Hi all, I try to get vm cpu stat by function "virDomainGetCPUStats", when the vm Cpu usage is 100%, I can see from the vm shell by "top", when the info Get by the "virDomainGetCPUStats" show only the "cpu_time" increased, "user_time" and "system_time" was not changed at all. Is that correct ? How can I get the vm cpu usage? nparams = virDomainGetCPUStats(domain, NULL, 0, -1, 1, 0); virDomainGetCPUStats(domain, params, nparams, -1, 1, 0); Thanks, Kevin.

2 2

[libvirt-users] Unexplained shutdown of VM on upgrade of libvirt package
by Chandana De Silva 19 Apr '13

19 Apr '13

I am running KVM on Centos 6.3 and am seeing an unexplained shut down of two guests. The libvirt package was upgraded to libvirt-0.10.2-18.el6_4.4.x86_64 at the time of the shutdown. Only the two guests shown below was affected, while 9 others running on the same hypervisor were not. Can some one help me to find the cause please ? Regards Chandana GUEST #1 ======== 2013-04-10 04:15:02.903+0000: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name guinness-a -S -M rhel6.3.0 -enable-kvm -m 4471 -smp 2,sockets=2,cores=1,threads=1 -uuid 894072ba-634c-40a2-9f70-0338d124abc3 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/guinness-a.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/libvirt/images/guinness-a.img,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,fd=28,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=54:52:00:98:7f:cc,bus=pci.0,addr=0x3 -netdev tap,fd=33,id=hostnet1 -device e1000,netdev=hostnet1,id=net1,mac=54:52:00:c4:d4:fd,bus=pci.0,addr=0x5 -netdev tap,fd=34,id=hostnet2 -device e1000,netdev=hostnet2,id=net2,mac=54:52:00:a3:33:24,bus=pci.0,addr=0x6 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:1 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 char device redirected to /dev/pts/11 2013-04-19 01:31:23.502+0000: shutting down qemu: terminating on signal 15 from pid 12852 GUEST #2 ======== 2013-03-24 22:30:36.881+0000: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name singha-a -S -M rhel6.3.0 -enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -uuid 52761f28-8f8d-4d79-a9c0-fd5222502cf4 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/singha-a.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/libvirt/images/singha-a.img,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,fd=32,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=54:52:00:2c:75:26,bus=pci.0,addr=0x3 -netdev tap,fd=33,id=hostnet1 -device e1000,netdev=hostnet1,id=net1,mac=54:52:00:b3:80:dd,bus=pci.0,addr=0x5 -netdev tap,fd=34,id=hostnet2 -device e1000,netdev=hostnet2,id=net2,mac=54:52:00:e6:aa:a2,bus=pci.0,addr=0x6 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 char device redirected to /dev/pts/5 2013-04-19 01:31:23.515+0000: shutting down qemu: terminating on signal 15 from pid 12852 PID 12582 is the libvirtd daemon, and I see this in the libvirtd log: 2013-04-19 01:31:23.492+0000: 13039: info : libvirt version: 0.10.2, package: 18.el6_4.4 (CentOS BuildSystem <http://bugs.centos.org>, 2013-04-18-16:13:45, c6b7.bsys.dev.centos.org) 2013-04-19 01:31:23.492+0000: 13039: error : virSecuritySELinuxReserveSecurityLabel:676 : internal error MCS level for existing domain label already reserved 2013-04-19 01:31:23.515+0000: 13035: error : virSecuritySELinuxReserveSecurityLabel:676 : internal error MCS level for existing domain label already reserved

1 0

[libvirt-users] How can I define a network using an exist host bridge
by Wangkai (Kevin,C) 18 Apr '13

18 Apr '13

Hi all, When I defined a network use the host bridge "virbr1" an error occurred : "libvir: error : Unable to create bridge virbr1: File exists" But how can I define this network use the host bridge "virbr1" ? <network> <name>def1</name> <bridge name='virbr1'/> <forward mode='nat'> <interface dev='eth0'/> </forward> </network> Thanks, Kevin

2 2

[libvirt-users] libvirt 1.0.3 Vs 1.0.4 / cgroup devices
by Mohamed Larabi 18 Apr '13

18 Apr '13

Hi there, I am using libvirt with lxc to create fedora 16 & 18 containers on fedora 18 host. first I did the setup with libvirt 1.0.3 and everything worked fine, then after upgrading to libvirt 1.0.4, I could not create character device on the guests : Test on the guest1 : # ls -l /dev total 0 lrwxrwxrwx. 1 root root 10 Apr 17 21:18 console -> /dev/pts/0 lrwxrwxrwx. 1 root root 11 Apr 17 21:18 core -> /proc/kcore lrwxrwxrwx. 1 root root 13 Apr 17 21:18 fd -> /proc/self/fd crw-rw-rw-. 1 root root 1, 7 Apr 17 21:18 full drwxr-xr-x. 2 root root 0 Apr 17 21:18 hugepages prw-------. 1 root root 0 Apr 17 21:18 initctl srw-rw-rw-. 1 root root 0 Apr 17 21:18 log drwxrwxrwt. 2 root root 40 Apr 17 21:18 mqueue crw-rw-rw-. 1 root root 1, 3 Apr 17 21:18 null crw-rw-rw-. 1 root root 5, 2 Apr 18 10:31 ptmx drwxr-xr-x. 2 root root 0 Apr 17 21:18 pts crw-r--r--. 1 root root 1, 8 Apr 17 21:19 random drwxrwxrwt. 2 root root 40 Apr 17 21:18 shm lrwxrwxrwx. 1 root root 15 Apr 17 21:18 stderr -> /proc/self/fd/2 lrwxrwxrwx. 1 root root 15 Apr 17 21:18 stdin -> /proc/self/fd/0 lrwxrwxrwx. 1 root root 15 Apr 17 21:18 stdout -> /proc/self/fd/1 lrwxrwxrwx. 1 root root 10 Apr 17 21:18 tty1 -> /dev/pts/0 crw-rw-rw-. 1 root root 1, 9 Apr 17 21:18 urandom crw-rw-rw-. 1 root root 1, 5 Apr 17 21:18 zero # rm -f /dev/random (successful) # mknod random c 1 8 mknod: `random': Operation not permitted Config on the host : knowing that selinux is set to permissive and c 1:8 rwm is in the cgroup devices list of the guest1 # cat /sys/fs/cgroup/devices/ libvirt/lxc/guest1/devices. list c 1:3 rwm c 1:5 rwm c 1:7 rwm c 1:8 rwm c 1:9 rwm c 5:0 rwm c 5:2 rwm c 10:229 rwm c 136:* rwm is this a change that was introduced intentially on 1.0.4 ? if yes, how can I make it work ? please advice Thank you in advance Mohamed

2 3

[libvirt-users] libvirt 1.0.3 Vs 1.0.4 / cgroup devices
by mohamed amine Larabi 18 Apr '13

18 Apr '13

Hi there, I am using libvirt with lxc to create fedora 16 & 18 containers on fedora 18 host. first I did the setup with libvirt 1.0.3 and everything worked fine, then after upgrading to libvirt 1.0.4, I could not create character device on the guests : Test on the guest1 : # ls -l /dev total 0 lrwxrwxrwx. 1 root root 10 Apr 17 21:18 console -> /dev/pts/0 lrwxrwxrwx. 1 root root 11 Apr 17 21:18 core -> /proc/kcore lrwxrwxrwx. 1 root root 13 Apr 17 21:18 fd -> /proc/self/fd crw-rw-rw-. 1 root root 1, 7 Apr 17 21:18 full drwxr-xr-x. 2 root root 0 Apr 17 21:18 hugepages prw-------. 1 root root 0 Apr 17 21:18 initctl srw-rw-rw-. 1 root root 0 Apr 17 21:18 log drwxrwxrwt. 2 root root 40 Apr 17 21:18 mqueue crw-rw-rw-. 1 root root 1, 3 Apr 17 21:18 null crw-rw-rw-. 1 root root 5, 2 Apr 18 10:31 ptmx drwxr-xr-x. 2 root root 0 Apr 17 21:18 pts crw-r--r--. 1 root root 1, 8 Apr 17 21:19 random drwxrwxrwt. 2 root root 40 Apr 17 21:18 shm lrwxrwxrwx. 1 root root 15 Apr 17 21:18 stderr -> /proc/self/fd/2 lrwxrwxrwx. 1 root root 15 Apr 17 21:18 stdin -> /proc/self/fd/0 lrwxrwxrwx. 1 root root 15 Apr 17 21:18 stdout -> /proc/self/fd/1 lrwxrwxrwx. 1 root root 10 Apr 17 21:18 tty1 -> /dev/pts/0 crw-rw-rw-. 1 root root 1, 9 Apr 17 21:18 urandom crw-rw-rw-. 1 root root 1, 5 Apr 17 21:18 zero # rm -f /dev/random (successful) # mknod random c 1 8 mknod: `random': Operation not permitted Config on the host : knowing that selinux is set to permissive and c 1:8 rwm is in the cgroup devices list of the guest1 # cat /sys/fs/cgroup/devices/libvirt/lxc/guest1/devices.list c 1:3 rwm c 1:5 rwm c 1:7 rwm c 1:8 rwm c 1:9 rwm c 5:0 rwm c 5:2 rwm c 10:229 rwm c 136:* rwm is this a change that was introduced intentially on 1.0.4 ? if yes, how can I make it work ? please advice Thank you in advance Amine

1 0

[libvirt-users] question about process power which has MCSx
by yue 17 Apr '13

17 Apr '13

hi,all a qemu-kvm process and its disk(image file) have the same MCS(s0:c111,c555). it express this process have access to this image. i do not know the power to access its image file is the max or min? if any other power this process(domain) has?how much? i want to know the exact power a qemu-kvm process has besides access its image file ,other kinds of files,dirs etc. my test case: after start a guestVM(its disk xml ,cache='none' error_policy='stop'), make some modification on its files and save them. then go to hypervisor, modify the MCS of guestVM's image file. 1.i can read those files(cache=none)?it should not be so. why? 2.then modify files and save, the guestVM hang, it is paused on UI. this is right qeum process can not write again. why this guestVM is hang? and can not be resumed 3.look at audit info. denied { write } for pid=52162 comm="qemu-kvm". that pid is 52162, is not my qemu-kvm's pid? why? thanks so much.

2 1

[libvirt-users] libvirt support for qcow2 rebase?
by Skardal, Harald 17 Apr '13

17 Apr '13

I have not found support in libvirt (nor virsh) for doing the equivalent of "qemu-img rebase ....". The use case: You have copied a qcow2 stack and the new files have different names or reside in a different directory. Therefore you need to change the backing file. Is there a way to do this? Is this a planned addition to libvirt? Harald

3 2

[libvirt-users] Any good writeups of using libvirt with LXC
by brian mullan 17 Apr '13

17 Apr '13

I've been experimenting a bit with using libvirt and LXC. But have not found many good examples of use so far. Anyone got any they can point me to. thanks brian

3 2

[libvirt-users] Update request: When support for live snapshot delete incl coalesce
by Skardal, Harald 17 Apr '13

17 Apr '13

Does the libvirt development team have a sense of when/which version of libvirt will support the deletion of live snapshots, incl. the coalesce. With the restriction that you cannot delete the most recent snapshot! Harald

2 1

[libvirt-users] Shouldn't vol-upload / virStorageVolUpload() be doing some format conversion?
by Guido Winkelmann 15 Apr '13

15 Apr '13

Hi, I just tried using vol-update to copy an image file to a storage pool, and I noticed that, at least in my configuration (qemu backend, storage pool of type "dir"), this command does not appear to be doing any kind of format conversion. It simply copied the source file as-is over the file in which the target volume was stored with no checks whether that even makes sense. The help text to this command says it supports offset and length, which - kinda, sorta - implies that I can write a block of bytes at offset n to a volume, attach that volume to a domain, and then the OS in the guest domain will find exactly the bytes I just wrote at exactly offset n in its newly attached harddisk/CDROM/whatever. Instead, trying to this with anything but raw images would probably just break the image file. AFAICS, in its current form, this command and this API-call are only useful in exactly two scenarios: - Both the source and target image are in raw format - Source and target image are in the same non-raw format (like qcow2 or vmdk) AND you are copying the entire volume at once. In all other cases - source and target are in different formats, source and target are in non-raw and you are trying to write only parts of a volume - this can only lead to a broken image file. As far as I see it, at the layer of abstraction libvirt offers, "volume" should not be synonymous with "the file the file the volume is stored in on disk", but rather with "the volume as a guest machine will get to see it". Regards, Guido

2 3

[libvirt-users] network under session
by Evaggelos Balaskas 15 Apr '13

15 Apr '13

Perhaps a stupid question, but i will give it a try: I have two machines on libvirtd session and network on usermod. Can i (somehow) cross these two machines ? machineA: ip addr add 10.10.10.101/24 dev eth0 ip route add default via 10.10.10.102 dev eth0 machineB: ip addr add 10.10.10.102/24 dev eth0 ip route add default via 10.10.10.101 dev eth0 -- Evaggelos Balaskas - Unix System Engineer http://gr.linkedin.com/in/evaggelosbalaskas

2 1

[libvirt-users] using transport protocol in live migration
by digvijay chauhan 15 Apr '13

15 Apr '13

Hello, I am working on live migration of virtual machine using xen and kvm.If i use qemu+ssh:///system then is the transport protocol used during live migration tcp or ssh?I mean i want to evaluate the performance of transport protocil during live migration using wireshark and netperf tool,so using this command will show tcp performance? Orelse i will have to use qemu+tcp:/// ?

2 2

[libvirt-users] how to start virbr0-nic when start NAT network virbr0
by yue 15 Apr '13

15 Apr '13

in my case each ethernet must in UP status even it is a NAT network where is the point i can start its virt-ethernet when i start a NAT-network? thanks

2 1

[libvirt-users] after snapshot-delete, the qcow2 image file size doesn't decrease
by me,apporc 15 Apr '13

15 Apr '13

After snapshot-delete, the qcow2 image file size doesn't decrease, isn't that a waste of disk space? Would someone please tell me how to decrease the file size when snapshot-delete, if that's possible? The image file name of my virtual machine is d0.qcow As follows: [root@test1 ]# virsh list Id Name State ---------------------------------------------------- 32 bfbe8ca8-8579-11e2-844a-001018951f48 running [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 3.6G cluster_size: 65536 [root@test1 ]# ls -lh total 3.6G -rw------- 1 qemu qemu 3.6G Apr 12 17:13 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root@test1 ]# virsh snapshot-list bfbe8ca8-8579-11e2-844a-001018951f48 Name Creation Time State ------------------------------------------------------------ [root@test1 8]# virsh snapshot-create bfbe8ca8-8579-11e2-844a-001018951f48 Domain snapshot 1365758005 created [root@test1 ]# virsh snapshot-create bfbe8ca8-8579-11e2-844a-001018951f48 Domain snapshot 1365758022 created [root@test1 bfbe8ca8-8579-11e2-844a-001018951f48]# virsh snapshot-list bfbe8ca8-8579-11e2-844a-001018951f48 Name Creation Time State ------------------------------------------------------------ 1365758005 2013-04-12 17:13:25 +0800 running 1365758022 2013-04-12 17:13:42 +0800 running [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 3.8G cluster_size: 65536 Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1 1365758005 127M 2013-04-12 17:13:25 00:00:53.141 2 1365758022 127M 2013-04-12 17:13:42 00:01:09.508 [root@test1 ]# ls -lh total 3.9G -rw------- 1 qemu qemu 3.9G Apr 12 17:14 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root@test1 ]# virsh snapshot-delete bfbe8ca8-8579-11e2-844a-001018951f48 1365758022 Domain snapshot 1365758022 deleted [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 3.8G cluster_size: 65536 Snapshot list: ID TAG VM SIZE DATE VM CLOCK 0 1970-01-01 08:00:00 00:00:00.000 [root@test1 ]# ls -lh total 3.9G -rw------- 1 qemu qemu 3.9G Apr 12 17:14 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root@test1 ]# virsh snapshot-delete bfbe8ca8-8579-11e2-844a-001018951f48 1365758005 Domain snapshot 1365758005 deleted [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 3.8G cluster_size: 65536 [root@test1 ]# ls -lh total 3.9G -rw------- 1 qemu qemu 3.9G Apr 12 17:14 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root@test1 ]# virsh snapshot-create bfbe8ca8-8579-11e2-844a-001018951f48 Domain snapshot 1365758311 created [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 3.8G cluster_size: 65536 Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1 1365758311 252M 2013-04-12 17:18:32 00:05:58.136 [root@test1 ]# ls -lh total 3.9G -rw------- 1 qemu qemu 3.9G Apr 12 17:18 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root@test1 ]# virsh snapshot-create bfbe8ca8-8579-11e2-844a-001018951f48 Domain snapshot 1365758338 created [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 4.1G cluster_size: 65536 Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1 1365758311 252M 2013-04-12 17:18:32 00:05:58.136 2 1365758338 252M 2013-04-12 17:18:58 00:06:24.272 [root@test1 ]# ls -lh total 4.1G -rw------- 1 qemu qemu 4.1G Apr 12 17:19 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root@test1 ]# virsh snapshot-list bfbe8ca8-8579-11e2-844a-001018951f48 Name Creation Time State ------------------------------------------------------------ 1365758311 2013-04-12 17:18:31 +0800 running 1365758338 2013-04-12 17:18:58 +0800 running [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 4.1G cluster_size: 65536 Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1 1365758311 252M 2013-04-12 17:18:32 00:05:58.136 2 1365758338 252M 2013-04-12 17:18:58 00:06:24.272 [root@test1 ]# virsh snapshot-delete bfbe8ca8-8579-11e2-844a-001018951f48 1365758338 Domain snapshot 1365758338 deleted [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 4.1G cluster_size: 65536 Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1 1365758311 252M 2013-04-12 17:18:32 00:05:58.136 [root@test1 ]# ls -lh total 4.1G -rw------- 1 qemu qemu 4.1G Apr 12 17:20 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root@test1 ]# virsh snapshot-delete bfbe8ca8-8579-11e2-844a-001018951f48 1365758311 Domain snapshot 1365758311 deleted [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 4.1G cluster_size: 65536 [root@test1 ]# ls -lh total 4.1G -rw------- 1 qemu qemu 4.1G Apr 12 17:20 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root@test1 ]# virsh snapshot-list bfbe8ca8-8579-11e2-844a-001018951f48 Name Creation Time State ------------------------------------------------------------

3 2

[libvirt-users] virt-install on powerpc64 issues
by Alexey Kardashevskiy 15 Apr '13

15 Apr '13

Hi! I am trying to setup a guest using virt-install script: /usr/bin/virt-install -n fc18guest5 -r 1024 \ --disk path=/home/aik/virtimg/fc18guest,size=8 \ -c /home/aik/virtimg/Fedora-18-ppc64-DVD.iso \ --video vga --arch=ppc64 -d --machine=pseries And it fails. I could not find any relevant log in /var/log/libvirt/ so I simply hacked /usr/local/bin/qemu-system-ppc64 to print all the parameters passed into it. So I got the command line (below, after the second question) where the "-device scsi-cd" parameter is cut in a middle so QEMU fails to start. 788 chars long - is there a limit? The second question is - where does virt-install store those xmls? I have to choose a new name for a machine even if virt-install failed, in the example it is "fc18guest5" (5 at the end). "virsh -c qemu:///system list" prints an empty list with no domains. Thanks! /usr/local/bin/qemu-system-ppc64 -name fc18guest5 -S -M pseries -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -uuid 71f8b17f-ca48-80fe-db58-4d933c66fe2d -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/home/aik/.config/libvirt/qemu/lib/fc18guest5.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -no-shutdown -device pci-ohci,id=usb,bus=pci,addr=0x1.0x2 -device spapr-vscsi,id=scsi0,reg=0x2000 -drive file=/home/aik/virtimg/fc18guest,if=none,id=drive-scsi0-0-0-0,format=raw -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2 -drive file=/home/aik/virtimg/Fedora-18-ppc64-DVD.iso,if=none,id=drive-scsi0-0-0-1,readonly=on,format=raw -device scsi-cd,bus=scsi0.0,ch The full log is here: [aik@vpl2 ~]$ ./start_installation.sh ++ /usr/bin/virt-install -n fc18guest5 -r 1024 --disk path=/home/aik/virtimg/fc18guest,size=8 -c /home/aik/virtimg/Fedora-18-ppc64-DVD.iso --video vga --arch=ppc64 -d --machine=pseries [Wed, 10 Apr 2013 15:06:10 virt-install 9880] DEBUG (cli:221) Launched with command line: /usr/bin/virt-install -n fc18guest5 -r 1024 --disk path=/home/aik/virtimg/fc18guest,size=8 -c /home/aik/virtimg/Fedora-18-ppc64-DVD.iso --video vga --arch=ppc64 -d --machine=pseries [Wed, 10 Apr 2013 15:06:10 virt-install 9880] DEBUG (cli:326) Requesting libvirt URI default [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (cli:328) Received libvirt URI qemu:///session [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (virt-install:259) Requesting virt method 'default', hv type 'default'. [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (virt-install:469) Received virt method 'hvm' [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (virt-install:470) Hypervisor name is 'kvm' [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (cli:935) DISPLAY is set: graphics defaulting to VNC. [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (cli:953) --graphics compat generated: vnc [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (DistroInstaller:209) DistroInstaller location is a local file/path: /home/aik/virtimg/Fedora-18-ppc64-DVD.iso [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (virt-install:626) Guest.has_install_phase: True Starting install... [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (Guest:1296) Generated install XML: <domain type='kvm'> <name>fc18guest5</name> <uuid>56b64ac6-9596-6e8e-5321-4fc583960065</uuid> <memory>1048576</memory> <currentMemory>1048576</currentMemory> <vcpu>1</vcpu> <os> <type arch='ppc64' machine='pseries'>hvm</type> <boot dev='cdrom'/> <boot dev='hd'/> </os> <features> <acpi/><apic/><pae/> </features> <clock offset="utc"/> <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/local/bin/qemu-system-ppc64</emulator> <disk type='file' device='disk'> <driver name='qemu'/> <source file='/home/aik/virtimg/fc18guest'/> <target dev='sda' bus='scsi'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu'/> <source file='/home/aik/virtimg/Fedora-18-ppc64-DVD.iso'/> <target dev='sdb' bus='scsi'/> <readonly/> </disk> <interface type='user'> <mac address='52:54:00:ca:ed:7a'/> </interface> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1'/> <console type='pty'/> <video> <model type='vga'/> </video> </devices> </domain> [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (Guest:1297) Generated boot XML: <domain type='kvm'> <name>fc18guest5</name> <uuid>56b64ac6-9596-6e8e-5321-4fc583960065</uuid> <memory>1048576</memory> <currentMemory>1048576</currentMemory> <vcpu>1</vcpu> <os> <type arch='ppc64' machine='pseries'>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/local/bin/qemu-system-ppc64</emulator> <disk type='file' device='disk'> <driver name='qemu'/> <source file='/home/aik/virtimg/fc18guest'/> <target dev='sda' bus='scsi'/> </disk> <disk type='block' device='cdrom'> <target dev='sdb' bus='scsi'/> <readonly/> </disk> <interface type='user'> <mac address='52:54:00:ca:ed:7a'/> </interface> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1'/> <console type='pty'/> <video> <model type='vga'/> </video> </devices> </domain> [Wed, 10 Apr 2013 15:06:12 virt-install 9880] ERROR (cli:439) internal error process exited while connecting to monitor: char device redirected to /dev/pts/4 (label charserial0) [0]/usr/local/bin/qemu-system-ppc64 [1]-name [2]fc18guest5 [3]-S [4]-M [5]pseries [6]-enable-kvm [7]-m [8]1024 [9]-smp [10]1,sockets=1,cores=1,threads=1 [11]-uuid [12]56b64ac6-9596-6e8e-5321-4fc583960065 [13]-no-user-config [14]-nodefaults [15]-chardev [16]socket,id=charmonitor,path=/home/aik/.config/libvirt/qemu/lib/fc18guest5.monitor,server,nowait [17]-mon [18]chardev=charmonitor,id=monitor,mode=control [19]-rtc [20]base=utc [21]-no-reboot [22]-no-shutdown [23]-device [24]pci-ohci,id=usb,bus=pci,addr=0x1.0x2 [25]-device [26]spapr-vscsi,id=scsi0,reg=0x2000 [27]-drive [28]file=/home/aik/virtimg/fc18guest,if=none,id=drive-scsi0-0-0-0,format=raw [29]-device [30]scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2 [31]-drive [32]file=/home/aik/virtimg/Fedora-18-ppc64-DVD.iso,if=none,id=drive-scsi0-0-0-1,readonly=on,format=raw [33]-device [34]scsi-cd,bus=scsi0.0,ch [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (cli:442) Traceback (most recent call last): File "/usr/bin/virt-install", line 636, in start_install noboot=options.noreboot) File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1249, in start_install noboot) File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1317, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2775, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error process exited while connecting to monitor: char device redirected to /dev/pts/4 (label charserial0) [0]/usr/local/bin/qemu-system-ppc64 [1]-name [2]fc18guest5 [3]-S [4]-M [5]pseries [6]-enable-kvm [7]-m [8]1024 [9]-smp [10]1,sockets=1,cores=1,threads=1 [11]-uuid [12]56b64ac6-9596-6e8e-5321-4fc583960065 [13]-no-user-config [14]-nodefaults [15]-chardev [16]socket,id=charmonitor,path=/home/aik/.config/libvirt/qemu/lib/fc18guest5.monitor,server,nowait [17]-mon [18]chardev=charmonitor,id=monitor,mode=control [19]-rtc [20]base=utc [21]-no-reboot [22]-no-shutdown [23]-device [24]pci-ohci,id=usb,bus=pci,addr=0x1.0x2 [25]-device [26]spapr-vscsi,id=scsi0,reg=0x2000 [27]-drive [28]file=/home/aik/virtimg/fc18guest,if=none,id=drive-scsi0-0-0-0,format=raw [29]-device [30]scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2 [31]-drive [32]file=/home/aik/virtimg/Fedora-18-ppc64-DVD.iso,if=none,id=drive-scsi0-0-0-1,readonly=on,format=raw [33]-device [34]scsi-cd,bus=scsi0.0,ch [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (cli:451) Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///session start fc18guest5 otherwise, please restart your installation. Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///session start fc18guest5 otherwise, please restart your installation. [aik@vpl2 ~]$ virsh -c qemu:///system list Id Name State ---------------------------------------------------- [aik@vpl2 ~]$ -- Alexey

2 9

[libvirt-users] Port forwarding for KVM
by 陳韋任 (Wei-Ren Chen) 13 Apr '13

13 Apr '13

Hi all, Let me illustrate what I want to do. I want to launch a QEMU "inside" a KVM virtual machine, then get that QEMU's vnc output. I am using libvirt 0.9.13 (`libvirtd --version`), and attach is my vm's original config xml. Is there a simple way to achieve my goal? I was told that iptable solution I found on the web is for "tap" interface, and I can use "hostfwd" QEMU option if I use "user" interface. For the latter approach, I basically follow this one [1] with the QEMU cmdline option below: <qemu:commandline> <qemu:arg value='-net user,hostfwd=::5902-:5901'/> </qemu:commandline> But virsh always keep saying: error: internal error Process exited while reading console log output: kvm: -net user,hostfwd=::5902-:5901: invalid option What I am missing here? I also found there was a patch for user mode port forwarding [2]. Does that mean I can write libvirt xml directly to do port forwarding? If so, could someone give me hint on how to write one? The last question is, do I have to change the interface type from "network" to "user" so that I can do port forwarding? Thanks in advance! :) [1] http://snippets.webaware.com.au/snippets/running-qemu-with-port-redirection… [2] http://www.redhat.com/archives/libvir-list/2012-May/msg00538.html Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667 Homepage: http://people.cs.nctu.edu.tw/~chenwj

3 3

[libvirt-users] Libvirtd dead, pid still exists. ( Problem might be with TLS interface of libvirtd )
by SHREE DUTH AWASTHI 12 Apr '13

12 Apr '13

Dear All, Please find few minutes from your time and guide us with some pointers if possible. We are facing a libvirtd crash when we are trying to connect to qemu by default TLS transport. # virsh -c qemu+tls://localhost/system version error: authentication failed: TLS handshake failed A TLS packet with unexpected length was received. error: failed to connect to the hypervisor I used my own CA and certificates (generated using http://libvirt.org/remote.html#Remote_libvirtd_configuration on Redhat PC) on both Kontron PC and our Board (with patched libvirt). Libvirtd.conf was modified so that libvirt is listening all IPs using default IP (so that it was possible to use same certificates on all machines) These directories and files created and used. /etc/pki/CA/cacert.pem /etc/pki/libvirt/private/serverkey.pem /etc/pki/libvirt/servercert.pem /etc/pki/libvirt/private/clientkey.pem /etc/pki/libvirt/clientcert.pem TLS connection worked fine with Kontron PC # virsh -c qemu+tls://localhost/system version Compiled against library: libvir 0.9.5 Using library: libvir 0.9.5 Using API: QEMU 0.9.5 Running hypervisor: QEMU 0.12.1 But libvirt crashed on our Board (using libvirt 0.10.2, gnutls-2.10.5-1_WR4.3.x86_64 and libudev-161-4 rpms ) # virsh -c qemu+tls://localhost/system version error: authentication failed: TLS handshake failed A TLS packet with unexpected length was received. error: failed to connect to the hypervisor GDB: Program received signal SIGABRT, Aborted. 0x00007f8591246005 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x00007f8591246005 in raise () from /lib64/libc.so.6 #1 0x00007f8591248e40 in abort () from /lib64/libc.so.6 #2 0x00007f8592a2fdc5 in ?? () from /lib64/libgcrypt.so.11 #3 0x00007f8592a303d5 in ?? () from /lib64/libgcrypt.so.11 #4 0x00007f8592a35697 in ?? () from /lib64/libgcrypt.so.11 #5 0x00007f8592a3579c in ?? () from /lib64/libgcrypt.so.11 #6 0x00007f8592a30a65 in ?? () from /lib64/libgcrypt.so.11 #7 0x00007f8592a30aa9 in ?? () from /lib64/libgcrypt.so.11 #8 0x00007f8592a30b19 in ?? () from /lib64/libgcrypt.so.11 #9 0x00007f8592a735df in ?? () from /lib64/libgcrypt.so.11 #10 0x00007f8592a7365f in ?? () from /lib64/libgcrypt.so.11 #11 0x00007f8592a6025a in ?? () from /lib64/libgcrypt.so.11 #12 0x00007f8592a6045a in ?? () from /lib64/libgcrypt.so.11 #13 0x00007f8592a3c1ef in ?? () from /lib64/libgcrypt.so.11 #14 0x00007f8592cd9d8c in ?? () from /usr/lib64/libgnutls.so.26 #15 0x00007f8592cc5e7a in ?? () from /usr/lib64/libgnutls.so.26 #16 0x00007f8592ccddd6 in ?? () from /usr/lib64/libgnutls.so.26 #17 0x00007f8592cce67f in ?? () from /usr/lib64/libgnutls.so.26 #18 0x00007f8592ccedaf in ?? () from /usr/lib64/libgnutls.so.26 #19 0x00007f8592cbaf85 in ?? () from /usr/lib64/libgnutls.so.26 #20 0x00007f8592cb6c55 in ?? () from /usr/lib64/libgnutls.so.26 #21 0x00007f8592cb7437 in gnutls_handshake () from /usr/lib64/libgnutls.so.26 #22 0x00007f8593a5961b in virNetTLSSessionHandshake () from /usr/lib64/libvirt.so.0 Please let us know if it is a known problem. If not, I will raise a new bug for the same. ( Atleast I coulnt find the the known issues ) Thanks and Regards, Shree Duth Awasthi.

3 8

[libvirt-users] Accessing libvirtd from multiple agents
by arvind viswanathan 12 Apr '13

12 Apr '13

Hi, I was wondering if multiple remote agents can access the same libvirtd. How do we prevent conflicting commands from the different agents. Can different access permission be set for the agents? (The documentation usually goes over the case where one agent can access multiple libvirtd and not this case) Thanks Arvind

4 4

[libvirt-users] virtio_ioport_write: unexpected address
by denghuancong 12 Apr '13

12 Apr '13

the guest is normally running, but the qemu log is printing the following message: what happen? thanks a lot. virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0

1 0

[libvirt-users] virtio_ioport_write: unexpected address
by denghuancong 12 Apr '13

12 Apr '13

the guest is normally running, but the qemu log is printing the following message: what happen? thanks a lot. virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0

1 0

Re: [libvirt-users] fail to convert qemu xml to args with libvirt-1.0.4: An error occurred, but the cause is unknown
by Yin Olivia-R63875 12 Apr '13

12 Apr '13

Hi Daniel, I also tried libvirt-1.0.4 on my X86 machine. user@x86:~ $ uname -a Linux 2.6.32-33-server #70-Ubuntu SMP Thu Jul 7 22:28:30 UTC 2011 x86_64 GNU/Linux user@x86:~ $ which virsh /usr/local/bin/virsh user@x86:~ $ /usr/local/bin/virsh --version 1.0.4 user@x86:~ $ cd libvirt-1.0.4/tests/qemuxml2argvdata user@x86:~/libvirt-1.0.4/tests/qemuxml2argvdata $ virsh domxml-to-native qemu-argv qemuxml2argv-disk-virtio.xml >1.dom error：An error occurred, but the cause is unknown Best Regards, Olivia > -----Original Message----- > From: Yin Olivia-R63875 > Sent: Thursday, April 11, 2013 10:18 AM > To: 'Daniel P. Berrange' > Cc: 'libvirt-users(a)redhat.com'; 'libvir-list(a)redhat.com' > Subject: RE: fail to convert qemu xml to args with libvirt-1.0.4: An error > occurred, but the cause is unknown > > Hi Daniel, > > Just Ping. > Did you ever successfully convert QEMU xml file to argv on other platforms? > > Best Regards, > Olivia > > > -----Original Message----- > > From: Yin Olivia-R63875 > > Sent: Tuesday, April 09, 2013 1:22 PM > > To: 'libvir-list(a)redhat.com' > > Cc: 'libvirt-users(a)redhat.com' > > Subject: fail to convert qemu xml to args with libvirt-1.0.4: An error > > occurred, but the cause is unknown > > > > Hi, > > > > I used to convert qemu XML to args with libvirt-1.0.3. > > But it failed to convert with libvirt-1.0.4. > > > > # virsh domxml-to-native qemu-argv test.xml >test.sh > > error: An error occurred, but the cause is unknown > > > > > > Comparing the debug file as below: > > 1) lbvirt-1.0.3 > > <cut> > > 2013-04-09 03:23:47.296+0000: 2669: debug : > > virEventPollInterruptLocked:716 : Interrupting > > 2013-04-09 03:23:47.296+0000: 2669: debug : virNetClientIO:1807 : All > > done with our call head=(nil) call=0x100871c0 rv=0 > > 2013-04-09 03:23:47.297+0000: 2670: debug : virEventPollRunOnce:640 : > > Poll got 1 event(s) > > 2013-04-09 03:23:47.297+0000: 2670: debug : > > virEventPollDispatchTimeouts:425 : Dispatch 0 > > 2013-04-09 03:23:47.297+0000: 2669: debug : virNetMessageFree:73 : > > msg=0x10087500 nfds=0 cb=(nil) > > 2013-04-09 03:23:47.297+0000: 2670: debug : > > virEventPollDispatchHandles:470 : Dispatch 1 > > 2013-04-09 03:23:47.297+0000: 2670: debug : > > virEventPollDispatchHandles:484 : i=0 w=1 > > 2013-04-09 03:23:47.297+0000: 2669: debug : virConnectClose:1483 : > > conn=0x100878b8 <cut> > > > > 2) libvirt-1.0.4 > > <cut> > > 2013-04-09 03:07:58.012+0000: 2834: debug : > > virEventPollInterruptLocked:716 : Interrupting > > 2013-04-09 03:07:58.012+0000: 2834: debug : virNetClientIO:1810 : All > > done with our call head=(nil) call=0x10089db8 rv=0 > > 2013-04-09 03:07:58.012+0000: 2835: debug : virEventPollRunOnce:640 : > > Poll got 1 event(s) > > 2013-04-09 03:07:58.012+0000: 2835: debug : > > virEventPollDispatchTimeouts:425 : Dispatch 0 > > 2013-04-09 03:07:58.012+0000: 2834: error : > > virNetClientProgramDispatchError:175 : An error occurred, but the > > cause is unknown > > 2013-04-09 03:07:58.012+0000: 2835: debug : > > virEventPollDispatchHandles:470 : Dispatch 1 > > 2013-04-09 03:07:58.012+0000: 2834: debug : virNetMessageFree:73 : > > msg=0x1008a0f8 nfds=0 cb=(nil) > > 2013-04-09 03:07:58.012+0000: 2835: debug : > > virEventPollDispatchHandles:484 : i=0 w=1 > > 2013-04-09 03:07:58.012+0000: 2835: debug : > > virEventPollDispatchHandles:498 : EVENT_POLL_DISPATCH_HANDLE: watch=1 > > events=1 > > 2013-04-09 03:07:58.012+0000: 2835: debug : > > virEventPollCleanupTimeouts:516 : Cleanup 0 > > 2013-04-09 03:07:58.013+0000: 2835: debug : > > virEventPollCleanupTimeouts:552 : Found 0 out of 0 timeout slots used, > > releasing 0 > > 2013-04-09 03:07:58.013+0000: 2835: debug : > virEventPollCleanupHandles:564 : > > Cleanup 2 > > 2013-04-09 03:07:58.013+0000: 2834: debug : virConnectClose:1483 : > > conn=0x1008a4b0 <cut> > > > > > > How can I debug this cause unknown error? > > > > Best Regards, > > Olivia

1 0