Hi Itamar,
To edit the disk size are you referring this "Another way i got is create
the VM with 1GB virtual template and expand the disk size after
deployment...but the problem here is disk will expand...but it will not
done any changes in the existing partition table..that means after expand
disk you need to manual login in to server and make the changes with the
help of fdisk and lvm commands..."
Or it's different then the upper one...please let me know how to perform
this...if any screen shot you can provide for better understanding..
Thanks,
Punit
On Wed, Aug 27, 2014 at 5:15 PM, Itamar Heim <iheim(a)redhat.com> wrote:
On 08/27/2014 12:08 PM, Punit Dambiwal wrote:
> Hi Itamar,
>
> Thanks for the update....Yes.. i want to create different size VM with
> the same OS template...
>
> ------------
> 3. we support "disk resize" since 3.4 (iirc), which you can do post VM
> provisioning.
>
> considering #3, then #1 should be easy to support as well these days.
> please open an RFE.
> ------------
>
> Could you please more elaborate point number 3...how to use it..i will
> go with this one ...
>
>
iirc, you just need to edit the disk size when vm is down or up (for up,
only for specific disk interfaces, virtio-blk, not ide, iirc)
Thanks,
> Punit
>
>
> On Wed, Aug 27, 2014 at 4:37 PM, Itamar Heim <iheim(a)redhat.com
> <mailto:iheim@redhat.com>> wrote:
>
> On 08/27/2014 04:18 AM, Punit Dambiwal wrote:
>
> Hi Michal,
>
> I want to deploy the VM with the template but the problem is in
> ovirt
> when you deploy the VM by template it copy the whole image(even
> thin or
> thick disk)...like if i have 40GB virtual size (actual size 1GB)
> disk....it will copy the whole 40GB to provision the virtual
> machine....so if i want to deploy 10 VM simultaneous then it
> will copy
> 4TB data and take long time to provision....
>
> I want the way i can make the template with small size....and
> once i
> choose to create the virtual machine with 40GB...the VM deploy
> with the
> small template on the 40GB disk... is it possible with ovirt.. ??
>
>
> so you want to provision a VM with a different disk size than
> template.
> good point. some thoughts:
> 1. for thinly provisioned (qcow2) - its COW, hence the same size.
> 2. for clone - actually, no reason shouldn't be supported easily.
> 3. we support "disk resize" since 3.4 (iirc), which you can do post
> VM provisioning.
>
> considering #3, then #1 should be easy to support as well these
> days. please open an RFE.
>
>
> Thanks,
> Punit
>
>
> On Tue, Aug 26, 2014 at 9:01 PM, Michal Skrivanek
> <michal.skrivanek(a)redhat.com
> <mailto:michal.skrivanek@redhat.com>
> <mailto:michal.skrivanek@__redhat.com
>
> <mailto:michal.skrivanek@redhat.com>>> wrote:
>
>
> On Aug 26, 2014, at 12:01 , Punit Dambiwal
> <hypunit(a)gmail.com <mailto:hypunit@gmail.com>
> <mailto:hypunit@gmail.com <mailto:hypunit@gmail.com>>>
> wrote:
>
> > Hi Michal,
> >
> > 2. I find disk size can not modify at the time of VM
> provisioning,is there any way to modify the VM disk size ??
> >
> > well, not really, AFAIK.
> > create another disk, move your data, remove the original
> Or
> create a bigger thin provisioned disk at the beginning...
> >
> > I didn't understand the mean...i can create the another
> disk...it's ok...but how to move the data from the existing
> disk to
> new disk at the time of the VM deployment... ?? is there
> any way to
> move the data.. ??
> Hi,
>
> You would have to do that inside the guest…the same way as
> you would
> do it on real hardware…mount both disks, move the relevant
> data
> not trivial and not automated
>
> >
> > Another question is there any way to mount the img like
> i will
> create the VM with blank template with my preferred disk
> size and
> leter on install the OS through any OS template ??? i know
> i can
> install the OS through CD-ISO but i don't want the manual
> installation…
>
> so you want to have a preinstalled OS…so how did you want
> to use it?
> I probably don't understand what are you trying to achieve.
> Anything else than having a Template with OS and you deploy
> VMs from
> that….you need to change disk sizes for each such VM? Could
> it be
> done by adding an additional disk?
>
> Thanks,
> michal
>
> >
> > Thanks,
> > Punit
> >
> >
> > On Tue, Aug 26, 2014 at 5:51 PM, Michal Skrivanek
> <michal.skrivanek(a)redhat.com
> <mailto:michal.skrivanek@redhat.com>
> <mailto:michal.skrivanek@__redhat.com
>
> <mailto:michal.skrivanek@redhat.com>>>
>
> wrote:
> >
> > On Aug 26, 2014, at 05:26 , Punit Dambiwal
> <hypunit(a)gmail.com <mailto:hypunit@gmail.com>
> <mailto:hypunit@gmail.com <mailto:hypunit@gmail.com>>>
> wrote:
> >
> > > Hi All,
> > >
> > > I have some questions regarding the VM deployment
> through OS
> template...
> > >
> > > 1. I have imported centos template from openstack
> glance (the
> actual size of the template is 16GB but used is 1GB)...now my
> question is if i deploy the new VM with this template,the
> process
> will copy the whole 16GB or just 1 GB to create the new VM ??
> >
> > if you deploy with thin provisioned disks it should be 1GB
> >
> > >
> > > 2. I find disk size can not modify at the time of VM
> provisioning,is there any way to modify the VM disk size ??
> >
> > well, not really, AFAIK.
> > create another disk, move your data, remove the original.
> > Or create a bigger thin provisioned disk at the beginning
> >
> > >
> > > Thanks,
> > > Punit
> > >
> > >
> > > On Mon, Aug 25, 2014 at 5:42 PM, Punit Dambiwal
> <hypunit(a)gmail.com <mailto:hypunit@gmail.com>
> <mailto:hypunit@gmail.com <mailto:hypunit@gmail.com>>> wrote:
> > > Hi All,
> > >
> > > I have some questions regarding the VM deployment
> through OS
> template...
> > >
> > > 1. I have imported centos template from openstack
> glance (the
> actual size of the template is 16GB but used is 1GB)...now my
> question is if i deploy the new VM with this template,the
> process
> will copy the whole 16GB or just 1 GB to create the new VM ??
> > >
> > > 2. I find disk size can not modify at the time of VM
> provisioning,is there any way to modify the VM disk size ??
> > >
> > > Thanks,
> > > Punit
> > >
> >
> >
>
>
>
>
>