On Thu, Jun 28, 2012 at 05:28:26PM +0200, Arindam Choudhury wrote: > What are the "state of art" of provisioning virtual machine? > > Can we transfer a LVM virtual machine image? > You can use *all* the normal Linux/unix tools, Xen doesn't create any restrictions there. So feel free to dd the volume to another volume, or use snapshots, or thinprov-snapshots, or whatever you want. -- Pasi > On Thu, Jun 28, 2012 at 4:26 PM, Pasi Kärkkäinen <[1]pasik@xxxxxx> wrote: > > On Wed, Jun 27, 2012 at 05:51:13PM +0200, Arindam Choudhury wrote: > > I am using xen hypervisor in fedora 17. I want to use LVM storage > for > > domU. > > > > LVM volumes work very well out-of-the-box as disks for Xen domUs. > > -- Pasi > > > On Wed, Jun 27, 2012 at 5:12 PM, Joseph Hom > <[1][2]jhom@xxxxxxxxxxxxx> wrote: > > > > What Xen are you using? OS? XCP? XenServer? > > > > > > > > Also what storage are you using? > > > > > > > > From: [2][3]xen-users-bounces@xxxxxxxxxxxxx > > [mailto:[3][4]xen-users-bounces@xxxxxxxxxxxxx] On Behalf Of > Arindam > > Choudhury > > Sent: Wednesday, June 27, 2012 5:42 AM > > To: xen users > > Subject: [Xen-users] provisioning virtual machine > > > > > > > > Hi, > > > > I am trying to provision virtual machines to create a virtual > machine > > cluster. If I try to transfer a pre-build virtual machine, its > too time > > consuming and hard on network. So the idea of using bootstrap or > > kickstart seems better. Can any body point a good tutorial how to > do > > this? > > > > Actually I have a master image and I have to copy it on all the > nodes > > and create virtual machines. Is there any other way to do it? > > > > Regards, > > Arindam > > > > References > > > > Visible links > > 1. mailto:[5]jhom@xxxxxxxxxxxxx > > 2. mailto:[6]xen-users-bounces@xxxxxxxxxxxxx > > 3. mailto:[7]xen-users-bounces@xxxxxxxxxxxxx > > -- > > xen mailing list > > [8]xen@xxxxxxxxxxxxxxxxxxxxxxx > > [9]https://admin.fedoraproject.org/mailman/listinfo/xen > > References > > Visible links > 1. mailto:pasik@xxxxxx > 2. mailto:jhom@xxxxxxxxxxxxx > 3. mailto:xen-users-bounces@xxxxxxxxxxxxx > 4. mailto:xen-users-bounces@xxxxxxxxxxxxx > 5. mailto:jhom@xxxxxxxxxxxxx > 6. mailto:xen-users-bounces@xxxxxxxxxxxxx > 7. mailto:xen-users-bounces@xxxxxxxxxxxxx > 8. mailto:xen@xxxxxxxxxxxxxxxxxxxxxxx > 9. https://admin.fedoraproject.org/mailman/listinfo/xen > -- > xen mailing list > xen@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/xen
