search for: librbd

I'm curious that why librbd sets this limitation? The rule first appeared in librbd.git commit d57485f73ab. Theoretically, a write-through cache is also safe for VM migration, if the cache implementation guarantees that cache invalidation and disk write are synchronous operations. For example, I'm using Ceph RBD images a...

On 7/29/19 3:51 AM, Ming-Hung Tsai wrote: > I'm curious that why librbd sets this limitation? The rule first > appeared in librbd.git commit d57485f73ab. Theoretically, a > write-through cache is also safe for VM migration, if the cache > implementation guarantees that cache invalidation and disk write are > synchronous operations. > > For example, I...

...d still not done... With "lsof -i", I can see a connection is established from my source hypervisor to a target hypervisor, likely for the purpose of copying data. nettop shows that this connection is constantly sending 50-60MBps traffic. The VM being migrated has a disk on ceph by using librbd. I wonder if anyone has seen similar issues, and how I could troubleshoot further. (I tried but failed to get qemu monitor to work on the VM...) Thanks. -Simon

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 everyone, To increase my odds of finding an answer I also wanted to ask here. This is my post from serverfault[1] in verbatim: While trying to get a cloned disk running from my OS snapshot I run into the problem that Libvirt cannot see existing images cloned from a snapshot. Created via: # rbd -p vmdisks clone vmdisks/coreos_2023@base vmdisks/coreos00.disk The base image has the one

...mu-img create RBD Format 2 images or am I > better off using `rbd` to create the image then booting from the disk > and performing the install, etc.? If you're using recent cuttlefish or dumpling releases of ceph, you can add settings to ceph.conf to make qemu-img and anything else using librbd create format 2 images. In the [client] or [global] section of /etc/ceph/ceph.conf, add: rbd default format = 2 Josh > Thanks for the assist. > > Best Regards, > Jon A > > > [1] > http://lists.ceph.com/pipermail/ceph-users-ceph.com/2013-June/002131.html > > > ___...

...> With "lsof -i", I can see a connection is established from my source > hypervisor to a target hypervisor, likely for the purpose of copying data. > nettop shows that this connection is constantly sending 50-60MBps traffic. > The VM being migrated has a disk on ceph by using librbd. > > I wonder if anyone has seen similar issues, and how I could troubleshoot > further. (I tried but failed to get qemu monitor to work on the VM...) > > Thanks. > -Simon > Hi, under certain conditions, like memory-intensive procedures inside guest, live migration effectivel...

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

Hi, When trying to attach a created volume to an instance using the virsh utility I am running into this error :- [] $ sudo virsh attach-device instance-00000015 disk.xml error: Failed to attach device from disk.xml error: internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk21' could not be initialized For experimental purpose I

...libz.so.1 (0x00007f08058a2000) libaio.so.1 => /lib/x86_64-linux-gnu/libaio.so.1 (0x00007f08056a0000) libiscsi.so.2 => /usr/lib/x86_64-linux-gnu/libiscsi.so.2 (0x00007f080547c000) libcurl-gnutls.so.4 => /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 (0x00007f080520a000) librbd.so.1 => /usr/lib/x86_64-linux-gnu/librbd.so.1 (0x00007f0804f06000) librados.so.2 => /usr/lib/x86_64-linux-gnu/librados.so.2 (0x00007f0803f8f000) libssh2.so.1 => /usr/lib/x86_64-linux-gnu/libssh2.so.1 (0x00007f0803d66000) libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libgli...

Hey Hilko, >> I'm guessing that you're using Ubuntu, am I right? Pretty good guess. :) For the time being I'm using 13.10. I know I've said it previously, but your right, I should include that info so I don't make people have to go digging. How do you normally deal with that warning? I typically rename the kvm binary, then link qemu-system-x86_64 but my concern is

Package: xen-hypervisor-4.5-amd64_4.5.0-1_amd64.deb Version: 4.5.0-1 Hi, I use xen with sdl, not with vnc. When I boot on xen-hypervisor-4.4-amd64, everything is fine. With Debian or Windows 8.1 I have a good display, But when I choose at boot, the xen-hypervisor-4.5-amd64, things go wrong. If I launch a xen Debian, I get some blur effect on the display. And when I launch a xen Windows8.1,

This series improves ceph rbd support in libguestfs. It uses the servers list, adds support for a custom username, and starts to add support for custom secret.

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.

...emu-kvm 13468 qemu mem REG 253,0 37056 100701754 /usr/lib64/libacl.so.1.1.0 qemu-kvm 13468 qemu mem REG 253,0 5342808 100841989 /usr/lib64/librados.so.2.0.0 qemu-kvm 13468 qemu mem REG 253,0 5789632 100768762 /usr/lib64/librbd.so.1.0.0 qemu-kvm 13468 qemu mem REG 253,0 435120 100842007 /usr/lib64/libcurl.so.4.3.0 qemu-kvm 13468 qemu mem REG 253,0 125336 33843740 /usr/lib64/iscsi/libiscsi.so.2.0.10900 qemu-kvm 13468 qemu mem REG 253,0 6264...

...0>] ? kthread_freezable_should_stop+0x70/0x70 [91128.972913] [<ffffffff8158c220>] ? gs_change+0x13/0x13 [91128.978826] ---[ end trace b8c31966cca731fb ]--- I''m able to reproduce this with ceph on a single server with 4 disks (4 filesystems/osds) and a small test program based on librbd. It is simply writing random bytes on a rbd volume (see attachment). Is this something I should care about? Any hint''s on solving this would be appreciated. Thanks, Christian

Split up the huge generator/actions.ml into several smaller files. Rich.