WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] Problem with windows domU

To: "Jorhe Blackknee" <jblackknee@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Problem with windows domU
From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Date: Wed, 29 Nov 2006 16:35:38 +0100
Delivery-date: Wed, 29 Nov 2006 07:36:41 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <50ca6c890611290728y3064428cs9d6a46f64a2b4764@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccTy3YgOylkBb6HSZSNz//vND4O+wAAC5tA
Thread-topic: [Xen-users] Problem with windows domU
> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Jorhe Blackknee
> Sent: 29 November 2006 15:29
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] Problem with windows domU
> 
> Hi,
> 
> I have installed xen 3.0.3 on gentoo 2006.1
> The machine is  a laptop with amd turion x2 ML-60.
> I can boot into xen, xend stars normally.
> Creation of linux domU is successfull but I can't
> create a windows domU. When I try to create it
> no error message appears, and it is shown on the
> xm list domains, but without any status.
> 
> The configuration file is:
> 
> kernel = "/usr/lib64/xen/boot/hvmloader"

Do you HAVE a hvmloader in this location? Is it an executable?

Do you have a qemu device model in the location listed below?

What's in /var/log/xen/qemu-*.log files?

You probably don't want the "cdrom=" line below (won't fix anything, but
it's "old style" cdrom configuration, and you're correctly using the NEW
style in the "disk=" line, so you can remove the surplus line and reduce
confusion for the future...)

--
Mats
> builder='hvm'
> memory = 512
> name = "winxp"
> disk = [ 'file:/xen-images/windows/winxp.img,ioemu:hda,w',
> 'file:/xen-images/windows/vista.iso,ioemu:hdc:cdrom,r' ]
> device_model = '/usr/lib64/xen/bin/qemu-dm'
> boot="d"
> cdrom = "/dev/hdc"
> sdl=1
> vnc=0
> vncviewer=0
> 
> The xm dmesg shows :
>  __  __            _____  ___   _____     ___
>  \ \/ /___ _ __   |___ / / _ \ |___ /    / _ \
>   \  // _ \ '_ \    |_ \| | | |  |_ \ __| | | |
>   /  \  __/ | | |  ___) | |_| | ___) |__| |_| |
>  /_/\_\___|_| |_| |____(_)___(_)____/    \___/
> 
>  http://www.cl.cam.ac.uk/netos/xen
>  University of Cambridge Computer Laboratory
> 
>  Xen version 3.0.3-0 (root@(none)) (gcc version 4.1.1 (Gentoo 4.1.1))
> Mon Nov 20 15:53:32 CET 2006
>  Latest ChangeSet: unavailable
> 
> (XEN) Command line: /boot/xen-3.0.3-0.gz dom0_mem=256M console=tty0
> (XEN) Physical RAM map:
> (XEN)  0000000000000000 - 000000000009fc00 (usable)
> (XEN)  000000000009fc00 - 00000000000a0000 (reserved)
> (XEN)  00000000000e0000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 0000000077fd0000 (usable)
> (XEN)  0000000077fd0000 - 0000000077fe5600 (reserved)
> (XEN)  0000000077fe5600 - 0000000077ff8000 (ACPI NVS)
> (XEN)  0000000077ff8000 - 0000000080000000 (reserved)
> (XEN)  00000000e0000000 - 00000000f0000000 (reserved)
> (XEN)  00000000fec00000 - 00000000fec02000 (reserved)
> (XEN)  00000000ffbc0000 - 00000000ffcc0000 (reserved)
> (XEN)  00000000fff00000 - 0000000100000000 (reserved)
> (XEN) System RAM: 1919MB (1965500kB)
> (XEN) Xen heap: 14MB (14420kB)
> (XEN) DMI 2.4 present.
> (XEN) Using APIC driver default
> (XEN) ACPI: RSDP (v002 HP                                    ) @
> 0x00000000000f79c0
> (XEN) ACPI: XSDT (v001 HPQOEM SLIC-MPC 0x00000001 HP   0x00000001) @
> 0x0000000077fe57b8
> (XEN) ACPI: FADT (v004 HP     0944     0x00000003 HP   0x00000001) @
> 0x0000000077fe5684
> (XEN) ACPI: SLIC (v001 HPQOEM SLIC-MPC 0x00000001 HP   0x00000001) @
> 0x0000000077fe5814
> (XEN) ACPI: MADT (v001 HP     0944     0x00000001 HP   0x00000001) @
> 0x0000000077fe598c
> (XEN) ACPI: MCFG (v001 HP     0944     0x00000001 HP   0x00000001) @
> 0x0000000077fe59f0
> (XEN) ACPI: TCPA (v002 HP     0944     0x00000001 HP   0x00000001) @
> 0x0000000077fe5a2c
> (XEN) ACPI: SSDT (v001 HP       HPQNLP 0x00000001 MSFT 0x0100000e) @
> 0x0000000077ff48fe
> (XEN) ACPI: SSDT (v001 HP     PSSTBLID 0x00000001 HP   0x00000001) @
> 0x0000000077ff4957
> (XEN) ACPI: DSDT (v001 HP        SB400 0x00010000 MSFT 0x0100000e) @
> 0x0000000000000000
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> (XEN) Processor #0 15:8 APIC version 16
> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> (XEN) Processor #1 15:8 APIC version 16
> (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 33, address 0xfec00000, GSI 0-23
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 21 low level)
> (XEN) ACPI: IRQ0 used by override.
> (XEN) ACPI: IRQ2 used by override.
> (XEN) ACPI: IRQ9 used by override.
> (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
> (XEN) Using ACPI (MADT) for SMP configuration information
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Initializing CPU#0
> (XEN) Detected 1995.084 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 Turion(tm) 64 X2 Mobile Technology TL-60 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 Turion(tm) 64 X2 Mobile Technology TL-60 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=2 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... works.
> (XEN) checking TSC synchronization across 2 CPUs:
> (XEN) CPU#0 had 727 usecs TSC skew, fixed it up.
> (XEN) CPU#1 had -727 usecs TSC skew, fixed it up.
> (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.:   0000000077000000->0000000077800000 (63488 pages
> to be allocated)
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: ffffffff80100000->ffffffff8056ea6c
> (XEN)  Init. ramdisk: ffffffff8056f000->ffffffff8056f000
> (XEN)  Phys-Mach map: ffffffff8056f000->ffffffff805ef000
> (XEN)  Start info:    ffffffff805ef000->ffffffff805ef49c
> (XEN)  Page tables:   ffffffff805f0000->ffffffff805f7000
> (XEN)  Boot stack:    ffffffff805f7000->ffffffff805f8000
> (XEN)  TOTAL:         ffffffff80000000->ffffffff80800000
> (XEN)  ENTRY ADDRESS: ffffffff80100000
> (XEN) Dom0 has maximum 2 VCPUs
> (XEN) Scrubbing Free RAM: ....................done.
> (XEN) Xen trace buffers: disabled
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen).
> 
> The xm log shows:
> [2006-11-29 16:22:52 xend 5624] INFO (__init__:1072) spawning device
> models: /usr/lib64/xen/bin/qemu-dm ['/usr/lib64/xen/bin/qemu-dm',
> '-d', '3', '-m', '512', '-boot', 'd', '-vcpus', '1', '-domain-name',
> 'winxp']
> [2006-11-29 16:22:52 xend 5624] INFO (__init__:1072) device 
> model pid: 6252
> [2006-11-29 16:22:52 xend.XendDomainInfo 5624] DEBUG (__init__:1072)
> Storing VM details: {'shadow_memory': '4', 'uuid':
> '5ea4f5fa-1296-7918-5a17-8c9169bf3e51', 'on_reboot': 'restart',
> 'start_time': '1164813772.98', 'on_poweroff': 'destroy', 'name':
> 'winxp', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1',
> 'memory': '512', 'on_crash': 'restart', 'image': '(hvm (kernel
> /usr/lib64/xen/boot/hvmloader) (device_model
> /usr/lib64/xen/bin/qemu-dm) (vcpus 1) (boot d) (vncunused 1) (sdl 1)
> (display :0.0) (xauthority /root/.xauthukFEhG))', 'maxmem': '512'}
> [2006-11-29 16:22:52 xend.XendDomainInfo 5624] DEBUG (__init__:1072)
> Storing domain details: {'console/port': '2', 'name': 'winxp',
> 'console/limit': '1048576', 'vm':
> '/vm/5ea4f5fa-1296-7918-5a17-8c9169bf3e51', 'domid': '3',
> 'cpu/0/availability': 'online', 'memory/target': '524288',
> 'store/ring-ref': '448073', 'store/port': '1'}
> [2006-11-29 16:22:53 xend 5624] DEBUG (__init__:1072) hvm_shutdown
> fired, shutdown reason=None
> [2006-11-29 16:22:53 xend.XendDomainInfo 5624] DEBUG (__init__:1072)
> XendDomainInfo.handleShutdownWatch
> [2006-11-29 16:22:53 xend 5624] DEBUG (__init__:1072) Waiting 
> for devices vif.
> [2006-11-29 16:22:53 xend 5624] DEBUG (__init__:1072) Waiting 
> for devices usb.
> [2006-11-29 16:22:53 xend 5624] DEBUG (__init__:1072) Waiting 
> for devices vbd.
> [2006-11-29 16:22:53 xend 5624] DEBUG (__init__:1072) Waiting for 768.
> [2006-11-29 16:22:53 xend 5624] DEBUG (__init__:1072)
> hotplugStatusCallback
> /local/domain/0/backend/vbd/3/768/hotplug-status.
> [2006-11-29 16:22:53 xend 5624] DEBUG (__init__:1072)
> hotplugStatusCallback
> /local/domain/0/backend/vbd/3/768/hotplug-status.
> [2006-11-29 16:22:53 xend 5624] DEBUG (__init__:1072) 
> hotplugStatusCallback 1.
> [2006-11-29 16:22:53 xend 5624] DEBUG (__init__:1072) Waiting 
> for 5632.
> [2006-11-29 16:22:53 xend 5624] DEBUG (__init__:1072)
> hotplugStatusCallback
> /local/domain/0/backend/vbd/3/5632/hotplug-status.
> [2006-11-29 16:22:53 xend 5624] DEBUG (__init__:1072) 
> hotplugStatusCallback 1.
> [2006-11-29 16:22:53 xend 5624] DEBUG (__init__:1072) Waiting 
> for devices irq.
> [2006-11-29 16:22:53 xend 5624] DEBUG (__init__:1072) Waiting 
> for devices pci.
> [2006-11-29 16:22:53 xend 5624] DEBUG (__init__:1072) Waiting for
> devices ioports.
> [2006-11-29 16:22:53 xend 5624] DEBUG (__init__:1072) Waiting 
> for devices tap.
> [2006-11-29 16:22:53 xend 5624] DEBUG (__init__:1072) Waiting 
> for devices vtpm.
> [2006-11-29 16:22:53 xend 5624] INFO (__init__:1072) Domain 
> winxp (3) unpaused.
> 
> 
> It seems like hvmloader cannot start.
> 
> Any ideas?
> 
> Regards
> Jorhe
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 
> 



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>