search for: rbd_cache_max_dirty

...lly, 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 as VM storage backend. The Ceph librbd supports synchronous write-through cache, by setting rbd_cache_max_dirty to zero, and setting rbd_cache_block_writes_upfront to true, thus it would be safe for VM migration. Is that true? Any suggestion would be appreciated. Thanks. Ming-Hung Tsai

...source 'name' attribute to control the RBD cache settings on a per-volume basis. Under libvirt-1.0.6 such VM's refuse to start: error: Failed to start domain foo error: unsupported configuration: ':' not allowed in RBD source volume name 'mypool/foo:rbd_cache_size=268435456:rbd_cache_max_dirty=134217728:rbd_cache_target_dirty=33554432:rbd_cache_max_dirty_age=5' So my question is how do I control the cache settings now? Thanks, JN

...#39; attribute to control the RBD cache settings on a per-volume basis. Under libvirt-1.0.6 such VM's refuse to start: >> error: Failed to start domain foo >> error: unsupported configuration: ':' not allowed in RBD source volume name 'mypool/foo:rbd_cache_size=268435456:rbd_cache_max_dirty=134217728:rbd_cache_target_dirty=33554432:rbd_cache_max_dirty_age=5' >> >> So my question is how do I control the cache settings now? > > You can set the cache mode with the cache attribute on the <driver> > element inside a <disk> [1]. This works for rbd with...

...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 as VM storage backend. The Ceph > librbd supports synchronous write-through cache, by setting > rbd_cache_max_dirty to zero, and setting > rbd_cache_block_writes_upfront to true, thus it would be safe for VM > migration. Is that true? Any suggestion would be appreciated. Thanks. The commit you refer to is very old and my hunch is that things looked different in 2012. Things might have changed since then...

...39;name' attribute to control the RBD cache settings on a per-volume basis. Under libvirt-1.0.6 such VM's refuse to start: > error: Failed to start domain foo > error: unsupported configuration: ':' not allowed in RBD source volume name 'mypool/foo:rbd_cache_size=268435456:rbd_cache_max_dirty=134217728:rbd_cache_target_dirty=33554432:rbd_cache_max_dirty_age=5' > > So my question is how do I control the cache settings now? You can set the cache mode with the cache attribute on the <driver> element inside a <disk> [1]. This works for rbd with QEMU 1.2 or later. QEM...

...ribute to control the RBD cache settings on a per-volume basis. Under libvirt-1.0.6 such VM's refuse to start: >>> error: Failed to start domain foo >>> error: unsupported configuration: ':' not allowed in RBD source volume name 'mypool/foo:rbd_cache_size=268435456:rbd_cache_max_dirty=134217728:rbd_cache_target_dirty=33554432:rbd_cache_max_dirty_age=5' >>> >>> So my question is how do I control the cache settings now? >> >> You can set the cache mode with the cache attribute on the <driver> >> element inside a <disk> [1]. This...

...... OK 123) QEMU XML-2-ARGV disk-drive-network-rbd-ipv6 ... OK 124) QEMU XML-2-ARGV disk-drive-network-rbd-no-colon ... Got expected error: unsupported configuration: ':' not allowed in RBD source volume name 'poolname/imagename:rbd_cache=1:rbd_cache_size=67108864:rbd_cache_max_dirty=0' OK 125) QEMU XML-2-ARGV disk-drive-no-boot ... OK 126) QEMU XML-2-ARGV disk-usb ... OK 127) QEMU XML-2-ARGV disk-usb-device ... OK 128) QEMU XML-2-ARGV disk-usb-device-removable...