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

[Brown, Chris (GE Healthcare)]

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20120126/4ac95d72/attachment-0001.html>