Spurious error message when the RHEV capacity is maxed out?
--_000_CF7D45AF5E0Esvempatitintricom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable We have about 900 vms in a RHEV-M 3.3 installation (3.3.2-0.50.el6ev) with = three hosts. Each VM has 1 socket, 1 core for CPU and 256 MB memory and 2 x 1TB disks + = one 5 GB boot disk. Each host has 2 cpu sockets with 4 cpu cores per socket. When we power on about 250 of these vms, we cannot power on any more vms. Attempting to do so gets the error (in the RHEV-M) console. Bad volume specification {'index': 0, 'iface': 'virtio', 'reqsize': '0', 'f= ormat': 'raw', 'bootOrder': '1', 'volumeID': '14aa7302-7f6d-4b80-922d-3fc09= 0695447', 'apparentsize': '5368709120', 'imageID': '97b1985e-e507-4927-91e9= -7393c7777de5', 'specParams': {}, 'readonly': 'false', 'domainID': '0c7abcc= c-1b97-4b39-ab96-e977a19fac3a', 'optional': 'false', 'deviceId': '97b1985e-= e507-4927-91e9-7393c7777de5', 'truesize': '0', 'poolID': '5849b030-626e-47c= b-ad90-3ce782d831b3', 'device': 'disk', 'shared': 'false', 'propagateErrors= ': 'off', 'type': 'disk'}. This looks like a spurious error, as we can power on the same VM after rebo= oting the hosts. And also, the hosts do not really look maxed out (CPU usage is around 25%, = memory around 50%), but no more vm=92s can be powered on. I was looking for a sizing guide, and found only https://access.redhat.com/= site/sites/default/files/attachments/rhev_sizing_0812.pdf Is there any other information available? --_000_CF7D45AF5E0Esvempatitintricom_ Content-Type: text/html; charset="Windows-1252" Content-ID: <43C5516411658D4E88AF942223A80EF2@internal> Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> </head> <body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin= e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami= ly: Calibri, sans-serif;"> <div>We have about 900 vms in a RHEV-M 3.3 installation (<span style=3D"col= or: rgb(17, 17, 17); font-family: Verdana; line-height: 24px;">3.3.2-0.50.e= l6ev) </span>with three hosts.</div> <div><br> </div> <div>Each VM has 1 socket, 1 core for CPU and 256 MB memory and 2 x 1TB dis= ks + one 5 GB boot disk.</div> <div><br> </div> <div>Each host has 2 cpu sockets with 4 cpu cores per socket.</div> <div><br> </div> <div>When we power on about 250 of these vms, we cannot power on any more v= ms.</div> <div><br> </div> <div>Attempting to do so gets the error (in the RHEV-M) console.</div> <div><br> </div> <div> <div>Bad volume specification {'index': 0, 'iface': 'virtio', 'reqsize': '0= ', 'format': 'raw', 'bootOrder': '1', 'volumeID': '14aa7302-7f6d-4b80-922d-= 3fc090695447', 'apparentsize': '5368709120', 'imageID': '97b1985e-e507-4927= -91e9-7393c7777de5', 'specParams': {}, 'readonly': 'false', 'domainID': '0c7abccc-1b97-4b39-ab96-e977a19fac3a= ', 'optional': 'false', 'deviceId': '97b1985e-e507-4927-91e9-7393c7777de5',= 'truesize': '0', 'poolID': '5849b030-626e-47cb-ad90-3ce782d831b3', 'device= ': 'disk', 'shared': 'false', 'propagateErrors': 'off', 'type': 'disk'}.</div> </div> <div><br> </div> <div>This looks like a spurious error, as we can power on the same VM after= rebooting the hosts.</div> <div><br> </div> <div>And also, the hosts do not really look maxed out (CPU usage is around = 25%, memory around 50%), but no more vm=92s can be powered on. </div> <div><br> </div> <div>I was looking for a sizing guide, and found only <a href=3D"https= ://access.redhat.com/site/sites/default/files/attachments/rhev_sizing_0812.= pdf" style=3D"font-size: medium; color: rgb(102, 51, 102);">https://access.= redhat.com/site/sites/default/files/attachments/rhev_sizing_0812.pdf</a></d= iv> <div><br> </div> <div>Is there any other information available?</div> <br> </body> </html> --_000_CF7D45AF5E0Esvempatitintricom_--
On 04/24/2014 12:31 AM, Satya Vempati wrote:
We have about 900 vms in a RHEV-M 3.3 installation (3.3.2-0.50.el6ev) with three hosts.
Each VM has 1 socket, 1 core for CPU and 256 MB memory and 2 x 1TB disks + one 5 GB boot disk.
Each host has 2 cpu sockets with 4 cpu cores per socket.
When we power on about 250 of these vms, we cannot power on any more vms.
is this a 'monday morning effect' (are you trying to launch them all together)?
Attempting to do so gets the error (in the RHEV-M) console.
Bad volume specification {'index': 0, 'iface': 'virtio', 'reqsize': '0', 'format': 'raw', 'bootOrder': '1', 'volumeID': '14aa7302-7f6d-4b80-922d-3fc090695447', 'apparentsize': '5368709120', 'imageID': '97b1985e-e507-4927-91e9-7393c7777de5', 'specParams': {}, 'readonly': 'false', 'domainID': '0c7abccc-1b97-4b39-ab96-e977a19fac3a', 'optional': 'false', 'deviceId': '97b1985e-e507-4927-91e9-7393c7777de5', 'truesize': '0', 'poolID': '5849b030-626e-47cb-ad90-3ce782d831b3', 'device': 'disk', 'shared': 'false', 'propagateErrors': 'off', 'type': 'disk'}.
This looks like a spurious error, as we can power on the same VM after rebooting the hosts.
And also, the hosts do not really look maxed out (CPU usage is around 25%, memory around 50%), but no more vm’s can be powered on.
I was looking for a sizing guide, and found only https://access.redhat.com/site/sites/default/files/attachments/rhev_sizing_0...
Is there any other information available?
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Apr 24, 2014, at 07:40 , Itamar Heim <iheim@redhat.com> wrote:
On 04/24/2014 12:31 AM, Satya Vempati wrote:
We have about 900 vms in a RHEV-M 3.3 installation (3.3.2-0.50.el6ev) with three hosts.
Each VM has 1 socket, 1 core for CPU and 256 MB memory and 2 x 1TB disks + one 5 GB boot disk.
Each host has 2 cpu sockets with 4 cpu cores per socket.
When we power on about 250 of these vms, we cannot power on any more vms.
is this a 'monday morning effect' (are you trying to launch them all together)?
even that would work, we just serialize the requests so it could only take a long time...
Attempting to do so gets the error (in the RHEV-M) console.
Bad volume specification {'index': 0, 'iface': 'virtio', 'reqsize': '0', 'format': 'raw', 'bootOrder': '1', 'volumeID': '14aa7302-7f6d-4b80-922d-3fc090695447', 'apparentsize': '5368709120', 'imageID': '97b1985e-e507-4927-91e9-7393c7777de5', 'specParams': {}, 'readonly': 'false', 'domainID': '0c7abccc-1b97-4b39-ab96-e977a19fac3a', 'optional': 'false', 'deviceId': '97b1985e-e507-4927-91e9-7393c7777de5', 'truesize': '0', 'poolID': '5849b030-626e-47cb-ad90-3ce782d831b3', 'device': 'disk', 'shared': 'false', 'propagateErrors': 'off', 'type': 'disk'}.
check both engine and vdsm logs to identify if it's on the engine side or some trouble at the host... Thanks, michal
This looks like a spurious error, as we can power on the same VM after rebooting the hosts.
And also, the hosts do not really look maxed out (CPU usage is around 25%, memory around 50%), but no more vm’s can be powered on.
I was looking for a sizing guide, and found only https://access.redhat.com/site/sites/default/files/attachments/rhev_sizing_0...
Is there any other information available?
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (3)
-
Itamar Heim -
Michal Skrivanek -
Satya Vempati