November 2023 - Users - Libvirt List Archives

Re: Libvirt and Ceph: libvirtd tries to open random RBD images

by Daniel P. Berrangé

On Mon, Nov 20, 2023 at 01:21:24PM +0000, Jayanth Reddy wrote: > Hello Daniel, > > Thank you for the response. Please also let me know why libvirtd says "No such file or directory" even though the block images exist and are healthy. I don't know the cause - all we're seeing is that the API call if ((ret = rbd_open_read_only(ptr->ioctx, vol->name, &image, NULL)) < 0) { is failing. Maybe RBD has permission denying access on this host ? Or is RBD preventing this host access the volume, becuase another VM has it in use With 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 :|

10 months, 4 weeks

2
4
0 / 0

Internal Error: libxenlight failed to create new domain "FreeBSD-13.2"

by marietto2008＠gmail.com

Hello to everyone. I'm trying to use xen as a hypervisor instead of kvm to boot FreeBSD on my ARM Chromebook where I have installed Devuan 5. A developer said that it can work. In fact he said : "That might work. libvirt + virt-manager with the xen accelerator might work on the ARM Chromebook. That's because as far as I know Xen integration in libvirt is done via linking to libxl directly and libxl is supported and working on ARM" Unfortunately something is not working properly. What I did has been to reboot the machine in xen,enable libvirtd & and virtlogd & and virt-manager &,but this is what happened : root@devuan-bunsen:/Dati/virt-manager-4.1.0# ./virt-manager & [3] 2507 root@devuan-bunsen:/Dati/virt-manager-4.1.0# info : libvirt version: 9.7.0 info : hostname: devuan-bunsen error : virConnectGetAllDomainStats:12595 : this function is not supported by the connection driver: virConnectGetAllDomainStats error : virDomainListAllSnapshots:519 : this function is not supported by the connection driver: virDomainListAllSnapshots [3]+ Completed ./virt-manager root@devuan-bunsen:/mnt/zroot2/zroot2# error : libxlDomainStartPerform:1256 : internal error: libxenlight failed to create new domain 'FreeBSD-13.2 Traceback (most recent call last): File "/Dati/virt-manager-4.1.0/./virtManager/asyncjob.py", line 72, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/Dati/virt-manager-4.1.0/./virtManager/createvm.py", line 2008, in _do_async_install installer.start_install(guest, meter=meter) File "/Dati/virt-manager-4.1.0/./virtinst/install/installer.py", line 695, in start_install domain = self._create_guest( ^^^^^^^^^^^^^^^^^^^ File "/Dati/virt-manager-4.1.0/./virtinst/install/installer.py", line 637, in _create_guest domain = self.conn.createXML(initial_xml or final_xml, 0) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/libvirt.py", line 4481, in createXML raise libvirtError('virDomainCreateXML() failed') libvirt.libvirtError: internal error: libxenlight failed to create new domain 'FreeBSD-13.2' you may also be interested to give a look at this picture : https://ibb.co/Lh0xkfy ...between the running processes I see this : # ps ax | grep qemu 1507 ? Sl 0:00 /usr/libexec/xen-qemu-system-i386 -xen-domid 0 -xen-attach -name dom0 -no graphic -M xenpv -daemonize -monitor none -serial none -parallel none -pidfile /run/qemu-dom0.pid The interesting point is that it is using xen-qemu-system-i386. Is it supposed to work on an ARM architecture ? What's the problem that I may have now ?

11 months

3
4
0 / 0

Libvirt/KVM/VLANs/teamed interfaces

by Ken D'Ambrosio

Hey, all. So, we've got some OpenStack controllers that I'm virtualizing, and it's going really well... until the most recent host I was dooing, the fifth of eight. Everything looked like it largely should, except that there was zero traffic on the VLANs on the VM. Sniffing physical ports showed it hitting the machine, but nothing made it into VLAN/namespace land on the VMs. After banging my head against the wall a lot, I realized that, for some reason, the interface team (which is hot/cold) was using the secondary interface, not the primary. I turned that interface down, the primary came up, and everything started working great. (It only became apparent that something like that might be the case when I compared the broken machine's output from "brctl listmacs br0", vs. that of a working machine.) Any idea what's _really_ not working, deep down on the stack? Is there a way around it? Thanks! -Ken

11 months

1
0
0 / 0

Permission Denied error when I try to open the image file stored on the ZFS disk accessed through sshfs from another machine...

by marietto2008＠gmail.com

Hello to everyone. I would like to boot the FreeBSD 13.2 image file using Libvirt + virt-manager. I have stored the image on the external hard drive,"formatted" with ZFS while I'm using Devuan 5 installed on my ARM (32 bit) Chromebook,where I have access to the ZFS disk using sshfs using this command : sshfs -o Compression=no -o allow_root -o transform_symlinks -o password_stdin root@192.168.1.2:/mnt/zroot2/zroot2 /mnt/zroot2/zroot2 <<< 'pass' This is the error I get when I try to boot the image file using virt-manager : error : qemuProcessReportLogError:1990 : internal error: process exited while connecting to monitor: 2023-11-28T20:53:46.882586Z qemu-system-arm: -blockdev {"driver":"file","filename":"/mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/FreeBSD-13.2-RELEASE-armv7.img","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}: Could not open '/mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/FreeBSD-13.2-RELEASE-armv7.img': Permission denied According with this post : https://forum.manjaro.org/t/virt-manager-doesnt-work-permission-denied/10... I tried to do the following : root@devuan-bunsen:/mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm# getfacl /mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/ getfacl: Removing leading '/' from absolute path names # file: mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/ # owner: root # group: root user::rwx group::rwx other::rwx root@devuan-bunsen:/mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm# setfacl -m user:libvirt-qemu:--x /mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/ setfacl: /mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/: Operation not supported Can someone help me to understand where the error is and how to fix it ? thanks.

11 months

3
4
0 / 0

Mentor moja global at CodePeak 2023!

by gautam.sharma＠iitg.ac.in

11 months

1
0
0 / 0

Enabling libiscsi with libvirt on Rocky 9

by will.gorman＠joyent.com

I am running into a problem attaching an iscsi disk to a VM in libvirt using "virsh attach-device" on Rocky 9 with the following error: "unable to execute QEMU command 'blockdev-add': Unknown driver 'iscsi'". I've found some indications that libiscsi is being removed from RHEL 9, like https://bugzilla.redhat.com/show_bug.cgi?id=1967133 but it's not clear to me what alternatives might be available for libvirt users that depend on the libiscsi-based block device driver. Are there alternate packages that can be installed to re-enable the iscsi block device driver for qemu on RHEL 9 based systems? Or would it be necessary to rebuild libvirt/qemu to get this block device driver to work again? Thanks, Will Gorman

11 months

3
2
0 / 0

Enabling libiscsi with libvirt on Rocky 9

by Will Gorman

I am running into a problem attaching an iscsi disk to a VM in libvirt using "virsh attach-device" on Rocky 9 with the following error: "unable to execute QEMU command 'blockdev-add': Unknown driver 'iscsi'". I've found some indications that libiscsi is being removed from RHEL 9, like https://bugzilla.redhat.com/show_bug.cgi?id=1967133 but it's not clear to me what alternatives might be available for libvirt users that depend on the libiscsi-based block device driver. Are there alternate packages that can be installed to re-enable the iscsi block device driver for qemu on RHEL 9 based systems? Or would it be necessary to rebuild libvirt/qemu to get this block device driver to work again? Thanks, Will Gorman

11 months, 1 week

1
0
0 / 0

Libvirt and Ceph: libvirtd tries to open random RBD images

by Jayanth Reddy

Hello Users, We're using libvirt with KVM and the orchestrator is Cloudstack. I raised the issue already at Cloudstack at https://github.com/apache/cloudstack/issues/8211 but appears to be at libvirtd. Below is our environment & issue description: It appears that one of our Cloudstack KVM clusters having 8 hosts is having the issue. We have HCI on these 8 hosts and there are approximately 700+ VMs running. But strange enough, there are these logs like below on hosts. Oct 25 13:38:11 hv-01 libvirtd[9464]: failed to open the RBD image '087bb114-448a-41d2-9f5d-6865b62eed15': No such file or directory Oct 25 20:35:22 hv-01 libvirtd[9464]: failed to open the RBD image 'ccc1168a-5ffa-4b6d-a953-8e0ac788ebc5': No such file or directory Oct 26 09:48:33 hv-01 libvirtd[9464]: failed to open the RBD image 'a3fe82f8-afc9-4604-b55e-91b676514a18': No such file or directory Oct 26 10:38:17 hv-01 libvirtd[9464]: End of file while reading data: Input/output error We've got DNS servers on which there is an`A` record resolving to all the IPv4 Addresses of 8 monitors and there have not been any issues with the DNS resolution. But the issue of "failed to open the RBD image 'ccc1168a-5ffa-4b6d-a953-8e0ac788ebc5': No such file or directory" gets more weird because the VM that is making use of that RBD image lets say "087bb114-448a-41d2-9f5d-6865b62eed15" is running on altogether different host like "hv-06". On further inspection of that specific Virtual Machine, it has been running on that host "hv-06" for more than 4 months or so (looked at "Last updated" field). Fortunately, the Virtual Machine has no issues and has been running since then. Thanks, Jayanth

11 months, 1 week

2
2
0 / 0

Problem setting up SGX domain

by Wojtek Porczyk

Hi, users@, I'm attempting to set up domain with SGX EPC memory. When starting it, I get this error: # virsh start astoria-test-1 error: Failed to start domain 'astoria-test-1' error: internal error: process exited while connecting to monitor: libnuma: Warning: /sys not mounted or invalid. Assuming one node: Permission denied 2023-11-16T14:04:26.919285Z qemu-system-x86_64: The nodes select no CPUs When removing <memory model='sgx-epc'> node from XML, the domain starts fine. I've attached is domain.xml for it, with the section commented. Also there are logs from happy and sad case. The libnuma error seems to stem from this place: https://github.com/numactl/numactl/blob/fc999282e6663d6844773e6065bbee327... This makes no sense to me, because the file is there and available: # sudo -u libvirt-qemu cat /sys/devices/system/node/node0/cpumap fff I also don't understand why qemu says "The nodes select no CPUs" (https://gitlab.com/qemu-project/qemu/-/blob/34a5cb6d8434303c170230644b2a7...). DDG has failed me in all cases. I've also tried to follow the recommendation from https://libvirt.org/formatdomaincaps.html#sgx-capabilities: For more details on the SGX feature, please follow resources in the SGX developer's document store. ...and the only think that I've found relevant to libvirt was this document: https://www.intel.com/content/www/us/en/developer/articles/technical/virt... which suggests to play with <qemu:commandline> instead. host: Debian 12, libvirt 9.0.0, QEMU 7.2, virtinst 4.1 (see dpkg-l attachment) guest: Ubuntu 22.04 (jammy) cloud image The domain in quesion was defined using virt-install with cloud-init, then I was editing XML with `virsh edit`. Relevant snippet from `virsh domcapabilities`: <sgx supported='yes'> <flc>yes</flc> <sgx1>yes</sgx1> <sgx2>no</sgx2> <section_size unit='KiB'>95744</section_size> <sections> <section node='0' size='95744' unit='KiB'/> </sections> </sgx> System-wide logs do not contain anything relevant. I'm happy to provide additional info if needed. Anyone can point me to a solution? -- pozdrawiam / best regards Wojtek Porczyk Gramine / Invisible Things Lab I do not fear computers, I fear lack of them. -- Isaac Asimov

11 months, 1 week

1
0
0 / 0

windows install fails with error 0x80070001

by daggs

Greetings, following an issue with my windows install, I've had to reinstall windows 11 on kvm. I start the vm and the install starts, the install process starts, I add the virtio scsi controller and the hdd gets detected. next I start the install and get the same error as see here: https://howfix.net/computer/0x80070001/ on when getting to the "Getting files ready for installation" stage. I suspect that there is a bug with the windows scsi virtio driver when using hdd pass-through this is the vm's xml: https://bpa.st/63RA my host system is based on qemu-8.1.2, libvirt-9.8.0, virtiofsd-1.8.0, virtio-win-0.1.229.1 and kernel-6.6.0. what can I do?

11 months, 2 weeks

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Users November 2023