On Feb 12, 2008 8:24 PM, christf1 <[EMAIL PROTECTED]> wrote: > > I tried the latest dev stream, and continued to have the problem. The > quick > fix is to simply touch the target file before launching 'virt-clone' > > touch <dir_to_VMs>/newvm.img > virt-clone -o existing_vm -n new_vm -o <dir_to_VMs>/newvm.img >
hi, i wonders virt-clone will work when one is doing LVM for domUs fro example here is mine virutal config file kernel = "/boot/vmlinuz-2.6.21-2952.fc8xen" ramdisk = "/boot/initrd-2.6.21-2952.fc8xen-domU.img" memory = 200 name = "myvm3" vif = [ 'ip=xxx.xxx.xx.xx' ] disk = [ 'phy:vg/vm2.root,sda1,w', 'phy:vg/vm2.swap,sda2,w', 'phy:vg/vm2.var,sda3,w' ] root = "/dev/sda1 ro" on_reboot = 'restart' on_crash = 'restart' On other hosts we are using loop back files for domU FS. thanks.
-- Fedora-xen mailing list [email protected] https://www.redhat.com/mailman/listinfo/fedora-xen
