- Users - libvirt List Archives

[libvirt-users] NVidia Grid on libvirt.
by Dominique Ramaekers 10 Aug '15

10 Aug '15

Hi, I'm investigating the possibility to use a Nvidia Grid graphics card to use in libvirt. I found this resource on the subject from the end of 2014: http://www.linux-kvm.org/images/b/b3/01x09b-VFIOandYou-small.pdf It should be possible. However libvirt didn't support it at that time. Does anyone has experience on the subject? Greetings, Dominique.

2 1

[libvirt-users] NVidia Grid on libvirt.
by Dominique Ramaekers 09 Aug '15

09 Aug '15

Hi, I'm investigating the possibility to use a Nvidia Grid graphics card to use in libvirt. I found this resource on the subject from the end of 2014: http://www.linux-kvm.org/images/b/b3/01x09b-VFIOandYou-small.pdf It should be possible. However libvirt didn't support it at that time. Does anyone has experience on the subject? Greetings, Dominique.

1 0

[libvirt-users] Enabling capabilities in a container
by Peter Steele 09 Aug '15

09 Aug '15

I'm using libvirt_lxc to create and manage various containers. I need to enable certain capabilities in a container to support ctdb, and as a quick solution I decided to just enable them all. I *thought* this would do the trick, adding the following XML to my container config: <features> <capabilities policy='allow'> </capabilities> </features> After adding this to my container, I restarted it and tried to start the ctdb service again: # systemctl start ctdb.service Job for ctdb.service failed. See 'systemctl status ctdb.service' and 'journalctl -xn' for details. # systemctl status ctdb.service ctdb.service - CTDB Loaded: loaded (/usr/lib/systemd/system/ctdb.service; disabled) Active: failed (Result: exit-code) since Tue 2015-08-04 14:10:39 PDT; 8s ago Process: 4612 ExecStart=/usr/sbin/ctdbd_wrapper /run/ctdb/ctdbd.pid start (code=exited, status=1/FAILURE) Aug 04 14:10:37 pws-01 systemd[1]: Starting CTDB... Aug 04 14:10:37 pws-01 ctdbd[4629]: CTDB starting on node Aug 04 14:10:37 pws-01 ctdbd[4631]: Starting CTDBD (Version 2.5.4) as PID: 4631 Aug 04 14:10:37 pws-01 ctdbd[4631]: Created PID file /run/ctdb/ctdbd.pid Aug 04 14:10:37 pws-01 ctdbd[4631]: Unable to set scheduler to SCHED_FIFO (Operation not permitted) Aug 04 14:10:37 pws-01 ctdbd[4631]: CTDB daemon shutting down Aug 04 14:10:39 pws-01 ctdbd_wrapper[4612]: CTDB exited during initialisation - check logs. Aug 04 14:10:39 pws-01 systemd[1]: ctdb.service: control process exited, code=exited status=1 Aug 04 14:10:39 pws-01 systemd[1]: Failed to start CTDB. Aug 04 14:10:39 pws-01 systemd[1]: Unit ctdb.service entered failed state. This implies that the container still doesn't have access to the capabilities it needs to use. I believe this error in fact is caused by the container not having the sys_nice capability. So I tried to allow this specific capability using: <features> <capabilities policy='default'> <sys_nice state='on'/> </capabilities> </features> This did not work either. So, what *is* the correct way to add capabilities to a container?

1 1

[libvirt-users] Cannot boot libvirt guests with OVMF. Raw qemu-kvm works as expected
by Ryan Barry 07 Aug '15

07 Aug '15

Using: edk2.git-0-20150803.b1141.ga0973dc.x86_64 edk2.git-ovmf-x64-0-20150802.b1139.gb234418.noarch On Fedora 22. Provisioning a i440FX system in virt-manager and attempting to boot results in successful EFI initialization, but the VM exits ungracefully after the bootloader (with F22 and CentOS 7 installer images). There's no really useful information in any of the logs. Using qemu-kvm directly (qemu-kvm -bios /usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd -m 1G -cdrom ~rbarry/Downloads/Fedora-Server-netinst-x86_64-22.iso) boots and loads successfully. What's the difference here? Where can I go for troubleshooting? libvirt XML is below: <domain type='kvm'> <name>fedora22</name> <uuid>7f363d28-881f-4240-97eb-9b8d49cfb282</uuid> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/var/lib/libvirt/qemu/nvram/fedora22_VARS.fd</nvram> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu mode='custom' match='exact'> <model fallback='allow'>Haswell-noTSX</model> </cpu> <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/bin/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/images/fedora22.qcow2'/> <target dev='vda' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/home/rbarry/Downloads/Fedora-Server-netinst-x86_64-22.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <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='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> <interface type='network'> <mac address='52:54:00:35:b6:00'/> <source network='default'/> <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='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/fedora22.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0'/> <address type='virtio-serial' controller='0' bus='0' port='2'/> </channel> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='spice' autoport='yes'> <image compression='off'/> </graphics> <sound model='ich6'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </sound> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <redirdev bus='usb' type='spicevmc'> </redirdev> <redirdev bus='usb' type='spicevmc'> </redirdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain>

2 6

[libvirt-users] UDP unicast network backend (QEMU)
by Stanley Karunditu 04 Aug '15

04 Aug '15

In 2012 QEMU added UDP unicast network backend support https://github.com/qemu/qemu/commit/0e0e7facc775e9bb020314f48751b3d09f316c8… Checked latest libvirt on the git repo, and didn't see this as an option. So tried to use the mcast tunnel mode. I keep getting duplicate packets with BPDUs and LLDP packets going between the Point to point connection between the VMs. VMs have bridges on them. When I used the TCP tunnel interface, if the client came up before the server end, the connection failed to establish. So both methods not super reliable. If I manually change the netdev settings to use unicast udp tunneling the connection is way more stable just like the GNS3 connections. Has anyone written support for UDP unicast network backend for QEMU and the patch is awaiting review? Searched mailing list and couldn't find a bug covering this. Just want to be sure no one has worked on this before creating a patch to add this support.

2 1

[libvirt-users] How to run libvirtd as non root user
by Anshul Arora (akarora) 31 Jul '15

31 Jul '15

Team, I note that libvertd runs as root user that is against the least privilege security model. root 307278 1 0 Jun20 ? 04:16:46 /usr/sbin/libvirtd -listen Appreciate pointers to alternate options that user could configure as a potential mitigation plan? Thanks, -Anshul

3 2

[libvirt-users] libvirt-1.2.17 I can't define lxc container
by Marcin Mirosław 30 Jul '15

30 Jul '15

Hello! I'd like to set up my first lxc container using libvirt. I'd like to start using the simplest configuration and next add things I need. So I've got xml as below: <domain type='lxc'> <name>vm1</name> <memory>32768</memory> <os> <type>exe</type> <init>/init</init> </os> <vcpu>1</vcpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <features> <capabilities policy='on'> </capabilities> </features> <devices> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='mount'> <source dir='/opt/vm-1-root'/> <target dir='/'/> </filesystem> <interface type='network'> <source network='default'/> </interface> <console type='pty' /> </devices> </domain> When I try to define container I'm getting: virsh # define /tmp/vm1.xml error: Failed to define domain from /tmp/vm1.xml error: invalid argument: could not find capabilities for ostype=exe domaintype=lxc I can't also find similar problem using web search engine. Maybe someone here can give me advice? Marcin # virsh -V Virsh command line tool of libvirt 1.2.17 See web site at http://libvirt.org/ Compiled with support for: Hypervisors: QEMU/KVM LXC VMWare ESX Test Networking: Remote Bridging Interface udev Nwfilter Storage: Dir Filesystem SCSI LVM Miscellaneous: Daemon Nodedev Secrets Debug Readline Modular

2 2

[libvirt-users] Custom bios image for qemu
by Phil Tooley 29 Jul '15

29 Jul '15

Hello all, So I am trying to get a qemu guest to use a custom patched seabios image rather than the default /usr/share/qemu/bios.bin I have tried changing the domain config file to include either: <os> --SNIP-- <loader readonly='yes' type='rom'>/home/telemin/qemu/seabios_patched.bin</loader> </os> OR domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0' --SNIP-- <qemu:commandline> <qemu:arg value='-smbios'/> <qemu:arg value='file=/home/telemin/qemu/seabios_patched.bin'/> </qemu:commandline> --SNIP-- And neither of these approaches result in the new seabios_patched.bin being used. I am clearly missing something here, can anyone with some more experience tell me what it is please? Many Thanks Phil Tooley

2 2

Re: [libvirt-users] Migrate Win2k3 to KVM
by Pierre Schweitzer 26 Jul '15

26 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Regarding product activation, there's nothing I can do. You've to call Microsoft to re-activate your W2k3 licence. This is due to hardware change on virtualization. Regards, On 25/07/2015 20:54, Ruzsinszky Attila wrote: > Hi Pierre, > > I think the boot is working! ;-) I changed my image to IDE disk and > W2k3 started booting but wants Product Activation ... What can I do > with this? I can't login. I think it is a loop when I click on OK > button in the warning window. > > TIA, Ruzsi > - -- Pierre Schweitzer <pierre at reactos.org> System & Network Administrator Senior Kernel Developer ReactOS Deutschland e.V. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVtLm1AAoJEHVFVWw9WFsLyUsQAKv0EnHnYZ+PkWMuRPvCS4xa WnvnEkwIBxqrSXIG/b8mZ676mb+3ba9nZO22HZTKqqAndCrxQ46vsC87YSw9akcX +Dt1EC+BWMwclG4x/LSFM44uN6ZuqRqXNWIHL1B/fZ4DUO41RQDzX0yokc16+lxE OwzQQ5Rf8gYqHRBP/CdbrrPbgVnoa08ejRt0uwWhrMJtWwcFYz4YmPHBDSJV+GM7 lp6uU835mWDRR2DzIQ7gpDAAu3f1O2TPy15wFlidVn6XqjIcxIF9QqDj+ktQmyk+ im+PeVeqTGL75H2hyQMcx8z/kJm3ZktuqlTWbY4JvpNqBSodTYjVM9QnDsGf9JR7 Wvb6iEvxkLzGODXQ+YS2NOF4NJfTV0Wg1aodx5y+seMVlmAmFapq9QgNU39JTjg/ reMcVqjj3Es3DrQWWTZw0Mcvg2E/zxM3I58zg4Flylfxb/Krd3W4GRchwSx+/3u5 pA2Xb+Qq6Db/rWljVKHjN+LYW9llhr+/yu/W9+FYv2qJl0zZnHui+uDgljx1Byax urjYE2XCfSzDXvayVo7xTbSzpBi7MX0NlJZoK7kY7i4f7IV4ZSQZ+7owa05pH05v KQwjZzuSClFItIKARQ3JqXhi1ybmCH3jsoRbls6grX/tfkpzBrn1KspCFGMq7Fl/ LmU5uWVuO0o5YmQppckz =VNFx -----END PGP SIGNATURE-----

1 0

Re: [libvirt-users] Migrate Win2k3 to KVM
by Pierre Schweitzer 25 Jul '15

25 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 25/07/2015 13:55, Ruzsinszky Attila wrote: > Hi Pierre, > > I got enough inspiration typing in the needed reg. keys. > > Here is a difference: What you wrote me: > > intelide >> { ErrorControl(REG_DWORD): 00000001 Group(REG_SZ): System Bus >> Extender Start(REG_DWORD): 00000000 Tag(REG_DWORD): 00000004 >> Type(REG_DWORD): 00000001 ImagePath(REG_SZ): >> system32\drivers\intelide.sys } >> > > My reg. keys: > > \ControlSet001\Services\IntelIde> ls Node has 0 subkeys and 5 > values size type value name [value if > type DWORD] 4 REG_DWORD <ErrorControl> 1 > [0x1] 40 REG_SZ <Group> 4 REG_DWORD <Start> > 4 [0x4] 4 REG_DWORD <Tag> 4 [0x4] 4 > REG_DWORD <Type> 1 [0x1] > > \ControlSet001\Services\IntelIde> cat Group Value <Group> of type > REG_SZ, data length 40 [0x28] System Bus Extender > > Do I have to change? Start and ImagePath are different. Let ImagePath, it should match your system more closely (and differences might be just in case, so no real matter). But you absolutely have to change Start. If Start isn't at 0x0, then, the driver will not be loaded at boot, and you won't be able to boot your Win2k3. - -- Pierre Schweitzer <pierre at reactos.org> System & Network Administrator Senior Kernel Developer ReactOS Deutschland e.V. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVs6/oAAoJEHVFVWw9WFsL8vcQAMd0C5zPHdwzoANR5peBl9mJ Z/9jY9/mF7E29yAmwKm0d3vXKgtja7v5vWar5rbyvSDpNKnUjQlwVdJEiGWwpcko 21xP7dC/IGGeEtn38wtfKOVZ0OQOAE1zs6YqbTDYSm1WgtTKNHvWjYQiPCwPmIYi cWqmXxF0SF2ADEiRjYlqZT2cd5Ersu+hy+bRlYGUxi4t2KhQf5vnz3kqZeY2BbDZ pG6xKRTvMDRqKiFdd3arUQ8ewJGjKvmKnGWz1ZgCvo75uzGoiuGmKDkIF6FJb3/+ +8nnFdYjd5b2NhryhIawxeZphAyMfIgt6Le1mFGgg2EBOD6xhFWv3WOLGSV775uu 29Q0+tPTE1+o8Ed1mtgaS1mRB/huPCMOMJtJS4sZ70wRdCz6i1pcYhQgXr44O1lz JzZxhnl79Zz0v/rlRIX2EF7t41rvIf//wgoA6jIhI7B15eGPlfGUaU2tMGGf8yGu yTcmuPKzfR1g8GJzYpNT8wFawEFOe3x2dRjA2kUdvUR1FziNdrUNxwpVOOBuOlX5 efVLf2ms+OOyIOnbSyzMOXL55K7a4HnHacCEjEvzvt60m4ZM7hcRGEE5L8Hi9LGP z2eDwRtefK6bL4Pg3hjkpBtsG42Pr6y5904MRGtLqwvmtWlTF+txafwahXQALpSi 5QEdWTWMQdI/LBZ/1LWz =tFUM -----END PGP SIGNATURE-----

1 0