- Users - libvirt List Archives

[libvirt-users] Error facing when starting the VM.
by cool dharma06 21 Nov '13

21 Nov '13

Hi, i am using eucalyptus -2.0.3 and libvirt 1.1.3 for xen -4.2.1. i found this error when starting the Vm via euca2ools(euca-run-instances) the error details are as follows: *libvirt: internal error: client socket is closed (code=1) * *hypervisor failed to start domain* But from virsh i checked everything is working fine. I dont know why the socket is getting closed when accessing from eucalyptus. GIve some suggestions to solve this error. Regards, cooldharma06.

1 0

[libvirt-users] Unable to configure libvirt
by Mahmood Naderan 20 Nov '13

20 Nov '13

Hello, When I want to install libvirt-0.10.0 from source, I get this error at the configure stage checking for libdevmapper.h... no configure: error: You must install device-mapper-devel/libdevmapper >= 1.0.0 to compile libvirt However the package is installed on my system # yum list device-mapper-libs.x86_64 Installed Packages device-mapper-libs.x86_64 1.02.74-10.el6 @base/$releasever What is the problem then? Regards, Mahmood

2 2

[libvirt-users] Failed to access the console after starting the lxc container
by Aarti Sawant 20 Nov '13

20 Nov '13

Hello, I am starting the system container without "/" directory So that it can share the host /bin /sbin /lib and /lib64 and i have sepeartely mounted /var, /etc and /usr directory for the container Below is xml file <domain type='lxc'> <name>test6</name> <memory>102400</memory> <os> <type>exe</type> <init>/sbin/init</init> </os> <vcpu>1</vcpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <console type='pty'/> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/lxc/test6/etc'/> <target dir='/etc'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/lxc/test6/var'/> <target dir='/var'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/lxc/test6/usr'/> <target dir='/usr'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/pg_data/'/> <target dir='/pg_data'/> </filesystem> <filesystem type='ram' accessmode='passthrough'> <source usage='0' units='KiB'/> <target dir='/dev/shm'/> </filesystem> <interface type='bridge'> <source bridge='br0' /> </interface> </devices> </domain> when i start the container it get start , but when i try to access console it get stuck virsh # list Id Name State ---------------------------------------------------- 18238 test4 running 20435 test6 running virsh # virsh # start test6 Domain test6 started virsh # console test6 Connected to domain test6 Escape character is ^] But when i mount the "/" in xml it works, i have also share host /bin,/sbin, /lib and /lib64. <domain type='lxc'> <name>test4</name> <memory>102400</memory> <os> <type>exe</type> <init>/sbin/init</init> </os> <vcpu>1</vcpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <console type='pty'/> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/lxc/test4/'/> <target dir='/'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/bin'/> <target dir='/bin'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/sbin'/> <target dir='/sbin'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/lib'/> <target dir='/lib'/> </filesystem> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/lib64'/> <target dir='/lib64'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/pg_data/'/> <target dir='/pg_data'/> </filesystem> <filesystem type='ram' accessmode='passthrough'> <source usage='0' units='KiB'/> <target dir='/dev/shm'/> </filesystem> <interface type='bridge'> <source bridge='br0' /> </interface> </devices> </domain> as i am new , can anyone explain me why my test6 container get stuck? And in system container if we need to share host filesystem y we need to mount them explicitly? Thanks, Aarti Sawant NTTDATA OSS Center Pune

2 1

[libvirt-users] virsh and multi source-dev
by Matthieu Simonin 20 Nov '13

20 Nov '13

Hi, I'm using LVM based storage pools and I'm wondering if there is a way to specify several source-dev on the command line for creating a volume group spread over several devices : one device /dev/sdc1 is ok: * virsh pool-define-as --name lvmpool --type logical --source-dev /dev/sdc1 --source-name vg --target /dev/vg I would like something like (but sadly doesn't work): ? virsh pool-define-as --name lvmpool --type logical --source-dev /dev/sdc1 --source-dev /dev/sdb1 --source-name vg --target /dev/vg ? Best regards, Matt

3 4

[libvirt-users] libivrt issue report , 1.1.0 version, while migrate VMs between two hosts, is it solved or other way to avoid it, thanks
by Guozhonghua 20 Nov '13

20 Nov '13

Libivrt 1.1.0 Migrate VM between two hosts using shell scripts. The issues is occurred about every 5 minutes, using gdb and the back trace is below: (gdb) c Continuing. [New Thread 0x7f78e7c11700 (LWP 48116)] [New Thread 0x7f78cf7fe700 (LWP 48129)] [New Thread 0x7f78ceffd700 (LWP 48306)] [New Thread 0x7f78ce7fc700 (LWP 62351)] [New Thread 0x7f78cdffb700 (LWP 62694)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f78ed24a700 (LWP 46120)] 0x00007f78ef553579 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x00007f78ef553579 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007f78ef555a45 in malloc () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007f78ef545ae3 in vasprintf () from /lib/x86_64-linux-gnu/libc.so.6 #3 0x00007f78f07a3e54 in virVasprintf (strp=0x7f78ed249b38, fmt=0x7f78f0959c48 "server=%p client=%p message=%p prog=%p", list=0x7f78ed249c00) at util/virstring.c:334 #4 0x00007f78f077d998 in virLogVMessage (source=VIR_LOG_FROM_FILE, priority=VIR_LOG_DEBUG, filename=0x7f78f0959bed "rpc/virnetserver.c", linenr=182, funcname=0x7f78f095a500 "virNetServerHandleJob", metadata=0x0, fmt=0x7f78f0959c48 "server=%p client=%p message=%p prog=%p", vargs=0x7f78ed249c00) at util/virlog.c:836 #5 0x00007f78f077d85d in virLogMessage (source=VIR_LOG_FROM_FILE, priority=VIR_LOG_DEBUG, filename=0x7f78f0959bed "rpc/virnetserver.c", linenr=182, funcname=0x7f78f095a500 "virNetServerHandleJob", metadata=0x0, fmt=0x7f78f0959c48 "server=%p client=%p message=%p prog=%p") at util/virlog.c:773 #6 0x00007f78f08acd86 in virNetServerHandleJob (jobOpaque=0x7f78f305f6a0, opaque=0x7f78f304a360) at rpc/virnetserver.c:181 #7 0x00007f78f07a8a5e in virThreadPoolWorker (opaque=0x7f78f304a0a0) at util/virthreadpool.c:144 #8 0x00007f78f07a842a in virThreadHelper (data=0x7f78f3049ec0) at util/virthreadpthread.c:205 #9 0x00007f78ef897e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x00007f78ef5c54bd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #11 0x0000000000000000 in ?? () (gdb) frame 6 #6 0x00007f78f08acd86 in virNetServerHandleJob (jobOpaque=0x7f78f305f6a0, opaque=0x7f78f304a360) at rpc/virnetserver.c:181 181 rpc/virnetserver.c: No such file or directory. (gdb) p job $1 = (virNetServerJobPtr) 0x7f78f305f6a0 (gdb) p srv $2 = (virNetServerPtr) 0x7f78f304a360 (gdb) p job->client $3 = (virNetServerClientPtr) 0x7f78f3054a60 (gdb) p job->msg $4 = (virNetMessagePtr) 0x7f78f3051480 (gdb) p job->prog $5 = (virNetServerProgramPtr) 0x7f78f3054c60 (gdb) $6 = (virNetServerProgramPtr) 0x7f78f3054c60 (gdb) frame 5 #5 0x00007f78f077d85d in virLogMessage (source=VIR_LOG_FROM_FILE, priority=VIR_LOG_DEBUG, filename=0x7f78f0959bed "rpc/virnetserver.c", linenr=182, funcname=0x7f78f095a500 "virNetServerHandleJob", metadata=0x0, fmt=0x7f78f0959c48 "server=%p client=%p message=%p prog=%p") at util/virlog.c:773 773 util/virlog.c: No such file or directory. (gdb) frame 3 #3 0x00007f78f07a3e54 in virVasprintf (strp=0x7f78ed249b38, fmt=0x7f78f0959c48 "server=%p client=%p message=%p prog=%p", list=0x7f78ed249c00) at util/virstring.c:334 334 util/virstring.c: No such file or directory. (gdb) p strp $7 = (char **) 0x7f78ed249b38 (gdb) p *strp $8 = 0x0 (gdb) p list $9 = (struct __va_list_tag *) 0x7f78ed249c00 (gdb) p *list $10 = {gp_offset = 48, fp_offset = 48, overflow_arg_area = 0x7f78ed249ce8, reg_save_area = 0x7f78ed249c20} ------------------------------------------------------------------------------------------------------------------------------------- ???????????????????????????????????????? ???????????????????????????????????????? ???????????????????????????????????????? ??? This e-mail and its attachments contain confidential information from H3C, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

2 2

[libvirt-users] Using hostdev to plug a PCI-E host device into Q35 pcie-root port
by Thomas Kuther 19 Nov '13

19 Nov '13

Hello, I'm trying to migrate a working qemu command line configuration to libvirt. The part I'm currently failing on is: $ qemu-system-x86_64 -M Q35 ... -device vfio-pci,host=05:00.0,bus=pcie.0 The right way to translate this into libvirt XML seems to be using <hostdev>, but I seem to be unable to plug it into the pcie-root port This is how the interesting part looks like when I let "virsh edit" generate an <address> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> [...] <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/> </hostdev> [...] To my understanding, this will plug the host device into the pci-bridge controller. The guest OS doesn't boot with this and resets right after bios. Manually setting <address type='pci' domain='0x0000' bus='0x00' slot='0x1E' function='0x0'/> cause XML validation failure. Is there any way in libvirt XML to plug a host's PCI-E device directly into the pcie-root port, like it works on qemu command line? I'm aware I could use something like <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=05:00.0,bus=pcie.0'/> </qemu:commandline> but I insist on running the VM as non-root, and if I got that right I need to configure at least one vfio device (or memory locking) in order for libvirt to set a proper RLIMIT_MEMLOCK value. Any help would be be appreciated. Regards, Thomas

2 3

Re: [libvirt-users] Unable to use more than 4 serial devices at once.
by Cole Robinson 19 Nov '13

19 Nov '13

On 11/17/2013 09:18 PM, Matthew Harrold wrote: > On Sun, Nov 17, 2013 at 7:44 PM, Cole Robinson <crobinso(a)redhat.com > <mailto:crobinso@redhat.com>> wrote: > On 11/17/2013 01:26 PM, Matthew Harrold wrote: > > Hi All. > > > > I'm trying to setup a guest within my hypervisor that acts as a Console > > Server, using 10 USB to Serial adapters. The Host is all setup and can > access > > each Serial Port without problems. > > > > I have attempted to add the Serial Connections to a Guest, using both > Virtual > > Machine Manager and by editing the .XML file, and I can add up to 4 Serial > > devices (Including one for console access to the guest) without any > issues at > > all. However when I try to add a fifth , the virtual machine refuses to > start > > > > > > Distro: Ubuntu 13.04 > > Kernel: 3.8.0-33-generic > > libvirtd: 1.0.2 > > QEMU:1.4.0 (Debian 1.4.0+dfsg-1expubuntu4) > > > > The log- > > > > _4 Serial Devices_ > > > > 2013-11-17 17:37:45.901+0000: starting up > > LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin > > QEMU_AUDIO_DRV=none /usr/bin/kvm -name Ubuntu12.04-Cisco -S -M pc-1.0 -m > 1024 > > -smp 2,sockets=2,cores=1,threads=1 -uuid > 1837c56f-6f84-2abe-8bdd-d7c974803b84 > > -no-user-config -nodefaults -chardev > > > socket,id=charmonitor,path=/var/lib/libvirt/qemu/Ubuntu12.04-Cisco.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=/mnt/DiskRepo/Ubuntu12.04-TFTP.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 > > -device > > > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 > > -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device > > ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev > > tap,fd=31,id=hostnet0,vhost=on,vhostfd=32 -device > > > virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e6:9c:c0,bus=pci.0,addr=0x3 > -chardev > > pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 > -chardev > > tty,id=charserial1,path=/dev/c1841-A -device > > isa-serial,chardev=charserial1,id=serial1 -chardev > > tty,id=charserial2,path=/dev/c2620-A -device > > isa-serial,chardev=charserial2,id=serial2 -chardev > > tty,id=charserial3,path=/dev/c2620-B -device > > isa-serial,chardev=charserial3,id=serial3 -vnc 0.0.0.0:0 > <http://0.0.0.0:0> <http://0.0.0.0:0> > > -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 > > W: kvm binary is deprecated, please use qemu-system-x86_64 instead > > char device redirected to /dev/pts/0 (label charserial0) > > > > > > _5 Serial Devices_ > > > > 2013-11-17 18:05:59.925+0000: starting up > > LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin > > QEMU_AUDIO_DRV=none /usr/bin/kvm -name Ubuntu12.04-Cisco -S -M pc-1.0 -m > 1024 > > -smp 2,sockets=2,cores=1,threads=1 -uuid > 1837c56f-6f84-2abe-8bdd-d7c974803b84 > > -no-user-config -nodefaults -chardev > > > socket,id=charmonitor,path=/var/lib/libvirt/qemu/Ubuntu12.04-Cisco.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=/mnt/DiskRepo/Ubuntu12.04-TFTP.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 > > -device > > > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 > > -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device > > ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev > > tap,fd=31,id=hostnet0,vhost=on,vhostfd=32 -device > > > virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e6:9c:c0,bus=pci.0,addr=0x3 > -chardev > > pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 > -chardev > > tty,id=charserial1,path=/dev/c1841-A -device > > isa-serial,chardev=charserial1,id=serial1 -chardev > > tty,id=charserial2,path=/dev/c2620-A -device > > isa-serial,chardev=charserial2,id=serial2 -chardev > > tty,id=charserial3,path=/dev/c2620-B -device > > isa-serial,chardev=charserial3,id=serial3 -chardev > > tty,id=charserial4,path=/dev/c2950-A -device > > isa-serial,chardev=charserial4,id=serial4 -vnc 0.0.0.0:0 > <http://0.0.0.0:0> <http://0.0.0.0:0> > > -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 > > W: kvm binary is deprecated, please use qemu-system-x86_64 instead > > char device redirected to /dev/pts/0 (label charserial0) > > qemu-system-x86_64: -device isa-serial,chardev=charserial4,id=serial4: > Device > > 'isa-serial' could not be initialized > > 2013-11-17 18:06:00.314+0000: shutting down > > > > Does anyone have any idea what's causing this? I have attempted using > > different Serial to USB adapters to rule out a hardware / configuration > issue > > on one of the adapters, but it makes no difference. If I try to start more > > than 4 Serial Devices, it refuses to start up. > > > Pretty sure that's just a qemu or PC limit for isa-serial. The alternative is > to use virtio serial which can handle many more ports. > - Cole > > > That sounds likely. Is there any documentation covering 'binding' a host > serial port to a virtio serial device? I've search but not found anything > relevant. > Hmm, that's a good question. Actually it doesn't look like there is any way to have <serial> use virtio. You can use channel to get something close, like: <channel type='pty'> <target type='virtio' name='my.port.2'/> </channel> However it won't appear as ttyS0 in the guest so it might not fit your usecase. Recent qemu has a PCI serial device which should allow for more than 4 serial ports, but support isn't wired up in libvirt yet. - Cole

1 0

[libvirt-users] Asterisk, pci passthrough, and pri card
by Mauricio Tavares 19 Nov '13

19 Nov '13

Has anyone been successfully running asterisk in libvirt with a pri card? I thought we had it working but we seem to be experiencing long (1h+) calls being dropped.

2 1

[libvirt-users] macvtap direct and ip spoofing
by vlad halilov 19 Nov '13

19 Nov '13

Hi there. I have configured kvm domain (rhel6.4) with ethernet bridged over macvtap, and found no filtration applied except mac. 'virsh' just silently ignoring attributes 'filterref' and 'ip address' in different formats. No error on validate stage. Config examples: ... <interface type='direct'> <mac address='52:54:00:31:ae:1a'/> <source dev='em1' mode='private'/> <filterref filter='clean-traffic'> <parameter name='IP' value='10.1.101.44'/> </filterref> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> ... or like these: ... <interface type='direct'> <mac address='52:54:00:31:ae:1a'/> <source dev='em1' mode='private'/> <ip address='10.1.101.44'/> <filterref filter='clean-traffic'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> ... With 'virsh create domain.xml', vm created, but dumpxml show that filterref is disappeared. I have not found any success stories with filtering rules and 'direct' interface types. Is it supported with this type? Or may be other tricks to protect network from vm spoofing and direct type? - vlad f halilov

2 2

[libvirt-users] Hot resize virtio-scsi device with multipath device backend
by Baptiste AGASSE 18 Nov '13

18 Nov '13

Hi all, I'm currently testing virtio-scsi on EL6.4. I've seen that we can resize scsi disk without restarting the guest for qcow files backend for example (this point is well documented). I want to know if it's possible to "hot resize" a multipath device attached to a guest via virtio-scsi. I use multipath device hosted to a SAN array to store data used on virtual guests. I've attached this device with virtio-scsi device to a guest. Now i want to resize this device without restarting my guest. I've resized the disk on my SAN array, refreshed iscsi connections and multipathed device to reflect the new size, but how to say to my guest that device have been resized ? I've tried "echo 1 > /sys/class/scsi_disk/2\:0\:0\:2/device/rescan" in my guest but it didn't works. I think i'm missing a step (libvirt notify the guest that the device have changed ?) and i don't find any documentation about resizing direct attached physical device via virtio-scsi. Is it possible to do this ? kernel.x86_64 2.6.32-358.14.1.el6 libvirt.x86_64 0.10.2-18.el6_4.14 qemu-kvm.x86_64 2:0.12.1.2-2.355.0.1.el6_4.9 Have a nice day. Regards. Bapiste.

1 0

[libvirt-users] Unable to use more than 4 serial devices at once.
by Matthew Harrold 17 Nov '13

17 Nov '13

Hi All. I'm trying to setup a guest within my hypervisor that acts as a Console Server, using 10 USB to Serial adapters. The Host is all setup and can access each Serial Port without problems. I have attempted to add the Serial Connections to a Guest, using both Virtual Machine Manager and by editing the .XML file, and I can add up to 4 Serial devices (Including one for console access to the guest) without any issues at all. However when I try to add a fifth , the virtual machine refuses to start *The Host-* Distro: Ubuntu 13.04 Kernel: 3.8.0-33-generic libvirtd: 1.0.2 QEMU:1.4.0 (Debian 1.4.0+dfsg-1expubuntu4) The log- *4 Serial Devices* 2013-11-17 17:37:45.901+0000: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name Ubuntu12.04-Cisco -S -M pc-1.0 -m 1024 -smp 2,sockets=2,cores=1,threads=1 -uuid 1837c56f-6f84-2abe-8bdd-d7c974803b84 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Ubuntu12.04-Cisco.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=/mnt/DiskRepo/Ubuntu12.04-TFTP.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=31,id=hostnet0,vhost=on,vhostfd=32 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e6:9c:c0,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev tty,id=charserial1,path=/dev/c1841-A -device isa-serial,chardev=charserial1,id=serial1 -chardev tty,id=charserial2,path=/dev/c2620-A -device isa-serial,chardev=charserial2,id=serial2 -chardev tty,id=charserial3,path=/dev/c2620-B -device isa-serial,chardev=charserial3,id=serial3 -vnc 0.0.0.0:0 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 W: kvm binary is deprecated, please use qemu-system-x86_64 instead char device redirected to /dev/pts/0 (label charserial0) *5 Serial Devices* 2013-11-17 18:05:59.925+0000: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name Ubuntu12.04-Cisco -S -M pc-1.0 -m 1024 -smp 2,sockets=2,cores=1,threads=1 -uuid 1837c56f-6f84-2abe-8bdd-d7c974803b84 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Ubuntu12.04-Cisco.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=/mnt/DiskRepo/Ubuntu12.04-TFTP.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=31,id=hostnet0,vhost=on,vhostfd=32 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e6:9c:c0,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev tty,id=charserial1,path=/dev/c1841-A -device isa-serial,chardev=charserial1,id=serial1 -chardev tty,id=charserial2,path=/dev/c2620-A -device isa-serial,chardev=charserial2,id=serial2 -chardev tty,id=charserial3,path=/dev/c2620-B -device isa-serial,chardev=charserial3,id=serial3 -chardev tty,id=charserial4,path=/dev/c2950-A -device isa-serial,chardev=charserial4,id=serial4 -vnc 0.0.0.0:0 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 W: kvm binary is deprecated, please use qemu-system-x86_64 instead char device redirected to /dev/pts/0 (label charserial0) qemu-system-x86_64: -device isa-serial,chardev=charserial4,id=serial4: Device 'isa-serial' could not be initialized 2013-11-17 18:06:00.314+0000: shutting down Does anyone have any idea what's causing this? I have attempted using different Serial to USB adapters to rule out a hardware / configuration issue on one of the adapters, but it makes no difference. If I try to start more than 4 Serial Devices, it refuses to start up. Thanks for your time, Matthew

2 1

[libvirt-users] /var/lib/libvirt/images on BTRFS (it works!)
by Gene Czarcinski 17 Nov '13

17 Nov '13

Some of you may be interested in running your qemu-kvm (or other) disk image files on BTRFS. After some fumbling around, I have found out how to do it so it works and works very well (especially if it is on an SSD). Anyone investigating running on BTRFS immediately finds out that there is a fragmentation problem (just putting image files on btrfs can result in them having between 50,000 and 100,000 extents). Some may have seen that adding nodatacow to the mount option is a solution ... it is not. So what is the solution? 1. execute: chattr +C /var/lib/libvirt/images or wherever your image files are. This needs to be done on the directory whether you have a separate subvol or not. 2. This ONLY works for new files and ONLY works for "raw" storage format files. Pretty much by definition, qcow2 files are sparse format files and that is the primary problem on btrfs. So that the vm creation wizard will create a new disk using the raw storage format, you need to select: Edit->Preferences->VM Details->Default Storage Format->Raw After then, an created virtual will have the correct disk format. You can use "filefrag" to verify that things are working. Gene

1 0

[libvirt-users] How to tell libvirt not to use qemu "accel=kvm" for a FreeBSD guest
by Christian Gagneraud 14 Nov '13

14 Nov '13

Hi there, I have used qemu to install FreeBSD 9.2 release, and i can boot it fine with: $ qemu-system-x86_64 -hda images/FreeBSD-9.2-RELEASE-amd64.img I then made virsh aware of my brand new VM (see attached XML), but when i run it via virsh, It hangs after the bootloader whith this message: Booting... CPU doesn't support long mode From the log, here is the generated qemu command: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin /usr/bin/qemu-system-x86_64 -name fbsd92-amd64 -S -machine pc-i440fx-1.5,accel=kvm,usb=off -m 512 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 11ae165e-b8a2-5083-fb77-37c0042725bf -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/fbsd92-amd64.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=/home/christiaga/projects/vms/images/FreeBSD-9.2-RELEASE-amd64.img,if=none,id=drive-ide0-0-0,format=raw -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:9c:94:3b,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 After many attempts, I pinned down the problem. To be able to boot the machine with the above command, I had to remove: * the accel=kvm in -machine * the -S (to "autostart" the VM) And change the -net tap,fd=24 to -net user,id=... So basically, the only thing i would like to tell libvirt is not to use accel=kvm, i guess the FreeBSD kernel is missing some feature (is it this PAE thing?) Does anyone how can i tell libvirt to do that? regards, Chris

3 5

[libvirt-users] Problem about lxc-enter-namespace interface
by hzguanqiang＠corp.netease.com 14 Nov '13

14 Nov '13

Hi experts, When I test lxc-enter-namespace interface, it turned out such an error: hzguanqiang@debian:~$ vir version Compiled against library: libvirt 1.1.4 Using library: libvirt 1.1.4 Using API: LXC 1.1.4 Running hypervisor: LXC 3.9.6 hzguanqiang@debian:~$ vir list Id Name State ---------------------------------------------------- 1544 instance-00000015 running hzguanqiang@debian:~$ vir lxc-enter-namespace 1544 --noseclabel /bin/df -hl error: Cannot get namespaces for 1545: Function not implemented hzguanqiang@debian:~$ ls /proc/self/ns ipc mnt net pid user uts What's the problem? ------------------ Best regards! GuanQiang 2013-11-14

2 10

[libvirt-users] UTS namespace
by Aarti Sawant 14 Nov '13

14 Nov '13

Hello, I am trying to set up UTS name space on centos 6.4 LXC container. one method is that we set the host name in /etc/sysconfig/network. hostname=test1 Is there any way so that i can set the hostname in libvirt xml while creating a container? I know using lxc-tools we can set hostname while creating by 2 ways - first while creating container using lxc-create -u test1 - Second by specifying lxc.utsname=test1 in config file Thanks Aarti Sawant NTTDATA OSS Center Pune

2 1

[libvirt-users] User Namespace in LXC
by Saurabh Deochake 14 Nov '13

14 Nov '13

Hi all, I'm trying to restrict privileges of root user inside the container. I searched about it and got to know about "idmap" element in domain XML. I added "idmap" element in my container's XML file: <idmap> <uid start='0' target='1000' count='10'/> <gid start='0' target='1000' count='10'/> </idmap> I restarted the container with updated XML file. When I execute "id" command to know if root user inside the container has been mapped with an user from host, i still get output uid as 0 # id -u root 0 Am I doing the steps right to check the user namespacing? Please help me out with this. Thanks in advance, Saurabh Deochake. NTT DATA OSS Center, Pune, India

2 6

[libvirt-users] Doc/web site problems
by Greg Ward 13 Nov '13

13 Nov '13

Hi all -- I have one meta-question, and two real questions. 1) What's the best place to report bugs in the docs, FAQ, web site, or wiki? I have found two -- see next points. (I'm happy to make the fixes myself if I can, but I'm pretty ignorant about libvirt. Can't fix the docs without knowing the truth.) 2) In the FAQ, under "networking is unavailable in virt-manager / virsh - libvirt's default network fails to start", it says "Here is a list of the networking-related packages that need to be installed for libvirt networking to work properly:". But it does not say if those packages are supposed to be installed on the host or the guest! It might be obvious to you, but it isn't to me. 3) In http://wiki.libvirt.org/page/Networking#Guest_configuration, it says "the following XML would be used in the guest:" ... but it doesn't say WHERE to put that configuration! Is it a snippet to add to an existing file? A new file I have to create? Something else? Very frustrating! ;-( Thanks -- Greg

2 4

[libvirt-users] Migration function is not supported by the connection driver: virDomainMigrate2
by Joseph Perrin 13 Nov '13

13 Nov '13

Greetings; I'm running Fedora 19, Xen 4.2.3, libvirt 1.0.5.6. I have two identical servers x1 & x2. I've read http://libvirt.org/migration.html & I've created certificates for tls according to http://wiki.libvirt.org/page/TLSSetup I can do this on both servers, and from a third admin server: # virsh -c xen+tls://x1.localdomain hostname x1.localdomain and... # virsh -c xen+tls://x2.localdomain hostname x2.localdomain It appears I can connect without issues. No matter what I try, I cannot get migration to work :-( x 1000! I've created a test DomU named "z19", which uses a DRBD block device between the two hosts. It's running on x1, (and obviously not on x2), and I want to migrate it to x2. When I attempt to migrate I get the following. (Although, I've tried every permutation of syntax I've read about. The following appears to be most reasonable for my situation?) # virsh migrate --live z19 xen+tls://x2.localdomain error: this function is not supported by the connection driver: virDomainMigrate2 # virsh -c xen+tls://x1.localdomain migrate z19 xen+tls://x2.localdomain error: this function is not supported by the connection driver: virDomainMigrate2 # virsh migrate --live z19 xen+ssh://root@x2.localdomain error: this function is not supported by the connection driver: virDomainMigrate2 I've set libvirtd.conf: log_level=1 Which reports nothing. There is a great amount of conflicting information on this topic. It's difficult to ascertain which to listen to. Any suggestions you could give me would be greatly appreciated. -Joseph

2 1

[libvirt-users] Lots of threads and increased IO load
by Gergely Horváth 13 Nov '13

13 Nov '13

Hello guys, We have a lot of small computers on top of two servers running QEMU/KVM virtualisation with libvirt. In this case, most of the VMs are not doing much work, some of them barely touches any "hardware" resources. I have two problems, they might be connected. When I do a bigger IO job on one of the VMs (like downloading files to local disk) all other VMs' IO load increases. Even our LDAP server's IO load is triggering an alert in our monitoring system - though that server barely does any IO throughout the day. The big IO job can NOT be considered big in the terms of the host computers IO capabilities, as it has two really fast SSD drives in hardware RAID 0 configuration. It can easily do hundreds of megabytes per second random write. The file copy I was running barely touched 50 MB/s. So this should not be a problem for the host's disks and I also do not understand why other computers IO load is increased. The second problem came when I looked at `iotop`, to see how much IO read and write is going on. The computer, that was doing the copying easily had like 20-30 threads writing pieces to the disk. Some of the threads are obviously "processor emulators" - they been running since the birth of the VM, but what are these other threads? TL;DR; Two questions than, to sum up everything: * How can I control and maybe decrease the number of threads spawned for a virtual machine? * How can I know what is the default IO caching for a VM, and what caching mechanism/policy should I set to minimise IO latency (i.e. I do not really care if the data is written to the disk later than the guest thinks) Thank you. P.S: We have been running hypertable servers the whole time, and even those did not generate such mess with IO... -- Üdvözlettel / Best regards Horváth Gergely | gergely.horvath(a)inepex.com IneTrack - Nyomkövetés egyszerűen | Inepex Kft. Ügyfélszolgálat: support(a)inetrack.hu | +36 30 825 7646 | support.inetrack.hu Web: www.inetrack.hu | nyomkovetes-blog.hu | facebook.com/inetrack Inepex - The White Label GPS fleet-tracking platform | www.inepex.com

2 3

[libvirt-users] Problem with bridged network configuration
by Bob Doolittle 13 Nov '13

13 Nov '13

Hi, When I initially boot my system, it fails to bring up the network. Once booted, if I run "systemctl restart network.service", or even stop, wait a while, then start, it starts up fine and all is well. I'm running Fedora 19 (updated). I followed the instructions on this page to set up a bridged network: http://wiki.libvirt.org/page/Networking I note however that I did *not* have any bridge (for NAT use) configured initially by default on my system, and followed the directions on this page to create it: https://fedoraproject.org/wiki/Getting_started_with_virtualization I have disabled the NetworkManager service, and created network initscripts for my em1 and br0 interfaces. I notice from the systemctl status output, that the network failure is logged, and only *after* that the br0 interface comes up. So I wonder if there is some ordering problem in spite of the fact that I have specified DELAY=0 for br0. I have included output from the following commands: systemctl status network.service (initially, when failed to come up) brctl show ip link ip address Also attached are the network initscripts for my em1 and br0 interfaces. Any guidance would be much appreciated! Thanks, Bob

3 3

[libvirt-users] Turning off polling
by Timothy Ehlers 12 Nov '13

12 Nov '13

Is it possible to turn off polling, we have 50~60 kvm instances per machine and have found that when libvirtd is running each KVM pid has 20% additional cpu usage. I turned on debug logging for 10 minutes and it seems to be 99% of this: virEventPollDispatchHandle But i cannot find a way to disable it. -- Tim Ehlers

2 1

[libvirt-users] InfiniBand Passthrough not working
by Michael Kruse 12 Nov '13

12 Nov '13

1 0

[libvirt-users] newer libvirt version issues
by Franky Van Liedekerke 12 Nov '13

12 Nov '13

Hi, since we're running more than 20 hosts per KVM server, we needed to update libvirt to at least 1.1.2 for virtlockd to be able to cope with this (due to an old hardcoded limit that was in there before). But where 1.1.0 compiles and runs just fine on a fully-patched CentOS 6.4 server, newer version have all kinds of issues: Every version of libvirt >= 1.1.2 crashes with a segfault on up-to-date CentOS 6.4 servers (see below). Also, versions of libvirt >= 1.1.3 need a change in the spec file to be able to compile: apparently the %doc entries that are different with 1.1.2 prevent rpmbuild to succeed on CentOS servers. Using the %doc lines as per the 1.1.2 spec file results in a working rpmbuild. The 1.1.4 version has issues with a symbol not found after compiling and letting it run: error : virDriverLoadModule:78 : failed to load module /usr/lib64/libvirt/connection-driver/libvirt_driver_network.so /usr/lib64/libvirt/connection-driver/libvirt_driver_network.so: undefined symbol: virNetworkList error : virDriverLoadModule:78 : failed to load module /usr/lib64/libvirt/connection-driver/libvirt_driver_storage.so /usr/lib64/libvirt/connection-driver/libvirt_driver_storage.so: undefined symbol: virAsprintf error : virDriverLoadModule:78 : failed to load module /usr/lib64/libvirt/connection-driver/libvirt_driver_nodedev.so /usr/lib64/libvirt/connection-driver/libvirt_driver_nodedev.so: undefined symbol: virNodeDeviceList 31677: error : virDriverLoadModule:78 : failed to load module /usr/lib64/libvirt/connection-driver/libvirt_driver_secret.so /usr/lib64/libvirt/connection-driver/libvirt_driver_secret.so: undefined symbol: virAsprintf 31677: error : virDriverLoadModule:78 : failed to load module /usr/lib64/libvirt/connection-driver/libvirt_driver_nwfilter.so /usr/lib64/libvirt/connection-driver/libvirt_driver_nwfilter.so: undefined symbol: virAsprintf 31677: error : virDriverLoadModule:78 : failed to load module /usr/lib64/libvirt/connection-driver/libvirt_driver_interface.so /usr/lib64/libvirt/connection-driver/libvirt_driver_interface.so: undefined symbol: virAsprintf 31677: error : virDriverLoadModule:78 : failed to load module /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so: undefined symbol: networkAllocateActualDevice 31677: error : virDriverLoadModule:78 : failed to load module /usr/lib64/libvirt/connection-driver/libvirt_driver_lxc.so /usr/lib64/libvirt/connection-driver/libvirt_driver_lxc.so: undefined symbol: networkAllocateActualDevice And every time libvirt segfaults, there's this in the logs: debug : virJSONValueToString:1133 : result={"id":"libvirt-6","error":{"class":"CommandNotFound","desc":"The command qom-list has not been found","data":{"name":"qom-list"}}} debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=32 timeout=1684 9479: debug : qemuMonitorJSONCheckError:341 : unable to execute QEMU command {"execute":"qom-list","arguments":{"path":"/"},"id":"libvirt-6"}: {"id":"libvirt-6","error":{"class":"CommandNotFound","desc":"The command qom-list has not been found","data":{"name":"qom-list"}}} 9479: error : qemuMonitorJSONCheckError:352 : internal error: unable to execute QEMU command 'qom-list': The command qom-list has not been found Any insights on any of these issues? Franky

1 0

[libvirt-users] Unable to shutdown/reboot a SLES 10 SP4 VM
by Padma Narwankar 11 Nov '13

11 Nov '13

Hello, I am unable to do a graceful shutdown or reboot of SLES 10 SP4 virtual machines (Kernel version: 2.6.16.60-0.85.1-default) with virsh shutdown or virsh reboot commands. (e.g virsh shutdown "vmname" ). On issuing these commands there is no impact on the VM. Also unable to perform the shutdown or reboot operations from the menu options available on the console when accessing the VM via the virt-manager. The virsh shutdown/reboot commands and the shutdown/reboot menu operations work fine for SLES 11 SP2 VMs. I've verified that the acpi daemon is running with the SLES 10 SP4 VM linux-kb8x:~ # ps aux | grep acpi root 8 0.0 0.0 0 0 ? S< 16:27 0:00 [kacpid] root 9 0.0 0.0 0 0 ? S< 16:27 0:00 [kacpi_notify] root 1830 0.0 0.0 2688 528 ? Ss 16:27 0:00 /sbin/acpid Is there any other process that needs to running for these operations to work or is there a known issue with SLES 10 SP4? Thanks, Padmaja

2 1

[libvirt-users] Error in snapshot create in libvirt 1.1.4
by Georg Meier 11 Nov '13

11 Nov '13

Hi list, i currently have the following issue: I did a test upgrade to libvirt 1.1.4 and now i cannot create new snapshots which can be reverted. Following Situation: Virtualization: kvm Disktype: qcow2 qemu XML: <cpu mode='host-passthrough'> </cpu> Creating of snapshot: virsh snapshot-create-as <guest> <name> <description> --atomic Now i craete a snapshot and as soon as i revert i get the following error: error : virCPUDefParseXML:367 : XML error: Non-empty feature list specified without CPU model I think the error is inside the snapshot xml (virsh snapshot-dumpxml): <cpu mode='host-passthrough'> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='osxsave'/> <feature policy='require' name='dca'/> <feature policy='require' name='pcid'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='xtpr'/> <feature policy='require' name='tm2'/> <feature policy='require' name='est'/> <feature policy='require' name='smx'/> <feature policy='require' name='vmx'/> <feature policy='require' name='ds_cpl'/> <feature policy='require' name='monitor'/> <feature policy='require' name='dtes64'/> <feature policy='require' name='pbe'/> <feature policy='require' name='tm'/> <feature policy='require' name='ht'/> <feature policy='require' name='ss'/> <feature policy='require' name='acpi'/> <feature policy='require' name='ds'/> <feature policy='require' name='vme'/> </cpu> In older libvirt versions < 1.0.0 the xml looks the following way (virsh snapshot-dumpxml): <cpu mode='host-passthrough' match='minimum'> <model>SandyBridge</model> <vendor>Intel</vendor> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='osxsave'/> <feature policy='require' name='dca'/> <feature policy='require' name='pcid'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='xtpr'/> <feature policy='require' name='tm2'/> <feature policy='require' name='est'/> <feature policy='require' name='smx'/> <feature policy='require' name='vmx'/> <feature policy='require' name='ds_cpl'/> <feature policy='require' name='monitor'/> <feature policy='require' name='dtes64'/> <feature policy='require' name='pbe'/> <feature policy='require' name='tm'/> <feature policy='require' name='ht'/> <feature policy='require' name='ss'/> <feature policy='require' name='acpi'/> <feature policy='require' name='ds'/> <feature policy='require' name='vme'/> </cpu> So for what ever reason the model and vendor tag are not copied inside the snapshot metadata xml when using cpu mode cpu-passthrough. virsh dumpxml with --update-cpu flag reports the correct cpu node with model and vendor tags. After a stop of libvirtd and loooking inside the xml file the cpu tag looks the following: <cpu mode='host-passthrough' match='minimum'> <model>SandyBridge</model> <vendor>Intel</vendor> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='osxsave'/> <feature policy='require' name='dca'/> <feature policy='require' name='pcid'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='xtpr'/> <feature policy='require' name='tm2'/> <feature policy='require' name='est'/> <feature policy='require' name='smx'/> <feature policy='require' name='vmx'/> <feature policy='require' name='ds_cpl'/> <feature policy='require' name='monitor'/> <feature policy='require' name='dtes64'/> <feature policy='require' name='pbe'/> <feature policy='require' name='tm'/> <feature policy='require' name='ht'/> <feature policy='require' name='ss'/> <feature policy='require' name='acpi'/> <feature policy='require' name='ds'/> <feature policy='require' name='vme'/> </cpu> After the start of libvirtd virsh reports the cpu tag with missing vendor and model. Does anybody else has this problem? Best regards Georg

1 0