search for: three18ti

On Mon, Nov 25, 2013 at 04:12:40PM -0700, Jon wrote: > 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... >

...generated and dumped xml for both my booting and non booting vms. The only consistent difference between the vm deployments is the addition on $hostname-storage6. Is there perhaps a way to specify which hd is the boot device? I appreciate any assistance. Thanks, Jon A [1] https://github.com/three18ti/Build-VM non Booting VM: ######################################################### # Generated: | <domain type='kvm'> | <name>arch_test2</name> | <memory unit='KiB'>4194304</memory> | <currentMemory unit='KiB'>4194304</currentM...

Hello Richard, Ok, I'll give it a shot. Thanks! Jin A On Nov 25, 2013 4:19 PM, "Richard W.M. Jones" <rjones@redhat.com> wrote: > On Mon, Nov 25, 2013 at 04:12:40PM -0700, Jon wrote: > > Hello Richard, > > > > I'm using: > > > > >> virt-sysprep 1.25.6 > > > > I honestly don't remember if the currently installed

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 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: >>

Hello Rich, Interesting. Thanks for the explanation. When you specify an rbd on the command line for virt-sysprep, do you expect the path to include the monitor address? e.g.: >> virt-sysprep -a rbd://host-name/pool-name/device-name If I understand correctly, libvirt is able to understand the ceph configuration, so when I create a device with qemu-img I only specify the protocol and

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

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

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'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, 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