search for: _guarntee_

...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 that will cause problems if I want a 32 bit vm... (I don't see a reason to run i386 these days, but I _guarntee_ you, I have a customer who /refuses/ to use 64bit vms...) >> The ceph package in Debian has been a mess until very recently Really? I have no problems with ceph. Until I upgraded to 13.10, I was using the opscode ppa; there are no 13.10 repis I'm the ppa... Ok... I take that back.... C...

...you want to use a particular binary: ./configure --with-qemu="qemu-system-x86_64" > I typically rename the kvm binary, then link qemu-system-x86_64 but > my concern is that will cause problems if I want a 32 bit vm... (I > don't see a reason to run i386 these days, but I _guarntee_ you, I > have a customer who /refuses/ to use 64bit vms...) x86-64 as a platform supports 32 bit operating systems. So there's no special KVM emulator required to run 32 bit VMs. > libvirt has no problem with my rbds. It's just libguestfs that doesn't like > my rbds... unles...

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