[Users] ovirt fails to start vm on EL based nodes
by Brown, Chris (GE Healthcare)
This is a multi-part message in MIME format.
------_=_NextPart_001_01CCDC7C.033AF09A
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
The ovirt engine is failing to start virtual machines on EL based nodes.
I think I have found the failure mode.
The engine log shows:
2012-01-26 16:01:45,200 INFO
[org.ovirt.engine.core.vdsbroker.CreateVmVDSCommand] (pool-5-thread-48)
FINISH, CreateVmVDSCommand, return: WaitForLaunch, log id: d1649a2
2012-01-26 16:01:45,953 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand]
(QuartzScheduler_Worker-89) START, DestroyVDSCommand(vdsId =3D
e7df9be0-47a0-11e1-80f3-00144f8d7c32,
vmId=3D6c84897b-4d2b-461b-ab64-b30bf9ff7b22, force=3Dfalse, =
secondsToWait=3D0,
gracefully=3Dfalse), log id: 1269b196
2012-01-26 16:01:45,997 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand]
(QuartzScheduler_Worker-89) FINISH, DestroyVDSCommand, log id: 1269b196
p012-01-26 16:01:46,020 INFO
[org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo]
(QuartzScheduler_Worker-89) Running on vds during rerun failed vm: null
2012-01-26 16:01:46,028 INFO
[org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo]
(QuartzScheduler_Worker-89) vm winxp running in db and not running in
vds - add to rerun treatment. vds kvmsrv03
2012-01-26 16:01:46,042 ERROR
[org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo]
(QuartzScheduler_Worker-89) Rerun vm
6c84897b-4d2b-461b-ab64-b30bf9ff7b22. Called from vds kvmsrv03
=20
On the EL node in libvirt.log in the <os> </os>section we see:
*unnecessary output surpressed*
<os>
<type arch=3D"x86_64"
machine=3D"pc-0.14">hvm</type>
<boot dev=3D"cdrom"/>
<boot dev=3D"hd"/>
<smbios mode=3D"sysinfo"/>
</os>
, flags=3D0
16:25:42.074: 10537: error : virNetClientProgramDispatchError:170 :
internal error process exited while connecting to monitor: Supported
machines are:
pc RHEL 6.2.0 PC (alias of rhel6.2.0)
rhel6.2.0 RHEL 6.2.0 PC (default)
rhel6.1.0 RHEL 6.1.0 PC
rhel6.0.0 RHEL 6.0.0 PC
rhel5.5.0 RHEL 5.5.0 PC
rhel5.4.4 RHEL 5.4.4 PC
rhel5.4.0 RHEL 5.4.0 PC
=20
Thus output of qemu-kvm on the EL node is:
[root@kvmsrv03 ~]# /usr/libexec/qemu-kvm -M ?
Supported machines are:
pc RHEL 6.2.0 PC (alias of rhel6.2.0)
rhel6.2.0 RHEL 6.2.0 PC (default)
rhel6.1.0 RHEL 6.1.0 PC
rhel6.0.0 RHEL 6.0.0 PC
rhel5.5.0 RHEL 5.5.0 PC
rhel5.4.4 RHEL 5.4.4 PC
rhel5.4.0 RHEL 5.4.0 PC
=20
And the output on a Fedora 16 node is:
[root@vmdev ~]# qemu-kvm -M ?
Supported machines are:
pc Standard PC (alias of pc-0.14)
pc-0.14 Standard PC (default)
fedora-13 Standard PC
pc-0.13 Standard PC
pc-0.12 Standard PC
pc-0.11 Standard PC, qemu 0.11
pc-0.10 Standard PC, qemu 0.10
isapc ISA-only PC
=20
Thus it appears that ovirt-engine is passing an un-recognized =
"machine=3D"
type when running on an EL node.
=20
- Chris
------_=_NextPart_001_01CCDC7C.033AF09A
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>The ovirt =
engine is failing to start virtual machines on EL based =
nodes.<o:p></o:p></p><p class=3DMsoNormal>I think I have found the =
failure mode.<o:p></o:p></p><p class=3DMsoNormal>The engine log =
shows:<o:p></o:p></p><p class=3DMsoNormal>2012-01-26 16:01:45,200 =
INFO [org.ovirt.engine.core.vdsbroker.CreateVmVDSCommand] =
(pool-5-thread-48) FINISH, CreateVmVDSCommand, return: WaitForLaunch, =
log id: d1649a2<o:p></o:p></p><p class=3DMsoNormal>2012-01-26 =
16:01:45,953 INFO =
[org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] =
(QuartzScheduler_Worker-89) START, DestroyVDSCommand(vdsId =3D =
e7df9be0-47a0-11e1-80f3-00144f8d7c32, =
vmId=3D6c84897b-4d2b-461b-ab64-b30bf9ff7b22, force=3Dfalse, =
secondsToWait=3D0, gracefully=3Dfalse), log id: =
1269b196<o:p></o:p></p><p class=3DMsoNormal>2012-01-26 16:01:45,997 =
INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] =
(QuartzScheduler_Worker-89) FINISH, DestroyVDSCommand, log id: =
1269b196<o:p></o:p></p><p class=3DMsoNormal>p012-01-26 16:01:46,020 =
INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] =
(QuartzScheduler_Worker-89) Running on vds during rerun failed vm: =
null<o:p></o:p></p><p class=3DMsoNormal>2012-01-26 16:01:46,028 =
INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] =
(QuartzScheduler_Worker-89) vm winxp running in db and not running in =
vds - add to rerun treatment. vds kvmsrv03<o:p></o:p></p><p =
class=3DMsoNormal>2012-01-26 16:01:46,042 ERROR =
[org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] =
(QuartzScheduler_Worker-89) Rerun vm =
6c84897b-4d2b-461b-ab64-b30bf9ff7b22. Called from vds =
kvmsrv03<o:p></o:p></p><p class=3DMsoNormal><o:p> </o:p></p><p =
class=3DMsoNormal>On the EL node in libvirt.log in the <os> =
</os>section we see:<o:p></o:p></p><p =
class=3DMsoNormal>*<b>unnecessary output =
surpressed</b>*<o:p></o:p></p><p =
class=3DMsoNormal> &=
nbsp; <os><o:p></o:p></p><p =
class=3DMsoNormal> &=
nbsp; &n=
bsp; <type =
arch=3D"x86_64" =
machine=3D"pc-0.14">hvm</type><o:p></o:p></p><p =
class=3DMsoNormal> &=
nbsp; &n=
bsp; <boot =
dev=3D"cdrom"/><o:p></o:p></p><p =
class=3DMsoNormal> &=
nbsp; &n=
bsp; <boot =
dev=3D"hd"/><o:p></o:p></p><p =
class=3DMsoNormal> &=
nbsp; &n=
bsp; <smbios =
mode=3D"sysinfo"/><o:p></o:p></p><p =
class=3DMsoNormal> &=
nbsp; </os><o:p></o:p></p><p =
class=3DMsoNormal>, flags=3D0<o:p></o:p></p><p =
class=3DMsoNormal>16:25:42.074: 10537: error : =
virNetClientProgramDispatchError:170 : internal error process exited =
while connecting to monitor: Supported machines are:<o:p></o:p></p><p =
class=3DMsoNormal>pc =
RHEL 6.2.0 PC (alias of rhel6.2.0)<o:p></o:p></p><p =
class=3DMsoNormal>rhel6.2.0 RHEL 6.2.0 PC =
(default)<o:p></o:p></p><p class=3DMsoNormal>rhel6.1.0 RHEL 6.1.0 =
PC<o:p></o:p></p><p class=3DMsoNormal>rhel6.0.0 RHEL 6.0.0 =
PC<o:p></o:p></p><p class=3DMsoNormal>rhel5.5.0 RHEL 5.5.0 =
PC<o:p></o:p></p><p class=3DMsoNormal>rhel5.4.4 RHEL 5.4.4 =
PC<o:p></o:p></p><p class=3DMsoNormal>rhel5.4.0 RHEL 5.4.0 =
PC<o:p></o:p></p><p class=3DMsoNormal><o:p> </o:p></p><p =
class=3DMsoNormal>Thus output of qemu-kvm on the EL node =
is:<o:p></o:p></p><p class=3DMsoNormal>[root@kvmsrv03 ~]# =
/usr/libexec/qemu-kvm -M ?<o:p></o:p></p><p class=3DMsoNormal>Supported =
machines are:<o:p></o:p></p><p =
class=3DMsoNormal>pc =
RHEL 6.2.0 PC (alias of rhel6.2.0)<o:p></o:p></p><p =
class=3DMsoNormal>rhel6.2.0 RHEL 6.2.0 PC =
(default)<o:p></o:p></p><p class=3DMsoNormal>rhel6.1.0 RHEL 6.1.0 =
PC<o:p></o:p></p><p class=3DMsoNormal>rhel6.0.0 RHEL 6.0.0 =
PC<o:p></o:p></p><p class=3DMsoNormal>rhel5.5.0 RHEL 5.5.0 =
PC<o:p></o:p></p><p class=3DMsoNormal>rhel5.4.4 RHEL 5.4.4 =
PC<o:p></o:p></p><p class=3DMsoNormal>rhel5.4.0 RHEL 5.4.0 =
PC<o:p></o:p></p><p class=3DMsoNormal><o:p> </o:p></p><p =
class=3DMsoNormal>And the output on a Fedora 16 node =
is:<o:p></o:p></p><p class=3DMsoNormal>[root@vmdev ~]# qemu-kvm -M =
?<o:p></o:p></p><p class=3DMsoNormal>Supported machines =
are:<o:p></o:p></p><p =
class=3DMsoNormal>pc =
Standard PC (alias of pc-0.14)<o:p></o:p></p><p =
class=3DMsoNormal>pc-0.14 Standard PC =
(default)<o:p></o:p></p><p class=3DMsoNormal>fedora-13 Standard =
PC<o:p></o:p></p><p class=3DMsoNormal>pc-0.13 Standard =
PC<o:p></o:p></p><p class=3DMsoNormal>pc-0.12 Standard =
PC<o:p></o:p></p><p class=3DMsoNormal>pc-0.11 Standard =
PC, qemu 0.11<o:p></o:p></p><p =
class=3DMsoNormal>pc-0.10 Standard PC, qemu =
0.10<o:p></o:p></p><p =
class=3DMsoNormal>isapc ISA-only =
PC<o:p></o:p></p><p class=3DMsoNormal><o:p> </o:p></p><p =
class=3DMsoNormal>Thus it appears that ovirt-engine is passing an =
un-recognized "machine=3D" type when running on an EL =
node.<o:p></o:p></p><p class=3DMsoNormal><o:p> </o:p></p><p =
class=3DMsoNormal>- Chris<o:p></o:p></p></div></body></html>
------_=_NextPart_001_01CCDC7C.033AF09A--