September 2015 - Users - libvirt List Archives

[libvirt-users] ceph rbd pool and libvirt manageability (virt-install)
by Jelle de Jong 29 Aug '18

29 Aug '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, I created a rbd pool and activated it, but I can't seem to create volumes in it with virsh or virt-install? # virsh pool-dumpxml myrbdpool <pool type='rbd'> <name>myrbdpool</name> <uuid>2d786f7a-2df3-4d79-ae60-1535bcf1c6b5</uuid> <capacity unit='bytes'>6997998301184</capacity> <allocation unit='bytes'>10309227031</allocation> <available unit='bytes'>6977204658176</available> <source> <host name='ceph01.powercraft.nl' port='6789'/> <host name='ceph02.powercraft.nl' port='6789'/> <host name='ceph03.powercraft.nl' port='6789'/> <name>libvirt-pool</name> <auth type='ceph' username='libvirt'> <secret uuid='029a334e-ed57-4293-bb99-ffafa8867122'/> </auth> </source> </pool> # virt-install --version 1.0.1 # virsh --version 1.2.9 I ended using virsh edit ceph-test.powercraft.nl and making creating the disk manually. <disk type='network' device='disk'> <auth username='libvirt'> <secret type='ceph' uuid='029a334e-ed57-4293-bb99-ffafa8867122'/> </auth> <source protocol='rbd' name='libvirt-pool/kvm01-storage'> <host name='ceph01.powercraft.nl' port='6789'/> <host name='ceph02.powercraft.nl' port='6789'/> <host name='ceph03.powercraft.nl' port='6789'/> </source> <target dev='vdc' bus='virtio'/> </disk> I use virt-install a lot to define, import and undefine domains, how can I use virt-install to manage my rdb disks? Kind regards, Jelle de Jong -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iJwEAQECAAYFAlV1xlQACgkQ1WclBW9j5HkbPQP+PjNrzvlqysslOp2Yk7wH4Mxy 2sh2dn96G0KOAHEeEn3BN6IWlnD1TADZbHdpTtMwkdv48Xwn0sP1s+3QDM4pb3gP n+z+dVxS8FouDIy/eiso3IBCj3g4TWbEX8ZHqs3jKqe0lZgAXBzB9xYSUowcEBrZ ddkPbr8p8ozWyOG+9V8= =lkK7 -----END PGP SIGNATURE-----

2 3

[libvirt-users] virRandomBits - not very random
by Brian Rak 01 Jun '18

01 Jun '18

I just ran into an issue where I had about 30 guests get duplicate mac addresses assigned. These were scattered across 30 different machines. Some debugging revealed that: 1) All the host machines were restarted within a couple seconds of each other 2) All the host machines had fairly similar libvirtd pids (within ~100 PIDs of each other) 3) Libvirt seeds the RNG using 'time(NULL) ^ getpid()' This perfectly explains why I saw so many duplicate mac addresses. Why is the RNG seed such a predictable value? Surely there has to be a better source of a random seed then the timestamp and the pid? The PID seems to me to be a very bad source of any randomness. I just ran a test across 60 of our hosts. 43 of them shared their PID with at least one other machine.

7 13

[libvirt-users] Libvirt bite sized tasks
by Michal Privoznik 21 Mar '16

21 Mar '16

Dear lists, I've just started new wiki page which aim is to summarize small and trivial tasks, that starting contributors can take, investigate and implement. The aim is to give them something easy to start with while not scaring them out about complexity of our code. The page can be found here: http://wiki.libvirt.org/page/BiteSizedTasks The name is copied from qemu wiki: http://wiki.qemu.org/BiteSizedTasks Please, feel free to extend the list. I plan to use it in the future when interviewing GSoC candidates. Michal

2 1

[libvirt-users] virDomainCoreDumpWithFormat files created as root
by NoxDaFox 19 Nov '15

19 Nov '15

Greetings, I am dumping a guest VM memory for inspection using the command "virDomainCoreDumpWithFormat" and the created files appear to belong to root (both user and group). I have searched around but didn't find any answer. Is there a way to instruct QEMU to create those files under a different user? Thank you.

5 7

[libvirt-users] libvirt 1.19: could not open drive file (permission denied)
by crequill 07 Oct '15

07 Oct '15

Hi, With libvrit 1.18 all is working fine: I can open my win7 VM on Archlinux without problem. But I cannot use it with libvirt 1.19: it could not open drive file (permission denied). In /etc/libvirt/qemu.conf, I have: - user: root - group: root And the drive file has root:root as owner. Why this configuration is running with libvirt 1.18 and not with libvirt 1.19 ? Many thanks for your reply. Christophe

2 6

[libvirt-users] Time syncing after VM suspend/resume
by Jérôme 29 Sep '15

29 Sep '15

Hi all. When resuming guest after suspend, the time is wrong (because the guest doesn't know it has been suspended). Apparently, ntp running on the guest doesn't solve this. At least on Linux system. I read it works on Windows guests. I don't understand why, so I'd appreciate a link to an explanation, but I understand it is out of scope for this list. The HW clock is correct and the guest agent is setup to use kvm-clock. Using the guest-set-time command does set the clock on the guest according to the host. But this is not triggered automatically on resume. I found discussions about this, even a patch proposal to call guest-set-time on resume, but all of this is one year old and I can't find any newer information. http://serverfault.com/questions/334698/how-to-keep-time-on-resumed-kvm-gue… https://www.redhat.com/archives/libvirt-users/2014-October/msg00009.html https://www.redhat.com/archives/libvir-list/2014-February/msg00520.html Is there any fresher information I have missed ? Thanks. -- Jérôme

5 6

[libvirt-users] VirtualBox + Virsh
by Julian Zhou 29 Sep '15

29 Sep '15

Hi I am trying to add a virtualbox domain to my virsh installation, I get: error: Failed to define domain from Ondria.xml >>https://gist.github.com/jztech101/5aeebb82412c1910dc1f<< error: internal error: unexpected domain type vbox, expecting one of these: qemu, kqemu, kvm, xen. virsh is compiled with VirtualBox support so I'm confused: Virsh -V >> Virsh command line tool of libvirt 1.2.2 See web site athttp://libvirt.org/ Compiled with support for: Hypervisors: QEMU/KVM LXC UML Xen LibXL OpenVZ VMWare VirtualBox Test Networking: Remote Network Bridging Interface netcf Nwfilter VirtualPort Storage: Dir Disk Filesystem SCSI Multipath iSCSI LVM RBD Sheepdog Miscellaneous: Daemon Nodedev AppArmor Secrets Debug Readline Modular. After some insight, I decided to run it like this instead: " virsh -c vbox:///session create Ondria.xml" Now I get: error: failed to connect to the hypervisor error: internal error: unable to initialize VirtualBox driver API So, after further insight, I ran "export VBOX_APP_HOME=/usr/lib/virtualbox" and tried again. Same error as above. (/usr/lib/virtualbox is where VBoxCPCOMC.so lies and I'm told the reason for the above error is it cannot find that file in any "normal" location. Help? It should be noted I installed VirtualBox-5.0 directly from the VBox Repo for Ubuntu 14.04LTS Regards, Julian Zhou

2 2

[libvirt-users] Fw: libvirtd service not starting
by Jonathan Rurka 26 Sep '15

26 Sep '15

On Thursday, September 24, 2015 12:29 PM, Jonathan Rurka <jon.rurka(a)yahoo.com> wrote: Yes the "which libvirtd" and "sudo virt-host-validate" commands return correct values However, I am having a new problem now; "UEFI" is not selectable under firmware: http://i.imgur.com/O4ypOTX.png I do have VT-d enabled in my bios, my processor supports VT-d, and I am booting ubuntu in UEFI mode. The yellow triangle says "Libvirt did not detect any UEFI/OVMF firmware image installed on the host.". Another person instructed me to set the nvram opeion in /etc/libvirt/qemu.conf to where I have my OVMF placed (which I downloaded from https://www.kraxel.org/repos/jenkins/edk2/) however it hasn't helped. it is set to: nvram = [ "/usr/share/edk2.git/ovmf-x64/OVMF_pure-efi.fd:/usr/share/edk2.git/ovmf-x64/OVMF_VARS-pure-efi.fd" ] On Thursday, September 24, 2015 3:29 AM, Kashyap Chamarthy <kchamart(a)redhat.com> wrote: On Thu, Sep 24, 2015 at 06:47:43AM +0200, Martin Kletzander wrote: > On Wed, Sep 23, 2015 at 11:00:34PM +0000, Jonathan Rurka wrote: > >Hello, I'm new to using libvirt. After a few days of installing and > >removing libvirt, virt-manager and a few others to get VT-d working > >with a virtual machine, I finally got the latest virt-manager and > >libvirt installed from source to get the most recent > >versions. However, when I start up virt-manager I get a popup saying > >"Unable to connect to libvirt; Verify that the 'libvirtd' deamon is > >running.". When running "service libvirtd start", I get an error > >saying libvirtd.service cannot be found. I can, however, use libvirtd > >from the command line. The service file does not exist > >in /lib/systemd/system/. > > > > Did you probably forget to specify the prefix to install it into? you > can do "which libvirtd" to see that you probably installed it into > /usr/local/sbin. Specifying the prefix should help. > > Getting to your "to get VT-d working", you should check whether > everything is enabled in BIOS. That's usually the case if it's not > working for you. [A small addendum to what Martin says.] Jon, you can use `virt-host-validate` to check the above, if everything is setup correctly, it should look like that: $ sudo virt-host-validate QEMU: Checking for hardware virtualization : PASS QEMU: Checking for device /dev/kvm : PASS QEMU: Checking for device /dev/vhost-net : PASS QEMU: Checking for device /dev/net/tun : PASS LXC: Checking for Linux >= 2.6.26 : PASS [. . .] -- /kashyap

2 1

[libvirt-users] PCI passthrough fails in virsh: iommu group is not viable
by Alex Holst 25 Sep '15

25 Sep '15

I would really appreciate some pointers on what I am doing wrong here. I have a need to run multiple virtual guests which have each their own GPU and some USB controllers passed-through. I am able to run one of the guests like this (assuming vfio stuff has happened elsewhere), but I would prefer to use virsh: kvm -M q35 -m 8192 -cpu host,kvm=off \ -smp 4,sockets=1,cores=4,threads=1 \ -bios /usr/share/seabios/bios.bin -vga none \ -device ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 \ -device vfio-pci,host=02:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on \ -device vfio-pci,host=02:00.1,bus=root.1,addr=00.1 \ -device vfio-pci,host=00:1d.0,bus=pcie.0 \ -device vfio-pci,host=00:1a.0,bus=pcie.0 \ -nographic -boot menu=on /vm2/foo.img I found the hardware addresses using lspci. When I invoke the same machine with virsh with what I believe are the same addresses, I get: virsh # start foo error: Failed to start domain foo error: internal error: process exited while connecting to monitor: 2015-08-12T18:24:10.651720Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x4: vfio: error, group 18 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver. 2015-08-12T18:24:10.651752Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x4: vfio: failed to get group 18 2015-08-12T18:24:10.651766Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x4: Device initialization failed. 2015-08-12T18:24:10.651781Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x4: Device 'vfio-pci' could not be initialized I have included dumpxml output below -- is the hostdev section wrong? <domain type='kvm'> <name>foo</name> <uuid>51f57655-11be-41bf-b925-2e6aef01f9c4</uuid> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <vcpu placement='static' current='1'>4</vcpu> <os> <type arch='x86_64' machine='pc-i440fx-utopic'>hvm</type> <bootmenu enable='yes'/> </os> <features> <acpi/> <apic/> <pae/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </features> <cpu mode='custom' match='exact'> <model fallback='allow'>SandyBridge</model> <topology sockets='1' cores='4' threads='1'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> <timer name='hypervclock' present='yes'/> </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/bin/kvm-spice</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/vm2/foo.img'/> <target dev='sda' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='block' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hdb' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' 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='0x05' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </controller> <interface type='direct'> <mac address='52:54:00:f0:47:f5'/> <source dev='p5p1' mode='bridge'/> <model type='e1000'/> <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='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='spice' autoport='yes'/> <video> <model type='cirrus' vram='16384' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </memballoon> </devices> </domain> -- Alex Holst

2 3

[libvirt-users] Guest cpuacct counters and others location
by Jean-Pierre Ribeauville 25 Sep '15

25 Sep '15

Hi, My piece of code ( C langage) uses cgroups to retrieve counters related to cpu and memory usage related to KVM guests hosted by the host where this code runs. I noticed that depending on the O.S. running on the host , these counters are not found at the same location : CentOS 7 : ls /sys/fs/cgroup/cpuacct/machine.slice/machine-qemu\\x2drhel6.0.scope/vcpu0 cgroup.clone_children cgroup.procs cpuacct.usage cpu.cfs_period_us cpu.rt_period_us cpu.shares notify_on_release cgroup.event_control cpuacct.stat cpuacct.usage_percpu cpu.cfs_quota_us cpu.rt_runtime_us cpu.stat tasks ]# RHEL6 : ls /cgroup/cpuacct/libvirt/qemu/VM_Orion-1/vcpu0 cgroup.event_control cgroup.procs cpuacct.stat cpuacct.usage cpuacct.usage_percpu notify_on_release tasks 1) May I assume that their meanings is identical ? 2) Is this difference due to the O.S. or to libvirt ? 3) I presume I've to check this point on Ubuntu , Debian and Fedora . Thanks J.P. Ribeauville P: +33.(0).1.47.17.20.49 . Puteaux 3 Etage 5 Bureau 4 jpribeauville(a)axway.com<mailto:jpribeauville@axway.com> http://www.axway.com<http://www.axway.com/> P Pensez à l'environnement avant d'imprimer.

2 1

[libvirt-users] libvirtd service not starting
by Jonathan Rurka 24 Sep '15

24 Sep '15

Hello, I'm new to using libvirt. After a few days of installing and removing libvirt, virt-manager and a few others to get VT-d working with a virtual machine, I finally got the latest virt-manager and libvirt installed from source to get the most recent versions. However, when I start up virt-manager I get a popup saying "Unable to connect to libvirt; Verify that the 'libvirtd' deamon is running.". When running "service libvirtd start", I get an error saying libvirtd.service cannot be found. I can, however, use libvirtd from the command line. The service file does not exist in /lib/systemd/system/. log from launching with "./virt-manager --debug": jon@jon-desktop:/media/jon/Data/Programs/virt-manager$ ./virt-manager --debug[Wed, 23 Sep 2015 15:59:22 virt-manager 3904] DEBUG (cli:256) Launched with command line: ./virt-manager --debug[Wed, 23 Sep 2015 15:59:22 virt-manager 3904] DEBUG (virt-manager:160) virt-manager version: 1.2.1[Wed, 23 Sep 2015 15:59:22 virt-manager 3904] DEBUG (virt-manager:161) virtManager import: <module 'virtManager' from '/media/jon/Data/Programs/virt-manager/virtManager/__init__.pyc'>[Wed, 23 Sep 2015 15:59:22 virt-manager 3904] DEBUG (virt-manager:220) GTK version: 3.14.13[Wed, 23 Sep 2015 15:59:22 virt-manager 3904] DEBUG (engine:467) libguestfs inspection support: False[Wed, 23 Sep 2015 15:59:22 virt-manager 3904] DEBUG (systray:153) Showing systray: False[Wed, 23 Sep 2015 15:59:22 virt-manager 3904] DEBUG (engine:237) About to connect to uris ['qemu:///system'][Wed, 23 Sep 2015 15:59:22 virt-manager 3904] DEBUG (manager:208) Showing manager[Wed, 23 Sep 2015 15:59:22 virt-manager 3904] DEBUG (engine:368) window counter incremented to 1[Wed, 23 Sep 2015 15:59:22 virt-manager 3904] DEBUG (connection:567) conn=qemu:///system changed to state=Connecting[Wed, 23 Sep 2015 15:59:22 virt-manager 3904] DEBUG (connection:886) Scheduling background open thread for qemu:///system[Wed, 23 Sep 2015 15:59:22 virt-manager 3904] DEBUG (connection:567) conn=qemu:///system changed to state=Disconnected[Wed, 23 Sep 2015 15:59:22 virt-manager 3904] DEBUG (error:99) error dialog message:summary=Unable to connect to libvirt. Verify that the 'libvirtd' daemon is running.details=Unable to connect to libvirt. Verify that the 'libvirtd' daemon is running. Libvirt URI is: qemu:///system Traceback (most recent call last): File "/media/jon/Data/Programs/virt-manager/virtManager/connection.py", line 902, in _do_open self._backend.open(self._do_creds_password) File "/media/jon/Data/Programs/virt-manager/virtinst/connection.py", line 148, in open open_flags) File "/usr/lib/python2.7/dist-packages/libvirt.py", line 105, in openAuth if ret is None:raise libvirtError('virConnectOpenAuth() failed')libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory Any help appreciated,Jon

3 2

[libvirt-users] Reg: Virsh managedsave Failing
by Vijaya Erukala 24 Sep '15

24 Sep '15

Hi All, We are trying to do "virsh managedsave" on a VM but it is failing with the following error. libvirtError: operation failed: domain save job: unexpectedly failed^M libvirt and qemu versions are as follows: libvirt-1.1.1-29.el7.x86_64 qemu-kvm-1.5.3-60.el7_0.11.x86_64 VM is provided with a small pxe image such that it pxe boots from a remote server. VM doesn't have any disk allocated with it and uses 4GB RAM,16 VCPUs. It mounts the root storage and all required folders from a remote server's NFS storage. Following is the file system once the VM is booted successfully. VM1:~ # df -h Filesystem Size Used Avail Use% Mounted on rootfs 2.0G 1.5G 601M 71% / root 2.0G 1.5G 601M 71% / tmpfs 7.1G 3.4M 7.1G 1% /dev/shm shm 7.1G 3.4M 7.1G 1% /dev/shm 10.0.0.3:/.storage 90G 20G 66G 23% /storage We have also tried to enable debug mode for libvirt process but no error message is getting logged except the error message above. Could someone help me debug this issue? Regards, Vijaya

2 1

[libvirt-users] compress support
by Surivinta Surivinta 24 Sep '15

24 Sep '15

Hi! I read some letters about compress/decompress support and think about it. How will be better implement this function? If I understand correctly api-guide when we use libvirt-stream (send/recv), program is waiting until read or send all data (like MPI send/recv functions). Compress/decompress functional in basically may be use with storage-volume functions, perhaps it would be better to implement via "storage-backend"? Maybe libvirt not needed this functional? Because there is many software which implement functions for compress/decompress and if we add many thing into libvirt, then this will be emacs. -- С уважением.

2 1

[libvirt-users] New software based on libvirt
by Gustav Fransson Nyvell 23 Sep '15

23 Sep '15

Hello, I'm introducing to you the decentralized cloud Cherrypop. Combining libvirt and LizardFS (as of now) it becomes a cloud completely without masters. Thus, any node is sufficient for the cloud to be up and therefore no wasted resources and no single point of failure. It's still pretty crude software but will work with some tinkering. Hope you try it and like it! For more information, source and binary: https://github.com/gustavfranssonnyvell/cherrypop //Gustav

4 4

[libvirt-users] error: internal error: Failed to reserve port 5908
by Bill Kenworthy 22 Sep '15

22 Sep '15

After saving a particular VM running WinXP, any attempt to resume it (even when no other VM's are running) generates the following error: olympus ~ # virsh restore /var/lib/libvirt/qemu/save/WinXP.save error: Failed to restore domain from /var/lib/libvirt/qemu/save/WinXP.save error: internal error: Failed to reserve port 5908 This started sometimes towards the end of last year with only the WinXP VM. libvirt is supporting a number of windows versions and a heap of linux VM's but its only WinXP that does this. Can someone give a hint as to what is causing it? BillK olympus ~ # virsh dumpxml WinXP <domain type='kvm'> <name>WinXP</name> <uuid>a9ddf88e-9ff4-46d0-9661-a5ccfacd104f</uuid> <memory unit='KiB'>4096000</memory> <currentMemory unit='KiB'>4096000</currentMemory> <vcpu placement='static'>2</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='i686' machine='pc-1.2'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='custom' match='exact'> <model fallback='allow'>Penryn</model> <vendor>Intel</vendor> <feature policy='require' name='tm2'/> <feature policy='require' name='est'/> <feature policy='require' name='monitor'/> <feature policy='require' name='ds'/> <feature policy='require' name='ss'/> <feature policy='require' name='vme'/> <feature policy='require' name='dtes64'/> <feature policy='require' name='ht'/> <feature policy='require' name='dca'/> <feature policy='require' name='pbe'/> <feature policy='require' name='tm'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='vmx'/> <feature policy='require' name='ds_cpl'/> <feature policy='require' name='xtpr'/> <feature policy='require' name='acpi'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup' track='guest'> <catchup threshold='123' slew='120'/> </timer> <timer name='pit' tickpolicy='delay'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/mnt/vm/WinXP/WinXP_disk1.qcow2'/> <target dev='hda' bus='ide'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/var/lib/libvirt/images/en_windows_xp_professional_with_service_pack_3_x86_cd_x14-80428.iso'/> <target dev='hdc' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> <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='0x05' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <interface type='bridge'> <mac address='00:00:00:00:00:18'/> <source bridge='fbr49'/> <virtualport type='openvswitch'> <parameters interfaceid='aa19a961-60ac-4c0b-8cca-adf102b47c83'/> </virtualport> <model type='rtl8139'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='spice' port='-1' autoport='no' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='8192' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> </domain> olympus ~ #

3 2

[libvirt-users] virt-install and kickstart networking
by Alex 22 Sep '15

22 Sep '15

Hi, I have a fedora22 host and trying to use virt-install to install a fedora22 guest. The host is configured with bridge networking, using eth0 as its local interface. It appears the guest is communicating on vnet0 instead of eth0, so it can never reach the outside to download the install files. Where is vnet0 configured? Is it set by default when a bridge is created? I have one other guest on this host, but it was created manually with virt-manager and doesn't have the same problem. I have the following virt-install command for installing: virt-install --name testme --hvm --memory 1024 --virt-type kvm \ --disk path=/var/lib/libvirt/images/testme.qcow2,size=16 \ --network bridge=br0:eth0,mac=52:54:00:35:dd:67 \ --os-variant=fedora22 \ --location http://192.168.1.7/~alex/fedora22/ \ --initrd-inject anaconda-setup.cfg --extra-args "inst.ks=file:/anaconda-setup.cfg" \ --graphics vnc,password=foobar,listen=192.168.1.1,port=5910 I have a bridge set up as br0 with eth0 as the network interface. virbr0 is the 192.168.122.0 network, with vnet0 and vnet1 apparently the interfaces for that network. Is the br0 specified in the --network command line the actual br0 or, what looks to be more likely, the virbr0 interface? If so, how do I configure it to instead use the real br0, so it can communicate with the rest of the hosts on the local network? Can someone also explain to me the relationship between the mac address that I set here with the virt-install command and the network line in the anaconda-setup.cfg file? Thanks, Alex

1 0

[libvirt-users] failure when trying to add a channel device via virsh attach-device
by Jean-Pierre Ribeauville 21 Sep '15

21 Sep '15

Hi, On a KVM host installed with following packages versions : [root@rhel6-roadster test_channels_OK]# rpm -qa | grep libvirt libvirt-devel-0.10.2-29.el6.x86_64 libvirt-0.10.2-29.el6.x86_64 libvirt-client-0.10.2-29.el6.x86_64 libvirt-java-0.4.9-1.el6.noarch libvirt-java-devel-0.4.9-1.el6.noarch libvirt-python-0.10.2-29.el6.x86_64 [root@rhel6-roadster test_channels_OK]# rpm -qa | grep qemu qemu-kvm-0.12.1.2-2.415.el6.x86_64 gpxe-roms-qemu-0.9.7-6.10.el6.noarch qemu-img-0.12.1.2-2.415.el6.x86_64 [root@rhel6-roadster test_channels_OK]# virsh --version 0.10.2 [root@rhel6-roadster test_channels_OK]# When trying to add a channel device via virsh attach-device , I got following errors : <channel type='unix'> <source mode='bind' path='//var/lib/libvirt/qemu/omnivision_123456.agent'/> <target type='virtio' name='omnivision_123456.agent' state='disconnected'/> <alias name='channel_OmniVision'/> <address type='virtio-serial' controller='0' bus='0' port='30'/> </channel> Guest is off : [root@rhel6-roadster test_channels_OK]# virsh attach-device Linux_2 add_channel_device.xml error: Failed to attach device from add_channel_device.xml error: Requested operation is not valid: cannot do live update a device on inactive domain [root@rhel6-roadster test_channels_OK]# Guest is running : [root@rhel6-roadster test_channels_OK]# virsh attach-device Linux_2 add_channel_device.xml error: Failed to update device from add_channel_device.xml error: XML error: unknown device type [root@rhel6-roadster test_channels_OK] Did I miss something ? Thanks for help. J.P. Ribeauville P: +33.(0).1.47.17.27.87 Puteaux 3 Etage 5 Bureau 4 jpribeauville(a)axway.com<mailto:jpribeauville@axway.com> http://www.axway.com<http://www.axway.com/> P Pensez à l'environnement avant d'imprimer.

2 2

[libvirt-users] Guest agent is not responding
by Marko Weber | 8000 18 Sep '15

18 Sep '15

hello, in my windows vm i installed qemu-guest-agent and rebootet the vm. In the settings for the vm i set via virt-manager a new channel "unix socket" "org.qemu.guest_agent.0" "virtio". when i try to do a snapshot via shell i get: virsh snapshot-create-as --domain win7new win7new-snap1 --disk-only --atomic --quiesce error: Guest agent is not responding: Guest agent not available for now I use gentoo on the Host. qemu is built with useflags: aio alsa caps curl fdt filecaps gtk iscsi jpeg lzo ncurses nls numa pin-upstream-blobs png python sdl seccomp smartcard ssh threads tls usb usbredir uuid vde vhost-net virtfs vnc xattr xfs libvirt: audit caps fuse iscsi libvirtd lvm lxc macvtap nls numa parted pcap policykit qemu udev vepa virt-network thanks for any tipps and hints. -- zbfmail - Mittendrin statt nur Datei!

2 3

[libvirt-users] hvm on x86_64 on binutils i386
by Bhasker C V 17 Sep '15

17 Sep '15

Hi, I have this setup kernel: x86_64 version 4.2.0 operating system (rootfs binutils etc.,) : i386 (ELF-32-bit) qemu-system : version 2.4.0 qemu-system-x86_64 (i386 binary) libvirt: 1.2.19 (i386 ) When I run the qemu-system-x86_64 binary with --enable-kvm, the guest machine is working properly as hvm. So QEMU can run x86_64 OS as hvm when I install using virt-install virt-install --name debian --cdrom ./debian-stretch-DI-a1-amd64-netinst.iso --disk /STOR/DEBIAN,bus=sata --ram 1024 --graphics vnc I expect the 64-bit kernel to load and start install in the guest but i get a complaint that the guest cannot boot since the cpu is not 64-bit capable (please use a kernel appropriate for your CPU) I tried adding the machine option to virt-install virt-install --name debian --cdrom ./debian-stretch-DI-a1-amd64-netinst.iso --disk /STOR/DEBIAN,bus=sata --ram 1024 --graphics vnc --machine pc-i440fx-2.0 No joy Tried changing the machine as hvm and also added --arch x86_64 none of them help ! Can someone tell me how to do this ? Just because the binutils and the OS is 32-bit I think libvirt must not refuse to hvm a x86_64 guest since the kernel is still x86_64 kernel and so so the kvm (module) I am guessing I am missing some option passed to virt-install or this is a limitation purely on libvirt (not qemu or kvm) Moreover QEMU is able to run a hvm guest x86_64 and manually running qemu does bootup the 64-bit kernel guests.

2 3

[libvirt-users] vport0p devices no suitable drver found ..
by Jean-Pierre Ribeauville 17 Sep '15

17 Sep '15

Hi, By using virtio-win-0.1.109.iso , it looks like vport0p devices are not configured (on a Windows 2008 R2 guest) due to no suitable driver found ( below setupapi.dev.log): [Boot Session: 2015/09/16 17:29:32.375] >>> [Device Install (Hardware initiated) - {6fde7547-1b65-48ae-b628-80be62016026}\vioserialport\4&7e8053e&1&03] >>> Section start 2015/09/16 17:29:56.046 ump: Creating Install Process: DrvInst.exe 17:29:56.109 ndv: Retrieving device info... ndv: Setting device parameters... ndv: Searching Driver Store and Device Path... dvi: {Build Driver List} 17:29:56.328 dvi: Searching for hardware ID(s): dvi: {6fde7547-1b65-48ae-b628-80be62016026}\vioserialport cpy: Policy is set to make all digital signatures equal. dvi: Enumerating INFs from path list 'C:\Windows\inf' inf: Searched 0 potential matches in published INF directory inf: Searched 36 INFs in directory: 'C:\Windows\inf' dvi: {Build Driver List - exit(0x00000000)} 17:29:59.000 ndv: Selecting best match from Driver Store (including Device Path)... dvi: {DIF_SELECTBESTCOMPATDRV} 17:29:59.000 dvi: No class installer for 'vport0p3' dvi: No CoInstallers found dvi: Default installer: Enter 17:29:59.015 dvi: {Select Best Driver} ! dvi: Selecting driver failed(0xe0000228) dvi: {Select Best Driver - exit(0xe0000228)} ! dvi: Default installer: failed! ! dvi: Error 0xe0000228: There are no compatible drivers for this device. dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 17:29:59.062 ndv: {Core Device Install} 17:29:59.062 ! ndv: Installing NULL driver! dvi: Set selected driver complete. dvi: {DIF_ALLOW_INSTALL} 17:29:59.687 dvi: No class installer for 'vport0p3' dvi: Default installer: Enter 17:29:59.687 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 17:29:59.687 dvi: {DIF_INSTALLDEVICE} 17:29:59.687 dvi: No class installer for 'vport0p3' dvi: Default installer: Enter 17:29:59.687 ! dvi: Installing NULL driver! dvi: Writing common driver property settings. dvi: {Restarting Devices} 17:30:00.093 dvi: Restart: {6FDE7547-1B65-48AE-B628-80BE62016026}\VIOSERIALPORT\4&7E8053E&1&03 dvi: Restart complete. dvi: {Restarting Devices exit} 17:30:00.187 dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 17:30:00.187 ndv: Device install status=0xe0000203 ndv: Performing device install final cleanup... ! ndv: Queueing up error report since device installation failed... ndv: {Core Device Install - exit(0xe0000203)} 17:30:00.187 ump: Server install process exited with code 0xe0000203 17:30:00.203 <<< Section end 2015/09/16 17:30:00.203 <<< [Exit status: FAILURE(0xe0000203)] Is there something I miss ? Thanks for help. J.P. Ribeauville P: +33.(0).1.47.17.27.87 Puteaux 3 Etage 5 Bureau 4 jpribeauville(a)axway.com<mailto:jpribeauville@axway.com> http://www.axway.com<http://www.axway.com/> P Pensez à l'environnement avant d'imprimer.

1 0

[libvirt-users] how to use {6FDE7547-1B65-48ae-B628-80BE62016026}\VIOSerialPort ?
by Jean-Pierre Ribeauville 17 Sep '15

17 Sep '15

Hi, When adding a channel device on a Win2008R2 Guest, I got this new thing within registry : Key Name: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\{6FDE7547-1B65-48ae-B628-80BE62016026}\VIOSerialPort\4&7e8053e&0&02 Class Name: <NO CLASS> Last Write Time: 9/16/2015 - 4:09 PM Value 0 Name: DeviceDesc Type: REG_SZ Data: vport0p2 Value 1 Name: Capabilities Type: REG_DWORD Data: 0xe6 Value 2 Name: UINumber Type: REG_DWORD Data: 0x2 Value 3 Name: ConfigFlags Type: REG_DWORD Data: 0 Value 4 Name: HardwareID Type: REG_MULTI_SZ Data: {6FDE7547-1B65-48ae-B628-80BE62016026}\VIOSerialPort Value 5 Name: CompatibleIDs Type: REG_MULTI_SZ Data: Value 6 Name: ContainerID Type: REG_SZ Data: {90e92d57-5573-11e5-9d8e-806e6f6e6963} Value 7 Name: LocationInformation Type: REG_SZ Data: RedHat VIOSerial Port Key Name: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\{6FDE7547-1B65-48ae-B628-80BE62016026}\VIOSerialPort\4&7e8053e&0&02\LogConf Class Name: <NO CLASS> Last Write Time: 9/16/2015 - 4:10 AM Key Name: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\{6FDE7547-1B65-48ae-B628-80BE62016026}\VIOSerialPort\4&7e8053e&0&02\Control Class Name: <NO CLASS> Last Write Time: 9/16/2015 - 4:09 PM How may I use theses infos to get/send datas to the host via this channel ? Thanks for help. Regards, J.P. Ribeauville P: +33.(0).1.47.17.27.87 Puteaux 3 Etage 5 Bureau 4 jpribeauville(a)axway.com<mailto:jpribeauville@axway.com> http://www.axway.com<http://www.axway.com/> P Pensez à l'environnement avant d'imprimer.

1 0

[libvirt-users] cpu frequency
by Paul Apostolescu 16 Sep '15

16 Sep '15

Is it possible to set the CPU frequency exposed to the guest operating system for a kvm-enabled virtual machine ? The documentation does not mention anything about it. Thanks.

2 1

[libvirt-users] VM in a VM on kvm/qemu
by Digimer 14 Sep '15

14 Sep '15

Hi all, For development reasons, I've setup a pair of VMs (host is Fedora 22) running EL6 as an HA cluster. On these two nodes, I host a 3rd VM (so Fedora 22 -> 2x EL 6.7 -> El 6.7). Currently, 'EL' == CentOS, but I can switch to RHEL proper if need be. To my happy surprise, it actually works! Of course, the two-deep EL6 guest is slow as molasses. I don't really care about making it usably fast because this setup is purely to dev/test the HA cluster VMs. That said, a minimal EL6 install currently takes about 2 hours. So testing deleting/creating guests is very slow. So my question is; Understanding it will never be good performance, is there anything I can do to make the VM-in-a-VM faster? I tried looking for docs on this, looking for ways to tune, CPU/BIOS options to set, etc, without much luck. Most google results are about vmware and other hypervisors. Any pointers/tips/clue-sticks will be much appreciated! -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education?

2 1

[libvirt-users] Backup a VM (using live external snapshot and blockcommit)
by Jérôme 12 Sep '15

12 Sep '15

Hi. I'm following here a conversation that was initiated on Kashyap's website [1]. We have a server we use as a host for virtual machines using KVM (virt-manager used for VM creation) and we would like to setup VM backups. Basically, we're thinking of a backup schedule like "keep 7 daily and 4 weekly backups". We'd rather not shutdown the VM every day so live backups would be nice. I've been doing my best with documentation found on the Internet. It is likely that the path I chose was not the best, so feel free to tell me if I'm asking the wrong questions and I should be proceeding totally differently. AFAIU, backups can be done at filesystem level (using LVM) and at virtualization level (using libvirt). We chose the libvirt way. AFAIU, live backups using libvirt may be done thanks to blockcommit as explained here on the wiki [2]. -> Considering our use case, is this the recommended way? Assuming yes, here is the plan. I wrote a script that does # Create snapshot virsh snapshot-create-as --domain $VM_NAME snap --diskspec vda,file=$VM_DIR/"$VM_NAME"-snap.qcow2 --disk-only --atomic --no-metadata --quiesce # Copy frozen backing file cp $VM_DIR/"$VM_NAME".qcow2 $SNAP_FILEPATH # Blockcommit snapshot back into backing file virsh blockcommit $VM_NAME vda --active --pivot # Remove snapshot file rm $VM_DIR/"$VM_NAME"-snap.qcow2 Variables should be self-explanatory: - VM_DIR is the directory where the VM are stored - VM_NAME is the name of the VM, and its qcow2 file is called VM_NAME.qcow2 - SNAP_FILEPATH is the full path (including name) where the backup should be created Using this scheme, we only keep snapshots for the time of the VM file copy, which is less than a minute. The backing chain is at most 'back <- snap', and most of the time just 'back'. If something ever happens to the VM (human error while being logged as root, attack from the internet,...), we'll turn off the VM, replace its qcow2 file and turn it back on. I understand that this method only saves disk states, so the VM will be started as if it had been powered-off suddenly while running (not quite: thanks to the '--quiesce' option, at least the disks are in a sane state). Not perfect but better than nothing. Those backups are meant to be used only when all else failed, anyway, it's not daily use. -> Does this make sense? Am I missing a feature or even a different approach that would make things simpler or more secure? Am I using libvirt snapshots for what they're not meant to? -> Anything wrong about my snapshot-create-as and blockcommit command lines? May I remove the snapshot with only a rm command? Now, a few side questions, as I might have messed up with the VM I was experimenting with. I used the same command lines as described above, except I didn't pass the '--no-metadata' option. Once the backing file was copied, I deleted the snapshot qcow2 file and thought I was done with it, until I realized the snapshot was still listed by virsh snapshot-list. And I couldn't find a way to delete it. (For the record, I asked on serverfault about that [3].) Ultimately, I found the snapshot's .xml descriptor and deleted it (in fact, moved it) while libvirtd was down. Now, the snapshot is not listed anymore. -> Am I getting away with it? Are there still some traces about that snapshot? Is my VM in an unsafe state? Anything I should do about it? -> What would be the proper way of dropping an external snapshot that was created without the '--no-metadata' option, then blockcommitted? I understand libvirt doesn't do it yet. Thanks for any hint. I naively thought our use case was pretty usual, and I must admit I didn't think I'd have to dive into this complexity, which is why I'm thinking there might be a more "common" way... [1] http://kashyapc.com/2014/10/07/libvirt-blockcommit-shorten-disk-image-chain… [2] http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit [3] http://serverfault.com/questions/721216/delete-orphan-libvirt-snapshot -- Jérôme

3 5

[libvirt-users] Transient VM Usage
by Mcburn 12 Sep '15

12 Sep '15

Hey at all, my Name is Jens-Uwe Sperling. Iám a young student in computer science. I want install a VM for testing at home. i had install a VM with virt-install and the default parameters. (Number cpu, mem etc.) After that i install my OS and configure it. Now i want work on this image in a transient way. So i can use the OS with the given config but every change i do from now should not change my image. I found three ways to do that: - Make a snapshot from my image and kill the snapshot after using. - Using the transient option in the xml file under disk. - Making a qcow2 image and run that. I test the last one but for that i must change my xml file to use the new image. A little bit better explained: i must detach the old disk and attach the new one. So my questions are: - Is the last one stable? - whats your experience with the option transient? - Is the performance when i snapshot the image okay? - Do you had make experience with transient images? Thank you very much P.S. Maybe when you dont understand a sentences ask me. I do my best to explain it better. Jens

5 5