- Users - libvirt List Archives

virsh edit does not work when <initiator> and <auth> is used in config
by Fourhundred Thecat 25 Jun '20

25 Jun '20

Hello, I am having problem when using: "virsh edit <vm_name>" my VM has network iscsi disk defined: <disk type='network' device='disk'> <driver name='qemu' type='raw'/> <source protocol='iscsi' name='iqn.1992-08.com.netapp:5481.60080e50001ff2000000000051aee24d/0'> <host name='10.1.212.52' port='3260'/> <initiator> <iqn name='iqn.2013-01.bla.bla:01:test'/> </initiator> <auth username='myname'> <secret type='iscsi' usage='libvirtiscsi'/> </auth> </source> ... </disk> when I defined thje VM the first time, as always, libvirt reorders the lines in the XML config file as it likes. One of the reordering it did, was to put the "<initiator>" block above the "<auth>" block. But once I want to edit, "virsh edit <vm_name>", whatever change I make, even unrelated to iscsi disk, it reports error: error: XML document failed to validate against schema: Unable to validate doc against /usr/share/libvirt/schemas/domain.rng Extra element devices in interleave Element domain failed to validate content after long trial and error, I found I can finally save it when I reorder the "<initiator>" and "<auth>" blocks, so that "<auth>" is above "<initiator>". Once i save it, libvirt then reorders it back to the order, which will generate erro next time I attemt to edit. Anyway, this seems like a bug, and especially evil one. How could I get rid of this behaviour? thanks,

2 1

volume pool for LXC
by Guy Godfroy 23 Jun '20

23 Jun '20

Hello, Is it possible to use volume pools for LXC ? For instance LVM pools. It seems to be supporte by LXC bare commands. From the man page of lxc-create : -B, --bdev backingstore 'backingstore' is one of 'dir', 'lvm', 'loop', 'btrfs', 'zfs', 'rbd', or 'best'. The default is 'dir', meaning that the container root filesystem will be a directory under /var/lib/lxc/container/rootfs. This backing store type allows the optional --dir ROOTFS to be specified, meaning that the container rootfs should be placed under the specified path, rather than the default. (The 'none' backingstore type is an alias for 'dir'.) If 'btrfs' is specified, then the target filesystem must be btrfs, and the container rootfs will be created as a new subvolume. This allows snapshotted clones to be created, but also causes rsync --one-filesystem to treat it as a separate filesystem. If backingstore is 'lvm', then an lvm block device will be used and the following further options are available: --lvname lvname1 will create an LV named lvname1 rather than the default, which is the container name. --vgname vgname1 will create the LV in volume group vgname1 rather than the default, lxc. --thinpool thinpool1 will create the LV as a thin-provisioned volume in the pool named thinpool1 rather than the default, lxc. --fstype FSTYPE will create an FSTYPE filesystem on the LV, rather than the default, which is ext4. --fssize SIZE will create a LV (and filesystem) of size SIZE rather than the default, which is 1G. If backingstore is 'loop', you can use --fstype FSTYPE and --fssize SIZE as 'lvm'. The default values for these options are the same as 'lvm'. If backingstore is 'rbd', then you will need to have a valid configuration in ceph.conf and a ceph.client.admin.keyring defined. You can specify the following options : --rbdname RBDNAME will create a blockdevice named RBDNAME rather than the default, which is the container name. --rbdpool POOL will create the blockdevice in the pool named POOL, rather than the default, which is 'lxc'. If backingstore is 'best', then lxc will try, in order, btrfs, zfs, lvm, and finally a directory backing store.

1 0

qemu hook: event for source host too
by Guy Godfroy 23 Jun '20

23 Jun '20

Hello, this is my first time posting on this mailing list. I wanted to suggest a addition to the qemu hook. I will explain it through my own use case. I use a shared LVM storage as a volume pool between my nodes. I use lvmlockd in sanlock mode to protect both LVM metadata corruption and concurrent volume mounting. When I run a VM on a node, I activate the desired LV with exclusive lock (lvchange -aey). When I stop the VM, I deactivate the LV, effectively releasing the exclusive lock (lvchange -an). When I migrate a VM (both live and offline), the LV has to be activated on both source and target nodes, so I have to use a shared lock (lvchange -asy). That's why I need a hook event on the source host too (as far as I know after my tests, the migration event is only triggered on the target host). Is such a feature a possibility? Thanks for your attention. Guy Godfroy

2 13

Missing vnet interface in migration
by Ales Musil 22 Jun '20

22 Jun '20

Hi, in oVirt we have come across issue with a missing vnet interface (Original bug report [0]). This happened once in a huge batch of migrations e.g 2 failed out of 1200 and we came to conclusion that this is happening somewhere out of our control as libvirt reports: 2020-05-17 02:34:11,530+0000 ERROR (migsrc/623f6cc1) [virt.vm] (vmId='623f6cc1-d49f-43a4-8170-b5fec01f2897') operation failed: binding 'vnet54' is already being removed (migration:278) Unfortunately we don't have libvirt logs and producing them might not be possible. Is there anything else we can do to tackle down this issue? Thank you. Regards, Ales [0] https://bugzilla.redhat.com/1837395 -- Ales Musil Software Engineer - RHV Network Red Hat EMEA <https://www.redhat.com> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

1 0

Feature request? Auto start vm upon next shutdown
by Marc Roos 22 Jun '20

22 Jun '20

Sometimes when you change the configuration, this configuration change will only be available after a shutdown. Not to have to monitor when the vm shuts down, to start it again. It could be nice to have libvirt start it one time. Something like: 1. change the network interface of a running guest 2. at the prompt of the virt-manager "Some changes may require a guest shutdown to take effect" introduce check box 'Auto start vm upon next shutdown' 3. shutdown the guest 4. after the guest completed shutdown, libvirt is automatically starting it again.

3 4

NVDIMM sizes and DIMM hot plug
by Milan Zamazal 19 Jun '20

19 Jun '20

Hi, I've found out that NVDIMM size and label size matter for regular (non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the guest OS will not accept the hot plugged memory and will complain with messages such as Block size [0x8000000] unaligned hotplug range: start 0x225000000, size 0x10000000 The start address above is also reported within <memory> element of the hot plugged memory in the domain XML: <address type='dimm' slot='1' base='0x225000000'/> Apparently, in order to make memory hot plug working in the guest OS, the inserted memory must be aligned to the platform memory alignment (128 MB on x86_64). I'd like to clarify, how libvirt makes the DIMM address above. How is the NVDIMM memory range determined? According to my experiments, it seems the NVDIMM specified <size> is taken, NVDIMM <label> size is subtracted from it and the resulting value is reduced to the nearest multiple of NVDIMM <alignsize>. Is this observation correct? Is it guaranteed to be stable in future versions? I need to determine the right NVDIMM size to make the subsequent memory modules correctly aligned and then I can't change the NVDIMM size, to not damage data stored in the NVDIMM. Additionally, when adjusting maxMemory due to NVDIMM presence, should I increase it by the specified NVDIMM <size> or a different value? Thank you, Milan

4 5

Guidance for First Timer
by Sanyam Rajpal 18 Jun '20

18 Jun '20

Hey everyone, I am a first-time contributor and I was interested in this project. I wanted to make some open source contributions and learn. I am not looking for getting enrolled in the program. Sanyam

2 1

Is it possible to configure libvirt's MAC generation?
by Ian Pilcher 16 Jun '20

16 Jun '20

Is it possible to configure libvirt to generate "predictable" MAC addresses for virtual NICS? (A configuration which accomplishes this by limiting the pool of available addresses would be acceptable for my use case.) Read on for why I want to do this ... I have a somewhat unusual use case. I am working with the OpenShift bare metal "IPI" installation process, which is documented here: https://openshift-kni.github.io/baremetal-deploy/4.4/Deployment.html At a high level, the installation process goes like this: 1. Install RHEL 8 on the "provisioner" node. 2. Configure a couple of bridges on the provisioner node, which will be used by the "bootstrap VM" (see below). 3. Create a configuration file & do various other things. 4. Run the installer a. Installer creates a "bootstrap VM" on the provisioning node, which does the actual work of kicking off the OpenShift installation. The bootstrap VM runs Red Hat Enterprise Linux CoreOS (RHCOS). b. Bootstrap VM requests an IP address via DHCP. <====== ****** Step 4b is problematic in this environment. Because of routing and firewall rules, I really need the bootstrap VM to have a predictable IP address. It is possible to configure a static IP address on the bootstrap VM via the CoreOS ignition file, and we've successfully done this, but ... RHCOS requests an IP address via DHCP *before* it processes the ignition file. If this fails, it appears to simply give up. So we need to have our DHCP server provide an address to the bootstrap VM, even if it isn't ever used. And of course, we're not allowed to configure the DHCP server to respond to any old MAC address that comes along; we're only allowed to respond to known MAC addresses. Hopefully this all makes sense, and hopefully it explains why being able to configure libvirt's MAC pool/sequence would allow things to work in this environment. Thanks! -- ======================================================================== In Soviet Russia, Google searches you! ========================================================================

6 6

Reintroduce modern CPU in model selection
by Gionatan Danti 15 Jun '20

15 Jun '20

Hi list, in virt-manager ver. 2.2.1 (fully upgraded CentOS 8.1), the CPU model list only shows ancient CPU (the most recent is Nehalem-IBRS). On the other hand, in virt-manager 1.5.x (fully upgraded CentOS 7.8) we have a rich selection of CPU (as recent as Icelake). Why was the list in newer virt-manager so much trimmed? Is it possible to enlarge it? Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it [1] email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

1 1

Live migration to another volume at the same host
by Paul van der Vlis 12 Jun '20

12 Jun '20

Hello, I am looking for a way to migrate a VM live to another location. The qcow2 images are now on /data , but I want to move some of them to a volume mounted on /data2 what's faster. Is this possible without downtime? With regards, Paul -- Paul van der Vlis Linux systeembeheer Groningen https://www.vandervlis.nl/

2 2