July 2017 - 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] Increasing video memory available to Windows
by Alex 15 Aug '17

15 Aug '17

Hi, I have a fedora25 system with a Windows10 host and would like to use it for photoshop. However, it complains the video memory is too low. I'm using the QXL driver and it appears to be limited to 256MB? I've installed the Red Hat QXL driver in Windows. I have 4GB of memory allocated overall, and could allocate more if necessary. How do I increase the available video memory? Photoshop reports that it's detected less than 512MB and isn't operating properly. When I view "Adapter Properties" is reports there is 2047 MB of available graphics memory and 2047 MB Shared System Memory. Attempts to modify with "virsh edit" the vram and other video-related variables for the host have failed. Included below is my qemu XML configuration. Any idea greatly appreciated. <domain type='kvm'> <name>alex-win10</name> <uuid>337f9410-3286-4ef5-a3e8-8271e38ea1e5</uuid> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu placement='static'>2</vcpu> <os> <type arch='x86_64' machine='pc-i440fx-2.4'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> <vmport state='off'/> </features> <cpu mode='host-model'> <model fallback='allow'/> </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/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/images/alex-win10.qcow2'/> <target dev='vda' bus='virtio'/> <boot order='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> <disk type='block' device='cdrom'> <driver name='qemu' type='raw'/> <source dev='/dev/sr0'/> <target dev='hdb' bus='ide'/> <readonly/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hdc' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='1' 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> <controller type='scsi' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:52:6b:61'/> <source bridge='br0'/> <model type='rtl8139'/> <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'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='spice' autoport='yes'> <listen type='address'/> <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='536870912' 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='2'/> </redirdev> <redirdev bus='usb' type='spicevmc'> <address type='usb' bus='0' port='3'/> </redirdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain>

2 3

[libvirt-users] creating new vm with virt-manager, existing disk failure
by Marko Weber | 8000 03 Aug '17

03 Aug '17

hello, i rsynced a kvm vm from one host to another. i start virt-manager and tell virt-manager to use an existing disk. i set cpu to haswell that is on the host. configure before start is set, and i start "begin installation". I get this output by virt-manager: Unable to complete install: 'internal error: process exited while connecting to monitor: 2017-07-19T09:27:10.861928Z qemu-system-x86_64: can't apply global Haswell-x86_64-cpu.cmt=on: Property '.cmt' not found' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 88, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 2288, in _do_async_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 477, in start_install doboot, transient) File "/usr/share/virt-manager/virtinst/guest.py", line 405, in _create_guest self.domain.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1062, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error: process exited while connecting to monitor: 2017-07-19T09:27:10.861928Z qemu-system-x86_64: can't apply global Haswell-x86_64-cpu.cmt=on: Property '.cmt' not found try to set it to another cpu and clicking start, i get this: Unable to complete install: 'Domain has already been started!' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 88, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 2288, in _do_async_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 455, in start_install raise RuntimeError(_("Domain has already been started!")) RuntimeError: Domain has already been started! how do i stop the already runing vm? virsh list dont show the vm and why do i get the error on haswell? lscpu: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 12 On-line CPU(s) list: 0-11 Thread(s) per core: 2 Core(s) per socket: 6 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 79 Model name: Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz Stepping: 1 CPU MHz: 2974.658 CPU max MHz: 4000.0000 CPU min MHz: 1200.0000 BogoMIPS: 7191.87 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 15360K NUMA node0 CPU(s): 0-11 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb cat_l3 cdp_l3 intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdt_a rdseed adx smap xsaveopt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts kind regards marko -- zbfmail - Mittendrin statt nur Datei!

3 3

[libvirt-users] Changing <on_reboot> in the domain XML file
by Sam Varshavchik 01 Aug '17

01 Aug '17

Using virsh edit, I made the following change to the domain XML file: <on_reboot>destroy</on_reboot> But this appears to do nothing. The VM guest is Windows 10, and when directing it to reboot, it still reboots, instead of shutting off the VM. I was trying to work around some kind of a bug, somewhere, that started happening after updating to Fedora 26 and qemu 2.9, where a reboot throws my Windows 10 guests into some kind of a bizarre automatic recovery mode, which then claims that the hard drive is hosed. It's not, and a forced shutdown followed by a cold start boots everything back up like nothing has happened (which I didn't figure out until reinstalling one of the guests, sigh...), and everything is peachy once again. So, anyway, I was trying to figure out a way around it, and <on_reboot>destroy</on-reboot> seemed to be exactly what I was looking for. Perusing qemu's man page, it seems that this option should result in a -no- reboot option getting added to qemu's command line. But, looking at the actual command line, after starting the VM, it's nowhere to be seen. A bit more Google-fu found this: http://blog.vmsplice.net/2011/04/how-to-pass-qemu-command-line-options.html And I manually added a -no-reboot option to the domain XML file that way. And you know what? After doing that, telling Windows 10 to reboot simply shuts off the VM. Wonderful. But that still leaves me wondering: what's up with the <on_reboot> tag? Why didn't it work? Is this a PEBCAK, or something worth throwing a ticket for?

2 2

[libvirt-users] libvirt virDomainDestroy
by llilulu 31 Jul '17

31 Jul '17

When stop a qemu vm via libvirt api, I call virDomainShutdown, I can seen the vm shutdown process, But I call virDomainDestroyFlags with VIR_DOMAIN_DESTROY_GRACEFULL ,I can't seen the vm shutdown process, virDomainDestroyFlags with VIR_DOMAIN_DESTROY_GRACEFULL is gave vm driver process a SIGTERM , how vm driver process SIGTERM signal (like qemu). Thanks

2 1

[libvirt-users] Libvirt and dnsmasq
by Erik Lukács 31 Jul '17

31 Jul '17

Hi Guys, I do. have a question on libvirt according dnsmasq. according to the Documentation libvirt initiates for each virtual Interface a dnsmasq process which listens on that interface. Now my Setup Looks like this: in Order to rebuild a Customers Setup i created a vm with several Interfaces ( machine1) and an API Server with two Interfaces ( machine2). Two of these interfaces net_ext and net_int are available on both vms. One of That Interface is meant for Internet (net_ext) the other other for intercommunication (net_int). The "Internet" network is Routed via another virtual Interface (net_infra) which is unavailable on both vms. On that network my outgoing Gateway, ntp and DNS Server is configured in the vms. This makes me crazy due to the fact that dns resolution on machine1 does not work until I either kill the dnsmasq process which listens on net_infra (this makes the system-wide dnsmasq also react on that interface) or I make config-changes mentioned below (but that persists only until the host is rebooted. Both vms and the host run with centos7 My problem now is, that dnsmasq is Running on every virtual interface. And every process only listens on its own interface. All changes are undone/reset by reboot. Of course during runtime (and with restart) i can add to "Interface=net_infra,net_ext" which temporarily fixes My Problem. Another thing I could do is killing the dnsmasq process on the interface and use the hosts own dnsmasq config. Without These changes on DNS resolution doesn't work within my machines ( as written DNS MUST be set on an ip on net_infra, which must not be bound to both vms). So my question: How do i einher configure dnsmasq Not to Start for each Interface on libvirt-start or how do i configure the dnsmasq-config for net_infra also to listen On net_ext. chattr +i /var/lib/libvirt/dnsmasq/net_infra.conf is Not an Option! Thanks in advance! Erik

2 1

Re: [libvirt-users] Xen died - Fedora upgrade from 21 to 26
by G Crowe 27 Jul '17

27 Jul '17

My server was installed as a "minimal install" in text mode, so there may be some difference between my setup and your laptop. Are you able to email the output of "systemctl list-unit-files" to me so that I can see what services are enabled? I tried installing a couple of the other drivers mentioned in the log file... # dnf install libvirt-daemon-driver-lxc # dnf install libvirt-daemon-driver-uml # dnf install libvirt-daemon-driver-vbox But this made no difference. I then tried disabling xenconsole.service, which fixed some things and broke others. - reboots now work (I don't have to hard power cycle - it was locking up when trying to kill both the libvirtd and the xenconsole services) - "virsh list" now works (shows an empty list) - "xl list" now gives an error instead of just locking up (the same error as if libvirtd wasn't running - see below). - "virsh define vmtest.xml" now gives an error (the same error that it gave before I installed libvirt-daemon-driver-libxl - see below) - libvirtd.service starts fine on bootup. Manually restarting libvirtd does not resolve the above problems. Note that on my Fedora 21 machine, it has libvirtd.service and xendomains.service and xenconsoled.service all running simultaneously, and it has been running for years without issues (even on reboots) Is there any documentation on what needs to be installed and/or running to use Xen, and what conflicts? Or is there any documentation on how Xen should be installed for the current version of Fedora? Thank you GC # virsh define vmtest.xml error: Failed to define domain from vmtest.xml error: invalid argument: could not find capabilities for arch=x86_64 domaintype=xen # xl list xencall: error: Could not obtain handle on privileged command interface: No such file or directory libxl: error: libxl.c:108:libxl_ctx_alloc: cannot open libxc handle: No such file or directory cannot init xl context On 27/07/2017 11:40 AM, Alvin Starr wrote: > I just tried my laptop and booted xen and can virsh list and xl seem > to work. > > > On 07/26/2017 06:27 PM, G Crowe wrote: >> Alvin, >> Thanks for that. I disabled the xendomains service (I had to do >> it twice, as it seemed to re-enable itself after the first reboot) >> and it now starts libvirtd automatically on startup. >> >> However, all is not well! >> "xl list" and "virsh list" will just hang >> "systemctl stop libvirtd" just hangs and after this "ps aux" lists >> the process as defunct >> root 673 0.0 0.0 0 0 ? Zsl 08:04 0:00 >> [libvirtd] <defunct> >> "kill -KILL 673" has no effect >> "shutdown -r now" also hangs (I have to physically power off the >> machine) irrespectively of whether I have tried to stop the service >> before shutdown or not. >> >> None of this happened yesterday when I manually started libvirtd >> after bootup (when xendomains was still running). >> >> The logs show nothing in error or warning category, just a heap of >> info (I have the logs set to level 2). Is there anything in >> particular that I should be looking for in the logs? >> >> >> >> Regarding the use of a VM to access the host in a remote location... >> I had considered this and there was little choice. The machine is on >> the end of a VDSL line and was installed to consolidate a few servers >> in that location in order to save power. I figured that automatically >> starting a VM that ran the networking was not much more risk than a >> physical server that had to start up its networking, and that has (so >> far) proven to be true with all of the remote restarts & power >> outages to date. The only other option is an expensive second link to >> the host, and I've decided to live with the possibility of having to >> talk someone through a restart over the phone rather than go down >> that route. >> >> Interestingly, with the NBN in Australia (the country-wide rollout of >> fibre or broadband to every premises) they have effectively converted >> all our phone lines to VoIP. This has resulted in the old physical >> landline now requiring one of the VMs to be running as well, so if I >> ever need to talk someone through a restart it will need to be on a >> mobile phone. >> >> >> Thank you >> >> GC >> >> >> On 27/07/2017 5:47 AM, Alvin Starr wrote: >>> I addressed the fix to Jim but I should have addressed it to you. >>> >>> >>> Try systemctl disable xendomains.service >>> >>> It is conflicting with libvirtd.service. >>> I found it by using >>> "systemd-analyze dot libvirtd.service | dot -Tgif > /tmp/dot1.gif" >>> >>> >>> It looks like libvirt-daemon-driver-xen or >>> libvirt-daemon-driver-libxl should disable the xendomains.service >>> >>> >>> On 07/26/2017 06:46 AM, G Crowe wrote: >>>> Jim, >>>> Thanks for that, I had manually installed >>>> libvirt-daemon-driver-xen, but also needed to install >>>> libvirt-daemon-driver-libxl. I can now create VMs and convert >>>> config formats. >>>> >>>> However the daemon still fails to start on bootup. It starts fine >>>> when I manually start it with "systemctl start libvirtd" but >>>> setting it to autostart with "systemctl enable libvirtd" seems to >>>> have no effect. When I look at the status, it tells me that the >>>> service is "enabled" which means that it starts on bootup (well, >>>> that's what it means for any other service). >>>> >>>> This is rather critical on this PC, as it has unattended restarts >>>> and the VPN/routing is done in one of the VMs (i.e. I can't get to >>>> it unless it auto-starts at least one VM). >>>> >>>> Unfortunatley there is nothing appearing in the libvirtd log over a >>>> reboot to help diagnose. >>>> >>>> Any suggestions? >>>> >>>> >>>> Thank you >>>> >>>> GC >>>> >>>> >>>> [root@testhost ~]# systemctl status libvirtd >>>> ● libvirtd.service - Virtualization daemon >>>> Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; >>>> enabled; vendor preset: enabled) >>>> Active: inactive (dead) >>>> Docs: man:libvirtd(8) >>>> http://libvirt.org >>>> >>>> >>>> >>>> >>>> On 25/07/2017 1:20 AM, Jim Fehlig wrote: >>>>> On 07/23/2017 04:25 PM, G Crowe wrote: >>>>>> Hi, >>>>>> I am trying to upgrade my Xen host (Dom0) and are having >>>>>> troubles getting it to work. >>>>>> >>>>>> I think that it has booted into a kernel that supports Xen >>>>>> (running 'xl info' does list some Xen capabilities), but I have >>>>>> three problems (that I have found so far). >>>>>> >>>>>> Firstly, the "libvirtd" daemon doesn't start on bootup (and as a >>>>>> result all 'virsh' commands fail). It is set to auto-start >>>>>> (systemctl enable libvirtd), and can be manually started >>>>>> (systemctl start libvirtd), but it will not auto-start on reboot. >>>>>> >>>>>> Secondly, Once I have manually started libvirtd, when I try to >>>>>> define a domain it gives me an error "could not find capabilities >>>>>> for arch=x86_64 domaintype=xen" and I haven't yet been able to >>>>>> define any domains. This domain type works fine on Fedora 21. >>>>>> >>>>>> Thirdly, I am unable to convert to/from xml config format, it >>>>>> gives me the error "error: invalid argument: unsupported config >>>>>> type xen-xl" however the format "xen-xl" works fine on the Fedora >>>>>> 21 machine. >>>>> >>>>> It sounds like the libvirt libxl driver is not loaded. Is the >>>>> libvirt-daemon-driver-libxl package installed? If it's installed, >>>>> enabling debug logging in libvirtd can provide hints why it is not >>>>> loading >>>>> >>>>> http://libvirt.org/logging.html >>>>> >>>>> Regards, >>>>> Jim >>>>> >>>>>> >>>>>> I had these same issues when I tried to upgrade to Fedora 25 and >>>>>> assumed that something had been broken and so abandoned further >>>>>> attempts to upgrade, however since Fedora 26 is the same I am now >>>>>> assuming that I have stuffed something up myself (or missed >>>>>> something). >>>>>> >>>>>> Fedora 21 uses kernel 3.19.3 and xen 4.4.1 >>>>>> Fedora 26 uses kernel 4.11.8 and xen 4.8.1 >>>>>> >>>>>> I have tried following the info on >>>>>> https://wiki.xen.org/wiki/Fedora_Host_Installation but it appears >>>>>> to be out of date now (I used this site when I started using Xen >>>>>> under Fedora 19, and when I upgraded to Fedora 21) >>>>>> >>>>>> Does anyone have any suggestions? outputs from "xl info" and the >>>>>> domain config are below. I have also tried disabling SELinux, but >>>>>> it made no difference. >>>>>> >>>>>> >>>>>> Thanks >>>>>> >>>>>> GC >>>>>> >>>>>> ----------------------------------------------- >>>>>> On the fedora 26 box..... >>>>>> # xl info >>>>>> host : family.mydomain.mytld >>>>>> release : 4.11.8-300.fc26.x86_64 >>>>>> version : #1 SMP Thu Jun 29 20:09:48 UTC 2017 >>>>>> machine : x86_64 >>>>>> nr_cpus : 4 >>>>>> max_cpu_id : 3 >>>>>> nr_nodes : 1 >>>>>> cores_per_socket : 4 >>>>>> threads_per_core : 1 >>>>>> cpu_mhz : 2712 >>>>>> hw_caps : >>>>>> b7ebfbff:77faf3bf:2c100800:00000121:0000000f:009c67af:00000000:00000100 >>>>>> >>>>>> virt_caps : hvm hvm_directio >>>>>> total_memory : 8072 >>>>>> free_memory : 128 >>>>>> sharing_freed_memory : 0 >>>>>> sharing_used_memory : 0 >>>>>> outstanding_claims : 0 >>>>>> free_cpus : 0 >>>>>> xen_major : 4 >>>>>> xen_minor : 8 >>>>>> xen_extra : .1 >>>>>> xen_version : 4.8.1 >>>>>> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p >>>>>> hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 >>>>>> xen_scheduler : credit >>>>>> xen_pagesize : 4096 >>>>>> platform_params : virt_start=0xffff800000000000 >>>>>> xen_changeset : >>>>>> xen_commandline : placeholder >>>>>> cc_compiler : gcc (GCC) 7.0.1 20170421 (Red Hat >>>>>> 7.0.1-0.15) >>>>>> cc_compile_by : mockbuild >>>>>> cc_compile_domain : [unknown] >>>>>> cc_compile_date : Wed May 3 21:23:49 UTC 2017 >>>>>> build_id : 1c6e5a40165e05837303942b54757ae1f2d5033d >>>>>> xend_config_format : 4 >>>>>> >>>>>> --------------------------------------------------- >>>>>> # cat vmtest.xml >>>>>> <domain type='xen' id='21'> >>>>>> <name>testVM</name> >>>>>> <memory unit='KiB'>2097152</memory> >>>>>> <currentMemory unit='KiB'>2097152</currentMemory> >>>>>> <vcpu placement='static'>1</vcpu> >>>>>> <os> >>>>>> <type arch='x86_64' machine='xenfv'>hvm</type> >>>>>> <loader type='rom'>/usr/lib/xen/boot/hvmloader</loader> >>>>>> <boot dev='network'/> >>>>>> </os> >>>>>> <features> >>>>>> <acpi/> >>>>>> <apic/> >>>>>> <pae/> >>>>>> </features> >>>>>> <clock offset='variable' adjustment='0' basis='utc'/> >>>>>> <on_poweroff>destroy</on_poweroff> >>>>>> <on_reboot>restart</on_reboot> >>>>>> <on_crash>restart</on_crash> >>>>>> <devices> >>>>>> <interface type='bridge'> >>>>>> <mac address='02:02:00:03:00:00'/> >>>>>> <source bridge='enp1s0'/> >>>>>> <script path='vif-bridge'/> >>>>>> </interface> >>>>>> <serial type='pty'> >>>>>> <target port='0'/> >>>>>> </serial> >>>>>> <console type='pty'> >>>>>> <target type='serial' port='0'/> >>>>>> </console> >>>>>> <input type='mouse' bus='ps2'/> >>>>>> <input type='keyboard' bus='ps2'/> >>>>>> <graphics type='vnc' port='5901' autoport='no' >>>>>> listen='192.168.131.54'> >>>>>> <listen type='address' address='192.168.131.54'/> >>>>>> </graphics> >>>>>> </devices> >>>>>> </domain> >>>>>> >>>>>> -------------------------------------- >>>>>> >>>>>> _______________________________________________ >>>>>> libvirt-users mailing list >>>>>> libvirt-users(a)redhat.com >>>>>> https://www.redhat.com/mailman/listinfo/libvirt-users >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> libvirt-users mailing list >>>> libvirt-users(a)redhat.com >>>> https://www.redhat.com/mailman/listinfo/libvirt-users >>> >> >

1 0

Re: [libvirt-users] Xen died - Fedora upgrade from 21 to 26
by G Crowe 27 Jul '17

27 Jul '17

Alvin, Thanks for that. I disabled the xendomains service (I had to do it twice, as it seemed to re-enable itself after the first reboot) and it now starts libvirtd automatically on startup. However, all is not well! "xl list" and "virsh list" will just hang "systemctl stop libvirtd" just hangs and after this "ps aux" lists the process as defunct root 673 0.0 0.0 0 0 ? Zsl 08:04 0:00 [libvirtd] <defunct> "kill -KILL 673" has no effect "shutdown -r now" also hangs (I have to physically power off the machine) irrespectively of whether I have tried to stop the service before shutdown or not. None of this happened yesterday when I manually started libvirtd after bootup (when xendomains was still running). The logs show nothing in error or warning category, just a heap of info (I have the logs set to level 2). Is there anything in particular that I should be looking for in the logs? Regarding the use of a VM to access the host in a remote location... I had considered this and there was little choice. The machine is on the end of a VDSL line and was installed to consolidate a few servers in that location in order to save power. I figured that automatically starting a VM that ran the networking was not much more risk than a physical server that had to start up its networking, and that has (so far) proven to be true with all of the remote restarts & power outages to date. The only other option is an expensive second link to the host, and I've decided to live with the possibility of having to talk someone through a restart over the phone rather than go down that route. Interestingly, with the NBN in Australia (the country-wide rollout of fibre or broadband to every premises) they have effectively converted all our phone lines to VoIP. This has resulted in the old physical landline now requiring one of the VMs to be running as well, so if I ever need to talk someone through a restart it will need to be on a mobile phone. Thank you GC On 27/07/2017 5:47 AM, Alvin Starr wrote: > I addressed the fix to Jim but I should have addressed it to you. > > > Try systemctl disable xendomains.service > > It is conflicting with libvirtd.service. > I found it by using > "systemd-analyze dot libvirtd.service | dot -Tgif > /tmp/dot1.gif" > > > It looks like libvirt-daemon-driver-xen or > libvirt-daemon-driver-libxl should disable the xendomains.service > > > On 07/26/2017 06:46 AM, G Crowe wrote: >> Jim, >> Thanks for that, I had manually installed >> libvirt-daemon-driver-xen, but also needed to install >> libvirt-daemon-driver-libxl. I can now create VMs and convert config >> formats. >> >> However the daemon still fails to start on bootup. It starts fine >> when I manually start it with "systemctl start libvirtd" but setting >> it to autostart with "systemctl enable libvirtd" seems to have no >> effect. When I look at the status, it tells me that the service is >> "enabled" which means that it starts on bootup (well, that's what it >> means for any other service). >> >> This is rather critical on this PC, as it has unattended restarts and >> the VPN/routing is done in one of the VMs (i.e. I can't get to it >> unless it auto-starts at least one VM). >> >> Unfortunatley there is nothing appearing in the libvirtd log over a >> reboot to help diagnose. >> >> Any suggestions? >> >> >> Thank you >> >> GC >> >> >> [root@testhost ~]# systemctl status libvirtd >> ● libvirtd.service - Virtualization daemon >> Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; >> vendor preset: enabled) >> Active: inactive (dead) >> Docs: man:libvirtd(8) >> http://libvirt.org >> >> >> >> >> On 25/07/2017 1:20 AM, Jim Fehlig wrote: >>> On 07/23/2017 04:25 PM, G Crowe wrote: >>>> Hi, >>>> I am trying to upgrade my Xen host (Dom0) and are having >>>> troubles getting it to work. >>>> >>>> I think that it has booted into a kernel that supports Xen (running >>>> 'xl info' does list some Xen capabilities), but I have three >>>> problems (that I have found so far). >>>> >>>> Firstly, the "libvirtd" daemon doesn't start on bootup (and as a >>>> result all 'virsh' commands fail). It is set to auto-start >>>> (systemctl enable libvirtd), and can be manually started (systemctl >>>> start libvirtd), but it will not auto-start on reboot. >>>> >>>> Secondly, Once I have manually started libvirtd, when I try to >>>> define a domain it gives me an error "could not find capabilities >>>> for arch=x86_64 domaintype=xen" and I haven't yet been able to >>>> define any domains. This domain type works fine on Fedora 21. >>>> >>>> Thirdly, I am unable to convert to/from xml config format, it gives >>>> me the error "error: invalid argument: unsupported config type >>>> xen-xl" however the format "xen-xl" works fine on the Fedora 21 >>>> machine. >>> >>> It sounds like the libvirt libxl driver is not loaded. Is the >>> libvirt-daemon-driver-libxl package installed? If it's installed, >>> enabling debug logging in libvirtd can provide hints why it is not >>> loading >>> >>> http://libvirt.org/logging.html >>> >>> Regards, >>> Jim >>> >>>> >>>> I had these same issues when I tried to upgrade to Fedora 25 and >>>> assumed that something had been broken and so abandoned further >>>> attempts to upgrade, however since Fedora 26 is the same I am now >>>> assuming that I have stuffed something up myself (or missed >>>> something). >>>> >>>> Fedora 21 uses kernel 3.19.3 and xen 4.4.1 >>>> Fedora 26 uses kernel 4.11.8 and xen 4.8.1 >>>> >>>> I have tried following the info on >>>> https://wiki.xen.org/wiki/Fedora_Host_Installation but it appears >>>> to be out of date now (I used this site when I started using Xen >>>> under Fedora 19, and when I upgraded to Fedora 21) >>>> >>>> Does anyone have any suggestions? outputs from "xl info" and the >>>> domain config are below. I have also tried disabling SELinux, but >>>> it made no difference. >>>> >>>> >>>> Thanks >>>> >>>> GC >>>> >>>> ----------------------------------------------- >>>> On the fedora 26 box..... >>>> # xl info >>>> host : family.mydomain.mytld >>>> release : 4.11.8-300.fc26.x86_64 >>>> version : #1 SMP Thu Jun 29 20:09:48 UTC 2017 >>>> machine : x86_64 >>>> nr_cpus : 4 >>>> max_cpu_id : 3 >>>> nr_nodes : 1 >>>> cores_per_socket : 4 >>>> threads_per_core : 1 >>>> cpu_mhz : 2712 >>>> hw_caps : >>>> b7ebfbff:77faf3bf:2c100800:00000121:0000000f:009c67af:00000000:00000100 >>>> >>>> virt_caps : hvm hvm_directio >>>> total_memory : 8072 >>>> free_memory : 128 >>>> sharing_freed_memory : 0 >>>> sharing_used_memory : 0 >>>> outstanding_claims : 0 >>>> free_cpus : 0 >>>> xen_major : 4 >>>> xen_minor : 8 >>>> xen_extra : .1 >>>> xen_version : 4.8.1 >>>> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p >>>> hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 >>>> xen_scheduler : credit >>>> xen_pagesize : 4096 >>>> platform_params : virt_start=0xffff800000000000 >>>> xen_changeset : >>>> xen_commandline : placeholder >>>> cc_compiler : gcc (GCC) 7.0.1 20170421 (Red Hat 7.0.1-0.15) >>>> cc_compile_by : mockbuild >>>> cc_compile_domain : [unknown] >>>> cc_compile_date : Wed May 3 21:23:49 UTC 2017 >>>> build_id : 1c6e5a40165e05837303942b54757ae1f2d5033d >>>> xend_config_format : 4 >>>> >>>> --------------------------------------------------- >>>> # cat vmtest.xml >>>> <domain type='xen' id='21'> >>>> <name>testVM</name> >>>> <memory unit='KiB'>2097152</memory> >>>> <currentMemory unit='KiB'>2097152</currentMemory> >>>> <vcpu placement='static'>1</vcpu> >>>> <os> >>>> <type arch='x86_64' machine='xenfv'>hvm</type> >>>> <loader type='rom'>/usr/lib/xen/boot/hvmloader</loader> >>>> <boot dev='network'/> >>>> </os> >>>> <features> >>>> <acpi/> >>>> <apic/> >>>> <pae/> >>>> </features> >>>> <clock offset='variable' adjustment='0' basis='utc'/> >>>> <on_poweroff>destroy</on_poweroff> >>>> <on_reboot>restart</on_reboot> >>>> <on_crash>restart</on_crash> >>>> <devices> >>>> <interface type='bridge'> >>>> <mac address='02:02:00:03:00:00'/> >>>> <source bridge='enp1s0'/> >>>> <script path='vif-bridge'/> >>>> </interface> >>>> <serial type='pty'> >>>> <target port='0'/> >>>> </serial> >>>> <console type='pty'> >>>> <target type='serial' port='0'/> >>>> </console> >>>> <input type='mouse' bus='ps2'/> >>>> <input type='keyboard' bus='ps2'/> >>>> <graphics type='vnc' port='5901' autoport='no' >>>> listen='192.168.131.54'> >>>> <listen type='address' address='192.168.131.54'/> >>>> </graphics> >>>> </devices> >>>> </domain> >>>> >>>> -------------------------------------- >>>> >>>> _______________________________________________ >>>> libvirt-users mailing list >>>> libvirt-users(a)redhat.com >>>> https://www.redhat.com/mailman/listinfo/libvirt-users >>>> >>> >> >> _______________________________________________ >> libvirt-users mailing list >> libvirt-users(a)redhat.com >> https://www.redhat.com/mailman/listinfo/libvirt-users >

1 0

[libvirt-users] Xen died - Fedora upgrade from 21 to 26
by G Crowe 27 Jul '17

27 Jul '17

Hi, I am trying to upgrade my Xen host (Dom0) and are having troubles getting it to work. I think that it has booted into a kernel that supports Xen (running 'xl info' does list some Xen capabilities), but I have three problems (that I have found so far). Firstly, the "libvirtd" daemon doesn't start on bootup (and as a result all 'virsh' commands fail). It is set to auto-start (systemctl enable libvirtd), and can be manually started (systemctl start libvirtd), but it will not auto-start on reboot. Secondly, Once I have manually started libvirtd, when I try to define a domain it gives me an error "could not find capabilities for arch=x86_64 domaintype=xen" and I haven't yet been able to define any domains. This domain type works fine on Fedora 21. Thirdly, I am unable to convert to/from xml config format, it gives me the error "error: invalid argument: unsupported config type xen-xl" however the format "xen-xl" works fine on the Fedora 21 machine. I had these same issues when I tried to upgrade to Fedora 25 and assumed that something had been broken and so abandoned further attempts to upgrade, however since Fedora 26 is the same I am now assuming that I have stuffed something up myself (or missed something). Fedora 21 uses kernel 3.19.3 and xen 4.4.1 Fedora 26 uses kernel 4.11.8 and xen 4.8.1 I have tried following the info on https://wiki.xen.org/wiki/Fedora_Host_Installation but it appears to be out of date now (I used this site when I started using Xen under Fedora 19, and when I upgraded to Fedora 21) Does anyone have any suggestions? outputs from "xl info" and the domain config are below. I have also tried disabling SELinux, but it made no difference. Thanks GC ----------------------------------------------- On the fedora 26 box..... # xl info host : family.mydomain.mytld release : 4.11.8-300.fc26.x86_64 version : #1 SMP Thu Jun 29 20:09:48 UTC 2017 machine : x86_64 nr_cpus : 4 max_cpu_id : 3 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2712 hw_caps : b7ebfbff:77faf3bf:2c100800:00000121:0000000f:009c67af:00000000:00000100 virt_caps : hvm hvm_directio total_memory : 8072 free_memory : 128 sharing_freed_memory : 0 sharing_used_memory : 0 outstanding_claims : 0 free_cpus : 0 xen_major : 4 xen_minor : 8 xen_extra : .1 xen_version : 4.8.1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : xen_commandline : placeholder cc_compiler : gcc (GCC) 7.0.1 20170421 (Red Hat 7.0.1-0.15) cc_compile_by : mockbuild cc_compile_domain : [unknown] cc_compile_date : Wed May 3 21:23:49 UTC 2017 build_id : 1c6e5a40165e05837303942b54757ae1f2d5033d xend_config_format : 4 --------------------------------------------------- # cat vmtest.xml <domain type='xen' id='21'> <name>testVM</name> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='x86_64' machine='xenfv'>hvm</type> <loader type='rom'>/usr/lib/xen/boot/hvmloader</loader> <boot dev='network'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='variable' adjustment='0' basis='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <interface type='bridge'> <mac address='02:02:00:03:00:00'/> <source bridge='enp1s0'/> <script path='vif-bridge'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5901' autoport='no' listen='192.168.131.54'> <listen type='address' address='192.168.131.54'/> </graphics> </devices> </domain> --------------------------------------

3 5

[libvirt-users] automatically reverting to a snapshot
by Dirty Dan 27 Jul '17

27 Jul '17

2 1

Re: [libvirt-users] Xen died - Fedora upgrade from 21 to 26
by Dominik Psenner 27 Jul '17

27 Jul '17

Note that this does not help with the original problem but points out a critical design flaw. To me your it infrastructure design has no working disaster recovery plan. You should always be able to access critical functionality and from there be able to restore complete functionality step by step. In your case the outermost functionality is the vm host. You should always be able to log into that machine once it has all cables plugged in, regardless of what runs on it (or not). This means that even though you might get this to work you should rethink your design so that you do not have to rely on the vm that does the networking. On 26 Jul 2017 12:50 p.m., "G Crowe" <gclvirtlist(a)crowie.net> wrote: Jim, Thanks for that, I had manually installed libvirt-daemon-driver-xen, but also needed to install libvirt-daemon-driver-libxl. I can now create VMs and convert config formats. However the daemon still fails to start on bootup. It starts fine when I manually start it with "systemctl start libvirtd" but setting it to autostart with "systemctl enable libvirtd" seems to have no effect. When I look at the status, it tells me that the service is "enabled" which means that it starts on bootup (well, that's what it means for any other service). This is rather critical on this PC, as it has unattended restarts and the VPN/routing is done in one of the VMs (i.e. I can't get to it unless it auto-starts at least one VM). Unfortunatley there is nothing appearing in the libvirtd log over a reboot to help diagnose. Any suggestions? Thank you GC [root@testhost ~]# systemctl status libvirtd ● libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: man:libvirtd(8) http://libvirt.org On 25/07/2017 1:20 AM, Jim Fehlig wrote: > On 07/23/2017 04:25 PM, G Crowe wrote: > >> Hi, >> I am trying to upgrade my Xen host (Dom0) and are having troubles >> getting it to work. >> >> I think that it has booted into a kernel that supports Xen (running 'xl >> info' does list some Xen capabilities), but I have three problems (that I >> have found so far). >> >> Firstly, the "libvirtd" daemon doesn't start on bootup (and as a result >> all 'virsh' commands fail). It is set to auto-start (systemctl enable >> libvirtd), and can be manually started (systemctl start libvirtd), but it >> will not auto-start on reboot. >> >> Secondly, Once I have manually started libvirtd, when I try to define a >> domain it gives me an error "could not find capabilities for arch=x86_64 >> domaintype=xen" and I haven't yet been able to define any domains. This >> domain type works fine on Fedora 21. >> >> Thirdly, I am unable to convert to/from xml config format, it gives me >> the error "error: invalid argument: unsupported config type xen-xl" however >> the format "xen-xl" works fine on the Fedora 21 machine. >> > > It sounds like the libvirt libxl driver is not loaded. Is the > libvirt-daemon-driver-libxl package installed? If it's installed, enabling > debug logging in libvirtd can provide hints why it is not loading > > http://libvirt.org/logging.html > > Regards, > Jim > > >> I had these same issues when I tried to upgrade to Fedora 25 and assumed >> that something had been broken and so abandoned further attempts to >> upgrade, however since Fedora 26 is the same I am now assuming that I have >> stuffed something up myself (or missed something). >> >> Fedora 21 uses kernel 3.19.3 and xen 4.4.1 >> Fedora 26 uses kernel 4.11.8 and xen 4.8.1 >> >> I have tried following the info on https://wiki.xen.org/wiki/Fedo >> ra_Host_Installation but it appears to be out of date now (I used this >> site when I started using Xen under Fedora 19, and when I upgraded to >> Fedora 21) >> >> Does anyone have any suggestions? outputs from "xl info" and the domain >> config are below. I have also tried disabling SELinux, but it made no >> difference. >> >> >> Thanks >> >> GC >> >> ----------------------------------------------- >> On the fedora 26 box..... >> # xl info >> host : family.mydomain.mytld >> release : 4.11.8-300.fc26.x86_64 >> version : #1 SMP Thu Jun 29 20:09:48 UTC 2017 >> machine : x86_64 >> nr_cpus : 4 >> max_cpu_id : 3 >> nr_nodes : 1 >> cores_per_socket : 4 >> threads_per_core : 1 >> cpu_mhz : 2712 >> hw_caps : b7ebfbff:77faf3bf:2c100800:000 >> 00121:0000000f:009c67af:00000000:00000100 >> virt_caps : hvm hvm_directio >> total_memory : 8072 >> free_memory : 128 >> sharing_freed_memory : 0 >> sharing_used_memory : 0 >> outstanding_claims : 0 >> free_cpus : 0 >> xen_major : 4 >> xen_minor : 8 >> xen_extra : .1 >> xen_version : 4.8.1 >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 >> hvm-3.0-x86_32p hvm-3.0-x86_64 >> xen_scheduler : credit >> xen_pagesize : 4096 >> platform_params : virt_start=0xffff800000000000 >> xen_changeset : >> xen_commandline : placeholder >> cc_compiler : gcc (GCC) 7.0.1 20170421 (Red Hat 7.0.1-0.15) >> cc_compile_by : mockbuild >> cc_compile_domain : [unknown] >> cc_compile_date : Wed May 3 21:23:49 UTC 2017 >> build_id : 1c6e5a40165e05837303942b54757ae1f2d5033d >> xend_config_format : 4 >> >> --------------------------------------------------- >> # cat vmtest.xml >> <domain type='xen' id='21'> >> <name>testVM</name> >> <memory unit='KiB'>2097152</memory> >> <currentMemory unit='KiB'>2097152</currentMemory> >> <vcpu placement='static'>1</vcpu> >> <os> >> <type arch='x86_64' machine='xenfv'>hvm</type> >> <loader type='rom'>/usr/lib/xen/boot/hvmloader</loader> >> <boot dev='network'/> >> </os> >> <features> >> <acpi/> >> <apic/> >> <pae/> >> </features> >> <clock offset='variable' adjustment='0' basis='utc'/> >> <on_poweroff>destroy</on_poweroff> >> <on_reboot>restart</on_reboot> >> <on_crash>restart</on_crash> >> <devices> >> <interface type='bridge'> >> <mac address='02:02:00:03:00:00'/> >> <source bridge='enp1s0'/> >> <script path='vif-bridge'/> >> </interface> >> <serial type='pty'> >> <target port='0'/> >> </serial> >> <console type='pty'> >> <target type='serial' port='0'/> >> </console> >> <input type='mouse' bus='ps2'/> >> <input type='keyboard' bus='ps2'/> >> <graphics type='vnc' port='5901' autoport='no' >> listen='192.168.131.54'> >> <listen type='address' address='192.168.131.54'/> >> </graphics> >> </devices> >> </domain> >> >> -------------------------------------- >> >> _______________________________________________ >> libvirt-users mailing list >> libvirt-users(a)redhat.com >> https://www.redhat.com/mailman/listinfo/libvirt-users >> >> > _______________________________________________ libvirt-users mailing list libvirt-users(a)redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users

2 2

[libvirt-users] Why cannot block copy local storage to network disk
by wyang 26 Jul '17

26 Jul '17

Hi, guys I was executing the following command to lively migrate local storage to network storage, [root@192-168-152-51 ~]# virsh blockcopy a75056a4-44e0-4b97-bc77-78142ee17038 vda —xml rbd.xml —wait —verbose —pivot error: argument unsupported: non-file destination not supported yet but I get the following error: error: argument unsupported: non-file destination not supported yet I check my libvirt source code, and find the following code sniff in /qemuDomainBlockCopyCommon/ function |if (!virStorageSourceIsLocalStorage(mirror)) { virReportError(VIR_ERR_ARGUMENT_UNSUPPORTED, "%s", _("non-file destination not supported yet")); } | it was introduced by Eric. commit e53ee6c123321a1775ef3b36e15a5fa351d10fe4 Author: Eric Blake eblake(a)redhat.com <http://mailto:eblake@redhat.com> Date: Fri Aug 29 16:30:46 2014 -0600 blockcopy: tweak how rebase calls into copy So my question is that why we cannot block copy to network storage? Thanks Wei

3 3

[libvirt-users] About seclabel configure,Migrate error
by 露露 25 Jul '17

25 Jul '17

libvirt version: 3.4.0 architecture: x86_64 ubuntu16.04-server hypervisor: kvm,qemu When migrate vm, I encounter error: "Migrate VM virt21 failed unsupported configuration: Unable to find security driver for model apparmor" but two host are same environment.before this error, migrate can be success. the source host seclabel configure is this : <seclabel type='dynamic' model='apparmor' relabel='yes'> <label>libvirt-8e4ec209-17ca-4b59-abb7-72f3984244f3</label> <imagelabel>libvirt-8e4ec209-17ca-4b59-abb7-72f3984244f3</imagelabel> </seclabel> I create a vm on the destination host ,the vm configure not seclabel congfigure. I reinstall libvirt on the destination host and migrate same vm, this error disappear.vm seclabel configure is default. I recreate a vm on the destination host ,the vm configure has the seclabel configure , I don't known the reason. Another question: I configure a vm xml's seclabel like this: <seclabel type='none' model='none'/> and then call virDomainCreate create the vm, call virsh dumpxml, the vm xml's seclabel is this: <seclabel type='none' model='none'/> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+0</label> <imagelabel>+0:+0</imagelabel> </seclabel> I don't the reason. Is a vm seclabel configure dynamic change when it running? Thanks

2 1

[libvirt-users] how libvirt create virbr0
by 露露 25 Jul '17

25 Jul '17

libvirt version: 3.4.0 architecture: x86_64 ubuntu16.04-server hypervisor: kvm,qemu when install libvirt from ubuntu distribution deb install libvirt, a virtual bridge virbr0 will be create . But when I build libvirt from souce code, how can I create a virbr0. If I want create another virtual bridge ,How can I create and start the virtual bridge. Thanks

2 1

[libvirt-users] transient configure turn to persistent configure
by 露露 25 Jul '17

25 Jul '17

libvirt version: 3.4.0 architecture: x86_64 ubuntu16.04-server hypervisor: kvm,qemu I call virDomainCreate create a transient vm, After a period of time ,I call virDomainDestroy, the vm configure is stil exist， the vm turn to persistent, I don't known the reason. Thanks

2 1

[libvirt-users] memory snapshot save error
by 露露 25 Jul '17

25 Jul '17

libvirt version: 3.4.0 architecture: x86_64 ubuntu16.04-server hypervisor: kvm,qemu when I want make a memery snapshot for a vm ,and I call virsh save ,but tell me this error: error: Failed to save domain 177 to /datapool/mm.img error: operation failed: domain save job: unexpectedly failed xml configure: <domain type='kvm' id='177'> <name>virt23</name> <uuid>e50c1d59-c4a3-4413-b6c9-20e90cced343</uuid> <metadata/> <memory unit='KiB'>10485760</memory> <currentMemory unit='KiB'>10485760</currentMemory> <vcpu placement='static'>1</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> <boot dev='hd'/> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/datapool/zhuohf/virt23.qcow2'/> <backingStore/> <target dev='vdc' bus='virtio'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/datapool/zhuohf/ubuntu-16.04.2-desktop-amd64.iso'/> [40/38156] <backingStore/> <target dev='hdc' bus='ide'/> <readonly/> <alias name='ide0-1-0'/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='piix3-uhci'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='network'> <mac address='52:54:00:e0:31:68'/> <source network='default' bridge='virbr0'/> <target dev='vnet11'/> <model type='rtl8139'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <graphics type='vnc' port='5909' autoport='yes' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='cirrus' vram='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <stats period='1'/> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+0</label> <imagelabel>+0:+0</imagelabel> </seclabel> </domain> before I encounter the same error,that time is my disk not free space，but this time I can't find error reason. Thanks

2 1

[libvirt-users] cannot set maxMemory
by 임영빈 21 Jul '17

21 Jul '17

Hi all, I'm testing the memory hotplugging on devstack (ocata version). According to the article in https://medium.com/@juergen_thomann/memory-hotplug-with-qemu-kvm-and-libvir… , I'm trying to create a virtual machine by setting <maxMemory>. However, I've got an error message in libvirt log as below. 2017-07-20 20:33:21.175+0000: 529: error : virDomainDefCheckUnsupportedMemoryHotplug:1192 : unsupported configuration: memory hotplug tunables <maxMemory> are not supported by this hypervisor driver virt-aa-helper: error: could not parse XML virt-aa-helper: error: could not get VM definition I'm using qemu hypervisor (2.8), and libvirt (2.5.0). As I know, these qemu, libvirt versions support hotplugging memory. Below is the xml file I used to create a virtual machine by using 'virsh create test.xml' command. <domain type='qemu'> <name>QEmu-fedora-i686</name> <uuid>c7a5fdbd-cdaf-9455-926a-d65c16db1809</uuid> <maxMemory slots='4' unit='KiB'>2097152</maxMemory> <memory>219200</memory> <currentMemory>219200</currentMemory> <vcpu>2</vcpu> <cpu> <numa> <cell id="0" cpus="0" memory="2097152" unit="KiB"/> </numa> </cpu> <driver name="qemu" type="qcow2" cache="none"/> <os> <type arch='i686' machine='pc'>hvm</type> <boot dev='cdrom'/> </os> <devices> <emulator>/usr/bin/qemu-system-ppc</emulator> <disk type='file' device='cdrom'> <source file='/home/user/boot.iso'/> <target dev='hdc'/> <readonly/> </disk> <disk type='file' device='disk'> <source file='/home/user/fedora.img'/> <target dev='hda'/> </disk> <interface type='network'> <source network='default'/> </interface> </devices> </domain> Does anyone know the reason? Thanks, Youngbin

1 0

[libvirt-users] SSH from host to domain using hostname
by c.monty＠web.de 20 Jul '17

20 Jul '17

Hello! I want to SSH from host to specific guest using hostname, e.g. ssh <user>@<guest> or ssh test@vm02-fai ssh to guest using IP works w/o issues. I found Wiki article for "NSS module" (http://wiki.libvirt.org/page/NSS_module) but there are no results for the following commands: ld4004:/home # virsh net-dhcp-leases default Expiry Time MAC address Protocol IP address Hostname Client ID or DUID ------------------------------------------------------------------------------------------------------------------- ld4004:/home # virsh domifaddr --source lease vm02-fai Name MAC address Protocol Address ------------------------------------------------------------------------------- ld4004:/home # virsh list Id Name State ---------------------------------------------------- 1 vm02-fai running dnsmasq is running: ld4004:/home # netstat -nulpd | grep dnsmasq udp 0 0 192.168.33.1:53 0.0.0.0:* 10318/dnsmasq udp 0 0 192.168.100.1:53 0.0.0.0:* 20145/dnsmasq udp 0 0 0.0.0.0:67 0.0.0.0:* 20145/dnsmasq How can I fix this issue? THX

4 14

[libvirt-users] libvirt administration tools
by Dominik Psenner 20 Jul '17

20 Jul '17

Hi! To give something back to the community I just now made our daily live backup scripts open source. It is hosted on github and licensed under the Apache-2.0. https://github.com/dpsenner/libvirt-administration-tools Feel free to use it in your production environment or fork and adapt it to fit your needs or even improve it and open pull requests! Cheers -- Dominik Psenner

1 0

[libvirt-users] What may be cause vm "in shutdown" state
by ahongloumeng＠163.com 20 Jul '17

20 Jul '17

Hello， We meet a question about vm state. System environment: linux version: centos 6.8 libvirt version: 3.4.0 qemu version: 2.4.1 When shutdown one of vms, the state of the vm stuck in in shutdown state. And the qemu process is gone. Look up the vm log /var/log/libvirt/qemu/vm.log: "qemu: terminating on signal 15 from pid 54601 2017-07-19 04:41:09.960+0000: shutting down, reason=crashed" What may be cause vm "in shutdown" state Thanks! ahongloumeng(a)163.com

1 0

[libvirt-users] Way to detect virtual machine cpu features
by Lei Zhang 19 Jul '17

19 Jul '17

Hello everyone I want to know how can I use libvirt to detect what cpu features a virtual machine will see. I guess I could do it in following way: 1. if cpu mode is 'custom', use 'virsh cpu-baseline --features' on the cpu model to get model features. 2. if cpu mode is 'host-passthrough' or 'host-model', do a 'virsh capabilities' to list cpu features of physical host, they are identical to features of virtual machine. Is this right way to do things? Look forward to your valuable comments. Best regards, Lei

2 2

Re: [libvirt-users] [Qemu-devel] [PATCH v2] hmp: allow cpu index for "info lapic"
by Igor Mammedov 19 Jul '17

19 Jul '17

On Wed, 19 Jul 2017 16:48:23 +0800 (CST) <wang.yi59(a)zte.com.cn> wrote: > >* wang.yi59(a)zte.com.cn (wang.yi59(a)zte.com.cn) wrote: > > > >> Hi Eduardo, > > >> > > >> Thank you for your reply! > > >> > > >> >On Mon, Jul 17, 2017 at 09:49:37PM -0400, Yi Wang wrote: > > >> > > >> >> Add [vcpu] index support for hmp command "info lapic", which is > > >> > > >> >> useful when debugging ipi and so on. Current behavior is not > > >> > > >> >> changed when the parameter isn't specified. > > >> > > >> >> > > >> > > >> >> Signed-off-by: Yi Wang <wang.yi59(a)zte.com.cn> > > >> > > >> >> Signed-off-by: Yun Liu <liu.yunh(a)zte.com.cn> > > >> > > >> > > > >> > > >> >We have 8 monitor commands (see below) that use the CPU set by > > >> >the "cpu" command (mon_get_cpu()) as input. Why is "info lapic" > > >> >special? > > >> > > >> When we debugging a problem of ipi, we wanted to verify lapic info > > >> on each vCPU, but we found that we could only get vCPU 0's lapic > > >> through "info lapic", so we supposed this patch could help those > > >> who have the same problem as us. > > > > > >I think Eduardo's point is that you can already do: > > > cpu 0 > > > info lapic > > > cpu 1 > > > info lapic > > Yes, I get it, thank you. > > The reason of the problem we met is that we use "virsh qemu-monitor-command", > > so the 'cpu' command didn't work. you can try to use qmp interface directly which supports specifying cpu for monitor commands: qemu supports: -- Command: human-monitor-command Execute a command on the human monitor and return the output. Arguments: 'command-line: string' the command to execute in the human monitor 'cpu-index: int' (optional) The CPU to use for commands that require an implicit CPU maybe "virsh qemu-monitor-command" can also do it, CCing libvirt list > > > > > > > > > --- > > Best wishes > > Yi Wang

1 0

[libvirt-users] Hot-migration of OVS Vlan configuration
by Antoine Millet 14 Jul '17

14 Jul '17

Hi list, I'm using OVS as backend for guest networking on my hypervisors. VLAN configuration for each interface is specified into the guest XML definition. When I need to change VLAN configuration of a running guest, I first edit the inactive XML to keep the changes for future boots, then I use ovs-vsctl to instruct the changes on the existing OVS Port. The problem happen when the guest is migrated to another hypervisor. The "active" XML is used to instantiate the VM on the destination and this XML doesn't incorporate the changes made to the inactive one. All the changes made on source are lost on the running guest at destination. I'm looking for a solution to this problem: - IFAIK, I cannot edit the "active" XML myself other than by using provided Libvirt API (like attach-device), and such API doesn't exists for VLANs modification on OVS interface - I cannot use a migration hook to pass changes made to the inactive XML into the active one because the inactive XML is not reachable from the hook - I found a patch allowing to transport some information attached to an OVS port during migration[1]. Unfortunately, this patch doesn't transport the VLAN configuration - Modification of the active XML during the migration itself is not desirable because it will complicate the migration process by requesting an external tool Did I miss something to achieve VLAN configuration migration? How to implement that into the Libvirt properly? Thanks! Antoine [1] https://www.redhat.com/archives/libvir-list/2012-September/msg01092 .html

2 3

Re: [libvirt-users] [Fwd: UEFI NVRAM variables]
by Laszlo Ersek 13 Jul '17

13 Jul '17

Hi, thank you, Andrea, for the forward. On 07/13/17 10:19, Andrea Bolognani wrote: > -------- Forwarded Message -------- > From: Thomas Meyer <thomas(a)m3y3r.de> > To: libvirt-users(a)redhat.com > Subject: [libvirt-users] UEFI NVRAM variables > Date: Wed, 12 Jul 2017 07:49:43 +0200 > >> Hi, >> >> how do I set the BootOrder variable in an NVRAM file for UEFI boot? This is one of the most frequently asked questions about OVMF. Short version: - alternative 1: use neither <boot dev="..."/> nor <boot index="..."/> in your domain XML, and manage the BootOrder and Boot#### variables entirely within the guest (using the OVMF Setup TUI and/or the efibootmgr utility). - alternative 2: use <boot index="..."/> in your domain XML, and it will mostly do what you want. Mid-size version: * Never use "-boot order=x,y,z" with OVMF, on the QEMU command line, because the guest-visible effects of this QEMU option are fully useless to UEFI guest firmware. For more details, please refer to <https://bugzilla.redhat.com/show_bug.cgi?id=1323085#c10>. Translating the above to libvirt, never use <boot dev='...'/> elements in your domain XML with UEFI guest firmware. (They are also discouraged by the libvirt documentation, for their non-unique meaning.) * The "-device xxx,bootindex=N" properties on the QEMU command line are usable and useful to UEFI guest firmware. (This is what libvirt's <boot order='N'/> per-device elements map to, which are also what the libvirt docs recommend.) However, the expressive power of these properties is still lesser than the expressive power of the UEFI boot options, therefore the best that OVMF can do here is a kind of auto-generation of all possible boot options, and filtering and reordering them based on translation and prefix-matching. For that, the long version: please refer to the OVMF whitepaper from a few years back, where I described this algorithm in excruciating detail: http://www.linux-kvm.org/downloads/lersek/ovmf-whitepaper-c770f8c.txt Search it for "Platform-specific boot policy". >> Is there a way to configure a domain with the bios qemu option instead of pflash? If you want to boot a guest with OVMF as firmware, but map the firmware as ROM, not as pflash, you can do it. For that, you have to use the unified OVMF image (called "OVMF.fd" most commonly), not the split image (called "OVMF_CODE.fd" and other variants). The <loader> element should look like: <loader>/usr/share/OVMF/OVMF.fd</loader> and the <nvram> element should not be present. This will map to "-bios OVMF.fd" on the QEMU command line. Be *strongly* warned though that by this, you are throwing away persistent non-volatile variables, and that the fake variable support that OVMF falls back to does not -- cannot -- conform to the UEFI spec. You will encounter obscure mis-behavior with variables. (One of the obvious glitches will be that Secure Boot settings will not survive a reboot.) >> >> Are there a tool available to manipulate the UEFI variables from the outside? No, there isn't, and as far as it's up to me, there won't be. (This is another of the most frequently asked questions.) The reason for this is that the representation of the variable store on the host filesystem (in /var/lib/libvirt/qemu/nvram/<guest>_VARS.fd) is the functional composition of three layers in the edk2 driver stack: - platform-specific pflash driver / layout - generic fault tolerant write driver (implementing a kind of journaled system, where you can "lose power" in the middle of a write operation, and your varstore won't be corrupted) - generic variable driver None of these are standardized in UEFI, and even restricting ourselves to edk2 (the reference implementation of PI/UEFI), only the last two layers are documented in Intel whitepapers. Regarding examples for the first layer, OVMF itself can be built with two distinct (and incompatible) variable store layouts, and the ArmVirtQemu varstore layout is again different. In other words, a host-side utility to parse and modify these files would have to reimplement the functionality of the above three layers, deal with, and clean up, interrupted writes (see the fault tolerant writer level), and generally keep chasing any pertinent changes in the edk2 codebase. (Upstream edk2 does not guarantee backwards compatibility with existent variable stores, and it does not provide conversion tools either.) If someone feels up to writing and continuously maintaining such a host-side utility, I won't try to prevent them. But, I won't be that person. Another approach would be to replace the above-mentioned variable driver stack in OVMF, with a custom "paravirt" variable driver implementation. This would be a large project, and even if I were sympathetic to it (which I'm not), I'm pretty sure it wouldn't be welcome to upstream edk2 (because competing, parallel implementations for the same thing are a big maintenance burden). I vaguely suspect that a giga-company whose name starts with G and refers to a very large number has done this, targeting their own (unreleased / proprietary) VMM, but to my knowledge their variable driver implementation is similarly unreleased / proprietary. Either way, massaging guest-produced data from the host side, be the data "UEFI variable content" or "disk image content", is also a security question. So the only one really feasible approach here would be a libguestfs-like tool that - booted a guest on top of the variable store, - implemented a kind of "firmware guest agent" that manipulated the variables "from the inside", - and used custom commands over virtio-serial, between host and guest. As I said, a large project. Thanks, Laszlo

1 1