cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy Coates <>
Subject Re: Identifying a VM's ROOT disk offering via the database
Date Mon, 24 Jun 2013 14:12:30 GMT
Hi Sanjay,

That may be the case, but how do you identify what Disk Offering those ROOT
disks are based on?

After you create a VM you can identify its Service Offering, but not its
Disk Offering - and that's what I'm trying to establish here.

Some of our Disk Offerings use SATA disks, some use SAS, or even Fiber
Channel.  When a VM is created from an ISO you can choose the Disk
Offering, but where is that information stored afterwards?  Likewise if I
made a template of that new VM's disk, would it continue to use the same
Disk Offering the original VM was made on, and where can I identify that?


On 24 June 2013 21:58, Sanjay Tripathi <> wrote:

> Andy,
> If you are deploying a VM from an ISO, the DATA DISK you select becomes
> the ROOT DISK for that VM and if you are deploying a VM from a template,
> then the size of template becomes the size of ROOT DISK and you can select
> additional DISK as DATA DISK from disk offering for the VM.
> --Sanjay
> > -----Original Message-----
> > From: Andy Coates []
> > Sent: Monday, June 24, 2013 6:33 PM
> > To:
> > Subject: Identifying a VM's ROOT disk offering via the database
> >
> > Hey,
> >
> > Does anyone know where in the database you can find out what Disk
> > Offering a VM's ROOT disk is based on?
> >
> > To follow on from that, if you made a template from a new VM (via ISO
> > image) that, for example, used MyDiskOfferingA, would further instances
> of
> > that template also use the same Disk Offering (as you cannot change the
> > ROOT disk offering from a template instantiation)?  The templates assign
> the
> > same disk size, I'm just not sure how it knows if it's a specific Disk
> Offering or
> > not.
> >
> > Thanks,
> > Andy.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message