- Users - libvirt List Archives

[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