- Users - libvirt List Archives

[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