Re: [Users] nested KVM

28 Sep 2012

      This is a multi-part message in MIME format.
--------------010902010807020702030807
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

On 09/27/2012 03:21 PM, ybronhei wrote:
...
On 09/26/2012 04:06 AM, Mark Wu wrote:
...
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_KV... 
. 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>
*
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
I've got error too during definition of nested kvm.
When i run qemu-kvm cpu ? i get: Unable to find x86 CPU definition. do 
you know why? what does this command show?
how do i add your configuration suggestion to my guest cpu?
Here's the output of  "qemu-kvm -cpu ?". It shows us which cpu models 
qemu can emulate.
x86       Opteron_G3
x86       Opteron_G2
x86       Opteron_G1
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]
You can use 'virsh edit' or edit the xml configuration file of the vm to 
specify the cpu model. Just put the cpu definition into the root 
(domain) tag.
<domain type='kvm'>
<cpu mode='custom' match='exact'>
<model fallback='allow'>core2duo</model>
<feature policy='require' name='vmx'/>
</cpu>

After that, you should be able to see it in the output of 'virsh 
dumpxml'.  And the cpuinfo from guest should read like this:

#cat /proc/cpuinfo
processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 15
model name    : Intel(R) Core(TM)2 Duo CPU     T7700  @ 2.40GHz
...
-- 
Yaniv Bronhaim.
RedHat, Israel
09-7692289
054-7744187
--------------010902010807020702030807
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/27/2012 03:21 PM, ybronhei wrote:
    <blockquote cite="mid:5063FE67.1080101@redhat.com" type="cite">
      <meta content="text/html; charset=ISO-8859-1"
        http-equiv="Content-Type">
      <div class="moz-cite-prefix">On 09/26/2012 04:06 AM, Mark Wu
        wrote:<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_guest_-_Nested_KVM">http://wiki.ovirt.org/wiki/Vdsm_Developers#Running_Node_as_guest_-_Nested_KVM</a>
          . 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>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
Users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a>
</pre>
      </blockquote>
      I've got error too during definition of nested kvm.<br>
      <br>
      When i run qemu-kvm cpu ? i get: Unable to find x86 CPU
      definition. do you know why? what does this command show?<br>
      <br>
      how do i add your configuration suggestion to my guest cpu?<br>
    </blockquote>
    Here's the output of  "qemu-kvm -cpu ?". It shows us which cpu
    models qemu can emulate.<br>
    x86       Opteron_G3<br>
    x86       Opteron_G2<br>
    x86       Opteron_G1<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>
    You can use 'virsh edit' or edit the xml configuration file of the
    vm to specify the cpu model. Just put the cpu definition into the
    root (domain) tag. <br>
    <domain type='kvm'><br>
      <cpu mode='custom' match='exact'><br>
        <model fallback='allow'>core2duo</model><br>
        <feature policy='require' name='vmx'/><br>
      </cpu><br>
    <br>
    After that, you should be able to see it in the output of 'virsh
    dumpxml'.  And the cpuinfo from guest should read like this:<br>
    <br>
    #cat /proc/cpuinfo <br>
    processor    : 0<br>
    vendor_id    : GenuineIntel<br>
    cpu family    : 6<br>
    model        : 15<br>
    model name    : Intel(R) Core(TM)2 Duo CPU     T7700  @ 2.40GHz
    <blockquote cite="mid:5063FE67.1080101@redhat.com" type="cite"> <br>
      <pre class="moz-signature" cols="72">-- 
Yaniv Bronhaim.
RedHat, Israel 
09-7692289
054-7744187</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------010902010807020702030807--

Mark Wu

tags

participants (1)