- Users - libvirt List Archives

[libvirt-users] systemctl libvirt-guests.service fails to start during host boot
by Benoit 26 Sep '16

26 Sep '16

Hi, I have been using qemu and kvm for a while but I am newbie to libvirt. (but I really like it :) I am on Parabola (fork of Archlinux, using systemd) I only got an issue regarding libvirt-guests service, when my host boots about 7 times to 10 I got a issue on the service. ------------------------------------------------------------------------ systemctl status libvirt-guests.service ● libvirt-guests.service - Suspend Active Libvirt Guests Loaded: loaded (/usr/lib/systemd/system/libvirt-guests.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2016-08-11 10:55:35 CEST; 36s ago Docs: man:libvirtd(8) http://libvirt.org Process: 347 ExecStart=/usr/lib/libvirt/libvirt-guests.sh start (code=exited, status=1/FAILURE) Main PID: 347 (code=exited, status=1/FAILURE) Aug 11 10:55:35 oms_apex_plaisir systemd[1]: Starting Suspend Active Libvirt Guests... Aug 11 10:55:35 oms_apex_plaisir libvirt-guests.sh[347]: Resuming guests on default URI... Aug 11 10:55:35 oms_apex_plaisir libvirt-guests.sh[347]: Resuming guest : error: failed to connect to the hypervisor Aug 11 10:55:35 oms_apex_plaisir libvirt-guests.sh[347]: error: no valid connection Aug 11 10:55:35 oms_apex_plaisir libvirt-guests.sh[347]: error: Failed to connect socket to '/var/run/libvirt/libvirt-sock' no such file Aug 11 10:55:35 oms_apex_plaisir systemd[1]: libvirt-guests.service: Main process exited, code=exited, status=1/FAILURE Aug 11 10:55:35 oms_apex_plaisir systemd[1]: Failed to start Suspend Active Libvirt Guests. Aug 11 10:55:35 oms_apex_plaisir systemd[1]: libvirt-guests.service: Unit entered failed state. Aug 11 10:55:35 oms_apex_plaisir systemd[1]: libvirt-guests.service: Failed with result 'exit-code'. ------------------------------------------------------------------------ it is like the service starts too early. When I restart the service everything is good and if I shutdown it sends the ACPI message correctly to my guests. I already seen lot of discussion but not able to find any working solution.. any idea to help me figure out the issue ? many thanks belette

2 5

[libvirt-users] Where to report Bug?
by Haitham El-Ghareeb 26 Sep '16

26 Sep '16

Hello,Today I got the following error message when I was trying to delete a Virtual Machine using "Virtual Machine Manager" Error is pasted herelibvirt - Permission Denied - Pastebin.com | | | | | | | | | | | libvirt - Permission Denied - Pastebin.com | | | | I know the error is in /usr/lib/python2.7/dist-packages/libvirt.py I am not sure where to report the error. This error is a simple one that can be easily fixed. Hope you can help me submit the error. Apologies for any inconvenience. ~Haitham

2 1

[libvirt-users] libvirt
by i.gerasimov＠wsmgroup.ru 24 Sep '16

24 Sep '16

hi, help me!) i broke my VM, changing configuration file fstab. Now it not boot. How do I get working VM?) and can't connected console -- С уважением, Герасимов Иван Дмитриевич WSM GROUP 8-909-793-01-51 ICQ 682218625

2 1

[libvirt-users] ANNOUNCE: ruby-libvirt 0.7.0
by Chris Lalancette 23 Sep '16

23 Sep '16

I'm pleased to release ruby-libvirt 0.7.0. ruby-libvirt is a ruby wrapper around the libvirt API. The changelog between 0.6.0 and 0.7.0 is: * Fix network lease API to allow arguments that libvirt allows * Implement VIRT_STORAGE_POOL_CREATE flags * Implement more VIR_STORAGE_VOL flags * Implement VIR_DOMAIN_QEMU_AGENT_COMMAND_SHUTDOWN * Implement virDomainDefineXMLFlags * Implement virDomainRename * Implement virDomainSetUserPassword * Implement VIR_DOMAIN_TIME_SYNC * Fix the return value from virStreamSourceFunc so volume upload works Version 0.7.0 is available from http://libvirt.org/ruby: Tarball: http://libvirt.org/ruby/download/ruby-libvirt-0.7.0.tgz Gem: http://libvirt.org/ruby/download/ruby-libvirt-0.7.0.gem It is also available from rubygems.org; to get the latest version, run: $ gem install ruby-libvirt Packages for it are also built for Fedora, and will be released shortly. As usual, if you run into questions, problems, or bugs, please feel free to mail me (clalancette at gmail.com) and the libvirt mailing list. Thanks to those who contributed to this release.

1 0

[libvirt-users] How to set QEMU qcow2 l2-cache-size using libvirt xml?
by Frank Myhr 20 Sep '16

20 Sep '16

QEMU's default qcow2 L2 cache size is too small for large images (and small cluster sizes), resulting in very bad performance. https://blogs.igalia.com/berto/2015/12/17/improving-disk-io-performance-in-… shows huge performance hit for a 20GB qcow2 with default 64kB cluster size: L2 Cache, MiB Average IOPS 1 (default) 5100 1.5 7300 2 12700 2.5 63600 The above link also gives the formula: optimal L2 cache size = L2 table size = (8 Byte) * (disk size) / (cluster size) and the QEMU command line for setting L2 cache size, which is not persistent, but must be specified at each invocation: qemu-system-x86_64 -drive file=hd.qcow2,l2-cache-size=2621440 I'd like to set the l2-cache-size in libvirt xml, but cannot make out how to do it. There are only hints in the comments at the above link and at http://wiki.libvirt.org/page/QEMUSwitchToLibvirt and an earlier unanswered question on this list https://www.redhat.com/archives/libvirt-users/2016-February/msg00036.html Has anyone successfully done this, and could you please give an example of the actual libvirt xml used? Thanks! Frank

2 2

[libvirt-users] qemu 2.7 / libvirt 2.2 / iPXE
by Gregory Gincley 17 Sep '16

17 Sep '16

Hi, I've been having some trouble lately with iPXE booting. I'm on Arch Linux vanilla 4.7.4 kernel qemu 2.7 libvirt 2.2.0 virt-manager 1.4.0 Since the upgrade from qemu 2.6.1 to 2.7 a few days ago. I'm no longer able to PXE boot using a bridged network connection. The PXE boot fails using NAT (host only) networking as well, when on a domain thats started by virt-manager, or through virsh. My networking setup is a bridge (br1) (shared device) established by systemd. Another machine on my LAN acts as a tFTP server and my router (tomato) directs all machines to it via this dnsmasq directive: 'dhcp-boot=pxelinux.0,nas,192.168.9.103' I have used this setup for years without issue. All other networking functionality appears to be fine if I boot into existing domains, skipping PXE rom. This occurs on domains created with 2.6.1 or with 2.7 Reverting to qemu 2.6.1 package corrects the issue. When I choose PXE boot, the machine immediately moves to a paused state (crashed). I only see this: Booting from ROM... iPXE (PCI 00:03.0) starting execution Followed by an immediate crash of qemu. The log simply states emulation error with some other information I don't understand memory contents perhaps. I can use qemu virtual networking and boot via local files served over tfp: eg: qemu-system-x86_64 -boot n -net nic,model=virtio,vlan=0 -net user,vlan=0,tftp=/tmp/tftp,bootfile=/pxelinux.0 I have also tried reverting to the 2.6.1 pxe-virtio.rom file while using qemu 2.7. Still I get the crash. So this appears to be some issue with how either libvirt/qemu is interacting with my network? I'm not sure what to look at next? Anyone else have similar issues? Thanks, Greg

1 0

[libvirt-users] New error: Failed to create chardev
by Iain Hallam 15 Sep '16

15 Sep '16

Hi. I'm running libvirt across a fleet of CentOS 7 desktops to provide VMs for other operating systems, and they've been running fine for the last year, through rebuilds, etc. In the last week, PCs that have been rebuilt no longer start our VMs, failing with the error: error: internal error: process exited while connecting to monitor: 2016-09-15T10:15:12.839724Z qemu-kvm: -chardev pty,id=charserial0: Failed to create chardev Various sites list remounting /dev/pts to solve this, with the command: mount -n -t devpts -o remount,mode=0620,gid=5 devpts /dev/pts After this command, the mount entry for devpts changed: devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,seclabel,gid=5,mode=620,ptmxmode=000) devpts on /dev/pts type devpts (rw,relatime,seclabel,gid=5,mode=620,ptmxmode=000) However, the chardev error is still present. The VM log in /var/log/libvirt/qemu shows: 2016-09-15 10:15:59.422+0000: starting up libvirt version: 1.2.17, package: 13.el7_2.5 (CentOS BuildSystem <http://bugs.centos.org>, 2016-06-23-14:23:27, worker1.bsys.centos.org) qemu version: 1.5.3 (qemu-kvm-1.5.3-105.el7_2.7) LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name centos6 -S -machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off -m 16384 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 901c9deb-1935-4cfe-b9b4-ea2221d10487 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-centos6/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot menu=on,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/vm/centos6-vda.qcow2,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -netdev tap,fd=23,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:02:59:93,bus=pci.0,addr=0x3,bootindex=1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on 2016-09-15T10:15:59.508359Z qemu-kvm: -chardev pty,id=charserial0: Failed to create chardev 2016-09-15 10:15:59.682+0000: shutting down Anyone got any ideas? The only configuration change we have introduced in the last few weeks is creating local user accounts and turning off NIS on those boxes. SELinux is set to Permissive. Thanks, Iain Hallam. -- iain(a)nineworlds.net http://www.iainhallam.com/

1 0

[libvirt-users] Help With Nested Virtualization
by Brandon Golway 08 Sep '16

08 Sep '16

(Copied from my post on the Arch Linux forums: https://bbs.archlinux.org/viewtopic.php?pid=1650650#p1650650) I have a FreeNAS 10 KVM setup via libvirt on my Arch server and I'd like to be able to test out the virtualization features in the nightly FreeNAS 10 builds but the problem is that I can't seem to get VT-x to correctly pass through to the guest. I have followed the [u][url= https://wiki.archlinux.org/index.php/KVM#Nested_virtualization]Nested Virtualization[/url][/u] section of the KVM wiki and I'm sure it's supported and enabled. Here's proof [code] [bran@nas ~]$ sudo systool -m kvm_intel -v | grep nested nested = "Y" [bran@nas ~]$ lscpu|grep Virtualization Virtualization: VT-x[/code] So the host/hardware isn't the problem, I believe the problem lies within libvirt. RedHat says to use [b]copy host CPU configuration[/b] or [b]host-passthrough[/b], with the latter being preferred. If I use the former I get the [b]CMT not supported[/b] error, but if I type in [b]host-passthrough[/b] which according to [u][url= https://bbs.archlinux.org/viewtopic.php?id=214539]this post[/url][/u] should work. When I set [b]host-passthrough[/b] it allows the system to boot up, but when I try to start a guest FreeNAS gives me the error that VT-x instructions aren't available, I have no idea how to check them either since the [b]proc[/b] pseudo-filesystem doesn't exist in BSD. I know for a fact that this isn't a problem with the FreeNAS builds because I've been testing them out for months on my Windows 10 desktop via VMware and nested virtualization works without issue, so it must be an issue with KVM/libvirt. Can someone clue me in on what the issue is? Here's the entire XML config for the FreeNAS VM [code] <domain type='kvm'> <name>FreeNAS_10</name> <uuid>ea816b85-7685-495a-bc97-28a882f190d7</uuid> <title>FreeNAS v10</title> <description>Nightly Alpha Test Releases</description> <memory unit='KiB'>6340608</memory> <currentMemory unit='KiB'>6340608</currentMemory> <vcpu placement='static'>4</vcpu> <os> <type arch='x86_64' machine='pc-i440fx-2.6'>hvm</type> <bootmenu enable='no'/> </os> <features> <acpi/> <apic/> <vmport state='off'/> </features> <cpu mode='host-passthrough'/> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <pm> <suspend-to-mem enabled='no'/> <suspend-to-disk enabled='no'/> </pm> <devices> <emulator>/usr/sbin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/storage/vm-storage/FreeNAS_Disk1.img'/> <target dev='vdb' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/storage/vm-storage/FreeNAS_Disk2.img'/> <target dev='vdc' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/storage/vm-storage/FreeNAS_Disk3.img'/> <target dev='vdd' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='directsync' io='native'/> <source file='/var/lib/libvirt/images/FreeNAS_10.img'/> <target dev='vde' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hda' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:24:5c:08'/> <source bridge='vmbridge'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <redirdev bus='usb' type='spicevmc'> <address type='usb' bus='0' port='1'/> </redirdev> <redirdev bus='usb' type='spicevmc'> <address type='usb' bus='0' port='2'/> </redirdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </memballoon> </devices> </domain>[/code] Thanks, Brandon Golway

4 6

[libvirt-users] Hiding hypervisor cpuid bit in Qemu
by Miller, Cody 07 Sep '16

07 Sep '16

Hello, I was hoping someone could help me with an issue I'm having with libvirt 1.3.3 and qemu 2.5.1. I'm trying to prevent qemu from exposing the 'hypervisor' cupid feature to my VMs. When running qemu directly I can use "-cpu ...,-hypervisor"; which works as expected. Using libvirt, I add "<feature policy='disable' name='hypervisor'/>" to the cpu section of the VMs xml. This however, does not prevent exposing the bit. Any help would be appreciated.

1 0

[libvirt-users] attaching storage pool error
by Johan Kragsterman 07 Sep '16

07 Sep '16

Hi! System centos7, system default libvirt version. I've succeeded to create an npiv storage pool, which I could start without problems. Though I couldn't attach it to the vm, it throwed errors when trying. I want to boot from it, so I need it working from start. I read one of Daniel Berrange's old(2010) blogs about attaching an iScsi pool, and draw my conclusions from that. Other documentation I haven't found. Someone can point me to a more recent documentation of this? Are there other mailing list in the libvirt/KVM communities that are more focused on storage? I'd like to know about these, if so, since I'm a storage guy, and fiddle around a lot with these things... There are quite a few things I'd like to know about, that I doubt this list cares about, or have knowledge about, like multipath devices/pools, virtio-scsi in combination with npiv-storagepool, etc. So anyone that can point me further....? Rgrds Johan

3 14