Maximum VM memory
--_000_803F768AF2CE4F0DBDB8069A62C5BEB5unilu_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 RGVhciBvdmlydCB1c2VycywNCg0KV2UgaGF2ZSBhIHNwZWNpYWwgbWFjaGluZSB3aGljaCBoYXMg MSBUQiBSQU0uDQoNClRoZSBpZGVhIGlzIHRvIGhhdmUgMy00IFZNcyBvbiB0aGVyZSB3aGljaCBz aG91bGQgYmUgc3BsaXQgbGlrZSA4NS81LzUvNSAlIG9mIHRvdGFsIFJBTS4NCg0KSSBoYXZlIHRo cmVlIHF1ZXN0aW9uczoNCg0KMS4gSXMgdGhlcmUgYW55IHJlYXNvbiBub3QgdG8gcHV0IHVwIGEg Vk0gd2l0aCBzbyBtdWNoIFJBTQ0KDQoyLiBIb3cgY2FuIEkgaW5jcmVhc2UgdGhlIG1heGltdW0g UkFNIHNpemUgZm9yIDY0IGJpdCBWTXM/DQoNCjMuIEhvdyBjYW4gSSBjcmVhdGUgYSBuZXcgT1Mg Zm9yIHRoZSBWTSBjcmVhdGlvbiB0aGF0IHN1cHBvcnRzID4gMTYgR0IgPyAoUmlnaHQgbm93IGkg aGF2ZSB0byBjaG9vc2UgUkhFTCA2NCBiaXRzIGV2ZW4gZm9yIERlYmlhbiBzeXN0ZW1zKQ0KDQpU aGFuayB5b3UgZm9yIHlvdXIgaGVscCwNCg0K4oCUDQpDaHJpc3RvcGhlDQoNCg0KDQo= --_000_803F768AF2CE4F0DBDB8069A62C5BEB5unilu_ Content-Type: text/html; charset="utf-8" Content-ID: <67A8A10803FFAE41B67512C9F7DDB1E5@uni.lux> Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KRGVhciBvdmlydCB1c2VycywNCjxk aXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPldlIGhhdmUg YSBzcGVjaWFsIG1hY2hpbmUgd2hpY2ggaGFzIDEgVEIgUkFNLjwvZGl2Pg0KPGRpdiBjbGFzcz0i Ij48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+VGhlIGlkZWEgaXMgdG8gaGF2 ZSAzLTQgVk1zIG9uIHRoZXJlIHdoaWNoIHNob3VsZCBiZSBzcGxpdCBsaWtlIDg1LzUvNS81ICUg b2YgdG90YWwgUkFNLjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4N CjxkaXYgY2xhc3M9IiI+SSBoYXZlIHRocmVlIHF1ZXN0aW9uczo8L2Rpdj4NCjxkaXYgY2xhc3M9 IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjEuIElzIHRoZXJlIGFueSBy ZWFzb24gbm90IHRvIHB1dCB1cCBhIFZNIHdpdGggc28gbXVjaCBSQU0mbmJzcDs8L2Rpdj4NCjxk aXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjIuIEhvdyBj YW4gSSBpbmNyZWFzZSB0aGUgbWF4aW11bSBSQU0gc2l6ZSBmb3IgNjQgYml0IFZNcz88L2Rpdj4N CjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjMuIEhv dyBjYW4gSSBjcmVhdGUgYSBuZXcgT1MgZm9yIHRoZSBWTSBjcmVhdGlvbiB0aGF0IHN1cHBvcnRz ICZndDsgMTYgR0IgPyAoUmlnaHQgbm93IGkgaGF2ZSB0byBjaG9vc2UgUkhFTCA2NCBiaXRzIGV2 ZW4gZm9yIERlYmlhbiBzeXN0ZW1zKTwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+ DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+VGhhbmsgeW91IGZvciB5b3VyIGhlbHAsPC9kaXY+DQo8 ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj7igJQ8L2Rp dj4NCjxkaXYgY2xhc3M9IiI+Q2hyaXN0b3BoZTxiciBjbGFzcz0iIj4NCjxkaXYgYXBwbGUtY29u dGVudC1lZGl0ZWQ9InRydWUiIGNsYXNzPSIiPg0KPG1ldGEgbmFtZT0iZm9ybWF0LWRldGVjdGlv biIgY29udGVudD0idGVsZXBob25lPW5vIiBjbGFzcz0iIj4NCjxwIHN0eWxlPSJmb250LWZhbWls eTogQXJpYWwsIHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTBwdDsgbGluZS1oZWlnaHQ6IDE2cHg7 IGNvbG9yOiByZ2IoMzMsIDMzLCAzMyk7IiBjbGFzcz0iIj4NCiZuYnNwOzwvcD4NCjwvZGl2Pg0K PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo= --_000_803F768AF2CE4F0DBDB8069A62C5BEB5unilu_--
This is a multi-part message in MIME format. --------------060004030001010102070907 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 10/05/15 13:17, Christophe TREFOIS wrote:
Dear ovirt users,
We have a special machine which has 1 TB RAM.
The idea is to have 3-4 VMs on there which should be split like 85/5/5/5 % of total RAM.
I have three questions:
1. Is there any reason not to put up a VM with so much RAM
One reason I can think of - migration of a VM with 1TB ram will most likely never complete and time out. I have problems migrating machines with 64GB or more of RAM on RHEV, If you don't need live migration then you should be OK. Alex --------------060004030001010102070907 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 10/05/15 13:17, Christophe TREFOIS wrote:<br> <blockquote cite="mid:803F768A-F2CE-4F0D-BDB8-069A62C5BEB5@uni.lu" type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> Dear ovirt users, <div class=""><br class=""> </div> <div class="">We have a special machine which has 1 TB RAM.</div> <div class=""><br class=""> </div> <div class="">The idea is to have 3-4 VMs on there which should be split like 85/5/5/5 % of total RAM.</div> <div class=""><br class=""> </div> <div class="">I have three questions:</div> <div class=""><br class=""> </div> <div class="">1. Is there any reason not to put up a VM with so much RAM <br> </div> </blockquote> <br> One reason I can think of - migration of a VM with 1TB ram will most likely never complete and time out. I have problems migrating machines with 64GB or more of RAM on RHEV,<br> <br> If you don't need live migration then you should be OK.<br> <br> Alex<br> </body> </html> --------------060004030001010102070907--
----- Original Message -----
From: "Christophe TREFOIS" <christophe.trefois@uni.lu> To: users@ovirt.org Sent: Sunday, May 10, 2015 3:17:12 PM Subject: [ovirt-users] Maximum VM memory
Dear ovirt users,
We have a special machine which has 1 TB RAM.
The idea is to have 3-4 VMs on there which should be split like 85/5/5/5 % of total RAM.
I have three questions:
1. Is there any reason not to put up a VM with so much RAM
i don't think there is a problem with that
2. How can I increase the maximum RAM size for 64 bit VMs?
i dont think you need to increase the maximum, max ram for 64bit os should be ok for your case with any cluster with compatibility of 3.1 and above (2TiB): $ engine-config --get VM64BitMaxMemorySizeInMB VM64BitMaxMemorySizeInMB: 524288 version: 3.0 VM64BitMaxMemorySizeInMB: 2097152 version: 3.1 VM64BitMaxMemorySizeInMB: 2097152 version: 3.2 VM64BitMaxMemorySizeInMB: 2097152 version: 3.3 VM64BitMaxMemorySizeInMB: 4096000 version: 3.4 VM64BitMaxMemorySizeInMB: 4096000 version: 3.5 VM64BitMaxMemorySizeInMB: 4194304 version: 3.6
3. How can I create a new OS for the VM creation that supports > 16 GB ? (Right now i have to choose RHEL 64 bits even for Debian systems)
please see [1] for customizing guest os information. please note this bug [2]: Bug 1218531 - Setting "Other OS" is default 32bit instead of 64bit and causes incorrect RAM size limit of 16GB for 64bit OS. should be part of ovirt 3.5.3 where the we change most OS to be 64bit by default so most linux distros will be considered 64bit (Linux, debian 7, suse, ubuntu..) [1] http://www.ovirt.org/OS_info#value_overriding [2] https://bugzilla.redhat.com/show_bug.cgi?id=1218531
Thank you for your help,
— Christophe
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Omer, Especially the last point of your response is a good thing! I came across the problem as well, when trying to increase a VM to be > 16 GB and by choosing any other 64 bit template it worked. Looking forward to these changes, -- Christophe -----Original Message----- From: Omer Frenkel [mailto:ofrenkel@redhat.com] Sent: dimanche, le 10 mai 2015 14:59 To: Christophe TREFOIS Cc: users@ovirt.org Subject: Re: [ovirt-users] Maximum VM memory ----- Original Message -----
From: "Christophe TREFOIS" <christophe.trefois@uni.lu> To: users@ovirt.org Sent: Sunday, May 10, 2015 3:17:12 PM Subject: [ovirt-users] Maximum VM memory
Dear ovirt users,
We have a special machine which has 1 TB RAM.
The idea is to have 3-4 VMs on there which should be split like 85/5/5/5 % of total RAM.
I have three questions:
1. Is there any reason not to put up a VM with so much RAM
i don't think there is a problem with that
2. How can I increase the maximum RAM size for 64 bit VMs?
i dont think you need to increase the maximum, max ram for 64bit os should be ok for your case with any cluster with compatibility of 3.1 and above (2TiB): $ engine-config --get VM64BitMaxMemorySizeInMB VM64BitMaxMemorySizeInMB: 524288 version: 3.0 VM64BitMaxMemorySizeInMB: 2097152 version: 3.1 VM64BitMaxMemorySizeInMB: 2097152 version: 3.2 VM64BitMaxMemorySizeInMB: 2097152 version: 3.3 VM64BitMaxMemorySizeInMB: 4096000 version: 3.4 VM64BitMaxMemorySizeInMB: 4096000 version: 3.5 VM64BitMaxMemorySizeInMB: 4194304 version: 3.6
3. How can I create a new OS for the VM creation that supports > 16 GB ? (Right now i have to choose RHEL 64 bits even for Debian systems)
please see [1] for customizing guest os information. please note this bug [2]: Bug 1218531 - Setting "Other OS" is default 32bit instead of 64bit and causes incorrect RAM size limit of 16GB for 64bit OS. should be part of ovirt 3.5.3 where the we change most OS to be 64bit by default so most linux distros will be considered 64bit (Linux, debian 7, suse, ubuntu..) [1] http://www.ovirt.org/OS_info#value_overriding [2] https://bugzilla.redhat.com/show_bug.cgi?id=1218531
Thank you for your help,
— Christophe
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (3)
-
Alex Crow -
Christophe TREFOIS -
Omer Frenkel