9:06 p.m.
This is a multi-part message in MIME format.
--------------030304070801080603090502
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
On 09/26/2012 12:58 AM, Nathanaël Blanchet wrote:
Hello,
I've tried many times to run a node as a guest in ovirt following
http://wiki.ovirt.org/wiki/Vdsm_Developers#Running_Node_as_guest_-_Nested...
. The result is that I'm able to register such a host in engine, but
it is impossible to start any vm on it. If I boot on an ISO, I can see
the first prompt and move between the items. But since I begin the
installation I have a blank screen and the vm goes into pause mode in
vit-manager. Then I have no way else than rebooting the hypervisor
guest because it is impossible to resume. When I get logs on the real
host, I can find this :
arning : x86Decode:1306 : Preferred CPU model Westmere not allowed by
hypervisor; closest supported model will be used
Sep 25 17:11:59 khamsin libvirtd[23053]: 2012-09-25 15:11:59.384+0000:
23054: warning : x86Decode:1306 : Preferred CPU model Westmere not
allowed by hypervisor; closest supported model will be used
Sep 25 17:12:19 khamsin libvirtd[23053]: 2012-09-25 15:12:19.150+0000:
23055: warning : x86Decode:1306 : Preferred CPU model Westmere not
allowed by hypervisor; closest supported model will be used
Sep 25 17:45:48 khamsin libvirtd[23053]: 2012-09-25 15:45:48.342+0000:
23058: warning : x86Decode:1306 : Preferred CPU model Westmere not
allowed by hypervisor; closest supported model will be used
Sep 25 18:07:05 khamsin libvirtd[23053]: 2012-09-25 16:07:05.834+0000:
23058: warning : x86Decode:1306 : Preferred CPU model Nehalem not
allowed by hypervisor; closest supported model will be used
Sep 25 18:44:47 khamsin libvirtd[23053]: 2012-09-25 16:44:47.340+0000:
23057: warning : x86Decode:1306 : Preferred CPU model Penryn not
allowed by hypervisor; closest supported model will be used
As you can see, I have tried many cpu type for launching this guest
hypervisor, but none of them is accepted by the hypervisor. Plus, I've
modified each time the family type in the cluster tab, but it is the
same.
On the hist:
#virsh capabilities gives
<cpu>
<arch>x86_64</arch>
<model>Westmere</model>
<vendor>Intel</vendor>
Thanks for your help
What does the command 'qemu-kvm -cpu ?' give ? Could you please try
the following guest cpu definition?
*
<cpu match='exact'>
<model>core2duo</model>
<feature policy='require' name='vmx'/>
</cpu>
*
--------------030304070801080603090502
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 09/26/2012 12:58 AM, Nathanaël Blanchet wrote:
<blockquote cite="mid:5061E2C1.2060800@abes.fr"
type="cite">Hello,
<br>
<br>
I've tried many times to run a node as a guest in ovirt following
<a class="moz-txt-link-freetext"
href="http://wiki.ovirt.org/wiki/Vdsm_Developers#Running_Node_as_gue...
. The result is that I'm able to register such a host in engine,
but it is impossible to start any vm on it. If I boot on an ISO, I
can see the first prompt and move between the items. But since I
begin the installation I have a blank screen and the vm goes into
pause mode in vit-manager. Then I have no way else than rebooting
the hypervisor guest because it is impossible to resume. When I
get logs on the real host, I can find this :
<br>
arning : x86Decode:1306 : Preferred CPU model Westmere not allowed
by hypervisor; closest supported model will be used
<br>
Sep 25 17:11:59 khamsin libvirtd[23053]: 2012-09-25
15:11:59.384+0000: 23054: warning : x86Decode:1306 : Preferred CPU
model Westmere not allowed by hypervisor; closest supported model
will be used
<br>
Sep 25 17:12:19 khamsin libvirtd[23053]: 2012-09-25
15:12:19.150+0000: 23055: warning : x86Decode:1306 : Preferred CPU
model Westmere not allowed by hypervisor; closest supported model
will be used
<br>
Sep 25 17:45:48 khamsin libvirtd[23053]: 2012-09-25
15:45:48.342+0000: 23058: warning : x86Decode:1306 : Preferred CPU
model Westmere not allowed by hypervisor; closest supported model
will be used
<br>
Sep 25 18:07:05 khamsin libvirtd[23053]: 2012-09-25
16:07:05.834+0000: 23058: warning : x86Decode:1306 : Preferred CPU
model Nehalem not allowed by hypervisor; closest supported model
will be used
<br>
Sep 25 18:44:47 khamsin libvirtd[23053]: 2012-09-25
16:44:47.340+0000: 23057: warning : x86Decode:1306 : Preferred CPU
model Penryn not allowed by hypervisor; closest supported model
will be used
<br>
<br>
As you can see, I have tried many cpu type for launching this
guest hypervisor, but none of them is accepted by the hypervisor.
Plus, I've modified each time the family type in the cluster tab,
but it is the same.
<br>
On the hist:
<br>
#virsh capabilities gives
<br>
<cpu>
<br>
<arch>x86_64</arch>
<br>
<model>Westmere</model>
<br>
<vendor>Intel</vendor>
<br>
<br>
Thanks for your help
<br>
</blockquote>
<br>
<br>
What does the command 'qemu-kvm -cpu ?' give ? Could you
please
try the following guest cpu definition?<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<pre style="border: 0px; font-family: 'Courier 10 Pitch', Courier,
monospace; font-size: 13px; font-style: normal; font-weight: normal; margin: 0px 0px
1.625em; outline: 0px; padding: 0.75em 1.625em; vertical-align: baseline;
background-color: rgb(244, 244, 244); font-variant: normal; line-height: 1.5; overflow:
auto; color: rgb(55, 55, 55); letter-spacing: normal; orphans: 2; text-align: start;
text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-position:
initial initial; background-repeat: initial initial;"><strong
style="border: 0px; font-family: inherit; font-size: 13px; font-style: inherit;
font-weight: bold; margin: 0px; outline: 0px; padding: 0px; vertical-align:
baseline;"><tt style="border: 0px; font-family: inherit; font-size: 13px;
font-style: inherit; font-weight: inherit; margin: 0px; outline: 0px; padding: 0px;
vertical-align: baseline;">
<cpu match='exact'>
<model>core2duo</model>
<feature policy='require' name='vmx'/>
</cpu>
</tt></strong></pre>
</body>
</html>
--------------030304070801080603090502--