- Users - libvirt List Archives

[libvirt-users] XP and virtio
by Mauricio Tavares 01 Aug '14

01 Aug '14

So I need to create a XP vm. I am using lvm logical volumes for its disk, so I am using virtio. I got the iso in http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/images/, but how do I feed it to the XP install? I did try to mount it as a floppy and it hung there on "please wait"; I guess that means it did not like a 70MB iso as its floppy. But it also does not seem to want to look for the drivers if I mount the .iso as a CD. What else can I try?

3 3

[libvirt-users] How to configure selinux for lxc in libvirt
by Qiang Guan 01 Aug '14

01 Aug '14

Hi guys, I want to use selinux for my lxc vm starting by libvirt. How to configure this? Is there any documents about using selinux with libvirt? Thanks for any advice~ -- ------------ Jackie Best Regards

1 0

[libvirt-users] multicast traffic no longer working after reboot
by Dennis Jacobfeuerborn 31 Jul '14

31 Jul '14

Hi, today a couple of Hypervisors got restarted due to a power outage. While the systems and the VMs on the are running fine multicast traffic between the guests is no longer working. I generate multicast udp packet using iperf in the guest and check on the host using tcpdump: tcpdump vnet0 => multicast packets are visible tcpdump vlanbr8 => multicast packets are visible tcpdump em1.8 => no multicast packets visible vlanbr8 is the bridge, vnet0 the interface of the guest and em1.8 the physical interface for vlan 8. I compared the settings in /sys/class/net/vlanbr8/bridge/multicast_* with a system where multicast works fine and see no differences. brctl showstp also shows "mc router" to be 1 for both interfaces and the bridge. All settings in /proc/sys/net/bridge/* are 0. Any ideas why the bridge doesn't seem to forward multicast packets? iperf with unicast udp also works fine so it's just multicast that is the problem. Regards, Dennis

2 3

[libvirt-users] problem when using qemu 2.0.0 + libvirt 1.2.6
by weiwei li 31 Jul '14

31 Jul '14

Hi I got a problem when using qemu 2.0.0 + libvirt 1.2.6 . It just can not define a kvm vm successfully , errors like this : # virsh define 5ab4f49c-c99f-4dbd-9d7d-17a946b4c5a7.xml error: Failed to define domain from 5ab4f49c-c99f-4dbd-9d7d-17a946b4c5a7.xml error: unknown OS type hvm After several tries, i found that Qemu2.0 /qemu-kvm1.2+ libvirt1.0.2 and lower version is ok Qemu2.0 /qemu-kvm1.2+ libvirt1.0.3 and higher version is failed I have checked system as bellows: 1 kvm,kvm_intel modules are loaded(centos 6.2 /kernel 2.6.32) 2 bios is ok for hvm 3 qemu is installed and emulator path in xml config file is correct 4 I also tried to install glusterfs-devel-3.2.7-1.el6.x86_64 and rebuild qemu , no use. 5 virsh capabilities can not get guest capabilities in the failure scenario so ,why Qemu2.0 /qemu-kvm1.2+ libvirt1.0.3 and above version could not work? thanks, weiwei

2 2

[libvirt-users] missing libvirt-sock and libvirt-bin after compile libvirt 1.2.6
by Yuanzhen Gu 30 Jul '14

30 Jul '14

Good morning there, I compiled and installed libvirt latest version 1.2.6, previously I have apt-get install libvirt-bin, which should be virsh --version: 0.9.8. after apt-get purge libvirt-bin, I compile the libvirt 1.2.6 and installed it, when configure, I did: ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc --with-esx=yes I have compiled qemu and installed too, and make a symbolic link to /usr/bin/qemu-system-x86_64 but my question is even I launch a vm in qemu, $virsh list showed nothing, further more, 1) if I use virtual machine manager, it get connection failiure, due to socket to '/var/run/libvirt/libvirt-sock'; No such file of dirctory. 2). there is missing libvirt-bin under /etc/init.d/, after compile and installed libvirt 1.2.6 3). I tried to start libvirtd daemon, sudo /usr/sbin/libvirtd/start shows "/usr/sbin/libvirtd: unexpected, non-option, command line arguments" 4). I've checked /var/log/libvirt/libvirtd.log which shows cannot find suitable emulator for x86_64 I've stuck here for whole afternoon yesterday, any help or suggestion is highly appreciated !! thanks a lot in advance ! Best, Yuanzhen Best, Yuanzhen Best, Yuanzhen

1 0

[libvirt-users] VM not booting with physical hardware attached
by Pierre Schweitzer 30 Jul '14

30 Jul '14

Dear all, I'm looking for a bit of help with a problematic VM. We have an hypervisor which has 4 eth ports. 3 are already used, and I wanted to pass the 4th one directly to a VM (which is fully working without it). So, I modified the XML accordingly (which matches our hardware), adding: <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x3'/> </source> </hostdev> I also activated Intel IOMMU in Linux (and rebooted). Then, I issued a virsh start <domain>. libvirt is able to fire the VM, but then the OS inside doesn't boot at all. I tried to go deeper into debugging and it seems that the VM cannot pass SeaBIOS anymore. It gets stuck in seabios, it seems. No "Booting" sentence displayed, only version of SeaBIOS, when I watch VNC ouput. I tried to use <bios useserial='yes'/> with a console to the VM. Nothing is displayed on the console. Here are the specs of the machine: -> Ubuntu 12.04LTS up to date -> libvirt 0.9.8-2ubuntu17.19 -> kvm 1.0+noroms-0ubuntu14.15 -> seabios 0.6.2-0ubuntu2.1 The ethernet card I try to attach is: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe Its PCI ID being: 14e4:1657 What are the possibilities to debug this issue? What are the possibilities to fix it as well? Thanks to everyone helping! With my best regards, -- Pierre Schweitzer <pierre(a)reactos.org> System & Network Administrator Senior Kernel Developer ReactOS Deutschland e.V.

1 1

[libvirt-users] lxc arp doesn't work at start for several seconds
by Jonathan Rudenberg 29 Jul '14

29 Jul '14

I’m running into an issue with libvirt-lxc networking. I have an init program that configures the eth0 interface with an IP and gateway when the container starts. I noticed that programs running in the container encountered “no route to host” errors and looked into it further. What I found is that ARP packets are not making it onto the gateway during the first few seconds of the container’s life. I have created a repro case that demonstrates this issue: https://github.com/titanous/libvirt-arp-bug All it does is configure eth0 and then ARPs the bridge IP. There are no ARP responses for ~4s and then everything starts working. The linked repo also contains pcap files from the veth and the bridge showing that the ARP packets are sent over the veth but don’t show up on the bridge. I’ve tested and run into this issue 100% of the time on Ubuntu 14.04 with libvirt 1.2.2 and Linux 3.13.0-32 as well as Fedora 20 with libvirt 1.1.3.5 and Linux 3.15.6-200. Any help would be appreciated, and I’m happy to provide more details if they would be useful. Thanks, Jonathan

2 2

[libvirt-users] Running domain-update memory not working
by usha basavaraju 29 Jul '14

29 Jul '14

>>> vm=co.lookupByName('test1') >>> vm.info() [1, 524288L, 524288L, 1, 20400000000L] >>> vm.setMemoryFlags(509952,1) # Live memory 0 >>> vm.info() [1, 524288L, 524288L, 1, 21430000000L] >>> vm.setMemoryFlags(509952,0) --- ## current memory 0 >>> vm.info() [1, 524288L, 524288L, 1, 21430000000L] >>> vm.XMLDesc() Not updating .. but api call not throwing any error.. What is the correct procedure for updating

2 1

[libvirt-users] [libivrt-user]problem when using qemu 2.0.0 + libvirt 1.2.6
by weiwei li 29 Jul '14

29 Jul '14

Hi I got a problem when using qemu 2.0.0 + libvirt 1.2.6 . It just can not define a kvm vm successfully , errors like this : # virsh define 5ab4f49c-c99f-4dbd-9d7d-17a946b4c5a7.xml error: Failed to define domain from 5ab4f49c-c99f-4dbd-9d7d-17a946b4c5a7.xml error: unknown OS type hvm after several tries, i found that Qemu2.0 /qemu-kvm1.2+ libvirt1.0.2 and lower version is ok Qemu2.0 /qemu-kvm1.2+ libvirt1.0.3 and higher version is failed I have checked system as bellows: 1 kvm,kvm_intel modules are loaded(centos 6.2 /kernel 2.6.32) 2 bios is ok for hvm 3 qemu is installed and emulator path in xml config file is correct 4 I also tried to install glusterfs-devel-3.2.7-1.el6.x86_64 and rebuild qemu , no use. so ,why Qemu2.0 /qemu-kvm1.2+ libvirt1.0.3 and above version could not work? thanks, vary much liweiwei

1 0

[libvirt-users] redirecting guest stdio to the host
by Alexander Binun 27 Jul '14

27 Jul '14

Dear Friends, I would ask you a question ; grateful in advance! I have a program running on a VM guest. Its output is valuable (for VM introspection) so I want to let the host module know about it. I prefer to redirect ' stdio" of a guest into a device at the host (a text file or my device that has the name "mydev" and the driver is written for it). I have the XML definition file for my VM in /etc/libvirt/qemu. I have added the section: <serial type="file"> <source path="/var/log/vm/vml.log"/> <target port="0"/> </serial> into the /devices section. That is I want the stdio to be streamed into the file /var/log/vm/vml.log at the host. Then I run simple textual commands at the guest (ls, pwd and so on). But I do not see /var/log/vm/vml.log created at the host. Please help me. Thanks in advance, Alexander Binun > > The command string for qemu will look like qemu -serial /dev/mydev ... But I would like to > modify the libvirt definition XML file (in /etc/libvirt/qemu). Stefan notes in his blog > (http://blog.vmsplice.net/2011/04/how-to-pass-qemu-command-line-options.html) that the options will > look like: ---------- Forwarded message ---------- Date: Wed, 28 May 2014 18:06:10 +0300 From: Eric Blake <eblake(a)redhat.com> To: Alexander Binun <binun(a)cs.bgu.ac.il> Cc: Stefan Hajnoczi <stefanha(a)gmail.com> yagel(a)cs.bgu.ac.il kahilm(a)post.bgu.ac.il qemu-devel(a)nongnu.org boaz.menuhin(a)gmail.com Paolo Bonzini <pbonzini(a)redhat.com> markbl(a)post.bgu.ac.il Subject: Re: excuse me for incorrect question... On 05/28/2014 08:43 AM, Alexander Binun wrote: > Eric, I aplogize for making your work complicated. [You top-posted again] No need to apologize - these lists exist to help people, and we were all new once. > > Should I send questions to libvirt-users(a)redhat.com instead ? I would ask more questions. Yes, if your questions are related to libvirt, then asking on a libvirt list will get you a better audience that may have better answers to your questions. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org On 05/28/2014 08:43 AM, Alexander Binun wrote: > Eric, I aplogize for making your work complicated. [You top-posted again] No need to apologize - these lists exist to help people, and we were all new once. > > Should I send questions to libvirt-users(a)redhat.com instead ? I would ask more questions. Yes, if your questions are related to libvirt, then asking on a libvirt list will get you a better audience that may have better answers to your questions. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org

3 3

[libvirt-users] Problem about Disk Dize of Destination and Source File after Do Blockcopy
by shyu 27 Jul '14

27 Jul '14

Hi There, There is a case I met about the destination file's disk size after do blockcopy Details as below: Env: # rpm -q libvirt qemu-kvm-rhev libvirt-1.1.1-29.el7.x86_64 qemu-kvm-rhev-1.5.3-60.el7ev_0.2.x86_64 1. Check source file # qemu-img info /var/lib/libvirt/images/rhel6.img image: /var/lib/libvirt/images/rhel6.img file format: qcow2 virtual size: 5.0G (5368709120 bytes) disk size: 1.2G cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false # ll -lash /var/lib/libvirt/images/rhel6.img 1.2G -rw-r--r--. 1 qemu qemu 1.2G Jul 22 11:04 /var/lib/libvirt/images/rhel6.img Here: Disk Size is "1.2G" 2. Do blockcopy # virsh domblklist rhel6 Target Source ------------------------------------------------ vda /var/lib/libvirt/images/rhel6.img # time virsh blockcopy rhel6 vda /var/lib/libvirt/images/copy.img --wait --verbose Block Copy: [100 %] Now in mirroring phase real 0m21.285s user 0m0.038s sys 0m0.018s 3. Check destination file's disk size # qemu-img info /var/lib/libvirt/images/copy.img image: /var/lib/libvirt/images/copy.img file format: qcow2 virtual size: 5.0G (5368709120 bytes) disk size: 2.0G cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false # ll -lash /var/lib/libvirt/images/copy.img 2.1G -rw-------. 1 qemu qemu 1.2G Jul 22 11:10 /var/lib/libvirt/images/copy.img Here: Disk Size is "2.0G" So my question is why the "disk size" is different between source file and destination file ? (Actually, the destination always change after I try many times, sometime it is same size as source, sometimes it is lager than source.) 4. Do --pivot After --pivot, the disk size is same size as after blockcopy -- Regards shyu

2 3

[libvirt-users] Migration b/w nodes with identical cpu featureset failing
by Andrey Korolyov 26 Jul '14

26 Jul '14

Hello, on libvirt 1.2.4 and two nodes with E5-2620 and E5-2650, I am not able to migrate vm with cpu=host-passthrough with error: internal error: can't get vmdef the only difference between sender and receiver` cpus is the frequency and identification string. Is this behaviour expected?

1 0

[libvirt-users] vhost-net requested but could not be initialized
by Asadullah Hussain 25 Jul '14

25 Jul '14

I am using a custom qemu to launch a vhost enabled VM. The qemu doesn't use the default "/dev/vhost-net" directory as character device. Due to this I am getting the error: qemu-system-x86_64: -netdev type=tap,id=net1,script=no,downscript=no,ifname=port3,vhost=on: vhost-net requested but could not be initialized Is there a way to tell libvirt to avoid using the default /dev/vhost-net file? I have tried using the pass-through arguments but libvirt still processes the command and throws the error. PS: I can successfully create a vhost VM using qemu command-line, so this is a libvirt issue. -- Cheers, Asadullah Hussain

3 9

[libvirt-users] how to read the libvirt log file
by Yuanzhen Gu 23 Jul '14

23 Jul '14

Hi folks, I need to trace how libvirt talk with qemu monitor, log everything when give command, but does anyone know what the format, and how to read the log file? for example: 2014-07-22 17:25:22.984+0000: 18571: debug : qemuMonitorIOProcess:356 : QEMU_MONITOR_IO_PROCESS: mon=0x7f733c000a40 buf={"timestamp": {"seconds": 1406049922, "microseconds": 983916}, "event": "STOP"} where to find the qemuMonitorIOProcess function, and what :356 means? Thanks very much! Best, Yuanzhen

2 2

Re: [libvirt-users] i686 guest failing to start at 50a2c45 (and earlier versions of 2.1-rc) with pc-i440fx-2.1
by Andrey Korolyov 19 Jul '14

19 Jul '14

On Fri, Jul 18, 2014 at 11:58 PM, Andrey Korolyov <andrey(a)xdel.ru> wrote: > Hello, > > 2.0 model works fine > > 2.1 crashes with following: > > /tmp/buildd/qemu-2.0.92+rev1/hw/i386/smbios.c:825: smbios_get_tables: > Assertion `smbios_smp_sockets >= 1' failed > > Not sure if bisect will help much, but the commit which introduced > this platform works well (3458b2b0). > > arg set follows: > > /usr/bin/kvm -name vm28456 -S -machine pc-i440fx-2.1,accel=kvm,usb=off > -cpu qemu32 -m 256 -realtime mlock=off -smp > 1,sockets=1,cores=12,threads=12 -numa node,nodeid=0,cpus=0,mem=256 > -uuid 46623576-d00b-42b4-b1cc-c5c780a8b5b3 -nographic -no-user-config > -nodefaults -chardev > socket,id=charmonitor,path=/var/lib/libvirt/qemu/vm28456.monitor,server,nowait > -mon chardev=charmonitor,id=monitor,mode=control -rtc > base=utc,clock=vm,driftfix=slew -global > kvm-pit.lost_tick_policy=discard -no-shutdown -boot strict=on -device > piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device > virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive > file=rbd:dev-rack2/vm28456-YoP:id=qemukvm:key=XXXXXX:auth_supported=cephx\;none:mon_host=10.6.0.1\:6789\;10.6.0.3\:6789\;10.6.0.4\:6789,if=none,id=drive-virtio-disk0,format=raw,cache=writeback > -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 > -netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=24 -device > virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:10:03:a8,bus=pci.0,addr=0x3 > -netdev tap,fd=25,id=hostnet1,vhost=on,vhostfd=26 -device > virtio-net-pci,netdev=hostnet1,id=net1,mac=52:54:00:10:03:a9,bus=pci.0,addr=0x4 > -chardev pty,id=charserial0 -device > isa-serial,chardev=charserial0,id=serial0 -chardev > socket,id=charchannel0,path=/var/lib/libvirt/qemu/vm28456.sock,server,nowait > -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.1 Nevermind, that was a result from wrong config generation (1 vcpu and 12 topology cores in the config, probably libvirt folks may be interested for checking this because libvirt allows such configuration for now).

2 1

[libvirt-users] starting lxcs from within a vm using libvirt
by Robb Walker 15 Jul '14

15 Jul '14

my goal for testing/simulations is to be able to run a vm on my desktop and within that vm run linux containers currently I can start an ubuntu trusty vm using libvirt as my broker to qemu or qemu-system-x86_64 directly and start a saucy-based lxc using lxc-tools. I invoke lxc-start -n name -f configfile and within a few seconds I'm logged into my saucy based lxc. I can't start the lxc thru libvirt i.e. virsh -c lxc:/// start domain Again, if I try to use libvirt to "install" and start the lxc from within the vm, no joy. Results below: >>> root@vullbvrt69:~# virt-install --connect lxc:/// -n vulslxc01 -r 512 --filesystem /qemu_lxc/ss_140521/,/ --serial pty --serial pty Starting install... Creating domain... | 0 B 00:00 error: failed to get domain '22542' error: Domain not found: No domain with matching name '22542' Domain creation completed. You can restart your domain by running: root@vullbvrt69:~# virsh -c lxc:/// list --all Id Name State ---------------------------------------------------- - vulslxc01 shut off root@vullbvrt69:~# virsh -c lxc:/// start vulslxc01 Domain vulslxc01 started root@vullbvrt69:~# virsh -c lxc:/// console vulslxc01 --devname serial1 error: The domain is not running root@vullbvrt69:~# virsh -c lxc:/// list --all Id Name State ---------------------------------------------------- - vulslxc01 shut off >>> My physical desktop is running precise 12.04.4 ----qemu-kvm 1.0+noroms-0ubuntu14.15 ----libvirt-bin 0.9.8-2ubuntu17.19 ----lxc 0.7.5-3ubuntu69 This physical machine launches the trusty vm from which in turn I'm trying to run lxcs via libvirt Trusty vm ----libvirt-bin 1.2.2-0ubuntu13.1.1 ----lxc 1.0.4-0ubuntu0.1 The saucy lxc was not created using lxc templates just a normal minbase debootstrap. I have run virt-install with -d. Nothing obvious jumps out except the above Domain not found virsh -c lxc:/// -d4 -l debug.out start domain_name dumps nothing into debug.out thx in advance for any and all help and apolgies in advance if I've dropped critical info to help sort this out This e-mail and any attachments may contain information that is confidential and proprietary and otherwise protected from disclosure. If you are not the intended recipient of this e-mail, do not read, duplicate or redistribute it by any means. Please immediately delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail or any attachments. The DRW Companies make no representations that this e-mail or any attachments are free of computer viruses or other defects.

2 3

Re: [libvirt-users] LVM Volume Creation
by Ravi Samji 15 Jul '14

15 Jul '14

Hi All, I'm having issue with creating LVM Volume via libvirt. We are running libvirtd 1.2 with KVM. We are creating Volume Group (VG01) outside of libvirt and defining a storage pool for it. Here is the StoragePool XML for the Volume Group created outside libvirt. <pool type="logical"> <name>VG01</name> <target> <path>/dev/VG01</path> </target> </pool> We are creating Logical Volume (ub_test01.img) through libvirt in the Volume Group (VG01) Here is the XML to create Storage Volume in LVM Storage Pool VG01. <volume type="block"> <name>ub_test01.img</name> <allocation>0</allocation> <capacity unit="M">1</capacity> <target> <format type="lvm2" /> </target> </volume> When I create the Logical Volume from libvirt using above XML and run lvs command to list logical volumes, this is what I see. LV VG Attr LSize Origin Snap% Move Log Copy% Convert --------------- ------- ------- ------- ----------------------- ------- ------- ------- ------- ------- foo VG01 -wi-a- 1.00g ub_test01.img VG01 swi-a- 4.00m [ub_test01.img_vorigin] 0.20 root ops-02 -wi-ao 227.08g swap_1 ops-02 -wi-ao 5.75g As you see, ub_test01.img shows that it has an Origin indicating that it was created as a snapshot, but, that Origin doesn't exist and wasn't specified. I'd appreciate if you anyone can help me understand what is going on and/or describe how to make libvirt create logical volumes not as a snapshot. I'm happy to enable debugging to see what command libvirt is running to create the volume if someone case describe how to enable debugging. Regards, Ravi Message sent via Atmail Open - http://atmail.org/

2 1

[libvirt-users] LVM Volume Creation
by Ravi Samji 14 Jul '14

14 Jul '14

Hi All, I'm having issue with creating LVM volume via libvirt. XML of LVM StoragePool is: VG01 /dev/VG01 (existing vg) XML of create volume in lvm pool is: ub_test01.img 0 1 When I create the volume with above XML defn, lvs command to list logical volume shows a value in the origin column indicating it was created as snapshot.. the strange thing is that the origin volume does not exist..! something strange going on. You can see the lvs output here See http://pastebin.com/prk6VqwD [1] I'd appreciate if you anyone can help me understand what is going on and/or describe how to make libvirt create logical volumes not as a snapshot. We are running libvirtd 1.2 with KVM. Regards, Ravi ------------------------- Message sent via Atmail Open - http://atmail.org/ Links: ------ [1] http://pastebin.com/prk6VqwD

2 1

[libvirt-users] Changing the default qemu path in libvirt
by satheesh 14 Jul '14

14 Jul '14

Hi All, I would like to change the default qemu path in libvirt xml and the changed path has to be used while installing VMs using virt-install. There was a similar question rasied some years back, I could not find the answer to the same. http://www.redhat.com/archives/libvir-list/2011-December/msg01100.html Is that possible right now?, If we have the support already, please point to the same. Thanks in advance. Regards, -Satheesh.

1 0

[libvirt-users] configuring a lxc guest to run 32bits from a 64bits host under libvirt-lxc
by Thierry Parmentelat 14 Jul '14

14 Jul '14

Hi there I have a couple of newbie questions concerning running a 32bits guest in a 64bits host using libvirt - lxc; I’m running libvirt-1.2.5 on fedora18 and fedora20 (a) is this supported at all, and (b) if so how do I configure this for a given guest ? guessing from the mere existence of http://www.redhat.com/archives/libvir-list/2011-February/msg01040.html I would think the answer to (a) is yes; anybody cares to confirm ? As far as (b), I would expect some flag could be set in the XML description of my guest so that libvirt can perform the proper syscall to personality() at the right point in the process hierarchy.. However I have not been able to spot this in the documentation so far, but OTOH the page on the XML configuration here http://libvirt.org/format.html appears to be empty so this might be a temporary hiccup ? in any case, any hint or insight on this matter would be much appreciated — Thierry

2 4

[libvirt-users] libvirt build issue - make check fails , file name long
by Raj Ravi 11 Jul '14

11 Jul '14

Hi, I was trying to build libvirt-0.10.2-29. Now, it builds fine in simple directory setting: like /home/itsme/test/libvirt/ But, if the directory setting is long: like /home/public/test/abc-v1/liibvrt-v1-v2/ = > it fails. Reason for failure is :qemumonitorjsontest I tried running the specific test case like : VIR_TEST_VERBOSE=1 ./qemumonitorjsontest ======================== 1) GetStatus ... libvir: XML-RPC error : Path /home/public/abc_v1_v2/libvirt_0.10.2_29/BUILD/libvirt-0.10.2/tests/qemumonitorjsontest.sock too long for unix socket: File name too long FAILED 2) GetVersion ... libvir: XML-RPC error : Path /home/public/abc_v1_v2/libvirt_0.10.2_29/BUILD/libvirt-0.10.2/tests/qemumonitorjsontest.sock too long for unix socket: File name too long FAILED 3) GetMachines ... libvir: XML-RPC error : Path /home/public/abc_v1_v2/libvirt_0.10.2_29/BUILD/libvirt-0.10.2/tests/qemumonitorjsontest.sock too long for unix socket: File name too long FAILED 4) GetCPUDefinitions ... libvir: XML-RPC error : Path /home/public/abc_v1_v2/libvirt_0.10.2_29/BUILD/libvirt-0.10.2/tests/qemumonitorjsontest.sock too long for unix socket: File name too long FAILED 5) GetCommands ... libvir: XML-RPC error : Path /home/public/abc_v1_v2/libvirt_0.10.2_29/BUILD/libvirt-0.10.2/tests/qemumonitorjsontest.sock too long for unix socket: File name too long FAILED ======================== Is this a known issue ? Is there any specific patch which addresses this issue ? Please let me know. Thanks, Raj

2 1

Re: [libvirt-users] LibVirt + QEMU & no-shutdown
by Michael D 11 Jul '14

11 Jul '14

Scratch that, seems to depend on guest or perhaps even boot device. Finnix live CD halts correctly. Ubuntu 14.04 does not. On 11 July 2014 15:27, Michael D <me(a)md-5.net> wrote: > I am currently running LibVirt with Qemu on Debian Wheezy: > > Versions: > > - libvirtd (libvirt) 1.2.4 > - qemu-x86_64 version 2.0.0 (Debian 2.0.0+dfsg-4~bpo70+1), Copyright > (c) 2003-2008 Fabrice Bellard > > It's all working perfectly, including ACPI: virsh shutdown guest. However > when I issue "halt" from the guest, the guest stops but libvirt thinks it > is still running: (virsh list outputs state: running). virsh dominfo does > the same thing: State: running > > I believe this is due to the -no-shutdown flag passed to qemu, making it > stop the CPUs rather than halt entirely. Is this however a bug that the > status is not updated correctly? I've taken a glance at the source and it > should SIGTERM qemu when it sees the stop, but evidently it isn't. > > > Thanks > > Michael >

1 0

[libvirt-users] LibVirt + QEMU & no-shutdown
by Michael D 11 Jul '14

11 Jul '14

I am currently running LibVirt with Qemu on Debian Wheezy: Versions: - libvirtd (libvirt) 1.2.4 - qemu-x86_64 version 2.0.0 (Debian 2.0.0+dfsg-4~bpo70+1), Copyright (c) 2003-2008 Fabrice Bellard It's all working perfectly, including ACPI: virsh shutdown guest. However when I issue "halt" from the guest, the guest stops but libvirt thinks it is still running: (virsh list outputs state: running). virsh dominfo does the same thing: State: running I believe this is due to the -no-shutdown flag passed to qemu, making it stop the CPUs rather than halt entirely. Is this however a bug that the status is not updated correctly? I've taken a glance at the source and it should SIGTERM qemu when it sees the stop, but evidently it isn't. Thanks Michael

2 2

[libvirt-users] How to config qga to support dompmsuspend
by Hong-Hua.Yin＠freescale.com 10 Jul '14

10 Jul '14

Hi, I tried to run domsuspend command on my PowerPC board but failed. # virsh dompmsuspend sdk --target mem error: Domain sdk could not be suspended error: argument unsupported: QEMU guest agent is not configured It seemed that support suspend-to-mem only from capabilities. # virsh capabilities <capabilities> <host> <uuid>52498f7c-d584-45d8-8a15-345b14fa0d10</uuid> <cpu> <arch>ppc</arch> <topology sockets='1' cores='2' threads='1'/> <pages unit='KiB' size='4'/> <pages unit='KiB' size='1024'/> <pages unit='KiB' size='4096'/> <pages unit='KiB' size='16384'/> <pages unit='KiB' size='65536'/> <pages unit='KiB' size='262144'/> <pages unit='KiB' size='1048576'/> </cpu> <power_management> <suspend_mem/> </power_management> <migration_features> <live/> <uri_transports> <uri_transport>tcp</uri_transport> </uri_transports> </migration_features> <topology> <cells num='1'> <cell id='0'> <memory unit='KiB'>2066304</memory> <cpus num='2'> <cpu id='0' socket_id='0' core_id='0' siblings='0'/> <cpu id='1' socket_id='0' core_id='1' siblings='1'/> </cpus> </cell> </cells> </topology> <secmodel> <model>none</model> <doi>0</doi> </secmodel> <secmodel> <model>dac</model> <doi>0</doi> <baselabel type='kvm'>+0:+0</baselabel> <baselabel type='qemu'>+0:+0</baselabel> </secmodel> </host> <guest> <os_type>hvm</os_type> <arch name='ppc'> <wordsize>32</wordsize> <emulator>/usr/bin/qemu-system-ppc</emulator> <machine maxCpus='1'>g3beige</machine> <machine maxCpus='32'>ppce500</machine> <machine maxCpus='1'>mac99</machine> <machine maxCpus='15'>mpc8544ds</machine> <machine maxCpus='1'>taihu</machine> <machine maxCpus='1'>ref405ep</machine> <machine maxCpus='1'>bamboo</machine> <machine maxCpus='1'>prep</machine> <machine maxCpus='1'>virtex-ml507</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/qemu-system-ppc</emulator> </domain> </arch> <features> <deviceboot/> <disksnapshot default='on' toggle='no'/> </features> </guest> </capabilities> I read from some document about qemu guest agent but still don't know how to config it as daemon in guest domain. Best Regards, Olivia

3 2

[libvirt-users] snapshot-create error
by Hong-Hua.Yin＠freescale.com 10 Jul '14

10 Jul '14

Hi, What's the difference between QEMU snapshot and libvirt snapshot? # qemu-img create -f qcow2 disk.img 512 Formatting 'disk.img', fmt=qcow2 size=512 encryption=off cluster_size=65536 lazy_refcounts=off # qemu-img info disk.img image: disk.img file format: qcow2 virtual size: 512 (512 bytes) disk size: 136K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false # /usr/bin/qemu-system-ppc -M ppce500 -enable-kvm -m 512 -nographic -kernel /dev/shm/uImage -initrd /dev/shm/ramdisk -append "root=/dev/ram rw console=ttyS0,115200" -serial tcp::4444,server,telnet -snapshot -hda disk.img QEMU 1.7.0 monitor - type 'help' for more information (qemu) QEMU waiting for connection on: telnet:0.0.0.0:4444,server (qemu) savevm (qemu) info snapshot unknown command: 'info snapshot' (qemu) info snapshots ID TAG VM SIZE DATE VM CLOCK 1 vm-20140709035738 173M 2014-07-09 03:57:38 00:00:07.401 Is there any special qemu command options or kernel configurations to allow libvirt create snapshot? I got the error as below: virsh # snapshot-create snap error: unsupported configuration: internal snapshots and checkpoints require all disks to be selected for snapshot The domain XML file is converted as below steps. # cat >snap.args <<EOF /usr/bin/qemu-system-ppc -name snap -M ppce500 -enable-kvm -m 512 -nographic -kernel /dev/shm/uImage -initrd /dev/shm/ramdisk -append "root=/dev/ram rw console=ttyS0,115200" -serial pty # virsh domxml-from-native qemu-argv snap.args >snap.xml # cat sdk.xml <domain type='kvm'> <name>sdk</name> <memory unit='KiB'>524288</memory> <currentMemory unit='KiB'>524288</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='ppc' machine='ppce500'>hvm</type> <kernel>/dev/shm/uImage</kernel> <initrd>/dev/shm/ramdisk</initrd> <cmdline>root=/dev/ram rw console=ttyS0,115200</cmdline> <boot dev='hd'/> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-ppc</emulator> <controller type='usb' index='0'/> <controller type='pci' index='0' model='pci-root'/> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </memballoon> </devices> </domain> Best Regards, Olivia

2 1