Dear List Colleagues: Wow! So much traffic on these neat but mysterious tools. I used the ''touch'' workaround today and got virt-clone working - thank you both to christf1 and to Cole! The relief was literally indescribable when it ran (...pressure, what pressure?!) I have been in touch with Cole and he informs me that the latest and greatest version of virt-clone can be gotten from the virt-manager devel repository and that this version does not need the ''touch'' work-around. For those of you who have not used virt-clone - when it finally works it is really great and as cloning is of vital importance to the project I am working on, many thanks to all who contribute to the virt-manager tools! In a previous post, on this thread today, it was mentioned that some of my results were unduplicable on the usage of switches such as "-f" and "--file" - interestingly, yesterday, the same day I experienced those problems I was unable to duplicate some of them, myself, when I went back to them. I do not know why this was/is the case or what happened, there the results I posted were copied from actual terminal windows where they had run. I am willing to run a set of tests against my machine with virt-clone and send them off to anyone interested in its functionality or lack thereof. I think that this is an important tool and I am willing to do whatever I can to help develop it. I have certainly found it to be ''touchy.'' Cole has asked me, as a repository using newbie - who had a lack of success gaining access - to report on my experience of trying to get stuff out of the repository and I will do so, shortly, and report my experience so others can benefit from my efforts to gain competence and my report on how this is done - some steps do seem to be skipped in the instructions on that site! Thanks, again to Cole for pointers on what was going wrong for me, there. It was great to see my questions about LVM and virt-clone answered today, before I could even ask them myself! Best, Petrus fedora-xen-request@redhat.com wrote:> Send Fedora-xen mailing list submissions to > fedora-xen@redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/fedora-xen > or, via email, send a message with subject or body ''help'' to > fedora-xen-request@redhat.com > > You can reach the person managing the list at > fedora-xen-owner@redhat.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Fedora-xen digest..." > > > Today''s Topics: > > 1. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Cole Robinson) > 2. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Daniel P. Berrange) > 3. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Daniel P. Berrange) > 4. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Asrai khn) > 5. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Daniel P. Berrange) > 6. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Cole Robinson) > 7. Xen packages for Vulnerability to CVE-2008-0600 (Russell McOrmond) > 8. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Christopher Fournier) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 12 Feb 2008 12:30:21 -0500 > From: Cole Robinson <crobinso@redhat.com> > Subject: Re: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk > size must be an int or a float. > To: christf1 <christf1@nortel.com> > Cc: fedora-xen@redhat.com > Message-ID: <47B1D7AD.3040102@redhat.com> > Content-Type: text/plain; charset=us-ascii > > christf1 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 >> >> Cheers! >> > > I''m not seeing this: > > hg clone http://hg.et.redhat.com/virt/applications/virtinst--devel > cd virtinst--devel > ./virt-clone -o xen-pv -n clone-pv -f /idontexist.img > > starts working, for an existing turned off guest named xen-pv on f8. > Is there anything you are doing differently? If so, can you detail it > and post the complete error message? > > Thanks, > Cole > > > > ------------------------------ > > Message: 2 > Date: Tue, 12 Feb 2008 17:35:27 +0000 > From: "Daniel P. Berrange" <berrange@redhat.com> > Subject: Re: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk > size must be an int or a float. > To: Asrai khn <asraikhn@gmail.com> > Cc: fedora-xen@redhat.com > Message-ID: <20080212173527.GK25829@redhat.com> > Content-Type: text/plain; charset=us-ascii > > On Tue, Feb 12, 2008 at 09:49:55PM +0500, Asrai khn wrote: > >> On Feb 12, 2008 8:24 PM, christf1 <christf1@nortel.com> 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 >> > > It won''t care what type of storage the original VM is using - it''ll > simply read the data off the original disk whether its a file or > block device or LVM vol. > > If you want to use LVM volumes in the destination VM, then you currently > need to manually create the LVM volume ahead of time - virt-clone itself > will not create new LVM volumes for you. This is in the future feature > list though, once libvirt storage management APIs are merged. > > Dan. >