- Users - libvirt List Archives

[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 24 Sep '19

24 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

[libvirt-users] Privacy Extension not working in VM
by Thomas Luening 23 Sep '19

23 Sep '19

Hello @ all With the rebuilding of my Server from Debian 9 to Debian 10, I also switch from Virtual Box to Libvirt/KVM. Due to new requirements for the VMs, now I have an actual problem, which unfortunately I can not solve. The problem has already been discussed in the German Debian-Forum ... unfortunately also without success. The facts: - ISP = Dual Stack with daily separation - Host and VM = Debian 10 - The VMs are via macvtap-device regular LAN-Clients - IPv4 = DHCP and NAT by DSL-Router - IPv6 = GUA via RA and SLAAC (2003::/3) - IPv4 works fine in the VM - IPv6 (NDP, RA, SLAAC) works basically also fine in the VM The existing problem in the VM: - MAC-Based GUA (2000::/3) is ok, both inbound and outbound - Outbound traffic via the second GUA (PE-Based) is filtered apparently, but not via packetfiltering, I don't know where. There are no error messages. On the part of the kernel in the VM and the IPv6-stack, everything looks completely ok, no error messages, except that Outbound-Traffic by the PE-Address is quietly blocked. The MAC- Based IPv6 works unchanged and without error as before. My questions: 1. Is there a special setting for the VM, to allow the use of Privacy Extensions for IPv6 unlimited? 2. Or is that possibly even a known and at the moment unsolved problem? 3. Or is this a intended limitation of virtualization? Can anyone help me with a solution or a hint? Thank you. BR, Tom

2 2

[libvirt-users] Certificate checking on TLS migrations to an IP address
by Milan Zamazal 23 Sep '19

23 Sep '19

Hi, I'm trying to add TLS migrations to oVirt, but I've hit a problem with certificate checking. oVirt uses the destination host IP address, rather than the host name, in the migration URI passed to virDomainMigrateToURI3. One reason for doing that is that a separate migration network may be used for migrations, while the host name resolves to the management network interface. But it causes a problem with certificate checking. The destination IP address is checked against the name, which is a host name, given in the destination certificate. That means there is mismatch and the migration fails. I don't think it'd be a very good idea to avoid the problem by putting IP addresses into server certificates. Is there any way to make TLS migrations working under these circumstances? For instance, SPICE remote-viewer allows the client to specify the certificate subject to expect on the host when connecting to it using an IP address. Can (or could) libvirt do something similar? Or is there any other mechanism to handle this problem? Thanks, Milan

2 7