- Users - libvirt List Archives

[libvirt-users] Virsh Fail to Connect to Hypervisor
by Xu, Rongjie (Nokia - CN/Hangzhou) 05 Jan '17

05 Jan '17

Hi, I am upgrading libvirt from 1.2.9 to 2.0.0 and I have successfully make the libvirtd running. However, virsh cannot connect to hypervisor with following errors: virsh # connect error: failed to connect to the hypervisor root@node-55:/usr/local# virsh -c 'qemu:///system' connect error: failed to connect to the hypervisor error: no connection driver available for qemu:///system Can you give me some suggestion about where will be the problem. Thanks. libvirtd is running: root@node-55:/usr/lib/python2.7/dist-packages# ps aux | grep -i libvirtd root 1246963 0.0 0.0 1245780 3428 ? Ssl 06:04 0:00 /usr/sbin/libvirtd --config /etc/libvirt/libvirtd.conf -l Best Regards Xu Rongjie (Max) Mobile:18658176819

2 1

[libvirt-users] Default firewall rules and forwarding to a guest
by Omer Aldemir 04 Jan '17

04 Jan '17

Hello, I am trying to understand how libvirt firewall rules are loaded as I have firewalld and iptables services are disabled. Where is the configuration files for firewall and NAT rules for libvirt? How can I load default firewall rules if I mess things up Also I have realized that followings is default ACCEPT all -- 0.0.0.0/0 192.168.122.0/24 ctstate RELATED,ESTABLISHED but If I am to forward a port for a real IP to internal guest machine I need ACCEPT all -- 0.0.0.0/0 192.168.122.0/24 state NEW,RELATED,ESTABLISHED (NEW state is required) and also of course a forwarding rule iptables -t nat -I PREROUTING -p tcp --dport 3389 -j DNAT --to-destination 192.168.122.16:3389 Is there a place I can make this rules static with LibVirt (not playing with firewalld and/or iptables service for Centos 7) Regards.

2 3

[libvirt-users] how to modified virsh's editor forever?
by dw 29 Dec '16

29 Dec '16

Hi: when I modify VM's xml file,the editor is VI,how to set to other editor forever? Now I can change the editor to VIM from VI with setting environment EDITOR=$my-favorite-editor, but after rebooting,it is VI again. thanks

2 2

[libvirt-users] nwfilters seem fundamentally unusable or unfinished
by J Mo 28 Dec '16

28 Dec '16

Hello! I just spent the last four days working with nwfilters only to decide that they are apparently unusable. I've come to the mailing list seeking input on this subject. First off, please forgive my offensiveness. I'm sure people worked hard on nwfilters and it looks like a lot of effort went into providing this functionality. This is also an extremely difficult subject to get right in the many possible use cases, so I'm very sympathetic to how difficult it would be to try and implement this. However, the existing system didn't work out for me, I've found a number of other people who are saying the same thing (it didn't work out for them), and I don't see any hope continuing down the path of trying to make it work. For now, I've given up on nwfilters and I created a hook script that works with my existing iptables rules and applies network filter policies on specific VM/guests where needed. If you are doing extensive VM network filtering in your environment, how did you do it? I've listed a bunch of my gripes below. Please correct me if I've gotten anything wrong here. I'm new to nwfilters so maybe I overlooked something or I might just misunderstand the whole thing and could be totally wrong. The first and primary problem that I have with nwfilters are that the documentation is poor. There is very little documentation which exists, and that which does exist seems like it was spat out just to fulfill business requirements that some documentation be produced, rather than an effort into creating good usable documentation. I've run into large amounts of undocumented behavior and I don't feel like reading the source code any further to figure out what the intent of these tools were. My second big issue, and a clue very few people actually use nwfilters in the wild, is the low quantity of examples and how-to docs I found while googling. Complex examples just don't seem to exist. Further, of those complex examples I did find, people were often going down the route of creating their own hook script programs to replace nwfilters, indicating that this isn't just me. Additionally... I discovered that nwfilters do not play well with existing system iptables/ebtables rules. There is some good examples on this regarding Red Hat's firewalld and how libvirt's nwfilters does not play well together if you google around a little. It seems like this was just not considered in scope, or the assumption was that the local host would not have any existing iptables/ebtables rules and that libvirt would have complete control over the hypervisor host. There is no documented means of controlling where libvirt inserts it's rules into an existing set of rules, and libvirt creates numerous rules in both ebtables and iptables, making the problem even more complex. nwfilter seems to have been designed with a bias towards user-networking. I am using bridged interfaces, and some features and virsh commands don't apply to this mode of operation. I've been able to produce scenarios where nwfilter would abandon rules after changes had been made to running guests, and the only way I could get rid of them was manual intervention (iptables/ebtables -F -X). There is no command/control to apply an existing nwfilter to a running guest, or to remove/clear the existing nwfilters on a running guest. This item is a huge indication that this isn't a production-ready feature set. I think the worst problem I've run into, however, is that I was able to create very simple nwfilters that either broke networking of the hypervisor system (stopped all traffic), or failed to drop traffic which should have been dropped. I still don't understand why nwfilter is often creating rules in the ebtables "nat" table instead of the "filter" table, where they belong. That one right there is a huge WTF -- packets never get inspected because the rules are in the wrong table! In general, I found the output iptables/ebables rules that nwfilter generated often did not reflect the obvious intent of the rules that went into the nwfilter xml configuration. This abstraction layer produces unreliable and/or confusing results. I put a series of rules into a nwfilter xml file and the iptables/ebtables rules that I get out are insane. Nwfilter rules in = mystery meat out. Priorities are a huge WTF that caused me a lot of grief. Are rules going to be assembled in iptables/ebtables in the order which they are declared in XML? (this is undocumented) If so, why do priorities exist? (undocumented). What is the default priority? Is it zero? (undocumented). Want to create a filter rule that will log certain packets? Apparently there is no logging functionality at all. Can't be done. Anything beyond the most basic packet allow/drop (even reject was an afterthought) isn't supported by nwfilter rules. Thanks for reading

1 0

Re: [libvirt-users] Audio in Windows 10 VM is distorted. Using ALSA.
by Žilvinas Žaltiena 22 Dec '16

22 Dec '16

Hi, I found the main reason for sound distortions on my system is guest timer configuration. The working one is: <clock offset="localtime"> <timer name="hypervclock" present="yes"/> <timer name="hpet" present="no"/> <timer name="rtc" present="yes" track="guest" tickpolicy="delay"/> </clock> ... <qemu:commandline>a <qemu:arg value='-machine'/> <qemu:arg value='kernel_irqchip=on'/> <qemu:arg value='-cpu'/> <qemu:arg value='host,migratable=no,+invtsc,hv_time,+kvm_pv_eoi,hv_relaxed,hv_spinlocks=0x1fff,hv_vendor_id=nv_fuck_you!,kvm=off'/> </qemu:commandline> The important part here is "host,migratable=no,+invtsc". It gives guest the invariant TSC (CPU must support it). This is a bit of a hack. Everything, except migratable=no, can be configured through proper XML elements, however +invtsc requires migratable=no, and I don't know a way to pass it other than using qemu:arg. Note it completely overrides qemus -cpu parameter created from other tags. Don't paste my qemu:arg of it. Run your VM without it, check libvirt log, and copy from it what is passed to qemu as -cpu parameter, then add migratable=no,+invtsc. 2016-12-20 4:41 GMT+02:00 Manuel Ullmann <ullman.alias(a)posteo.de>: > Hi, > > I can’t seem to find a solution for my last VM issue. > I have distorted sound, when I play the Windows 10 device test > sound. Only the Windows sound is affected. Mpd of the host is playing just > fine > meanwhile. I am using ich9 as emulated card, which is detected and > installed correctly. The VM is using vfio-igd passthrough, so vnc or > spice are not used. > I tried to match the Windows driver configuration, which only supports > 16 bit output. I have a 24 bit USB headphone amplifier, which does not > support it (S32_LE only). Trying direct playback on the PCH card jack > did not help though. > > The headphone amplifier is connected via optical Toslink, so there is > standard snd_hda_intel output used (snd_usb_audio is not involved). > Passing the USB part through I get much clearer output, but still have > popping sounds. Googling around, they seem to be quite common on Windows > 10, although I had it working fine on two bare-metal machines. > > I have tried fixed settings matching the ones of the dmixed device > too. Don’t know, what is polled with enabled poll option. I also tried > sdl and pulseaudio, which did not help. For the latter not so surprising > since it is an Alsa pipe. The former was worse. > > The goal of this setup is having the same playlist state on both > systems and using the better audio framework for music playback (Windows > uses > too much software layers). Of course the popping sounds on audio device > passthrough also would be annoying, but that might be a different issue. > > Best regards, > Manuel > > used alsa device: > pcm.dmixed { > type asym > playback.pcm { > # See plugin:dmix at http://www.alsa-project.org/ > alsa-doc/alsa-lib/pcm_plugins.html > type dmix > > # Don't block other users, e.g. the Timidity midi-player > daemon > # http://www.alsa-project.org/ > alsa-doc/alsa-lib/pcm_plugins.html > ipc_key_add_uid false > > ipc_key 1025 > ipc_perm 0660 > ipc_gid audio > > # Don't put the rate here! Otherwise it resets the rate & > channels set below, as shown by: cat /proc/asound/card0/pcm0p/sub0/ > hw_params > slave { > # 2 for stereo, 6 for surround51, 8 for surround71 > channels 2 > pcm { > format S16_LE > #format S32_LE > > #rate 44100 > rate 48000 > > # http://www.alsa-project.org/ > alsa-doc/alsa-lib/pcm_plugins.html > # Maybe helps > nonblock true > type hw > card "PCH" > device 0 > subdevice 0 > } > > # mplayer2 chooses 1024 > # period_size 512 with buffer_size 16384 stops > crackling in xmame > # 320 breaks flash - https://bbs.archlinux.org/ > viewtopic.php?id=129458 > #period_size 512 > period_size 1024 > > # 4096 might make sound crackle > # mplayer2 chooses 8192. Half-Life 2 chooses 16384. > # If too large, use CONFIG_SND_HDA_PREALLOC_SIZE= > 2048 > buffer_size 8192 > } > } > capture.pcm "schneeball" > } > > libvirt xml snippets: > > <sound model='ich9'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x09' > function='0x0'/> > </sound> > ... > <qemu:env name='QEMU_AUDIO_DRV' value='alsa'/> > <qemu:env name='QEMU_DAC_FIXED_SETTINGS' value='0'/> > <qemu:env name='QEMU_DAC_TRY_POLL' value='0'/> > <qemu:env name='QEMU_DAC_TIMER_PERIOD' value='0'/> > <qemu:env name='QEMU_DAC_BUFFER_SIZE' value='0'/> > <qemu:env name='QEMU_DAC_PERIOD_SIZE' value='0'/> > <qemu:env name='QEMU_DAC_DEV' value='dmixed'/> > > _______________________________________________ > libvirt-users mailing list > libvirt-users(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users

2 1

[libvirt-users] how to create container image for an existing container
by WANG Cheng D 21 Dec '16

21 Dec '16

Dear all, I installed 8 containers using "yum --installroot=/root/fedora16lxc" to create the container filesystem. Now I want to manage these containers with openstack. So I need to deploy these containers by openstack which needs the container image. Can anyone tell me how to export my existing container's image? I am not sure if openstack can create container without an image file. And I don't want to use Docker. Thank you in advance. Cheng

1 0

[libvirt-users] Audio in Windows 10 VM is distorted. Using ALSA.
by Manuel Ullmann 21 Dec '16

21 Dec '16

Hi, I can’t seem to find a solution for my last VM issue. I have distorted sound, when I play the Windows 10 device test sound. Only the Windows sound is affected. Mpd of the host is playing just fine meanwhile. I am using ich9 as emulated card, which is detected and installed correctly. The VM is using vfio-igd passthrough, so vnc or spice are not used. I tried to match the Windows driver configuration, which only supports 16 bit output. I have a 24 bit USB headphone amplifier, which does not support it (S32_LE only). Trying direct playback on the PCH card jack did not help though. The headphone amplifier is connected via optical Toslink, so there is standard snd_hda_intel output used (snd_usb_audio is not involved). Passing the USB part through I get much clearer output, but still have popping sounds. Googling around, they seem to be quite common on Windows 10, although I had it working fine on two bare-metal machines. I have tried fixed settings matching the ones of the dmixed device too. Don’t know, what is polled with enabled poll option. I also tried sdl and pulseaudio, which did not help. For the latter not so surprising since it is an Alsa pipe. The former was worse. The goal of this setup is having the same playlist state on both systems and using the better audio framework for music playback (Windows uses too much software layers). Of course the popping sounds on audio device passthrough also would be annoying, but that might be a different issue. Best regards, Manuel used alsa device: pcm.dmixed { type asym playback.pcm { # See plugin:dmix at http://www.alsa-project.org/alsa-doc/alsa-lib/pcm_plugins.html type dmix # Don't block other users, e.g. the Timidity midi-player daemon # http://www.alsa-project.org/alsa-doc/alsa-lib/pcm_plugins.html ipc_key_add_uid false ipc_key 1025 ipc_perm 0660 ipc_gid audio # Don't put the rate here! Otherwise it resets the rate & channels set below, as shown by: cat /proc/asound/card0/pcm0p/sub0/hw_params slave { # 2 for stereo, 6 for surround51, 8 for surround71 channels 2 pcm { format S16_LE #format S32_LE #rate 44100 rate 48000 # http://www.alsa-project.org/alsa-doc/alsa-lib/pcm_plugins.html # Maybe helps nonblock true type hw card "PCH" device 0 subdevice 0 } # mplayer2 chooses 1024 # period_size 512 with buffer_size 16384 stops crackling in xmame # 320 breaks flash - https://bbs.archlinux.org/viewtopic.php?id=129458 #period_size 512 period_size 1024 # 4096 might make sound crackle # mplayer2 chooses 8192. Half-Life 2 chooses 16384. # If too large, use CONFIG_SND_HDA_PREALLOC_SIZE=2048 buffer_size 8192 } } capture.pcm "schneeball" } libvirt xml snippets: <sound model='ich9'> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </sound> ... <qemu:env name='QEMU_AUDIO_DRV' value='alsa'/> <qemu:env name='QEMU_DAC_FIXED_SETTINGS' value='0'/> <qemu:env name='QEMU_DAC_TRY_POLL' value='0'/> <qemu:env name='QEMU_DAC_TIMER_PERIOD' value='0'/> <qemu:env name='QEMU_DAC_BUFFER_SIZE' value='0'/> <qemu:env name='QEMU_DAC_PERIOD_SIZE' value='0'/> <qemu:env name='QEMU_DAC_DEV' value='dmixed'/>

2 1

[libvirt-users] virDomainBlockInfo for local volume
by Shahar Havivi 21 Dec '16

21 Dec '16

Hi, I am using virStorageVolGetInfo to get the volume size virStorageVol.download to download a normal file for VDSM project. I want to add support for block devices as well, I was able to see the size via virDomainBlockInfo and download via virDomain.blockPeek which is works fine for both file and block device. 1. Can I depend on virDomainBlockInfo for non block devices? 2. Does the virDomainBlockInfo return the correct physical size for normal file? 3. Performance wise do we have a difference between virStorageVol.download and virDomain.blockPeek? Assuming the VMs are down, this is the code I intend to use for all formats: vm = con.lookupByName(options.vmname) info = vm.blockInfo(src) physical = info[2] off = 0 size = 0 with open(dest, 'w+') as f: while off < physical: if (physical - off) < bufsize: size = physical - off else: size = bufsize buf = vm.blockPeek(src, off, size) f.write(buf) off += size

2 3

[libvirt-users] Trying virgl in fedora 25
by Gianluca Cecchi 15 Dec '16

15 Dec '16

Hello, I'm trying to test what found here: http://blog.wikichoon.com/2016/05/spice-openglvirgl-acceleration-on.html and here: https://www.kraxel.org/blog/tag/virgl/ My system is a fedora 25 laptop, born in version 23 and gradually updated to 24 and 25 now. I had a fedora 25 guest that worked ok with "normal"spice and I'm trying to configure with virgl Main components currently installed on host: qemu-kvm-2.7.0-7.fc25.x86_64 libvirt-2.2.0-2.fc25.x86_64 virt-manager-1.4.0-4.fc25.noarch VirtualGL-2.4-7.fc25.x86_64 Commands executed to modify configuration: [root@ope46 qemu]# virt-xml f25 --confirm --edit --video clearxml=yes,model=virtio,accel3d=yes --- Original XML +++ Altered XML @@ -94,8 +94,9 @@ <address type="pci" domain="0x0000" bus="0x00" slot="0x04" function="0x0"/> </sound> <video> - <model type="virtio" heads="1" primary="yes"/> - <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x0"/> + <model type="virtio"> + <acceleration accel3d="yes"/> + </model> </video> <redirdev bus="usb" type="spicevmc"> <address type="usb" bus="0" port="1"/> Define 'f25' with the changed XML? (y/n): y Domain 'f25' defined successfully. [root@ope46 qemu]# virt-xml f25 --confirm --edit --graphics clearxml=yes,type=spice,gl=on,listen=none WARNING qemu/libvirt version may not support spice GL --- Original XML +++ Altered XML @@ -86,9 +86,9 @@ </channel> <input type="mouse" bus="ps2"/> <input type="keyboard" bus="ps2"/> - <graphics type="spice" autoport="yes"> - <listen type="address"/> - <image compression="off"/> + <graphics type="spice" autoport="no"> + <gl enable="yes"/> + <listen type="none"/> </graphics> <sound model="ich6"> <address type="pci" domain="0x0000" bus="0x00" slot="0x04" function="0x0"/> Define 'f25' with the changed XML? (y/n): y Domain 'f25' defined successfully. [root@ope46 qemu]# I don't know if the WARNING above is a generic one or if it makes any pre-check to system... Anyway both from vrt-manager and virsh I get error [root@ope46 qemu]# virsh start f25 error: Failed to start domain f25 error: internal error: process exited while connecting to monitor: 2016-12-13T11:18:37.784324Z qemu-system-x86_64: egl: no drm render node available 2016-12-13T11:18:37.784375Z qemu-system-x86_64: Failed to initialize EGL render node for SPICE GL [root@ope46 qemu]# and this in /var/log/libvirt/qemu/f25.log: 2016-12-13 11:18:37.584+0000: starting up libvirt version: 2.2.0, package: 2.fc25 (Fedora Project, 2 016-11-14-21:04:29, buildvm-25.phx2.fedoraproject.org) qemu version: 2.7.0(qemu-2.7.0-7.fc25), host name: ope46.ceda.polimi.it LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-k vm -name guest=f25,debug-threads=on -S -object secret,id=masterKey0,format= raw,file=/var/lib/libvirt /qemu/domain-2-f25/master-key.aes -machine pc-i440fx-2.6,accel=kvm,usb=off,vmport=off -cpu Nehalem - m 4096 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid d4c23620-b805-4656-9b97-d9d4ab9d ba63 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/ var/lib/libvirt/qemu/domain-2- f25/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x8 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive if=none,id=drive-ide0-0-0,readonly=on -device ide-cd,bus=ide.0,unit=0,drive= drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive file=/var/lib/libvirt/images/ f25.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive- scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2 -netdev tap,fd=26,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:17:49:49,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev= charchannel0,id=channel0,name=com.redhat.spice.0 -spice port=0,disable-ticketing,gl=on,seamless-migration=on -device virtio-vga,id=video0,virgl=on,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=1 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on char device redirected to /dev/pts/1 (label charserial0) 2016-12-13T11:18:37.784324Z qemu-system-x86_64: egl: no drm render node available 2016-12-13T11:18:37.784375Z qemu-system-x86_64: Failed to initialize EGL render node for SPICE GL 2016-12-13 11:18:37.891+0000: shutting down What can I check? Any pre-requisite in laptop video adapter or other? Thanks in advance, Gialuca

2 1

Re: [libvirt-users] virsh not detecting hugepage mount; disabled by config?
by Manuel Ullmann 14 Dec '16

14 Dec '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Thanks a lot you two, yes hugetlbfs is not mounted, when libvirtd is started… It was a long night. Did put it to fstab and since I do not allocate them on regular boots, it won’t eat my ram (that was the main consideration for doing it like this). As a last means before going to sleep, I added <qemu:arg value='-numa'/> <qemu:arg value='node,memdev=mem42'/> <qemu:arg value='-object'/> <qemu:arg value='memory-backend-file,size=6G,mem-path=/var/lib/hugetlbfs,share=on,id=mem42'/> to the xml which worked too (surprise), but I have it working now in the intended way. Then I never got to the last part of the qemu.conf option comment so I had to do another 3 reboots. Well, reading helps. So the fstab entry reads now: hugetlbfs /var/lib/hugetlbfs/libvirt/qemu hugetlbfs relatime,rw,pagesize=1073741824 0 0 with /var/lib/hugetlbfs being the mount point in qemu.conf. At least I didn’t forget to create the mount point before rebooting. Best regards, Manuel > Hi, > > I use gentoo with desktop+systemd profile to run Windows 10 VM with pci > passthrough and hugetlbs. > > Things I had to do for hugetlbs: > 1) Made sure their support was enabled in kernel > 2) Passed parameters for their allocation to kernel. There are other > ways, but I use 1GB page size and I have to allocate them before memory > gets fragmented. Note, you do that with hugepages=3072. > 3) Passed hugetlbs settings to libvirt VM domain (XML). > > That is it. I don't mount them myself. I think (can't check now) they > are automounted to /dev/hugetlbs. By default, libvirtd runs as root, and > qemu as user qemu. Consuming hugetlb and releasing them should be > transparent. > > I suggest starting without softlevel=qemuvm into default runlevel, and > then check /proc/meminfo. Hugetlbs total and free should be > 0. Do the > same with qemuvm runlevel. Maybe this runlevel misses something. > > On 2016-12-14 00:05, Manuel Ullmann wrote: >> Hi, >> >> I’m struggling with virsh not detecting my hugepage mount. >> >> I have the following kernel command line: >> BOOT_IMAGE=/vmlinuz-4.8.13-gentoo root=/dev/mapper/gensd-gentoo ro quiet >> splash intel_iommu=on video=efifb:off,vesafb:off,simplefb:off >> splash=verbose,theme:livedvd-aurora kvm.ignore_msrs=1 >> transparent_hugepage=never hugepages=3072 softlevel=qemuvm >> >> My startup script outputs the following: >> hugetlbfs /var/lib/hugetlbfs hugetlbfs >> rw,relatime,pagesize=2097152,uid=77,gid=77,mode=0770 0 0 >> [2016.12.13 22:22:50 virsh 2808] ERROR Failed to start domain win10 >> [2016.12.13 22:22:50 virsh 2808] ERROR internal error: hugetlbfs >> filesystem is not mounted or disabled by administrator config >> virsh was unsuccessful >> >> So hugetlbfs is definitively mounted, but virsh does either not detect >> it or some magical option, that I’ve not found in a day searching for >> it, disables it (the documentation could explain that better). Since the >> Ubuntu guys refer to the KVM_HUGEPAGES environment, I tried adding it to >> start-stop-daemon environment, but it seems non-relevant. 77 is the qemu >> user id, but I’m quite sure the permission issues were excluded (tried >> root permissions as well). Besides I had permission errors occasionally >> occasionally and don’t have them anymore. If you could provide a hint to >> the magical administrator configuration option, that would be helpful. >> Tried hugeadm as well, pointing the config to the correct destination. >> >> Thanks in advance, >> Manuel >> >> PS: >> The virsh script reads like this: >> #!/bin/sh >> cmdline="$(cat /proc/cmdline)" >> if [[ "${cmdline##* }" == "softlevel=qemuvm" ]]; then >> mount -o rw,relatime,pagesize=2097152,uid=77,gid=77,mode=0770 -t >> hugetlbfs hugetlbfs /var/lib/hugetlbfs >> sysctl kernel.shmmax=6442450944 >> cat /proc/mounts | grep hugetlb >> /var/log/virsh.log >> sed -i -e '/^hugetlb/{s/^/\#/}' /etc/libvirt/qemu.conf >> counter=0 >> while [ "${counter}" -lt 10 && ! -S /var/run/libvirt/libvirt-sock ]; do >> sleep 1 >> counter=$(( ++counter )) >> done >> if [ $counter -gt 9 ]; then >> echo "libvirtd socket generation timed out" >> /var/log/virsh.log >> fi >> if pidof libvirtd &>/dev/null; then >> LC_ALL=C /usr/bin/virsh -l /var/log/virsh.log start win10 >> if [ $? -gt 0 ]; then >> echo "virsh was unsuccessful" >> /var/log/virsh.log >> reboot >> fi >> else >> echo "libvirtd is not started" >> /var/log/virsh.log >> reboot >> fi >> fi >> >> reboot is more convenient, since this is a vfio-igd passthrough vm. >> >> >> _______________________________________________ >> libvirt-users mailing list >> libvirt-users(a)redhat.com >> https://www.redhat.com/mailman/listinfo/libvirt-users >> -----BEGIN PGP SIGNATURE----- iQQcBAEBCAAGBQJYUVAKAAoJELgK9xQKkpX6sTof/2fdLX9qjiNgecKEIzHKEjBY ln6o7E0nMY796Jf3HQ/v620uVZS3Nf4dRSFC9NVetzAgVcQizwko0ikVDsaCZlNP 5HojcRm2SK8c5CgU/ZLdLPp73PgrORtKYytYldhPQFebgOpNCJGzWAPXGnoLK78s aHsKGKb5R79+K2Bq5DAQGR5N9wiV84Oi+afNjBunjj1dT+80YPAAtXuRKkDdD3lQ hVBEdzgRLWW48FdEhIp2TlTJCyx4OwMGnIXaOPXrQSyMW6Omn49ZXYqwIgsOW45S bzFZ4BPuqhrANne4YDPjuxwtL65YUKAyHZWl/bTBmqkFrpjecxYDnlg219t2KsiM k3W9GQ0CWR74f0lJLULaV+ome13ydga5pDRe6+dyi7g0O7/4DTPuxQTRo07UiA/i dQmvtzTAbGdSpGqyFBQqIFGMG4sB8kypXp1PIK06jX1Muon6WCdzAzt1IztLeuSW qUj/srdnD9rLWWPlIV2NCZ3E5Da4szRD8gbhNIG2hg+Ss50pLdIFwlUbfksryY7B B6L6KmpOw4LrpCZVFBeFhG5lFns9YSvYNKvSBRwJaxl838j8Kr8B1bo51nMYERL1 wJXK9IyFqx8jkbmFvfwXij5lx3DFBrLEQwymGmaLmJ4FQmnA9491L2F3K+NyG8kX Yi/w+Xh9ZARoRy8/2SmVYwvB1vZkFpf04adocHxIYMT1P3ZLpCktu3P/DMdkdR26 DcnQedl7qbf7NeldxMiY0zTAti85VFuQggFQlRrB36pRdOXvFMk3mNLBiifICNvP 32sTl/9HnmscWCTSebmK/KjQjrLf9ijbc3V942WziwkEyDbOhfTUn0JfcZJl0FdM OQ0j00t5wv14KFPP/hpWqRiypwXpboHLpB4k718NZElObUOob0ziz6PJc5iCzJDW AkNbO1sEDgWN/pPorAYKPtre3TV6qk/k6A13zgNmMdZA4ZHRq6dsZLzCLnEaLwJE G5WFveDyi4COVpelysArTPrw6aL4LAzIhkRN5A5YCANgsPtnhjql6XmL3sTSN93Z R42klgPKNZVq5Bkdp2EpE70X+F/4j2jhRNznVp3YDU+6q6aNWHdqw7jCAhEji0aA 49gR3tIUgXp1883zc0vSFIMnCwYQQoCjqGpVZXWLtbxAmJrz5c4XeUCnpplfJW3Z jRS19MEy6HgKmdkq1a4bRG5XFc87Ga2JWqwSXpGb1EsMvyMU3CQq47D98WqaeC9p JTOuLMpYvlH+EEbEkL/deysLGVZ7QDTr5P4L+wOzN9jhSOrnIoNlVU5DVP7dhT2L z1d3UY3cFhoVFLKyfbLF+flK7Y5aygQ/eO/+MlXmd9TI+2qTVehNSXiYTEnnsO0= =1DU1 -----END PGP SIGNATURE-----

1 0