| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
[Xen-users] Problem with installing/running domU OS on HVM machine
Hi,
I have problem installing or running domU OS (Windows XP or Redhat 7.3).
The machine runs CentOS 4.4 X86_64, Xen-3.0.3. Paravirtual domU works
without problem.
The problem is that when I run command "xm create <config>", nothing
would happen. hvmloader does not seem get started at all. I've tried
installing both 64bit and 32bit vnc, sdl but did not see any difference.
Anything special about installing domU over X86_64 dom0?
Simon
======================================================================
$ xm info
host : vms.domain.com
release : 2.6.16.29-xen0
version : #2 SMP Fri Nov 3 11:31:44 PST 2006
machine : x86_64
nr_cpus : 2
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 2004
hw_caps :
178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f
total_memory : 2046
free_memory : 720
xen_major : 3
xen_minor : 0
xen_extra : .3-0
xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p
hvm-3.0-x86_64
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
cc_compiler : gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)
cc_compile_by : root
cc_compile_domain : domain.com
cc_compile_date : Fri Nov 3 11:36:51 PST 2006
xend_config_format : 2
=======================================================================
$ xm dmesg
__ __ _____ ___ _____ ___
\ \/ /___ _ __ |___ / / _ \ |___ / / _ \
\ // _ \ '_ \ |_ \| | | | |_ \ __| | | |
/ \ __/ | | | ___) | |_| | ___) |__| |_| |
/_/\_\___|_| |_| |____(_)___(_)____/ \___/
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.0.3-0 (root@xxxxxxxxxxxxxxx) (gcc version 3.4.6 20060404
(Red Hat 3.4.6-3)) Fri Nov 3 11:36:51 PST 2006
Latest ChangeSet: unavailable
(XEN) Command line: /xen.gz dom0_mem=1024M
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009f000 (usable)
(XEN) 000000000009f000 - 00000000000a0000 (reserved)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000007fee0000 (usable)
(XEN) 000000007fee0000 - 000000007fee3000 (ACPI NVS)
(XEN) 000000007fee3000 - 000000007fef0000 (ACPI data)
(XEN) 000000007fef0000 - 000000007ff00000 (reserved)
(XEN) 00000000f0000000 - 00000000f4000000 (reserved)
(XEN) 00000000fec00000 - 0000000100000000 (reserved)
(XEN) System RAM: 2046MB (2095612kB)
(XEN) Xen heap: 14MB (14420kB)
(XEN) found SMP MP-table at 000f3cb0
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 DELL ) @
0x00000000000f83c0
(XEN) ACPI: RSDT (v001 DELL bMk 0x42302e31 AWRD 0x00000000) @
0x000000007fee3040
(XEN) ACPI: FADT (v001 DELL bMk 0x42302e31 AWRD 0x00000000) @
0x000000007fee3100
(XEN) ACPI: BOOT (v001 DELL bMk 0x42302e31 AWRD 0x00000000) @
0x000000007fee8b40
(XEN) ACPI: SSDT (v001 PTLTD POWERNOW 0x00000001 LTP 0x00000001) @
0x000000007fee8c80
(XEN) ACPI: HPET (v001 DELL bMk 0x42302e31 AWRD 0x00000098) @
0x000000007fee8ec0
(XEN) ACPI: MCFG (v001 DELL bMk 0x42302e31 AWRD 0x00000000) @
0x000000007fee8f40
(XEN) ACPI: SLIC (v001 DELL bMk 0x42302e31 AWRD 0x0100000e) @
0x000000007fee8fc0
(XEN) ACPI: MADT (v001 DELL bMk 0x42302e31 AWRD 0x00000000) @
0x000000007fee8bc0
(XEN) ACPI: DSDT (v001 DELL AWRDACPI 0x00001000 MSFT 0x0100000e) @
0x0000000000000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 15:11 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
(XEN) Processor #1 15:11 APIC version 16
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
(XEN) ACPI: IRQ9 used by override.
(XEN) ACPI: IRQ14 used by override.
(XEN) ACPI: IRQ15 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x10b9a201 base: 0xfed00000
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2004.216 MHz processor.
(XEN) CPU0: AMD Flush Filter disabled
(XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
(XEN) CPU: L2 Cache: 512K (64 bytes/line)
(XEN) CPU 0(2) -> Core 0
(XEN) AMD SVM Extension is enabled for cpu 0.
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU1: AMD Flush Filter disabled
(XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
(XEN) CPU: L2 Cache: 512K (64 bytes/line)
(XEN) CPU 1(2) -> Core 1
(XEN) AMD: Disabling C1 Clock Ramping Node #0
(XEN) AMD SVM Extension is enabled for cpu 1.
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=0 apic2=-1 pin2=-1
(XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
(XEN) ...trying to set up timer (IRQ0) through the 8259A ... failed.
(XEN) ...trying to set up timer as Virtual Wire IRQ... failed.
(XEN) ...trying to set up timer as ExtINT IRQ...spurious 8259A
interrupt: IRQ7.
(XEN) works.
(XEN) checking TSC synchronization across 2 CPUs:
(XEN) CPU#0 had 881 usecs TSC skew, fixed it up.
(XEN) CPU#1 had -881 usecs TSC skew, fixed it up.
(XEN) BAD HPET period 4294967295.
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 2 CPUs
(XEN) Machine check exception polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Domain 0 kernel supports features = { 0000001f }.
(XEN) Domain 0 kernel requires features = { 00000000 }.
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000003000000->0000000004000000 (258048 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff80100000->ffffffff80590648
(XEN) Init. ramdisk: ffffffff80591000->ffffffff8075c800
(XEN) Phys-Mach map: ffffffff8075d000->ffffffff8095d000
(XEN) Start info: ffffffff8095d000->ffffffff8095d49c
(XEN) Page tables: ffffffff8095e000->ffffffff80967000
(XEN) Boot stack: ffffffff80967000->ffffffff80968000
(XEN) TOTAL: ffffffff80000000->ffffffff80c00000
(XEN) ENTRY ADDRESS: ffffffff80100000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Initrd len 0x1cb800, start at 0xffffffff80591000
(XEN) Scrubbing Free RAM: .....................done.
(XEN) Xen trace buffers: disabled
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen).
===========================================================================
$ cat /etc/xen/win.hvm
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 512
name = "winxp"
vif = [ 'type=ioemu, bridge=xenbr0' ]
disk = [ 'file:/xvms/winxp.img,ioemu:hda,w',
'file:/xvms/iso/winxp.iso,hdc:cdrom,r' ]
on_poweroff = 'destroy'
on_reboot = 'destroy'
on_crash = 'destroy'
device_model = '/usr/lib/xen/bin/qemu-dm'
boot='d'
sdl=1
vnc=0
vncviewer=0
=============================================================================
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
| <Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-users] Problem with installing/running domU OS on HVM machine,
Simon Gao <=
|
|
|
| |
|
Home