similar to: Re: RBD volume not made available to Xen virtual guest on openSUSE 15.2 (with libvirt 6.0.0)

Hi there, Since upgrading to openSUSE 15.2 (which includes libvirt 6.0.0) the virtual guests don't get their RBD disks made available to them. On openSUSE 15.1 (which includes libvirt 5.1.0) that worked fine. The XML is as follows: <domain type='xen' id='7'>   <name>mytwotel-a</name>   <uuid>a56daa5d-c095-49d5-ae1b-00b38353614e</uuid>  

On a Friday in 2020, Marcel Juffermans wrote: >Hi there, > >Since upgrading to openSUSE 15.2 (which includes libvirt 6.0.0) the >virtual guests don't get their RBD disks made available to them. On >openSUSE 15.1 (which includes libvirt 5.1.0) that worked fine. The XML >is as follows: > [...] >I tried to strace libvirtd. The results are as follows: > >On

It's QEMU 4.2.1-lp152.9.6.1. I've tried updating it from the Open Build Service repos but there's too many version conflicts. Marcel On 26/10/20 9:02 pm, Ján Tomko wrote: > On a Friday in 2020, Marcel Juffermans wrote: >> Hi there, >> >> Since upgrading to openSUSE 15.2 (which includes libvirt 6.0.0) the >> virtual guests don't get their RBD disks

Hello, Current version adding 'auth_supported=none' at the end of disk path and failing to do an authentication with specified cephx key: <source protocol='rbd' name='rbd/vmxxxxxxxxx:id=qemukvm:key=[cut]==:auth_supported=cephx'> <host name='10.0.0.13' port='6789'/> <host name='10.0.0.10' port='6789'/>

Hi everybody, my background: I'm doing Xen since 10++ years, many years with DRBD for high availability, since some time I'm using preferable GlusterFS with FUSE as replicated storage, where I place the image-files for the vms. In my current project we started (successfully) with Xen/GlusterFS too, but because the provider, where we placed the servers, uses widely CEPH, we decided to

Hi there, I met one problem that guest fail to boot up when Selinux is enabled with guest storage based on ceph. However, I can boot the guest with qemu directly. I also can boot it up with Selinux disabled. Not sure it is a libvirt bug or wrong use case. 1. Enable Selinux # getenforce && iptables -L Enforcing Chain INPUT (policy ACCEPT) target prot opt source destination

Hi all, I'd like to get a few storage statistics from a running vm. I'd like to know read and write data about QCOW2 devices and about RBD volumes. I did try to execute a command similar to this: virsh qemu-monitor-command vm-vnc '{ "execute": "query-block"}' as described here:

Hello, I have virtual machines running with a ceph storage backend. When creating an external qcow2 snapshot with a libvirt version without support for the new object secret passing, the backing file info would list the ceph secret in plain,e.g. # virsh snapshot-create-as vm-123 --no-metadata --disk-only --diskspec sda,file=/var/lib/libvirt/qemu/snapshot/vm-123-wrapper.qcow2 # qemu-img info

Hello, I'm trying to using virsh update-device to update the CDROM from type='file' to ceph rbd iso with type='network'. But I always get error: Failed to update device from disk error: internal error: unable to execute QEMU command 'change': error connecting: Operation not supported I'm using libvirt-libs-3.10.0-1.el7.x86_64 with centos7.4 my original cdrom xml:

On Mon, Nov 25, 2013 at 12:52:21PM -0700, Jon wrote: > Hello, > > I'm having trouble connecting to rbd images. It seems like somewhere the > name is getting chewed up. I wonder if this is related to my previous > troubles [1] [2] with rbd images. > > I'm trying to add an rbd image, but when I launch the guestfs object I get > an error: > > >>

On Mon, Nov 04, 2013 at 06:35:42PM -0700, Jon wrote: > Hello, > > I'm having a problem when trying to use virt-sysprep against vms that have > rbd disk images. When I run virt-sysprep I get the following error: > > >> root@kitt:~/libguestfs-1.22.4# virt-sysprep -d server-clone-test > --firstboot firstboot.sh > >> Examining the guest ... > >>

Hello Richard, I'm using: >> virt-sysprep 1.25.6 I honestly don't remember if the currently installed version is from the tarball or pulled from the github source... Now that you mention it, I think it could even be the version with my "hack" to fix virt-sysprep... Which version are you building? I see there's a: >>

On Mon, Nov 25, 2013 at 09:58:50PM +0000, Richard W.M. Jones wrote: > On Mon, Nov 25, 2013 at 12:52:21PM -0700, Jon wrote: > > Hello, > > > > I'm having trouble connecting to rbd images. It seems like somewhere the > > name is getting chewed up. I wonder if this is related to my previous > > troubles [1] [2] with rbd images. > > > > I'm

Hello, I'm having trouble connecting to rbd images. It seems like somewhere the name is getting chewed up. I wonder if this is related to my previous troubles [1] [2] with rbd images. I'm trying to add an rbd image, but when I launch the guestfs object I get an error: >> libguestfs: trace: launch = -1 (error) I'm adding a single RBD >> libguestfs: trace: add_drive

Hello, I'm having a problem when trying to use virt-sysprep against vms that have rbd disk images. When I run virt-sysprep I get the following error: >> root@kitt:~/libguestfs-1.22.4# virt-sysprep -d server-clone-test --firstboot firstboot.sh >> Examining the guest ... >> Fatal error: exception Guestfs.Error("rbd: image name must begin with a '/'") My

Hello Richard, Thanks for the reply. Indeed this behaviour exists in 1.25.6. Grepping through the source [1], there are a number of files in "./po/*.po[t]?" that contain this message, but I think it's ./src/drives.c where the fail condition is actually detected / set. On line 300 there is an if statement that checks the first character is a slash: if (exportname[0] !=

Hello Richard, Haha, ok, here's a good one: I commented that if statement out at line 300, applied your patch (I see you updated the github of this code, perhaps that's the best place to grab the code from), and when I run virt-sysprep, I get the following parameter for my disk drive: >> qemu-system-x86_64: -drive

On Wed, Nov 06, 2013 at 02:25:54PM -0700, Jon wrote: > Hello Richard, > > Haha, ok, here's a good one: I commented that if statement out at line 300, > applied your patch (I see you updated the github of this code, perhaps > that's the best place to grab the code from), and when I run virt-sysprep, > I get the following parameter for my disk drive: > > >>

On Fri, Jul 18, 2014 at 11:58 PM, Andrey Korolyov <andrey@xdel.ru> wrote: > Hello, > > 2.0 model works fine > > 2.1 crashes with following: > > /tmp/buildd/qemu-2.0.92+rev1/hw/i386/smbios.c:825: smbios_get_tables: > Assertion `smbios_smp_sockets >= 1' failed > > Not sure if bisect will help much, but the commit which introduced > this platform works

Hello Everyone, My pc run in CentOS 7.4 and install libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph 10.2.10 ALL-in-One. I use python-sdk with libvirt and run [self.domain.updateDeviceFlags(xml, libvirt.VIR_DOMAIN_AFFECT_LIVE)] on CDROM (I want to change media path). However, I enable libvirt debug log , the log as below: "2018-02-26 13:09:13.638+0000: 50524: debug :