12:25 p.m.
This is a multi-part message in MIME format.
--------------080901070606020804050005
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Hi,
Thanks for your answer. everything is all right now, I've managed to
resolve the issue thanks to your suggestion.
This is what I've done:
1. I recall that my processor is a Westmere one
2. first on the hypervisor :
[root@node ~]# qemu-kvm -version
QEMU emulator version 1.0.1 (qemu-kvm-devel), Copyright (c)
2003-2008 Fabrice Bellard
this qemu-kvm release is the one from the F17 update repository
3. still on the hypervisor
[root@node ~]# qemu-kvm -cpu ?
x86 Opteron_G3
x86 Opteron_G2
x86 Opteron_G1
x86 SandyBridge
x86 Nehalem
x86 Penryn
x86 Conroe
x86 [n270]
x86 [athlon]
x86 [pentium3]
x86 [pentium2]
x86 [pentium]
x86 [486]
x86 [coreduo]
x86 [kvm32]
x86 [qemu32]
x86 [kvm64]
x86 [core2duo]
x86 [phenom]
x86 [qemu64]
So we can see there that no Westmere or neither Opteron_G4 is
supported by 1.0.1 qemu-kvm. the consequence is this message on the
hypervisor logs : "Preferred CPU model Westmere not allowed by
hypervisor; closest supported model will be used"
4. when doing "ps aux | grep enable-kvm", we see the -cpu flag being
kvm64, a generic kvm processor. But none of the proposed item into
the "CPU name" cluster field matches with "kvm64", that's the
reason
why it's impossible there to run a nested KVM. A kvm64 item should
successfully launch the vm, but it will never be implemented into
the ovirt webadmin because nested KVM is only for testing purpose
(and vm performances are very bad !)
5. So what doing when we have a Westmere processor type and a F17 so as
to successfully run a nested kvm???? upgrading to qemu 1.2 thanks to
the virt preview repository
(http://fedoraproject.org/wiki/Virtualization_Preview_Repository)
now running qemu-kvm -cpu ? gives :
[root@node ~]# qemu-kvm -cpu ?
x86 Opteron_G4
x86 Opteron_G3
x86 Opteron_G2
x86 Opteron_G1
x86 SandyBridge
x86 Westmere
x86 Nehalem
x86 Penryn
x86 Conroe
x86 [n270]
x86 [athlon]
x86 [pentium3]
x86 [pentium2]
x86 [pentium]
x86 [486]
x86 [coreduo]
x86 [kvm32]
x86 [qemu32]
x86 [kvm64]
x86 [core2duo]
x86 [phenom]
x86 [qemu64]
Now when running the hypervisor with the Westmere cpu flag is
successfull and the kvm64 flag is not used anymore. Then, chosing
the Westmere Family into the CPU family cluster field will launch
the nested vm with the right Westmere flag !
Obviously, qemu-kvm 1.2 will be included by default into F18 and all of
this will be deprecated but waiting for, upgrading the qemu version can
be very useful having a running test environnment with many virtual
hypervisor when the hardware is a Wetmere family one.
Le 26/09/2012 04:06, Mark Wu a écrit :
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>
*
--
Nathanaël Blanchet
Supervision réseau
Pôle exploitation et maintenance
Département des systèmes d'information
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14
blanchet(a)abes.fr
--------------080901070606020804050005
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">
Hi,<br>
<br>
Thanks for your answer. everything is all right now, I've managed to
resolve the issue thanks to your suggestion. <br>
This is what I've done:<br>
<ol>
<li>I recall that my processor is a Westmere one<br>
</li>
<li>first on the hypervisor :<br>
[root@node ~]# qemu-kvm -version<br>
QEMU emulator version 1.0.1 (qemu-kvm-devel), Copyright (c)
2003-2008 Fabrice Bellard<br>
<br>
this qemu-kvm release is the one from the F17 update repository<br>
<br>
</li>
<li>still on the hypervisor<br>
[root@node ~]# qemu-kvm -cpu ?<br>
x86
Opteron_G3<br>
x86
Opteron_G2<br>
x86
Opteron_G1<br>
x86 SandyBridge<br>
x86
Nehalem<br>
x86
Penryn<br>
x86
Conroe<br>
x86
[n270]<br>
x86
[athlon]<br>
x86
[pentium3]<br>
x86
[pentium2]<br>
x86
[pentium]<br>
x86
[486]<br>
x86
[coreduo]<br>
x86
[kvm32]<br>
x86
[qemu32]<br>
x86
[kvm64]<br>
x86
[core2duo]<br>
x86
[phenom]<br>
x86
[qemu64]<br>
<br>
<br>
<br>
So we can see there that no Westmere or neither Opteron_G4 is
supported by 1.0.1 qemu-kvm. the consequence is this message on
the hypervisor logs : "Preferred CPU model Westmere not allowed
by hypervisor; closest supported model will be used"<br>
<br>
</li>
<li>when doing "ps aux | grep enable-kvm", we see the -cpu flag
being kvm64, a generic kvm processor. But none of the proposed
item into the "CPU name" cluster field matches with "kvm64",
that's the reason why it's impossible there to run a nested KVM.
A kvm64 item should successfully launch the vm, but it will
never be implemented into the ovirt webadmin because nested KVM
is only for testing purpose (and vm performances are very bad !)<br>
<br>
</li>
<li>So what doing when we have a Westmere processor type and a F17
so as to successfully run a nested kvm???? upgrading to qemu 1.2
thanks to the virt preview repository
(<a class="moz-txt-link-freetext"
href="http://fedoraproject.org/wiki/Virtualization_Preview_Repositor...>)
now running qemu-kvm -cpu ? gives :<br>
[root@node ~]# qemu-kvm -cpu ?<br>
x86
Opteron_G4<br>
x86
Opteron_G3<br>
x86
Opteron_G2<br>
x86
Opteron_G1<br>
x86 SandyBridge<br>
x86
Westmere<br>
x86
Nehalem<br>
x86
Penryn<br>
x86
Conroe<br>
x86
[n270]<br>
x86
[athlon]<br>
x86
[pentium3]<br>
x86
[pentium2]<br>
x86
[pentium]<br>
x86
[486]<br>
x86
[coreduo]<br>
x86
[kvm32]<br>
x86
[qemu32]<br>
x86
[kvm64]<br>
x86
[core2duo]<br>
x86
[phenom]<br>
x86
[qemu64]<br>
<br>
Now when running the hypervisor with the Westmere cpu flag is
successfull and the kvm64 flag is not used anymore. Then,
chosing the Westmere Family into the CPU family cluster field
will launch the nested vm with the right Westmere flag !</li>
</ol>
<p>Obviously, qemu-kvm 1.2 will be included by default into F18 and
all of this will be deprecated but waiting for, upgrading the qemu
version can be very useful having a running test environnment with
many virtual hypervisor when the hardware is a Wetmere family one.<br>
</p>
<div class="moz-cite-prefix">Le 26/09/2012 04:06, Mark Wu a
écrit :<br>
</div>
<blockquote cite="mid:50626322.6020307@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
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 moz-do-not-send="true"
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>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Nathanaël Blanchet
Supervision réseau
Pôle exploitation et maintenance
Département des systèmes d'information
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14
<a class="moz-txt-link-abbreviated"
href="mailto:blanchet@abes.fr">blanchet@abes.fr</a> </pre>
</body>
</html>
--------------080901070606020804050005--