[Users] ovirt fails to start vm on EL based nodes

Fri Jan 27 13:11:39 EST 2012

Actually this seems to be indicated as a bug here: http://ovirt.org/wiki/Engine_Node_Integration#Engine_core_machine

It is noted under "Additional Configuration" 

--> "These 2 steps are currently required due to bugs, they will be changed/removed once the patches that will fix them will be merged."

--> Change the default emulated VM type by executing:

--> psql -U postgres engine -c "update vdc_options set option_value='pc-0.14' where option_name='EmulatedMachine' and version='3.0';"

If this is the case I can open a bug on it as I searched bugzilla and do not see one open as pertains to this issue.

- Chris

From: Brown, Chris (GE Healthcare) 
Sent: Friday, January 27, 2012 8:47 AM
To: 'Haim Ateya'; Ofer Schreiber
Cc: users at ovirt.org
Subject: RE: [Users] ovirt fails to start vm on EL based nodes

Is this something that could be turned into a documented "tunable" parameter for those that wish to use EL based distributions as nodes?

- Chris

From: Haim Ateya [mailto:hateya at redhat.com] 
Sent: Friday, January 27, 2012 3:12 AM
To: Ofer Schreiber
Cc: Brown, Chris (GE Healthcare); users at ovirt.org
Subject: Re: [Users] ovirt fails to start vm on EL based nodes

On Jan 27, 2012, at 11:01, Ofer Schreiber <oschreib at redhat.com> wrote:

	Great debugging. 

	Sounds like the 'EmulatedMachine' (hope that's the right attr) in engine-config is configured for fedora based nodes. 

	Would you mind openning a bug on this?

	Although I'm not sure oVirt supports RHEL completely. 

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.

Ofer. 

On 27 Jan 2012, at 00:44, "Brown, Chris (GE Healthcare)" <Christopher.Brown at med.ge.com> wrote:

	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 = e7df9be0-47a0-11e1-80f3-00144f8d7c32, vmId=6c84897b-4d2b-461b-ab64-b30bf9ff7b22, force=false, secondsToWait=0, gracefully=false), 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

	On the EL node in libvirt.log in the <os> </os>section we see:

	*unnecessary output surpressed*

	                <os>

	                                <type arch="x86_64" machine="pc-0.14">hvm</type>

	                                <boot dev="cdrom"/>

	                                <boot dev="hd"/>

	                                <smbios mode="sysinfo"/>

	                </os>

	, flags=0

	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

	Thus output of qemu-kvm on the EL node is:

	[root at 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

	And the output on a Fedora 16 node is:

	[root at 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

	Thus it appears that ovirt-engine is passing an un-recognized "machine=" type when running on an EL node.

	- Chris

	_______________________________________________
	Users mailing list
	Users at ovirt.org
	http://lists.ovirt.org/mailman/listinfo/users

	_______________________________________________
	Users mailing list
	Users at ovirt.org
	http://lists.ovirt.org/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20120127/8f638eca/attachment-0002.html>