You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Antonio Packery <An...@t-systems.co.za> on 2014/06/25 14:24:07 UTC

Datadisk Limit per VM

Hi,

I noticed there is a limit for 6 datadisks that can be attached to a VM for all hypervisors other than XenServer 6 and above which supports 13.

I am interested to know why this limitation exists?

Regards
Antonio



Disclaimer: This message and/or attachment(s) may contain privileged, confidential and/or personal information. If you are not the intended recipient you may not disclose or distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error. T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only and is not endorsed by T-Systems.

This message and/or attachment(s) may contain privileged or confidential         
information. If you are not the intended recipient you may not disclose or        
distribute any of the information contained within this message. In such
case you must destroy this message and inform the sender of the error.
T-Systems does not accept liability for any errors, omissions, information
and viruses contained in the transmission of this message. Any opinions, 
conclusions and other information contained within this message not related 
to T-Systems' official business is deemed to be that of the individual only 
and is not endorsed by T-Systems.        
                                                                                  
T-Systems - Business Flexibility



Re: Datadisk Limit per VM

Posted by Antonio Packery <An...@t-systems.co.za>.
Please help with the mysql commands to change this setting.

On 06/26/2014 07:08 AM, Antonio Packery wrote:

Thanks Koushik, I was just wondering if there was a technology reason for this limit?

  Original Message
From: Koushik Das
Sent: Thursday 26 June 2014 06:20
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Reply To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: RE: Datadisk Limit per VM


These values are meant to be set based on the specifications for a hypervisor version and type. These are stored in the hypervisor_capabilities table in the db. If you think that for some specific hypervisor version the values are not correct, feel free to change it.

-----Original Message-----
From: Antonio Packery [mailto:Antonio.Packery@t-systems.co.za]
Sent: Wednesday, 25 June 2014 5:54 PM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: Datadisk Limit per VM

Hi,

I noticed there is a limit for 6 datadisks that can be attached to a VM for all hypervisors other than XenServer 6 and above which supports 13.

I am interested to know why this limitation exists?

Regards
Antonio



Disclaimer: This message and/or attachment(s) may contain privileged, confidential and/or personal information. If you are not the intended recipient you may not disclose or distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error. T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only and is not endorsed by T-Systems.

This message and/or attachment(s) may contain privileged or confidential
information. If you are not the intended recipient you may not disclose or
distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error.
T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only
and is not endorsed by T-Systems.

T-Systems - Business Flexibility



Disclaimer: This message and/or attachment(s) may contain privileged, confidential and/or personal information. If you are not the intended recipient you may not disclose or distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error. T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only and is not endorsed by T-Systems.

This message and/or attachment(s) may contain privileged or confidential
information. If you are not the intended recipient you may not disclose or
distribute any of the information contained within this message. In such
case you must destroy this message and inform the sender of the error.
T-Systems does not accept liability for any errors, omissions, information
and viruses contained in the transmission of this message. Any opinions,
conclusions and other information contained within this message not related
to T-Systems' official business is deemed to be that of the individual only
and is not endorsed by T-Systems.

T-Systems - Business Flexibility


Disclaimer: This message and/or attachment(s) may contain privileged, confidential and/or personal information. If you are not the intended recipient you may not disclose or distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error. T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only and is not endorsed by T-Systems.

This message and/or attachment(s) may contain privileged or confidential         
information. If you are not the intended recipient you may not disclose or        
distribute any of the information contained within this message. In such
case you must destroy this message and inform the sender of the error.
T-Systems does not accept liability for any errors, omissions, information
and viruses contained in the transmission of this message. Any opinions, 
conclusions and other information contained within this message not related 
to T-Systems' official business is deemed to be that of the individual only 
and is not endorsed by T-Systems.        
                                                                                  
T-Systems - Business Flexibility

Re: Datadisk Limit per VM

Posted by Kirk Kosinski <ki...@gmail.com>.
If that is the case please file a bug and (importantly) include the
supporting documentation, unless you can find an existing bug for this.
 As mentioned earlier the distinction between allowed and supported is
important.  With old XenServer versions, for example, you can add more
disks than what is supported with xe commands, but if too many VMs in a
pool have too many disks there can be problems.

Best regards,
Kirk

On 06/26/2014 02:57 AM, Antonio Packery wrote:
> Hi Kirk,
> 
> For KVM, 20 data block devices is supported if using virtio paravirtualization drivers but CloudStack is set to allow only 10.
> 
> Regards
> Antonio
> 
> On 06/26/2014 11:43 AM, Kirk Kosinski wrote:
> 
> Hi, the limit is supposed to be based on what the hypervisor supports.
> CloudStack cannot support more disks than what the hypervisor supports.
>  In some cases the hypervisor might allow adding more disks than the
> officially supported number, but this is not a good idea so by default
> CloudStack follows the official limits.
> 
> Best regards,
> Kirk
> 
> On 06/25/2014 10:08 PM, Antonio Packery wrote:
>> Thanks Koushik, I was just wondering if there was a technology reason for this limit?
>>
>>   Original Message
>> From: Koushik Das
>> Sent: Thursday 26 June 2014 06:20
>> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
>> Reply To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
>> Subject: RE: Datadisk Limit per VM
>>
>>
>> These values are meant to be set based on the specifications for a hypervisor version and type. These are stored in the hypervisor_capabilities table in the db. If you think that for some specific hypervisor version the values are not correct, feel free to change it.
>>
>> -----Original Message-----
>> From: Antonio Packery [mailto:Antonio.Packery@t-systems.co.za]
>> Sent: Wednesday, 25 June 2014 5:54 PM
>> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
>> Subject: Datadisk Limit per VM
>>
>> Hi,
>>
>> I noticed there is a limit for 6 datadisks that can be attached to a VM for all hypervisors other than XenServer 6 and above which supports 13.
>>
>> I am interested to know why this limitation exists?
>>
>> Regards
>> Antonio
>>
>>
>>
>> Disclaimer: This message and/or attachment(s) may contain privileged, confidential and/or personal information. If you are not the intended recipient you may not disclose or distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error. T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only and is not endorsed by T-Systems.
>>
>> This message and/or attachment(s) may contain privileged or confidential
>> information. If you are not the intended recipient you may not disclose or
>> distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error.
>> T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only
>> and is not endorsed by T-Systems.
>>
>> T-Systems - Business Flexibility
>>
>>
>>
>> Disclaimer: This message and/or attachment(s) may contain privileged, confidential and/or personal information. If you are not the intended recipient you may not disclose or distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error. T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only and is not endorsed by T-Systems.
>>
>> This message and/or attachment(s) may contain privileged or confidential
>> information. If you are not the intended recipient you may not disclose or
>> distribute any of the information contained within this message. In such
>> case you must destroy this message and inform the sender of the error.
>> T-Systems does not accept liability for any errors, omissions, information
>> and viruses contained in the transmission of this message. Any opinions,
>> conclusions and other information contained within this message not related
>> to T-Systems' official business is deemed to be that of the individual only
>> and is not endorsed by T-Systems.
>>
>> T-Systems - Business Flexibility
>>
> 
> 
> 
> Disclaimer: This message and/or attachment(s) may contain privileged, confidential and/or personal information. If you are not the intended recipient you may not disclose or distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error. T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only and is not endorsed by T-Systems.
> 
> This message and/or attachment(s) may contain privileged or confidential         
> information. If you are not the intended recipient you may not disclose or        
> distribute any of the information contained within this message. In such
> case you must destroy this message and inform the sender of the error.
> T-Systems does not accept liability for any errors, omissions, information
> and viruses contained in the transmission of this message. Any opinions, 
> conclusions and other information contained within this message not related 
> to T-Systems' official business is deemed to be that of the individual only 
> and is not endorsed by T-Systems.        
>                                                                                   
> T-Systems - Business Flexibility
> 

Re: Datadisk Limit per VM

Posted by Antonio Packery <An...@t-systems.co.za>.
Hi Kirk,

For KVM, 20 data block devices is supported if using virtio paravirtualization drivers but CloudStack is set to allow only 10.

Regards
Antonio

On 06/26/2014 11:43 AM, Kirk Kosinski wrote:

Hi, the limit is supposed to be based on what the hypervisor supports.
CloudStack cannot support more disks than what the hypervisor supports.
 In some cases the hypervisor might allow adding more disks than the
officially supported number, but this is not a good idea so by default
CloudStack follows the official limits.

Best regards,
Kirk

On 06/25/2014 10:08 PM, Antonio Packery wrote:
> Thanks Koushik, I was just wondering if there was a technology reason for this limit?
>
>   Original Message
> From: Koushik Das
> Sent: Thursday 26 June 2014 06:20
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
> Reply To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
> Subject: RE: Datadisk Limit per VM
>
>
> These values are meant to be set based on the specifications for a hypervisor version and type. These are stored in the hypervisor_capabilities table in the db. If you think that for some specific hypervisor version the values are not correct, feel free to change it.
>
> -----Original Message-----
> From: Antonio Packery [mailto:Antonio.Packery@t-systems.co.za]
> Sent: Wednesday, 25 June 2014 5:54 PM
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
> Subject: Datadisk Limit per VM
>
> Hi,
>
> I noticed there is a limit for 6 datadisks that can be attached to a VM for all hypervisors other than XenServer 6 and above which supports 13.
>
> I am interested to know why this limitation exists?
>
> Regards
> Antonio
>
>
>
> Disclaimer: This message and/or attachment(s) may contain privileged, confidential and/or personal information. If you are not the intended recipient you may not disclose or distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error. T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only and is not endorsed by T-Systems.
>
> This message and/or attachment(s) may contain privileged or confidential
> information. If you are not the intended recipient you may not disclose or
> distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error.
> T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only
> and is not endorsed by T-Systems.
>
> T-Systems - Business Flexibility
>
>
>
> Disclaimer: This message and/or attachment(s) may contain privileged, confidential and/or personal information. If you are not the intended recipient you may not disclose or distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error. T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only and is not endorsed by T-Systems.
>
> This message and/or attachment(s) may contain privileged or confidential
> information. If you are not the intended recipient you may not disclose or
> distribute any of the information contained within this message. In such
> case you must destroy this message and inform the sender of the error.
> T-Systems does not accept liability for any errors, omissions, information
> and viruses contained in the transmission of this message. Any opinions,
> conclusions and other information contained within this message not related
> to T-Systems' official business is deemed to be that of the individual only
> and is not endorsed by T-Systems.
>
> T-Systems - Business Flexibility
>



Disclaimer: This message and/or attachment(s) may contain privileged, confidential and/or personal information. If you are not the intended recipient you may not disclose or distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error. T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only and is not endorsed by T-Systems.

This message and/or attachment(s) may contain privileged or confidential         
information. If you are not the intended recipient you may not disclose or        
distribute any of the information contained within this message. In such
case you must destroy this message and inform the sender of the error.
T-Systems does not accept liability for any errors, omissions, information
and viruses contained in the transmission of this message. Any opinions, 
conclusions and other information contained within this message not related 
to T-Systems' official business is deemed to be that of the individual only 
and is not endorsed by T-Systems.        
                                                                                  
T-Systems - Business Flexibility

Re: Datadisk Limit per VM

Posted by Kirk Kosinski <ki...@gmail.com>.
Hi, the limit is supposed to be based on what the hypervisor supports.
CloudStack cannot support more disks than what the hypervisor supports.
 In some cases the hypervisor might allow adding more disks than the
officially supported number, but this is not a good idea so by default
CloudStack follows the official limits.

Best regards,
Kirk

On 06/25/2014 10:08 PM, Antonio Packery wrote:
> Thanks Koushik, I was just wondering if there was a technology reason for this limit?
> 
>   Original Message
> From: Koushik Das
> Sent: Thursday 26 June 2014 06:20
> To: users@cloudstack.apache.org
> Reply To: users@cloudstack.apache.org
> Subject: RE: Datadisk Limit per VM
> 
> 
> These values are meant to be set based on the specifications for a hypervisor version and type. These are stored in the hypervisor_capabilities table in the db. If you think that for some specific hypervisor version the values are not correct, feel free to change it.
> 
> -----Original Message-----
> From: Antonio Packery [mailto:Antonio.Packery@t-systems.co.za]
> Sent: Wednesday, 25 June 2014 5:54 PM
> To: users@cloudstack.apache.org
> Subject: Datadisk Limit per VM
> 
> Hi,
> 
> I noticed there is a limit for 6 datadisks that can be attached to a VM for all hypervisors other than XenServer 6 and above which supports 13.
> 
> I am interested to know why this limitation exists?
> 
> Regards
> Antonio
> 
> 
> 
> Disclaimer: This message and/or attachment(s) may contain privileged, confidential and/or personal information. If you are not the intended recipient you may not disclose or distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error. T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only and is not endorsed by T-Systems.
> 
> This message and/or attachment(s) may contain privileged or confidential
> information. If you are not the intended recipient you may not disclose or
> distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error.
> T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only
> and is not endorsed by T-Systems.
> 
> T-Systems - Business Flexibility
> 
> 
> 
> Disclaimer: This message and/or attachment(s) may contain privileged, confidential and/or personal information. If you are not the intended recipient you may not disclose or distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error. T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only and is not endorsed by T-Systems.
> 
> This message and/or attachment(s) may contain privileged or confidential         
> information. If you are not the intended recipient you may not disclose or        
> distribute any of the information contained within this message. In such
> case you must destroy this message and inform the sender of the error.
> T-Systems does not accept liability for any errors, omissions, information
> and viruses contained in the transmission of this message. Any opinions, 
> conclusions and other information contained within this message not related 
> to T-Systems' official business is deemed to be that of the individual only 
> and is not endorsed by T-Systems.        
>                                                                                   
> T-Systems - Business Flexibility
> 

Re: Datadisk Limit per VM

Posted by Antonio Packery <An...@t-systems.co.za>.
Thanks Koushik, I was just wondering if there was a technology reason for this limit?

  Original Message
From: Koushik Das
Sent: Thursday 26 June 2014 06:20
To: users@cloudstack.apache.org
Reply To: users@cloudstack.apache.org
Subject: RE: Datadisk Limit per VM


These values are meant to be set based on the specifications for a hypervisor version and type. These are stored in the hypervisor_capabilities table in the db. If you think that for some specific hypervisor version the values are not correct, feel free to change it.

-----Original Message-----
From: Antonio Packery [mailto:Antonio.Packery@t-systems.co.za]
Sent: Wednesday, 25 June 2014 5:54 PM
To: users@cloudstack.apache.org
Subject: Datadisk Limit per VM

Hi,

I noticed there is a limit for 6 datadisks that can be attached to a VM for all hypervisors other than XenServer 6 and above which supports 13.

I am interested to know why this limitation exists?

Regards
Antonio



Disclaimer: This message and/or attachment(s) may contain privileged, confidential and/or personal information. If you are not the intended recipient you may not disclose or distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error. T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only and is not endorsed by T-Systems.

This message and/or attachment(s) may contain privileged or confidential
information. If you are not the intended recipient you may not disclose or
distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error.
T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only
and is not endorsed by T-Systems.

T-Systems - Business Flexibility



Disclaimer: This message and/or attachment(s) may contain privileged, confidential and/or personal information. If you are not the intended recipient you may not disclose or distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error. T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only and is not endorsed by T-Systems.

This message and/or attachment(s) may contain privileged or confidential         
information. If you are not the intended recipient you may not disclose or        
distribute any of the information contained within this message. In such
case you must destroy this message and inform the sender of the error.
T-Systems does not accept liability for any errors, omissions, information
and viruses contained in the transmission of this message. Any opinions, 
conclusions and other information contained within this message not related 
to T-Systems' official business is deemed to be that of the individual only 
and is not endorsed by T-Systems.        
                                                                                  
T-Systems - Business Flexibility

RE: Datadisk Limit per VM

Posted by Koushik Das <ko...@citrix.com>.
These values are meant to be set based on the specifications for a hypervisor version and type. These are stored in the hypervisor_capabilities table in the db. If you think that for some specific hypervisor version the values are not correct, feel free to change it.

-----Original Message-----
From: Antonio Packery [mailto:Antonio.Packery@t-systems.co.za] 
Sent: Wednesday, 25 June 2014 5:54 PM
To: users@cloudstack.apache.org
Subject: Datadisk Limit per VM

Hi,

I noticed there is a limit for 6 datadisks that can be attached to a VM for all hypervisors other than XenServer 6 and above which supports 13.

I am interested to know why this limitation exists?

Regards
Antonio



Disclaimer: This message and/or attachment(s) may contain privileged, confidential and/or personal information. If you are not the intended recipient you may not disclose or distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error. T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only and is not endorsed by T-Systems.

This message and/or attachment(s) may contain privileged or confidential         
information. If you are not the intended recipient you may not disclose or        
distribute any of the information contained within this message. In such case you must destroy this message and inform the sender of the error.
T-Systems does not accept liability for any errors, omissions, information and viruses contained in the transmission of this message. Any opinions, conclusions and other information contained within this message not related to T-Systems' official business is deemed to be that of the individual only 
and is not endorsed by T-Systems.        
                                                                                  
T-Systems - Business Flexibility