- Users - libvirt List Archives

external snapshot create error
by Eyüp Hakan Duran 21 Apr '21

21 Apr '21

Dear all, I have been creating external snapshots of my KVM/QEMU VMs for more than a year on a host machine that runs Manjaro Linux. The current version of libvirt I am using is 1:7.1.0-3. I just noticed that the script I am using for this purpose has been failing. More specifically the command below returns with the error message indicated underneath the command: sudo virsh snapshot-create-as --no-metadata --domain myVM myVM-state --diskspec hda,file=overlay.qcow2 --disk-only --atomic error: XML document failed to validate against schema: Unable to validate doc against /usr/share/libvirt/schemas/domainsnapshot.rng Extra element disks in interleave Element domainsnapshot failed to validate content I also tried different versions of the command above with similar results, such as: sudo virsh snapshot-create-as mvVM --no-metadata myVM-state --diskspec hda,snapshot=external,file=overlay.qcow2 --disk-only --atomic Any pointers will be greatly appreciated! Hakan Duran

2 2

could not start libvirt service
by shafnamol N 15 Apr '21

15 Apr '21

Hi, I am using *CentOS 8*. I have built *libvirt* with the following method: $ meson build -Dsystem=true $ ninja -C build $ ninja -C build install But the problem is when i started it # systemctl start libvirtd Job for libvirtd.service failed because the control process exited with error code. See "systemctl status libvirtd.service" and "journalctl -xe" for details. i tried to get the status of libvirt # systemctl status libvirtd libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) What will be the problem? Thanks for the help in advanc....

3 3

Confusion over networking configuration - I might be able to do some documentation
by Ed B 12 Apr '21

12 Apr '21

Hi libvirt users, I have been using libvirt on Debian Linux for a few months. (Mostly with virt-manager. I haven't yet learned all of the command line commands.) I'm currently confused by bridge mode networking, which I think is what I require to address the particular use case, which I will describe: My use case: Prior to this I have been using routed mode to organize my VMs. Most of the VMs I deploy are for services (web servers, mail servers, etc) so I require them to have static IP addresses on my local network. ==== An aside / comment: I *can* set those static IPs using the command line virsh net-edit (from memory) command and then change the settings in the xml files. However, since this seems like something that many users would require regularly it would be nice to be able to set static IP in the GUI when configuring with virt-manager. I assume that the same people who maintain libvirt also maintain virt-manager? If I'm wrong please re-direct me. Returning to the main discussion: It would be more convenient for me personally if I were able to set the IP addresses of these VMs using static addresses configured via an external DHCP server. I believe I can do this if my network is in "bridge" mode instead of NAT or Routed. I know this should be possible from reading information online but there doesn't seem to be any option for this in the virt-manager GUI. ==== To give more details on my setup: My network has a pfsense instance which is able to provide IP addresses to local machines. I would like to use the same pfsense machine to provide IP addresses to virtual machines. If I am not mistaken, the only way to do this would be to bridge the network on which the VMs reside to the network on which the pfsense machine resides. I will provide some screenshots to illustrate my confusion. When creating a new virtual network, I assume that I do not want to enable DHCPv4, because I want the pfsense system to allocate IP addresses. I do not know whether I should leave "Enable ipv4 network address space definition" or what the value should be. See image below. [cid:4e926d97-7a58-4350-93cc-0db7c401c075] Further in the setup (step 4), I assume I need to choose "Forward to physical network" rather than "Isolated virtual network". For the destination option, I do not know what should be chosen. I don't fully understand how this option works. For "Mode" there are three options: NAT, Routed and finally "Open". I cannot find any documentation which indicates what "Open" means. NAT and Routed are clearly not the correct options here - by a process of elimination that would imply that "Open" means "bridged" but I have a feeling that this is incorrect and I don't understand something else. Again, see screengrab below. [cid:f2ea4e34-c418-48d3-86b2-d7ff1002990a] I am quite keen to contribute something to documentation. At the moment I don't understand enough about how libvirt works to be able to do this. Apologies if my questions have been directed to the wrong people. If this is the case could you please re-direct me to the right place to ask such questions? Best regards

3 2

move mount permission denied
by Jiatong Shen 12 Apr '21

12 Apr '21

Hello community! I am faced with a mysterious [error]( https://gist.github.com/jshen28/5f29eed51e0a1308684214b35f009478) which says move mount is not permissioned. We are using libvirt with openstack-helm which running libvirt in a docker based k8s environment. /dev/termination-log is a device created and attached by k8s and mount looks like `/dev/mapper/ubuntu--vg-root on /var/log/termination-log type ext4 (rw,relatime,errors=remount-ro,data=ordered)` Any idea why this happens? appreciate the help! -- Best Regards, Jiatong Shen

2 1

how to use external snapshots with memory state
by Riccardo Ravaioli 12 Apr '21

12 Apr '21

Hi all, Best wishes for 2021! :) So I've been reading and playing around with live snapshots and still haven't figured out how to use an external memory snapshot. My goal is to take a disk+memory snapshot of a running VM and, if possible, save it in external files. As far as I understand, I can run: $ virsh snapshot-create $VM ... and that'll take an *internal* live snapshot of a given VM, consisting of its disks and memory state, which will be stored in the qcow2 disk(s) of the VM. In particular, the memory state will be stored in the first disk of the VM. I can then use the full range of snapshot commands available: revert, list, current, delete. Now, an external snapshot can be taken with: $ virsh snapshot-create-as --domain $VM mysnapshot --diskspec vda,file=/home/riccardo/disk_mysnapshot.qcow2,snapshot=external --memspec file=/home/riccardo/mem_mysnapshot.qcow2,snapshot=external ... with as many "--diskspec" as there are disks in the VM. I've read the virsh manual and the libvirt API documentation, but it's not clear to me what exactly I can do then with an external snapshot, in particular with the file containing the memory state. In articles from 7-8 years ago people state that external memory snapshots cannot be reverted... is it still the case today? If so, what's a typical usage for such files? If not with libvirt, is it possible to revert to an external memory + disk state in other ways, for instance through qemu commands? Thanks! Riccardo

2 4

live migrate storage to different volume on the same host
by Jing-Wei Su 12 Apr '21

12 Apr '21

Hello experts, I would like to move the qcow2 disk images of a running VM to a different storage because of the maintenance of the underlying storage on the same host. I found the live migration is not allowable on the same host using virsh. Is there any suggestion or better practices for this? Thank you, Derek

2 1

libvirt 7.2.0 domainbackup
by Thomas Stein 12 Apr '21

12 Apr '21

Hello one and all. Just wanted to check out the new feature domainbackup but having trouble to configure it. I thought I just have to put <domainbackup> <disks> <disk name='vda' type='file'> <target file='/var/lib/libvirt/jitsi'/> <driver type='raw'/> </disk> </disks> </domainbackup> at the top level of my domain xml file but that does not seem to work. I get: error: XML document failed to validate against schema: Unable to validate doc against /usr/share/libvirt/schemas/domain.rng Element domain has extra content: domainbackup Can someone please push me in the right direction? cheers, t.

2 5

submitting a patch to fix documentation errors
by Tom Ammon 10 Apr '21

10 Apr '21

Hello, While using the libvirt application development guide for python ( https://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/index.html) I found a couple of errors in the example code that I'd like to fix. I've created a branch and committed the fixes locally, and I'm ready to push them. I plan to use git send-email to submit the patch. Which list should I use in the --to= ? Should it be libvirt-users(a)redhat.com? This is my first contribution to this project. I've read the best practices and contributing guidelines on libvirt.org, but if I make mistakes in the workflow I'd appreciate your help to correct them. Thanks! Tom -- ----------------------------------------------------------------------------- Tom Ammon M: (737) 400-9042 thomasammon(a)gmail.com -----------------------------------------------------------------------------

2 2

Creating Virtual machine with .OVF format
by Ajay Kumar 09 Apr '21

09 Apr '21

Hello members, I would like to create virtual machine images with some pre-installed software in a .*OVF/OVA* format. So that I can use these* OVF *images/templates for any hypervisor to create a VM. Do you have any suggestions or some available web scripts/links to do this..? Thanks, Ajay

3 2

XML for working mips64el guest
by Skyler Mäntysaari 08 Apr '21

08 Apr '21

Hi there, How do I get a working xml for mips64el guest when using virt-manager? The host system is running Ubuntu, but I believe that this is the right list for things relating to libvirt. It errors with: --------------------------------------------- Unable to complete install: 'this function is not supported by the connection driver: 'mips64el' architecture is not supported by CPU driver' 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/createvm.py", line 2089, in _do_async_install guest.installer_instance.start_install(guest, meter=meter) File "/usr/share/virt-manager/virtinst/install/installer.py", line 542, in start_install domain = self._create_guest( File "/usr/share/virt-manager/virtinst/install/installer.py", line 491, in _create_guest domain = self.conn.createXML(install_xml or final_xml, 0) File "/usr/lib/python3/dist-packages/libvirt.py", line 4034, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirt.libvirtError: this function is not supported by the connection driver: 'mips64el' architecture is not supported by CPU driver --------------------------------------------- This is what I'm trying to use: --------------------------------------------- <domain type="qemu"> <name>debian9-mips64el</name> <metadata> <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0"> <libosinfo:os id="http://debian.org/debian/9"/> </libosinfo:libosinfo> </metadata> <memory>1048576</memory> <currentMemory>1048576</currentMemory> <vcpu>2</vcpu> <os> <type arch="mips64el" machine="malta">hvm</type> <cmdline>nokaslr root=/dev/sda1 console=ttyS0</cmdline> <boot dev="hd"/> </os> <clock offset="utc"/> <devices> <emulator>/usr/bin/qemu-system-mips64el</emulator> <controller type="pci" index="0" model="pci-root"/> <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/var/lib/libvirt/images/mip64el/stretch/disk.qcow2"/> <target dev="hda" bus="ide"/> </disk> <interface type="network"> <source network="default"/> <mac address="52:54:00:c5:63:f5"/> </interface> <console type="pty"/> </devices> </domain> ---------------------------------------------------------------------------------------------------------------

1 0