Bug 234783

Summary: virt-manager (perhaps xen itself?) doesn't allow HVM guest
Product: [Fedora] Fedora Reporter: Andy Burns <fedora>
Component: virt-managerAssignee: Daniel Berrangé <berrange>
Status: CLOSED NOTABUG QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-04-01 23:22:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andy Burns 2007-04-01 22:55:33 UTC
Description of problem:

Intel S5000PAL motherboard, latest firmware, virtualisation is enabled in BIOS,
virt-manager prevents creation on fully virtual domU.

Version-Release number of selected component (if applicable):

F7t3

How reproducible:

100%

Steps to Reproduce:
1. install F7t3 in dom0
2. attempt to install XP in domU with virt-manager
3.
  
Actual results:

Only paravirtual guests available

Expected results:

Choice of paravirtual or HVM guests

Additional info:

Snippets from various commands

# cat /proc/cpuinfo

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Xeon(R) CPU            5110  @ 1.60GHz
stepping        : 6
cpu MHz         : 1595.964
cache size      : 4096 KB
flags           : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush
dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor
ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm

# xm dmesg

(XEN) Initializing CPU#0
(XEN) Detected 1595.964 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX disabled by Feature Control MSR.
(XEN) CPU0: Intel(R) Xeon(R) CPU            5110  @ 1.60GHz stepping 06
(XEN) Mapping cpu 0 to node 255
(XEN) Booting processor 1/6 eip 90000

(XEN) *** LOADING DOMAIN 0 ***
(XEN) Domain 0 kernel supports features = { 0000001f }.
(XEN) Domain 0 kernel requires features = { 00000000 }.

Comment 1 Andy Burns 2007-04-01 22:59:26 UTC
Running virt-manager again I notice that it displays a red warning triangle with
the message that "The host CPUs do support virtualization, but it it isn't
enabled in the BIOS"

Originally virtualuzation /was/ disabled in BIOS, but now it /is/ enabled, just
about to power-cycle machine to make sure.

Comment 2 Andy Burns 2007-04-01 23:22:40 UTC
It seems the host machine needs a power-cycle, rather than just rebooting after
exiting BIOS setup for the virtualization change to take effect, sorry for the
noise.