similar to: Creating a snapshot from a KVM VM fails

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>  

I'm having some trouble creating KVM domains with RBD block devices using virsh. I've managed to get virsh to define the domain, but it gives an error when trying to start the domain: error: Failed to start domain test0 error: internal error process exited while connecting to monitor: char device redirected to /dev/pts/3 kvm: -drive

Hi, I'm using virsh to instance a VM in my environment, but I'm running on some issues. I created the following domain file: <domain type='kvm'> <name>demovm</name> <uuid>4a9b3f53-fa2a-47f3-a757-dd87720d9d1d</uuid> <memory unit='KiB'>4194304</memory> <currentMemory

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

Hi, Thanks a lot for the answer. > An internal snapshot of a VM requires that the VM has at least one disk > using a QCOW2 volume or similar. The memory state is saved in that > image. Your VM has only a RAW disk image and thus it can't be used for > internal snapshot. Ok, that makes sense... > You can either use an external snapshot (the memory image is stored >

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, I would like to use RBD Format 2 images so I can take advantage of layering. However, when I use "qemu-img create -f rbd rbd:data/foo 10G", I get format 1 RBD images. (Actually, when I use the "-f rbd" flag, qemu-img core dumps, but it looks like that feature may have been deprecated [1]) Is there any way to have qemu-img create RBD Format 2 images or am I better off

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

Hi, I've recently been working on setting up a set of libvirt compute nodes that will be using a ceph rbd pool for storing vm disk image files. I've got a couple of issues I've run into. First, per the standard ceph documentation examples [1], the way to add a disk is to create a block in the VM definition XML that looks something like this: <disk type='network'

Miscellaneous fixes to: - Handling of Ceph drives now works end-to-end (RHBZ#1026688). - In particular, you can now use rbd:/// URIs in guestfish (and they work). - Parse Ceph & NBD network drives from libvirt XML correctly, so that existing domains with Ceph/NBD drives can be added (eg. using guestfish -d option). - Add more testing of the above.

http://rwmj.wordpress.com/2013/03/12/accessing-ceph-rbd-sheepdog-etc-using-libguestfs/#comment-8806 I came across this link and and i was able to retrieve the rbd image. $ guestfish ><fs> set-attach-method appliance ><fs> add-drive /dev/null ><fs> config -set drive.hd0.file=rbd:pool/volume ><fs> run I was able to retrieve file from rbd image using the above

Hi, I am doing some experimentation with xen and Ceph and have a problem booting my guest when my disk = [] uses an alternate block script. Installation from a .iso was ok since the boot device was a file but now trying to boot from the rbd neither the hvmbuilder or pygrub can start as they treat the first value after target= as the /dev node to try and use. My disk parameter looks like: disk =

Hello All, On my host machine, I'm using kvm, libvirt, ceph and ubuntu versions as follows: >> QEMU emulator version 1.5.0 (Debian 1.5.0+dfsg-3ubuntu5), Copyright (c) 2003-2008 Fabrice Bellard >> root at kitt:~# virsh --version: 1.1.1 >> ceph version 0.67.4 (ad85b8bfafea6232d64cb7ba76a8b6e8252fa0c7) >> VERSION="13.10, Saucy Salamander" >> Linux kitt

Hi, I'm trying to run virt-sysprep against a disk in Ceph RBD storage but I appear to be unable to do so. The commands (bold) and outputs I've had are: On Ceph node: *virt-sysprep -a rbd://localhost/libvirt-pool/ubuntu-12-04-beanstalk001* libguestfs: new guestfs handle 0x113b060 rbd://localhost/libvirt-pool/ubuntu-12-04-beanstalk001: No such file or directory libguestfs: trace: close

how to use python-guestfs to access rbd device? The function i found is g.add_drive_opts, but i dono know how it receive ceph's configuration. I found this link http://rwmj.wordpress.com/2013/03/12/accessing-ceph-rbd-sheepdog-etc-using-libguestfs/ Is that the only way i should use to access ceph rbd? Can we use python-guestfs to get the same effect? Thanks

Hi, I''ve been working on getting a working blktap driver allowing to access ceph RBD block devices without relying on the RBD kernel driver and it finally got to a point where, it works and is testable. Some of the advantages are: - Easier to update to newer RBD version - Allows functionality only available in the userspace RBD library (write cache, layering, ...) - Less issue when

I am running some qemu-kvm virtual machines via libvirt using Ceph RBD as the back-end storage. Today I was testing an update to libvirt-1.0.6 on one of my hosts and discovered that it includes this change: [libvirt] [PATCH] Forbid use of ':' in RBD pool names ...People are known to be abusing the lack of escaping in current libvirt to pass arbitrary args to QEMU. I am one of those

i will test it out and will update you.. Thankyou so much for your reply kind regards Shumaila Naeem Software Engineer , Ovex Technologies On Thu, Mar 13, 2014 at 5:15 PM, Richard W.M. Jones <rjones@redhat.com>wrote: > On Thu, Mar 13, 2014 at 03:06:17PM +0500, Shumaila Naeem wrote: > > >

Hi Lucian, It seems to be upstream libvirt-1.2.15-2 with options with_xen and with_libxl enabled. http://cbs.centos.org/koji/buildinfo?buildID=1348 Regards, Jean-Marc Le 28/10/2015 09:38, Nux! a ?crit : > Pasi, > > Where are these RPMs, how are they built, what exactly are the differences vs the stock ones? > > Regards, > Lucian > > -- > Sent from the Delta quadrant

Hello everybody, This is a cross post to libvirt-users, libguestfs and ceph-users. I came back from FOSDEM 2016 and this was my 7th year or so and seen the awesome development around visualization going on and want to thank everybody for there contributions. I seen presentations from oVirt, OpenStack and quite a few great Redhat people, just like the last previous years. I personally been