[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Host does not support virtualization type 'xen'



Hi Steve,

what do you mean by qemu-kvm? Do you mean I need to run a command "qemu-kvm -cpu"?
But it says the command couldn't be found. I am a newbie of Xen, so please correct me if I misunderstood something.

Here is the result from virsh capabilities:

# virsh capabilities
<capabilities>

  <host>
    <cpu>
      <arch>x86_64</arch>
      <features>
        <pae/>
      </features>
    </cpu>
    <power_management>
      <suspend_mem/>
      <suspend_disk/>
    </power_management>
    <migration_features>
      <live/>
      <uri_transports>
        <uri_transport>xenmigr</uri_transport>
      </uri_transports>
    </migration_features>
  </host>

  <guest>
    <os_type>xen</os_type>
    <arch name='x86_64'>
      <wordsize>64</wordsize>
      <emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
      <machine>xenpv</machine>
      <domain type='xen'>
      </domain>
    </arch>
  </guest>

  <guest>
    <os_type>xen</os_type>
    <arch name='i686'>
      <wordsize>32</wordsize>
      <emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
      <machine>xenpv</machine>
      <domain type='xen'>
      </domain>
    </arch>
    <features>
      <pae/>
    </features>
  </guest>

  <guest>
    <os_type>hvm</os_type>
    <arch name='i686'>
      <wordsize>32</wordsize>
      <emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
      <loader>/usr/lib/xen/boot/hvmloader</loader>
      <machine>xenfv</machine>
      <domain type='xen'>
      </domain>
    </arch>
    <features>
      <pae/>
      <nonpae/>
      <acpi default='on' toggle='yes'/>
      <apic default='on' toggle='no'/>
      <hap default='off' toggle='yes'/>
      <viridian default='off' toggle='yes'/>
    </features>
  </guest>

  <guest>
    <os_type>hvm</os_type>
    <arch name='x86_64'>
      <wordsize>64</wordsize>
      <emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
      <loader>/usr/lib/xen/boot/hvmloader</loader>
      <machine>xenfv</machine>
      <domain type='xen'>
      </domain>
    </arch>
    <features>
      <acpi default='on' toggle='yes'/>
      <apic default='on' toggle='no'/>
      <hap default='off' toggle='yes'/>
      <viridian default='off' toggle='yes'/>
    </features>
  </guest>

</capabilities>

Do you think the output is normal?

Thanks,

Su

On Wed, Mar 14, 2012 at 10:11 AM, Steven Timm <timm@xxxxxxxx> wrote:
I think the reason that virt-install doesn't want to do
a paravirtualized install on this machine (virt-install -p)
is because xm info is listing "virt_caps :hvm"
i.e. only hardware virtualization supported.
I am not sure how you would change that.  the version of Xen
I run doesn't list a virt_caps field at all in xm info.
But I am almost positive that if the virt_caps field
is there, virt-install will look at it and not like it.

There are probably the output from some virsh commands you
could do to, such as virsh capabilities.
what does
qemu-kvm -cpu ?
tell you?

Steve Timm





On Tue, 13 Mar 2012, Su Zhang wrote:

Steve,

Here are the outputs:

]# xm info
\host                   : XenTester
release                : 3.1.0-rc9+
version                : #1 SMP Mon Mar 12 18:18:34 CDT 2012
machine                : x86_64
nr_cpus                : 2
nr_nodes               : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 2527
hw_caps                :
bfebfbff:20100800:00000000:00000940:0008e3fd:00000000:00000001:00000000
virt_caps              : hvm
total_memory           : 4026
free_memory            : 1171
free_cpus              : 0
xen_major              : 4
xen_minor              : 1
xen_extra              : .2
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
xen_commandline        :
cc_compiler            : gcc version 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC)
cc_compile_by          : su
cc_compile_domain      : (none)
cc_compile_date        : Mon Mar 12 16:39:43 CDT 2012
xend_config_format     : 4


# cat /proc/cpuinfo
processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 23
model name    : Intel(R) Core(TM)2 Duo CPU     T9400  @ 2.53GHz
stepping    : 6
cpu MHz        : 2527.074
cache size    : 6144 KB
fpu        : yes
fpu_exception    : yes
cpuid level    : 10
wp        : yes
flags        : fpu de tsc msr pae cx8 apic sep cmov pat clflush acpi mmx
fxsr sse sse2 ss ht syscall nx lm constant_tsc nopl aperfmperf pni est ssse3
cx16 sse4_1 hypervisor lahf_lm dts
bogomips    : 5054.14
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:

processor    : 1
vendor_id    : GenuineIntel
cpu family    : 6
model        : 23
model name    : Intel(R) Core(TM)2 Duo CPU     T9400  @ 2.53GHz
stepping    : 6
cpu MHz        : 2527.074
cache size    : 6144 KB
fpu        : yes
fpu_exception    : yes
cpuid level    : 10
wp        : yes
flags        : fpu de tsc msr pae cx8 apic sep cmov pat clflush acpi mmx
fxsr sse sse2 ss ht syscall nx lm constant_tsc nopl aperfmperf pni est ssse3
cx16 sse4_1 hypervisor lahf_lm dts
bogomips    : 5054.14
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:


# uname -a
Linux XenTester 3.1.0-rc9+ #1 SMP Mon Mar 12 18:18:34 CDT 2012 x86_64 x86_64
x86_64 GNU/Linux


How can I check if the libvirtd is correctly configured or if other things
have been misconfigured?

Thanks in advance,

On Tue, Mar 13, 2012 at 10:23 PM, Steven C Timm <timm@xxxxxxxx> wrote:

      

     What’s the output of xm info in dom0, particularly hw_caps and
     xen_caps.

     What’s output of /proc/cpuinfo.

      

     The way you have the system configured, the system doesn’t
     recognize that your system is capable of running paravirtualized
     xen.  This could be a misconfigured libvirtd or wrong version of
     libvirtd tools, or a misconfigured kernel that is not sending
     the right flags to xm info.

      

     Also, what’s uname –a of your kernel in dom0.

      

     Steve Timm

      

      

     From: xen-users-bounces@xxxxxxxxxxorg
     [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Su Zhang
     Sent: Tuesday, March 13, 2012 9:59 PM
     To: xen-users@xxxxxxxxxxxxx
     Subject: [Xen-users] Host does not support virtualization type
     'xen'

      

     Hello Community,

      I successfully installed and run xen (xm list and xm info can
     output appropriately).
      However, while I was installing domU image by using
     virt-install -p at domU OS. I encountered an
     error information" Host does not support virtualization type
     'xen' ".
     I built xen from source. Some of my friends have the same issue,
     but if they use pre-build xen, the issue will go away.
     However, I want to insist in using my version of xen (build from
     source). Does anyone can give any hint about this error?

     I'll appreciate if any suggestions can be given,

     Thanks,

     --
     Su Zhang
     Ph.D Candidate
     Computing and Information Sciences
     Kansas State University




--
Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University



------------------------------------------------------------------
Steven C. Timm, Ph.D  (630) 840-8525
timm@xxxxxxxx  http://home.fnal.gov/~timm/
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Group Leader.
Lead of FermiCloud project.



--
Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.