- Users - libvirt List Archives

[libvirt-users] FYI mail problems for libvirt lists
by Daniel P. Berrangé 20 Nov '19

20 Nov '19

It has come to our attention that many, possibly even all, people with non-redhat.com email addresses are unable to send mail to most libvirt mailing lists, receiving bounce messages saying the address doesn't exist eg Final-Recipient: rfc822; libvirt-users(a)redhat.com Action: failed Status: 5.0.0 Remote-MTA: dns; us-smtp-inbound-1.mimecast.com Diagnostic-Code: smtp; 550 Invalid Recipient - https://community.mimecast.com/docs/DOC-1369#550 [boadZMN8PrGodBBK6pzKWg.us309] In my testing, libvir-list(a)redhat.com is the only list that is currently accepting incoming mail from non-redhat.com addresses. I see bounces from libvirt-users(a)redhat.com, libvirt-ci(a)redhat.com, libvirt-announce(a)redhat.com and libvirt-security(a)redhat.com, as well as from the undocumented alias libvirt-list(a)redhat.com We believe outgoing mail delivery is still working normally in all cases. The problems appear to be caused by some changes that Red Hat administrators made to the email infrastructure recently. We have a severity 1 ticket open for this issue and are taking all possible steps to escalate it & get it resolved at the soonest opportunity. In the mean time if any users need assistance with libvirt questions, please feel free to ignore our normal guidance and use the main development list libvir-list(a)redhat.com for questions, as this appears to still be working. Alternatively you can use IRC #virt on irc.oftc.net If you need to report any security issues with libvirt, please try the libvirt-security(a)redhat.com list first, but if you get a bounce then email myself directly. Please accept our apologies for the disruption this is causing to the libvirt mailing lists. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|

1 1

[libvirt-users] Descriptions of mdev types?
by Milan Zamazal 20 Nov '19

20 Nov '19

Hi, when retrieving an mdev device info using `virsh nodedev-dumpxml' or the libvirt API, something like the following is returned: <capability type='mdev_types'> <type id='nvidia-210'> <name>GRID M60-2B4</name> <deviceAPI>vfio-pci</deviceAPI> <availableInstances>4</availableInstances> </type> ... </capability> Besides device_api, available_instances and (optional) `name', `description' of the given mdev type may be optionally provided in /sys/.../mdev_supported_types/... for each of the available mdev types. I can see in the sources that libvirt doesn't try to retrieve it -- is it intentionally or is it just an omission? If the latter, could it be added, please? It looks like a useful piece of information for the user to get an idea what the given mdev type means. Thanks, Milan

3 3

[libvirt-users] libvirt_lxc memory limit, emulator process part of the cgroup?
by Maximilian Philipps 14 Nov '19

14 Nov '19

hi, I am currently investigating a bug with libvirt lxc. Whenever I do a systemctl daemon-reload on the host, my container loses his memory limit and then reports having access to 8 exabyte of memory. I have tracked the issue down to two parts: memory.limit_in_bytes jumps from the correct value to 9223372036854771712. libvirt lxc appears to set the memory limit in transient way without writing a config for systemd. I can't prevent memory.limit_in_bytes changing by setting the correct value through systemctl set-property --runtime <scope> MemoryLimit= tasks in the memory cgroup gets cleaned up. After starting the container the cgroup contains 3 pid. The pid of the libvirt_lxc process, the pid of the init process in the container and third unknown pid that doesn't exists in /proc/. After a demon-reload only the init process remains in the cgroup and unless I move the libvirt_lxc process into the cgroup the memory limit isn't enforced. I have also noticed that when starting libvirtd it complains about GetMachineByPID failing for the libvirt_lxc process. This leaves me with one big question, the the emulator process libvirt_lxc supposed to be part of the container's cgroup or not? The leader of the container is the init process in the container. I am unsure on how the additional emulator process is supposed to be registered. Using: Debian Stretch, libvirt 5.0.0-4, systemd 241-7~deb10u1 and hybrid cgroups. Regards, Maximilian Philipps

2 1

[libvirt-users] Understanding the use of virt-install from the CLI (Linux)
by jonetsu 07 Nov '19

07 Nov '19

Hello, I've created several VMs using virt-manager and am using them. This time around though, I'd like to use the CLI approach. The problem resides in defining a storage space. This is using virt-install 1.5.1 on Xubuntu 18.04. For the occasion I created a new directory to store images. So I specify this new directory: virt-install \ --name=arch01 \ --disk path=/Share2/KVMImages/arch01.qcow2 \ --disk size=10 \ [ ... ] The above will not work as it reports: 'must be a file or a device, not a directory' So I specify a file: [ ... ] --disk path=/Share2/KVMImages/arch01.qcow2 \ --disk size=10 \ [ ... ] And it reports: 'Size must be specified for non existent volume 'arch01.qcow2'' But the size is already specified as one of the options. This is where I'm puzzled about the process. What is going on ?

3 4

[libvirt-users] Where can I find the slirp-helper?
by Han Han 07 Nov '19

07 Nov '19

For the libvirt 5.8 release, I find that there is a new comment in qemu.conf: #slirp_helper = "/usr/bin/slirp-helper" It indicates that there is a slirp-helper to help setup slirp network. But I cannot find it even after I built the latest qemu(v4.1.0-1378-g98b2e3c9ab) and libvirt (v5.9.0-rc1-2-g73f91d659b). Could you please tell me where I can find that helper program? Thanks -- Best regards, ----------------------------------- Han Han Quality Engineer Redhat. Email: hhan(a)redhat.com Phone: +861065339333

2 2

[libvirt-users] 32 bit support
by Phill. Whiteside 04 Nov '19

04 Nov '19

Hi good people, I've got a bit of a weird issue. I'm using QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.19) And after some considerable time of not using it for 32bit installations I now find that it can no longer install some older 32 bit installations (e.g. https://phillw.net/isos/lubuntu/natty/ ) The CPU goes to 100% and then after a while it just stops (I'm using virt-manager v1.5.1) I'm running lubuntu 18.04 (64 bit) on an i7 chipset that runs 64 bit debian / centos and MS server 2019 KVM instances via virt-manager without problems. Any pointers would be appreciated, Phill.

4 5

[libvirt-users] It takes long time to start kvm virtual machine with nwfilter in docker container.
by John Y. 04 Nov '19

04 Nov '19

1. It takes minutes to start the virtual machine when I add "filterref" to libvirt.xml and run command "virsh start vm1". It also takes minutes to destroy the virtual machine. <interface type="bridge"> <mac address="fa:16:3e:fa:f7:94"/> <target dev="tap69e948b0-bf"/> <source bridge="br02"/> <model type="virtio"/> <filterref filter="no-arp-spoofing"> <parameter name="IP" value="192.168.2.2"/> <parameter name="MAC" value="fa:16:3e:fa:f7:94"/> </filterref> </interface> 2. I found some logs in /var/log/libvirt/libvirtd.log 2019-11-04 03:46:18.495+0000: 15257: info : virFirewallApplyRule:815 : Applying rule '/usr/sbin/ebtables --concurrent -t nat -D PREROUTING -i tap69e948b0-bf -j libvirt-J-tap69e948b0-bf' 2019-11-04 03:46:18.495+0000: 15257: debug : virCommandRunAsync:2499 : About to run /usr/sbin/ebtables --concurrent -t nat -D PREROUTING -i tap69e948b0-bf -j libvirt-J-tap69e948b0-bf 2019-11-04 03:46:18.496+0000: 15257: debug : virFileClose:111 : Closed fd 24 2019-11-04 03:46:18.496+0000: 15257: debug : virFileClose:111 : Closed fd 26 2019-11-04 03:46:18.496+0000: 15257: debug : virFileClose:111 : Closed fd 29 2019-11-04 03:46:18.496+0000: 15257: debug : virCommandRunAsync:2502 : Command result 0, with PID 16291 2019-11-04 03:46:19.242+0000: 15257: debug : virCommandRun:2350 : Result invalid value 255, stdout: '' stderr: '2019-11-04 03:46:19.239+0000: 16291: debug : virFileClose:111 : Closed fd 26 2019-11-04 03:46:19.239+0000: 16291: debug : virFileClose:111 : Closed fd 29 2019-11-04 03:46:19.239+0000: 16291: debug : virFileClose:111 : Closed fd 24 Illegal target name 'libvirt-J-tap69e948b0-bf'. ' 2019-11-04 03:46:19.242+0000: 15257: debug : virFirewallApplyRuleDirect:704 : Ignoring error running command 2019-11-04 03:46:19.242+0000: 15257: debug : virFileClose:111 : Closed fd 25 2019-11-04 03:46:19.243+0000: 15257: debug : virFileClose:111 : Closed fd 28 2019-11-04 03:46:19.243+0000: 15257: info : virFirewallApplyRule:815 : Applying rule '/usr/sbin/ebtables --concurrent -t nat -D POSTROUTING -o tap69e948b0-bf -j libvirt-P-tap69e948b0-bf' 2019-11-04 03:46:19.243+0000: 15257: debug : virCommandRunAsync:2499 : About to run /usr/sbin/ebtables --concurrent -t nat -D POSTROUTING -o tap69e948b0-bf -j libvirt-P-tap69e948b0-bf 2019-11-04 03:46:19.243+0000: 15257: debug : virFileClose:111 : Closed fd 24 2019-11-04 03:46:19.243+0000: 15257: debug : virFileClose:111 : Closed fd 26 2019-11-04 03:46:19.244+0000: 15257: debug : virFileClose:111 : Closed fd 29 2019-11-04 03:46:19.244+0000: 15257: debug : virCommandRunAsync:2502 : Command result 0, with PID 16292 2019-11-04 03:46:19.990+0000: 15257: debug : virCommandRun:2350 : Result invalid value 255, stdout: '' stderr: '2019-11-04 03:46:19.986+0000: 16292: debug : virFileClose:111 : Closed fd 26 2019-11-04 03:46:19.986+0000: 16292: debug : virFileClose:111 : Closed fd 29 2019-11-04 03:46:19.986+0000: 16292: debug : virFileClose:111 : Closed fd 24 Illegal target name 'libvirt-P-tap69e948b0-bf'. ' 2019-11-04 03:46:19.990+0000: 15257: debug : virFirewallApplyRuleDirect:704 : Ignoring error running command 2019-11-04 03:46:19.990+0000: 15257: debug : virFileClose:111 : Closed fd 25 2019-11-04 03:46:19.990+0000: 15257: debug : virFileClose:111 : Closed fd 28 3. It works fine on hosts. 4. It works fine in other host's libvirt container. How can I solve this problem? Best regards, John

2 2

[libvirt-users] Memory ballooning
by Mauricio Tavares 31 Oct '19

31 Oct '19

So I as I was searching for the difference between memory and currentMemory, I bumped into http://www.espenbraastad.no/posts/memory-ballooning/ Is the problem this ancient post mention still an issue?

1 0

[libvirt-users] win10 vm stuck in automatic repair
by Jack Kamm 27 Oct '19

27 Oct '19

Hello, I have a Windows 10 guest, when I boot it, it goes in to Automatic Repair mode, and after some time reports it was unable to repair the PC. This is from an older snapshot ("snapshot1"), and if I try switching back to a more recent snapshot ("snapshot2"), libvirt reports that it can't find the snapshot: > libvirt.libvirtError: internal error: Child process (/usr/bin/qemu-img > snapshot -a snapshot2 /var/lib/libvirt/images/win10.qcow2) unexpected > exit status 1: qemu-img: Could not apply snapshot 'snapshot2': Failed > to load snapshot: Invalid argument Does anyone have any ideas why this might have happened, or any suggestions for how I can go about diagnosing/fixing this? This was a pretty simple Windows 10 VM, that I used for Microsoft Office. Everything was managed through virt-manager and most settings left at the original defaults. Thanks, Jack

1 1

[libvirt-users] Reg: Adding "edu" device using XML file
by bharath paulraj 24 Oct '19

24 Oct '19

Hi Team, I am exploring "edu" device in QEMU to add my own custom device. I am able to add the device using the command line. Would it be possible to add the device using XML file through libvirt? -- Regards, Bharath

2 4

[libvirt-users] X11 apps on lxc
by Jesus 21 Oct '19

21 Oct '19

Hi How can I run X11 apps on the local X11 using libvirt lxc? I already had this runing on centos 7 but I upgraded to centos 8 (I rebuild libvirt) and the socket is not in the /tmp/.X11-unix/ folder of the vm any more. Can somebody help with this? Thanks!!

2 1

[libvirt-users] [libvirt]Some questions about live migration
by Luyao Zhong 18 Oct '19

18 Oct '19

Hi libvirt experts, I have some questions about live migration. * If a live migration failed during migrating, will the domain exist on the destination host? * Is the flag VIR_MIGRATE_PAUSED make sense to live migration? It's a little confusing for me. Does that indicate if I set this flag, then the domain on the destination will not disappear even if the migration is failed, and it will in 'paused' status? If not setting this flag, what will it be? It may be similar to the question above. I filed a bug https://bugzilla.redhat.com/show_bug.cgi?id=1762703 about this flag, since its description is not very clear. Thanks in advance, looking forward to your reply. Regards, Luyao -- 2.7.4

2 1

[libvirt-users] Transient permission denied errors when sending audit logs
by Roman Mohr 17 Oct '19

17 Oct '19

Hi, In kubevirt we are running into a strange permission problem on libvirt-5.0. We see transient "Permission Denied" errors when "virAuditSend" wants to send an audit log. [1] shows the logs of one of these containers. Here an example: {"component":"virt-launcher","level":"warning","msg":"Failed to send audit message virt=kvm vm=\"kubevirt-test-default_testvmit2pqrkrlrwbhptcjcs4n67jn6pjqvmtd7pkrpdmkrl5sldzs4rxr9zdg8m45jxz\" uuid=56a33283-f6d7-4002-b188-1fed83186545 vm-ctx=+107:+107 img-ctx=+107:+107 model=dac: Permission denied","pos":"virAuditSend:141","subcomponent":"libvirt","thread":"30","timestamp":"2019-10-08T23:58:40.651000Z"} We recently switched in kubevirt to a dedicated selinux policy and remove the general "privileged" flag from the containers where we run libvirt in. This is very likely related to it, but we can't make sense out of it, because: * It randomly affects one out of a few hundred containers which we start * It is not bound to a specific node * It is only transient on that container. After a few denials libvirt can just continue. * Sometimes it is accompanied with a transient "Permission denied" on /dev/null from our code in that container (so not from something which libvirt tries to do). Has someone seen something like this before in different environments? Best Regards, Roman [1] https://storage.googleapis.com/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt…

2 2

[libvirt-users] create virtual network fails with virt-manager
by Marko Horn 16 Oct '19

16 Oct '19

hello list, creatig a virtual network via virt-manager fails. gentoo linux vanilla-sources 5.3.1 virt-manager 2.2.1 qemu 4.0 libvirt 5.5.0 the error output of Error creating virtual network: internal error: Failed to apply firewall rules /sbin/iptables -w --table filter --insert LIBVIRT_INP --in-interface virbr1 --protocol tcp --destination-port 67 --jump ACCEPT: iptables: No chain/target/match by that name. Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/createnet.py", line 472, in _async_net_create netobj.create() File "/usr/lib64/python3.6/site-packages/libvirt.py", line 2993, in create if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self) libvirt.libvirtError: internal error: Failed to apply firewall rules /sbin/iptables -w --table filter --insert LIBVIRT_INP --in-interface virbr1 --protocol tcp --destination-port 67 --jump ACCEPT: iptables: No chain/target/match by that name. /sbin/iptables exists any ideas? kind regards m@rko -- zbfmail - Mittendrin statt nur Datei! Datei sein ist alles!

2 2

[libvirt-users] Fwd: Libvirt-QEMU : Multiplex the output from qemu's serial port to a pty as well as a file (basically redirect console to file as well as pty device)
by gokul cg 11 Oct '19

11 Oct '19

Hi Folks , As per https://libvirt.org/formatdomain.html#elementsConsole Regardless of the type, character devices can have an optional log file associated with them. Whether the lgging functionality is same as mapping device to file ? Whether libvirt xml syntax below both 1 and 2 are same ? 1) <serial type='pty'> <log file='/var/lib/nova/instances/7151c8b7-1ea5-4701-bb79-b482d9e253b8/console.log' append='off'/> <target port='0'/> </serial> 2) <serial type='pty'> <source path='/tmp/serial.log'/> <target port='0'/> </serial> is it possible to multiplex the output from qemu's serial port to a pty as well as a file (basically redirect console to file as well as pty device)? Regards Gokul

1 2

[libvirt-users] hidden state='on' not working
by Michael Lipp 08 Oct '19

08 Oct '19

Hi, I have set <kvm> <hidden state='on'/> </kvm> in my configuration file. But looking at the command line, I see -cpu ...,hypervisor=on,... Should the setting result in hypervisor=off (or -hypervisor) - Michael

2 2

[libvirt-users] Emulated TPM doesn't work on Debian Buster
by procmem＠riseup.net 07 Oct '19

07 Oct '19

Hi. I am very interested in the security properties a totally open TPM can give our users - its use as a universal smartcard to protect all types of keys. When adding the virtual 1.2 or 2.0 TPM I get the vague error below. OS is Debian stable with standard packages. Error starting domain: Unable to find 'swtpm' binary in $PATH: No such file or directory Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 66, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1400, in startup self._backend.create() File "/usr/lib/python3/dist-packages/libvirt.py", line 1080, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirt.libvirtError: Unable to find 'swtpm' binary in $PATH: No such file or directory

3 5

[libvirt-users] Error validating install location: Distro 'rhel8' does not exist in our dictionary
by Kaushal Shriyan 07 Oct '19

07 Oct '19

Hi, I am running the below command to spawn CentOS8 based Virtual Machines using KVM based technology virt-install --name=centos8 > --file=/linuxkvmguestosdisk/var/lib/libvirt/images/centos8 --file-size=100 > --nonsparse --vcpus=2 --ram=8096 --network=bridge:br0 --os-type=linux > --os-variant=rhel8 --graphics none > --location=/linuxkvmguestosdisk/var/lib/libvirt/isos/CentOS-8-x86_64-1905-dvd1.iso > --extra-args="console=ttyS0" > ERROR Error validating install location: Distro 'rhel8' does not exist > in our dictionary Any clue and i look forward to hearing from you. Thanks in advance. Best Regards,

4 4

Re: [libvirt-users] Internal error reported by libvirt while creating a VM
by Andrea Bolognani 04 Oct '19

04 Oct '19

Re-added the list. Please *do not* drop the libvirt-users mailing list from the recipients again! On Thu, 2019-10-03 at 16:42 -0400, Ajay Kumar wrote: > Hi Andrea, > > Thank you for your help, > > The above issues are addressed while reinstalling libvirt 4.0.0. Currently, I could create a VMs on libvirt. > > I have another issue while configuring/editing win10.xml file. > After edit or insert of few lines in win10.XML file using virsh i.e at /etc/libvirt/qem$ virsh edit win10 Saying that you changed "few lines" is not at all useful: if you hope to get any help from the list, you'll have to share the *exact* changes you made each time and the full XML configuration that resulted from them. > I am getting a below error. > @ubuntu-kvm3:/etc/libvirt/qemu$ virsh edit win10 > error: internal error: Child process (LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /usr/local/bin/qemu-system-x86_64 -help) unexpected exit status 126: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied > > I understand that this could be the problem of AppArmor security feature it doesn't allow new binary such as (qemu-system-x86_64) to execute > > Later I have followed the below link to address > [ https://www.reddit.com/r/VFIO/comments/9pi2cd/how_to_set_up_qemu_30_on_ubun… > 6. Create AppArmor rules so libvirt can use the binary ] > > here i have added few lines in 2 files as per the procedure. later when i restart apparmor I got the below error Again, saying that you added "few lines" is not helpful because we have no idea what those lines look like, so it's simply impossible for anyone to figure out the root cause of the error message you're seeing. Please share the *exact* changes you made. -- Andrea Bolognani / Red Hat / Virtualization

1 0

[libvirt-users] network namespace for multiple overlapping nat networks?
by Fred Clift 04 Oct '19

04 Oct '19

I have noticed that you can't have multiple separate NAT style libvirt networks defined with the same private IP blocks. For example I have this default network: <network> <name>default</name> <uuid>13baf167-02ff-4312-928c-b82ed4df5785</uuid> <forward mode='nat'> <nat> <port start='1024' end='65535'/> </nat> </forward> <bridge name='virbr1' stp='on' delay='0'/> <mac address='52:54:00:9c:8f:7c'/> <ip address='192.168.122.1' netmask='255.255.255.0'> <dhcp> <range start='192.168.122.2' end='192.168.122.25'/> </dhcp> </ip> </network> I can't define another nat network that uses the same IP address range. I assume this is an implementation limit because of how the iptables rules are written/work for doing the NAT. I'd like to have 10 networks with the same default IP address, attached to 10 vms that all run off the same read-only image. I know that I could use different ranges and then have my vms use dhcp, and or a few other similar ways. I'm limited by the virtual image I want to run (close source OS, licensed-and-IP-locked software - I have plenty of licences for instances). I'd love to replace my 10 instances all with their own IPs on a public bridge with 10 NAT'd instances all using the same IP each on their own little network world - so I'd make a separate bridge for each, but of course it doesn't work. I have a proof-of-concept setup where I use a routed private network + nat with the application vm and a small linux vm in pairs. The linux vms have a public IP, and a private bridge with a fixed ip to be the default route of the app vm. Then the app vm can have a fixed ip, route to a fixed default route, and get natted to whatever it's buddy router vm's public IP is. This works - but then I have 20 vms instead of 10. They are small and dont use much cpu, but they use ram... which is somewhat constraining. And I have to maintain a router image. I'm going to settle for this setup If I have to, but I'd rather not. So I had the bright idea of somehow routing/natting each vm through a network namespace. I could perhaps avoid having to have a whole separate linux instance just to get a copy of the network stack to do nat with. I'm kind of struggling to see how I'd could have each libvirt vm run in it's own namespace. I don't think it is possible actually. But perhaps I could use an extra set of IPs and an extra bridge/veth-pair to work some kind of magic. Anyone out there doing something like this? Can you help me wrap my head around how to mix libvirt kvm VMs and network namespaces? Is there some other simpler way to achieve what I want? Thanks. Fred Clift fred(a)clift.org

1 0

[libvirt-users] Using encrypted volumes
by Dominik Reusser 02 Oct '19

02 Oct '19

I was encouraged [1] to use the storage encryption mechanism of libvirt [2]. However, it is not clear to me how to generate a corresponding encrypted volume. Preferably, I would like to use virt-install to arrive at such an encrypted volume, similar to e.g. virt-install --connect qemu:///system -n testImage -r 2048 --os-type=linux --disk testImage.img,device=disk,bus=virtio,size=8,sparse=true,format=raw --os-variant debian10 --vnc --location ftp://ftp2.de.debian.org/debian/dists/buster/main/installer-amd64/ I already asked a related question on server fault [3], but this is a better targeted audience. Sorry for double-posting. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933385 [2] https://libvirt.org/formatstorageencryption.html#StorageEncryption [3] https://serverfault.com/questions/986488/how-to-enable-volumeencryption-dur…

1 0

Re: [libvirt-users] Internal error reported by libvirt while creating a VM
by Andrea Bolognani 02 Oct '19

02 Oct '19

On Tue, 2019-10-01 at 17:55 -0400, Ajay Kumar wrote: > Hi Andrea, > > Thank you for your response. Sure I don't CC to libvirt developers. Please keep the list in the loop, though! I've re-added it. > I am getting an error while creating a Win10 virtual machine using VMM or virt-manager GUI. > I could configure the windows 10 quest using its XML file only ofter creating a VM using virt-manager GUI in the following the path /etc/libvirt/qemu. > > The modified QEMU emulator is running correctly > @ubuntu-kvm3:/usr/local/bin$ ls > ivshmem-client qemu-ga qemu-io qemu-pr-helper virsh virt-host-validate virt-pki-validate vmi-dump-memory vmi-process-list vmi-win-offsets > ivshmem-server qemu-img qemu-nbd qemu-system-x86_64 virt-admin virt-login-shell virt-xml-validate vmi-module-list vmi-win-guid This only proves that you've installed it, not that it works. And as I said, the modified binary probably works fine on its own but libvirt might not be able to drive it, at least without tweaks. > @ubuntu-kvm3:/etc/libvirt/qemu$ ls > networks Just for the record, you're not supposed to modify files in /etc/libvirt/qemu directly; use virsh instead. > I couldn't see guest XML file here(because the VM creation was not done). > attached snap displaying error while creating a VM. If you run $ virt-manager --debug from the command line you will get a lot of output, including the XML that's passed to libvirt. Please attempt the installation again, capture that output in a plain text file and send it to the list as an attachment. Also run $ /usr/local/bin/qemu-system-x86_64 -machine help and attach the output of that command, too. That should help us figure out what's wrong. -- Andrea Bolognani / Red Hat / Virtualization

1 0

[libvirt-users] Internal error reported by libvirt while creating a VM
by Ajay Kumar 01 Oct '19

01 Oct '19

Hi, am Ajay Kumar. I am trying to create a virtual machine on the remote host (where libvirt 5.8.0) was installed using a virtual machine manager which are running on the local ubuntu machine. *The specification of my remote host are:* *Hypervisor: *KVM *QEMU version:* QEMU emulator version 2.4.0.1, Copyright (c) 2003-2008 Fabrice Bellard The below error is propagating when I am trying to install KVM-VMI ( https://github.com/KVM-VMI/kvm-vmi/tree/kvmi) with modified QEMU, and there is a modified QEMU involved, in /usr/local/bin/qemu-system-x86_64. The below particular error propagating when I am trying to create a virtual machine using VMM gui (virt-manager). Unable to complete install: 'internal error: process exited while connecting to monitor: (process:7400): GLib-WARNING **: 18:19:45.044: ../../../../glib/gmem.c:489: custom memory allocation vtable not supported 2019-09-30T18:19:45.046714Z qemu-system-x86_64: -msg timestamp=on: Unsupported machine type Use -machine help to list supported machines!' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 2553, in _do_async_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 498, in start_install doboot, transient) File "/usr/share/virt-manager/virtinst/guest.py", line 434, in _create_guest domain = self.conn.createXML(install_xml or final_xml, 0) File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3603, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirtError: internal error: process exited while connecting to monitor: (process:7400): GLib-WARNING **: 18:19:45.044: ../../../../glib/gmem.c:489: custom memory allocation vtable not supported 2019-09-30T18:19:45.046714Z qemu-system-x86_64: -msg timestamp=on: Unsupported machine type Use -machine help to list supported machines! -- *With Best Regards:* Ajay

2 1

[libvirt-users] virsh -c lxc:/// setvcpus and <vcpu> configuration fails
by info＠layer7.net 23 Sep '19

23 Sep '19

Hi folks! i created a server with this XML file: <domain type='lxc'> <name>lxctest1</name> <uuid>227bd347-dd1d-4bfd-81e1-01052e91ffe2</uuid> <metadata> <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0"> <libosinfo:os id="http://centos.org/centos/6.9"/> </libosinfo:libosinfo> </metadata> <memory unit='KiB'>1024000</memory> <currentMemory unit='KiB'>1024000</currentMemory> <vcpu>2</vcpu> <numatune> <memory mode='strict' placement='auto'/> </numatune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> </os> <idmap> <uid start='0' target='200000' count='65535'/> <gid start='0' target='200000' count='65535'/> </idmap> <features> <privnet/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='mount' accessmode='mapped'> <source dir='/mnt'/> <target dir='/'/> </filesystem> <interface type='network'> <mac address='00:16:3e:3e:3e:bb'/> <source network='Public Network'/> </interface> <console type='pty'> <target type='lxc' port='0'/> </console> </devices> </domain> I would expect it to have 2 cpu cores and 1 GB RAM. The RAM config works. The CPU config does not: [root@lxctest1 ~]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 24 On-line CPU(s) list: 0-23 Thread(s) per core: 2 Core(s) per socket: 6 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel CPU family: 6 Model: 62 Model name: Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz Stepping: 4 CPU MHz: 2399.950 BogoMIPS: 4205.88 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 15360K NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23 It gives me all CPU's from the host. I also tried it with <cpu> <topology sockets='1' cores='2' threads='1'/> </cpu> That didnt help too. I tried to modify the vcpus through virsh: #virsh -c lxc:/// setvcpus lxctest1 2 error: this function is not supported by the connection driver: virDomainSetVcpus Which didnt work too. This happens on: Centos 7 Kernel: 5.1.15-1.el7.elrepo.x86_64 #virsh -V Virsh command line tool of libvirt 4.5.0 See web site at https://libvirt.org/ Compiled with support for: Hypervisors: QEMU/KVM LXC ESX Test Networking: Remote Network Bridging Interface netcf Nwfilter VirtualPort Storage: Dir Disk Filesystem SCSI Multipath iSCSI LVM RBD Gluster ZFS Miscellaneous: Daemon Nodedev SELinux Secrets Debug DTrace Readline and also on Fedora 30 Kernel: 5.2.9-200.fc30.x86_64 # virsh -V Virsh command line tool of libvirt 5.1.0 See web site at https://libvirt.org/ Compiled with support for: Hypervisors: QEMU/KVM LXC LibXL OpenVZ VMware PHYP VirtualBox ESX Hyper-V Test Networking: Remote Network Bridging Interface netcf Nwfilter VirtualPort Storage: Dir Disk Filesystem SCSI Multipath iSCSI LVM RBD Sheepdog Gluster ZFS Miscellaneous: Daemon Nodedev SELinux Secrets Debug DTrace Readline ----------- Can anyone please tell me what i am doing wrong here ? Thank you ! Greetings Oliver

3 3

[libvirt-users] experience with balloon memory ?
by Lentes, Bernd 23 Sep '19

23 Sep '19

Hi ML, i'm thinking about using balloon memory for our domains. We have about 15 domains running concurrently, and i think it might be nice if a domain requires more RAM it grabs it, and if it don't need it anymore, it releases it. But i have no experience with it. So i have some questions: - is live migration possible with balloon ? - is it stable ? - the domain needs an appropriate driver i think ? - are there drivers for Windows 7 and 10 ? - are there drivers for Linux, which kernel version do i need ? - does someone have experience with it ? Is there a kind of "best practise" ? Thanks. Bernd -- Bernd Lentes Systemadministration Institut für Entwicklungsgenetik Gebäude 35.34 - Raum 208 HelmholtzZentrum münchen bernd.lentes(a)helmholtz-muenchen.de phone: +49 89 3187 1241 phone: +49 89 3187 3827 fax: +49 89 3187 2294 http://www.helmholtz-muenchen.de/idg Perfekt ist wer keine Fehler macht Also sind Tote perfekt Helmholtz Zentrum Muenchen Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH) Ingolstaedter Landstr. 1 85764 Neuherberg www.helmholtz-muenchen.de Aufsichtsratsvorsitzende: MinDir'in Prof. Dr. Veronika von Messling Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Kerstin Guenther Registergericht: Amtsgericht Muenchen HRB 6466 USt-IdNr: DE 129521671

1 0