- Users - libvirt List Archives

[libvirt-users] virConnectClose
by llilulu 22 Aug '17

22 Aug '17

libvirt version: 3.4.0 When invoke virConnectDomainEventRegisteAny register event on a hypervisor connection, before virConnecClose, should I invoke virConnectDomainEventDeregisterAny. If a hypervisor connection close unexpected, call virConnectDomainEventDeregisterAny will return error? Can tell me more detail about event? This libvirt doc not more description. Thanks

1 0

[libvirt-users] Increasing video memory available to Windows
by Alex 14 Aug '17

14 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] virsh blockcommit fails regularily (was: virtual drive performance)
by Dominik Psenner 14 Aug '17

14 Aug '17

Hi, a small update on this. We have migrated the virtualized host to use the virtio drivers and now the drive performance is improved so that we can see a constant transfer rate. Before it used to be the same rate but regularly dropped to a few bytes/sec for a few seconds and then was fast again. However we still observe that the following fails regularily: $ virsh snapshot-create-as --domain domain --name backup --no-metadata --atomic --disk-only --diskspec hda,snapshot=external $ virsh blockcommit domain hda --active --pivot error: failed to pivot job for disk hda error: block copy still active: disk 'hda' not ready for pivot yet Could not merge changes for disk hda of domain. VM may be in invalid state. Then running the following in the morning succeeds and successfully pivotes the snapshot into the base image while the vm is live: $ virsh blockjob domain hda --abort $ virsh blockcommit domain hda --active --pivot Successfully pivoted We run the backup process every day once and it failed on the following days: 2017-07-07 2017-07-20 2017-07-27 2017-08-12 2017-08-14 Looking at this it roughly happens once a week and the guest from then on writes into the snapshot backlog. That snapshot backlog file grows about 8gb every day and thus the issue always needs immediate attention. Any ideas what could cause this issue? Is this a bug (race condition) of `virsh blockcommit` that sometimes fails because it is invoked at the wrong time? Cheers, Dominik 2017-07-07 9:21 GMT+02:00 Dominik Psenner <dpsenner(a)gmail.com>: > Of course the cronjob fails when trying to virsh blockcommit and not when > creating the snapshot, sorry for the noise. > > 2017-07-07 9:15 GMT+02:00 Dominik Psenner <dpsenner(a)gmail.com>: > >> Hi, >> >> different day, same issue.. cronjob runs and fails: >> >> $ virsh snapshot-create-as --domain domain --name backup --no-metadata >> --atomic --disk-only --diskspec hda,snapshot=external >> error: failed to pivot job for disk hda >> error: block copy still active: disk 'hda' not ready for pivot yet >> Could not merge changes for disk hda of domain. VM may be in invalid >> state. >> >> Then running the following in the morning succeeds and successfully >> pivotes the snapshot into the base image while the vm is live: >> >> $ virsh blockjob domain hda --abort >> $ virsh blockcommit domain hda --active --pivot >> Successfully pivoted >> >> This need of manual interventions is becoming a tiring job.. >> >> I someone else seeing the same issue or has an idea what the cause could >> be? >> Can I trust the output and is the base image really up to the latest >> state? >> >> Cheers >> >> 2017-07-02 10:30 GMT+02:00 Dominik Psenner <dpsenner(a)gmail.com>: >> >>> Just a little catch-up. This time I was able to resolve the issue by >>> doing: >>> >>> virsh blockjob domain hda --abort >>> virsh blockcommit domain hda --active --pivot >>> >>> Last time I had to shut down the virtual machine and do this while being >>> offline. >>> >>> Thanks Wang for your valuable input. As far as the memory goes, there's >>> plenty of head room: >>> >>> $ free -h >>> total used free shared buff/cache >>> available >>> Mem: 7.8G 1.8G 407M 9.7M >>> 5.5G 5.5G >>> Swap: 8.0G 619M 7.4G >>> >>> 2017-07-02 10:26 GMT+02:00 王李明 <wanglm(a)certusnet.com.cn>: >>> >>>> mybe this is because you physic host memory is small >>>> >>>> then this will Causing instability of the virtual machine >>>> >>>> But I'm just guessing >>>> >>>> You can try to increase your memory >>>> >>>> >>>> >>>> >>>> >>>> Wang Liming >>>> >>>> >>>> >>>> >>>> >>>> *发件人:* libvirt-users-bounces(a)redhat.com [mailto:libvirt-users-bounces@ >>>> redhat.com] *代表 *Dominik Psenner >>>> *发送时间:* 2017年7月2日 16:22 >>>> *收件人:* libvirt-users(a)redhat.com >>>> *主题:* Re: [libvirt-users] virtual drive performance >>>> >>>> >>>> >>>> Hi again, >>>> >>>> just today an issue I've thought to be resolved popped up again. We >>>> backup the machine by doing: >>>> >>>> virsh snapshot-create-as --domain domain --name backup --no-metadata >>>> --atomic --disk-only --diskspec hda,snapshot=external >>>> >>>> # backup hda.qcow2 >>>> >>>> virsh blockcommit domain hda --active --pivot >>>> >>>> Every now and then this process fails with the following error message: >>>> >>>> error: failed to pivot job for disk hda >>>> error: block copy still active: disk 'hda' not ready for pivot yet >>>> Could not merge changes for disk hda of domain. VM may be in invalid >>>> state. >>>> >>>> I expect live backups are a great asset and should work. Is this a bug >>>> that may relates also to the virtual drive performance issues we observe? >>>> >>>> Cheers >>>> >>>> >>>> >>>> 2017-07-02 10:10 GMT+02:00 Dominik Psenner <dpsenner(a)gmail.com>: >>>> >>>> Hi >>>> >>>> a small update on this. I just migrated the vm from the site to my >>>> laptop and fired it up. The exact same xml configuration (except file paths >>>> and such) starts up and bursts with 50Mb/s to 115Mb/s in the guest. This >>>> allows only one reasonable answer: the cpu on my laptop is somehow better >>>> suited to emulate IO than the CPU built into the host on site. The host >>>> there is a HP proliant microserver gen8 with xeon processor. But the >>>> processor there is also never capped at 100% when the guest copies files. >>>> >>>> I just ran another test by copying a 3Gb large file on the guest. What >>>> I can observe on my computer is that the copy process is not at a constant >>>> rate but rather starts with 90Mb/s, then drops down to 30Mb/s, goes up to >>>> 70Mb/s, drops down to 1Mb/s, goes up to 75Mb/s, drops to 1Mb/s, goes up to >>>> 55Mb/s and the pattern continues. Please note that the drive is still >>>> configured as: >>>> >>>> <driver name='qemu' type='qcow2' cache='none' io='threads'/> >>>> >>>> and I would expect a constant rate that is either high or low since >>>> there is no caching involved and the underlying hard drive is a samsung ssd >>>> evo 850. To have an idea how fast that drive is on my laptop: >>>> >>>> $ dd if=/dev/zero of=testfile bs=1M count=1000 oflag=direct >>>> 1000+0 records in >>>> 1000+0 records out >>>> 1048576000 bytes (1.0 GB, 1000 MiB) copied, 2.47301 s, 424 MB/s >>>> >>>> >>>> >>>> I can further observe that the smaller the saved chunks are the slower >>>> the overall performance is: >>>> >>>> dd if=/dev/zero of=testfile bs=512K count=1000 oflag=direct >>>> 1000+0 records in >>>> 1000+0 records out >>>> 524288000 bytes (524 MB, 500 MiB) copied, 1.34874 s, 389 MB/s >>>> >>>> $ dd if=/dev/zero of=testfile bs=5K count=1000 oflag=direct >>>> 1000+0 records in >>>> 1000+0 records out >>>> 5120000 bytes (5.1 MB, 4.9 MiB) copied, 0.105109 s, 48.7 MB/s >>>> >>>> $ dd if=/dev/zero of=testfile bs=1K count=10000 oflag=direct >>>> 10000+0 records in >>>> 10000+0 records out >>>> 10240000 bytes (10 MB, 9.8 MiB) copied, 0.668438 s, 15.3 MB/s >>>> >>>> $ dd if=/dev/zero of=testfile bs=512 count=20000 oflag=direct >>>> 20000+0 records in >>>> 20000+0 records out >>>> 10240000 bytes (10 MB, 9.8 MiB) copied, 1.10964 s, 9.2 MB/s >>>> >>>> Could this be a limiting factor? Does qemu/kvm do many many writes of >>>> just a few bytes? >>>> >>>> >>>> Ideas, anyone? >>>> >>>> Cheers >>>> >>>> >>>> >>>> 2017-06-21 20:46 GMT+02:00 Dan <srwx4096(a)gmail.com>: >>>> >>>> On Tue, Jun 20, 2017 at 04:24:32PM +0200, Gianluca Cecchi wrote: >>>> > On Tue, Jun 20, 2017 at 3:38 PM, Dominik Psenner <dpsenner(a)gmail.com> >>>> wrote: >>>> > >>>> > > >>>> > > to the following: >>>> > > >>>> > > <disk type='file' device='disk'> >>>> > > <driver name='qemu' type='qcow2' cache='none'/> >>>> > > <source file='/var/data/virtuals/machines/windows-server-2016- >>>> > > x64/image.qcow2'/> >>>> > > <backingStore/> >>>> > > <target dev='hda' bus='scsi'/> >>>> > > <address type='drive' controller='0' bus='0' target='0' unit='0'/> >>>> > > </disk> >>>> > > >>>> > > Do you see any gotchas in this configuration that could prevent the >>>> > > virtualized guest to power on and boot up? >>>> > > >>>> > > >>>> > When I configure like this, from a linux guest point of view I get >>>> this >>>> > Symbios Logic SCSI Controller: >>>> > 00:08.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a >>>> > >>>> > But htis is true only if you add the SCSI controller too, not only >>>> the disk >>>> > definition. >>>> > In my case >>>> > >>>> > <controller type='scsi' index='0'> >>>> > <address type='pci' domain='0x0000' bus='0x00' slot='0x08' >>>> > function='0x0'/> >>>> > </controller> >>>> > >>>> > Note the slot='0x08' that is reflected into the first field of lspci >>>> inside >>>> > my linux guest. >>>> > So between your controllers you have to add the SCSI one >>>> > >>>> > In my case (Fedora 25 with virt-manager-1.4.1-2.fc25.noarch, >>>> > qemu-kvm-2.7.1-6.fc25.x86_64, libvirt-2.2.1-2.fc25.x86_64) with "Disk >>>> bus" >>>> > set as SCSI in virt-manager, the xml defintiion for the guest is >>>> > automatically updated with the controller if not existent yet. >>>> > And the disk definition sections is like this: >>>> > >>>> > <disk type='file' device='disk'> >>>> > <driver name='qemu' type='qcow2'/> >>>> > <source file='/var/lib/libvirt/images/slaxsmall.qcow2'/> >>>> > <target dev='sda' bus='scsi'/> >>>> > <boot order='1'/> >>>> > <address type='drive' controller='0' bus='0' target='0' >>>> unit='0'/> >>>> > </disk> >>>> > >>>> > So I think you should set dev='sda' and not 'hda' in your xml for it >>>> > >>>> >>>> I am actually very curious to know if that would make a difference. I >>>> don't have a such windows vm images ready to test at present. >>>> >>>> Dan >>>> > I don't kknow if w2016 contains the symbios logic drivers already >>>> > installed, so that a "simple" reboot could imply an automatic >>>> > reconfiguration of the guest.... >>>> > Note also that in Windows when the hw configuration is considered >>>> heavily >>>> > changed, you could be asked to register again (I don't think that the >>>> IDE >>>> > --> SCSI should imply it...) >>>> > >>>> > Gianluca >>>> >>>> > _______________________________________________ >>>> > libvirt-users mailing list >>>> > libvirt-users(a)redhat.com >>>> > https://www.redhat.com/mailman/listinfo/libvirt-users >>>> >>>> >>>> >>>> >>>> -- >>>> >>>> Dominik Psenner >>>> >>>> >>>> >>>> >>>> -- >>>> >>>> Dominik Psenner >>>> >>> >>> >>> >>> -- >>> Dominik Psenner >>> >> >> >> >> -- >> Dominik Psenner >> > > > > -- > Dominik Psenner > -- Dominik Psenner

2 2

[libvirt-users] libvirt: XML-RPC error : Cannot write data: Broken pipe
by netsurfed 10 Aug '17

10 Aug '17

Hi all, I think it's a bug, when call virDomainGetState after "service libvirtd stop", I receive signal SIGPIPE. I want to know how to avoid this problem? And Other interfaces will also encounter this problem？ Below the bt information: Below some information about my hypervisor: root@ubuntu-05:/datapool/zhuohf# virsh -v 3.4.0 root@ubuntu-05:/datapool/zhuohf# qemu-x86_64 -version qemu-x86_64 version 2.9.0 Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers

4 6

[libvirt-users] ANNOUNCE: Oz 0.16.0 release
by Chris Lalancette 08 Aug '17

08 Aug '17

All, I'm pleased to announce release 0.16.0 of Oz. Oz is a program for doing automated installation of guest operating systems with limited input from the user. Release 0.16.0 is a bugfix and feature release for Oz. Some of the highlights between Oz 0.15.0 and 0.16.0 are: * Windows 10 and 2016 support * All timeouts are now configurable * Ubuntu 16.04, 16.10, 17.04 support * Mageia 2, 3, 4, 5 support * Properly find UEFI firmware, which should fix aarch64 installs * Fedora 24, 25, 26 support * FreeBSD 11 support * Replace internal use of pycurl with requests * OpenSUSE Leap support * Timeouts are now based on time, not the number of iterations of the loop * Modern Fedora and RHEL guests will print out a lot more anaconda debugging information to the terminal that oz-install was launched from A tarball and zipfile of this release is available on the Github releases page: https://github.com/clalancette/oz/releases . Packages for Fedora rawhide and 26 have been built in Koji and will eventually make their way to stable. Instructions on how to get and use Oz are available at http://github.com/clalancette/oz/wiki . If you have questions or comments about Oz, please feel free to contact me at clalancette at gmail.com, or open up an issue on the github page: http://github.com/clalancette/oz/issues . Thanks to everyone who contributed to this release through bug reports, patches, and suggestions for improvement. Chris Lalancette

1 0

[libvirt-users] Avoiding console prints by Libvirt Qemu python APIs
by swaroop sp 07 Aug '17

07 Aug '17

Hi, I am trying to check if a domain exists by using the libvirt python API *"lookupbyname()*". If the domain does not exist, it prints an error message on the console saying "*Domain not found*". I need the errors or logs only in syslog. I have tried redirecting stderr and stdout. But, it doesn't have any effect. I have also tried playing around with the libvirt logging settings described in https://libvirt.org/logging.html . No effect again. "stdio_handler" flag in /etc/libvirt/qemu.conf is set to "file" as well. Following is my test code: import os, sysimport libvirt conn = libvirt.open('qemu:///system') # Find the application in the virsh domaintry: sys.stdout = open(os.devnull, "w") sys.stderr = open(os.devnull, "w") dom = conn.lookupByName('abcd') sys.stdout = sys.__stdout__ sys.stderr = sys.__stderr__except Exception as e: syslog.syslog (syslog.LOG_ERR, 'Could not find the domain. ERROR: %s.' % (e)) sys.stdout = sys.__stdout__ sys.stderr = sys.__stderr__ Output: $ python test.py libvirt: QEMU Driver error : Domain not found: no domain with matching name 'abcd' $ Is there a way to avoid this console print? Regards, Swaroop

2 1

[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] Understanding the contents of virsh dump --memory-only
by Arnabjyoti Kalita 02 Aug '17

02 Aug '17

Hello, I was trying to understand the ELF file generated by the virsh dump (--memory-only) command. I have successfully generated a dump of the VM memory using this command. I specifically am trying to understand the loadable segments of this ELF file. I ran readelf -a <filename> to get the information that I need. Below shows the details of the loadable segments in a much better format :- Loading ELF header #1. offset: 1320 filesize: 655360 memsize: 655360 vaddr: 0 paddr: 0 align: 0 flags: 0 Loading ELF header #2. offset: 656680 filesize: 65536 memsize: 65536 vaddr: 0 paddr: a0000 align: 0 flags: 0 Loading ELF header #3. offset: 722216 filesize: 1072955392 memsize: 1072955392 vaddr: 0 paddr: c0000 align: 0 flags: 0 Loading ELF header #4. offset: 1073677608 filesize: 67108864 memsize: 67108864 vaddr: 0 paddr: f4000000 align: 0 flags: 0 Loading ELF header #5. offset: 1140786472 filesize: 67108864 memsize: 67108864 vaddr: 0 paddr: f8000000 align: 0 flags: 0 Loading ELF header #6. offset: 1207895336 filesize: 8192 memsize: 8192 vaddr: 0 paddr: fc054000 align: 0 flags: 0 Loading ELF header #7. offset: 1207903528 filesize: 262144 memsize: 262144 vaddr: 0 paddr: fffc0000 align: 0 flags: 0 I wanted to know why in this case, is the virtual address (denoted by vaddr) 0 for each of the loadable segments ? Will it be okay if I load the elf file taking the values of physical address (denoted by paddr) into account ? Specifically after loading the file, can I be certain that all of my contents will have been loaded into memory address starting from 0 ? Will the loaded contents be present in the exact location as specified (by paddr) here ? Thanks and Regards. Arnab

2 2

[libvirt-users] Libvirt fails on network disk with ISCSI protocol
by Fred Rolland 02 Aug '17

02 Aug '17

Hi, I am working on oVirt, and I am trying to run a VM with a network disk with ISCSI protocol ( the storage is on a Cinder server). Here is the disk XML I use: <disk device="disk" snapshot="no" type="network"> <address bus="0" controller="0" target="0" type="drive" unit="0" /> <source name="iqn.2010-10.org.openstack:volume-37fea687-040c-4a88-844c-117d1a90e9b2" protocol="iscsi"> <host name="10.35.0.20" port="3260" /> </source> <target bus="scsi" dev="sda" /> <boot order="1" /> <driver cache="none" error_policy="stop" io="threads" name="qemu" type="raw" /> </disk> I get the following error: libvirtError: internal error: process exited while connecting to monitor: 2017-08-02T14:38:58.378430Z qemu-kvm: -drive file=iscsi:// 10.35.0.20:3260/iqn.2010-10.org.openstack%3Avolume-37fea687-040c-4a88-844c-117d1a90e9b2,format=raw,if=none,id=drive-scsi0-0-0-0,cache=none,werror=stop,rerror=stop,aio=threads: Failed to parse URL : iscsi:// 10.35.0.20:3260/iqn.2010-10.org.openstack%3Avolume-37fea687-040c-4a88-844c-117d1a90e9b2 It seems that the ':' character got changed on the way to %3A. Any suggestions on the root cause of this issue? Thanks, Fred Rolland

2 2

[libvirt-users] Regarding KVM-Qemu Migration code
by Aditya Bhardwaj 02 Aug '17

02 Aug '17

Respected Sir, I need to modify kvm-qemu migration code. Please tell me where i can find the code. -- *Thank youWith Regards:Aditya Bhardwaj* *Dept. of CSE * *NITTTR (Ministry of MHRD, Govt. of India)* *Sector-26, **Chandigarh - 160019 INDIA* https://scholar.google.co.in/citations?user=rEHhEnEAAAAJ&hl=en

2 1

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

31 Jul '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 26 Jul '17

26 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 26 Jul '17

26 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 26 Jul '17

26 Jul '17

2 1

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

26 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 임영빈 20 Jul '17

20 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