<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Is this something that could be turned into a documented "tunable" parameter for those that wish to use EL based distributions as nodes?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>- Chris<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Haim Ateya [mailto:hateya@redhat.com] <br><b>Sent:</b> Friday, January 27, 2012 3:12 AM<br><b>To:</b> Ofer Schreiber<br><b>Cc:</b> Brown, Chris (GE Healthcare); users@ovirt.org<br><b>Subject:</b> Re: [Users] ovirt fails to start vm on EL based nodes<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>On Jan 27, 2012, at 11:01, Ofer Schreiber <<a href="mailto:oschreib@redhat.com">oschreib@redhat.com</a>> wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal>Great debugging. <o:p></o:p></p><p class=MsoNormal>Sounds like the 'EmulatedMachine' (hope that's the right attr) in engine-config is configured for fedora based nodes. <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>Would you mind openning a bug on this?<o:p></o:p></p></div><div><p class=MsoNormal>Although I'm not sure oVirt supports RHEL completely. <o:p></o:p></p></div></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I don't think it's a bug; mean while, you can change 'EmulatedMachine' in vdc_options table from 'pc-0.14' to 'rhel6.2.0', restart Jboss, and it should work.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Ofer. <o:p></o:p></p><div><p class=MsoNormal dir=RTL style='text-align:right;direction:rtl;unicode-bidi:embed'><span dir=LTR><o:p> </o:p></span></p></div></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>On 27 Jan 2012, at 00:44, "Brown, Chris (GE Healthcare)" <<a href="mailto:Christopher.Brown@med.ge.com">Christopher.Brown@med.ge.com</a>> wrote:<span lang=AR-SA dir=RTL><o:p></o:p></span></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>The ovirt engine is failing to start virtual machines on EL based nodes.<o:p></o:p></p><p class=MsoNormal>I think I have found the failure mode.<o:p></o:p></p><p class=MsoNormal>The engine log shows:<o:p></o:p></p><p class=MsoNormal>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=MsoNormal>2012-01-26 16:01:45,953 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (QuartzScheduler_Worker-89) START, DestroyVDSCommand(vdsId = e7df9be0-47a0-11e1-80f3-00144f8d7c32, vmId=6c84897b-4d2b-461b-ab64-b30bf9ff7b22, force=false, secondsToWait=0, gracefully=false), log id: 1269b196<o:p></o:p></p><p class=MsoNormal>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=MsoNormal>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=MsoNormal>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=MsoNormal>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=MsoNormal> <o:p></o:p></p><p class=MsoNormal>On the EL node in libvirt.log in the <os> </os>section we see:<o:p></o:p></p><p class=MsoNormal>*<b>unnecessary output surpressed</b>*<o:p></o:p></p><p class=MsoNormal> <os><o:p></o:p></p><p class=MsoNormal> <type arch="x86_64" machine="pc-0.14">hvm</type><o:p></o:p></p><p class=MsoNormal> <boot dev="cdrom"/><o:p></o:p></p><p class=MsoNormal> <boot dev="hd"/><o:p></o:p></p><p class=MsoNormal> <smbios mode="sysinfo"/><o:p></o:p></p><p class=MsoNormal> </os><o:p></o:p></p><p class=MsoNormal>, flags=0<o:p></o:p></p><p class=MsoNormal>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=MsoNormal>pc RHEL 6.2.0 PC (alias of rhel6.2.0)<o:p></o:p></p><p class=MsoNormal>rhel6.2.0 RHEL 6.2.0 PC (default)<o:p></o:p></p><p class=MsoNormal>rhel6.1.0 RHEL 6.1.0 PC<o:p></o:p></p><p class=MsoNormal>rhel6.0.0 RHEL 6.0.0 PC<o:p></o:p></p><p class=MsoNormal>rhel5.5.0 RHEL 5.5.0 PC<o:p></o:p></p><p class=MsoNormal>rhel5.4.4 RHEL 5.4.4 PC<o:p></o:p></p><p class=MsoNormal>rhel5.4.0 RHEL 5.4.0 PC<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Thus output of qemu-kvm on the EL node is:<o:p></o:p></p><p class=MsoNormal>[root@kvmsrv03 ~]# /usr/libexec/qemu-kvm -M ?<o:p></o:p></p><p class=MsoNormal>Supported machines are:<o:p></o:p></p><p class=MsoNormal>pc RHEL 6.2.0 PC (alias of rhel6.2.0)<o:p></o:p></p><p class=MsoNormal>rhel6.2.0 RHEL 6.2.0 PC (default)<o:p></o:p></p><p class=MsoNormal>rhel6.1.0 RHEL 6.1.0 PC<o:p></o:p></p><p class=MsoNormal>rhel6.0.0 RHEL 6.0.0 PC<o:p></o:p></p><p class=MsoNormal>rhel5.5.0 RHEL 5.5.0 PC<o:p></o:p></p><p class=MsoNormal>rhel5.4.4 RHEL 5.4.4 PC<o:p></o:p></p><p class=MsoNormal>rhel5.4.0 RHEL 5.4.0 PC<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>And the output on a Fedora 16 node is:<o:p></o:p></p><p class=MsoNormal>[root@vmdev ~]# qemu-kvm -M ?<o:p></o:p></p><p class=MsoNormal>Supported machines are:<o:p></o:p></p><p class=MsoNormal>pc Standard PC (alias of pc-0.14)<o:p></o:p></p><p class=MsoNormal>pc-0.14 Standard PC (default)<o:p></o:p></p><p class=MsoNormal>fedora-13 Standard PC<o:p></o:p></p><p class=MsoNormal>pc-0.13 Standard PC<o:p></o:p></p><p class=MsoNormal>pc-0.12 Standard PC<o:p></o:p></p><p class=MsoNormal>pc-0.11 Standard PC, qemu 0.11<o:p></o:p></p><p class=MsoNormal>pc-0.10 Standard PC, qemu 0.10<o:p></o:p></p><p class=MsoNormal>isapc ISA-only PC<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Thus it appears that ovirt-engine is passing an un-recognized "machine=" type when running on an EL node.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>- Chris<o:p></o:p></p></div></blockquote><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br><a href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a><o:p></o:p></span></p></div></blockquote></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br><a href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a><o:p></o:p></span></p></div></blockquote></div></body></html>