> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> shal@xxxxxxx
> Sent: 09 November 2006 15:51
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] APIC support
>
> Hello,
>
> I am new in xen world.
>
> I have a bug.
>
> My configuration:
> Fedora Core 6 x86_64 with Core 2 Duo (6700) on a P965 Intel
> motherboard.
> The VT technology is ON in BIOS.
>
> I have try to install a Windows XP SP2 on a full virtualiztion.
> I have succes for the first step : windows CD boot and copy files for
> installation . But when the windows restart there are problem.
>
> problems depends of the configuration.
>
> If apic is on I have:
> (XEN) (GUEST: 24) HVM Loader
> (XEN) (GUEST: 24) Detected Xen v3.0.3-rc3-1.2798.f
> (XEN) (GUEST: 24) Writing SMBIOS tables ...
> (XEN) (GUEST: 24) Loading ROMBIOS ...
> (XEN) (GUEST: 24) Creating MP tables ...
> (XEN) (GUEST: 24) Loading Cirrus VGABIOS ...
> (XEN) (GUEST: 24) Loading ACPI ...
> (XEN) (GUEST: 24) Loading VMXAssist ...
> (XEN) (GUEST: 24) VMX go ...
> (XEN) (GUEST: 24) VMXAssist (Oct 17 2006)
> (XEN) (GUEST: 24) Memory size 500 MB
> (XEN) (GUEST: 24) E820 map:
> (XEN) (GUEST: 24) 0000000000000000 - 000000000009F000 (RAM)
> (XEN) (GUEST: 24) 000000000009F000 - 00000000000A0000 (Reserved)
> (XEN) (GUEST: 24) 00000000000A0000 - 00000000000C0000 (Type 16)
> (XEN) (GUEST: 24) 00000000000F0000 - 0000000000100000 (Reserved)
> (XEN) (GUEST: 24) 0000000000100000 - 000000001F3F0000 (RAM)
> (XEN) (GUEST: 24) 000000001F3F0000 - 000000001F3FA000 (ACPI Data)
> (XEN) (GUEST: 24) 000000001F3FA000 - 000000001F3FD000 (ACPI NVS)
> (XEN) (GUEST: 24) 000000001F3FD000 - 000000001F3FE000 (Type 19)
> (XEN) (GUEST: 24) 000000001F3FE000 - 000000001F3FF000 (Type 18)
> (XEN) (GUEST: 24) 000000001F3FF000 - 000000001F400000 (Type 17)
> (XEN) (GUEST: 24) 00000000FEC00000 - 0000000100000000 (Type 16)
> (XEN) (GUEST: 24)
> (XEN) (GUEST: 24) Start BIOS ...
> (XEN) (GUEST: 24) Starting emulated 16-bit real-mode: ip=F000:FFF0
> (XEN) (GUEST: 24) rombios.c,v 1.138 2005/05/07 15:55:26
> vruppert Exp $
> (XEN) (GUEST: 24) Remapping master: ICW2 0x8 -> 0x20
> (XEN) (GUEST: 24) Remapping slave: ICW2 0x70 -> 0x28
> (XEN) (GUEST: 24) VGABios $Id: vgabios.c,v 1.61 2005/05/24
> 16:50:50 vruppert Exp
> $
> (XEN) (GUEST: 24) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $
> $Date: 2005/05/07
> 15:55:26 $
> (XEN) (GUEST: 24)
> (XEN) (GUEST: 24) ata0-0: PCHS=8322/16/63 translation=lba
> LCHS=522/255/63
> (XEN) (GUEST: 24) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk
> (4096 MBytes)
> (XEN) (GUEST: 24) ata0 slave: Unknown device
> (XEN) (GUEST: 24)
> (XEN) (GUEST: 24) Booting from Hard Disk...
> (XEN) (GUEST: 24) unsupported PCI BIOS function 0x0E
> (XEN) (GUEST: 24) int13_harddisk: function 15, unmapped
> device for ELDL=81
> (XEN) (GUEST: 24) *** int 15h function AX=E980, BX=00F2 not
> yet supported!
> (XEN) hvm_vioapic_write_indirect: version register read only
> (XEN) hvm_vioapic_write_indirect: version register read only
> (XEN) hvm_vioapic_write_indirect: version register read only
> (XEN) This hvm_vlapic is for P4, no work for De-assert init
This is NOT a problem - just warnings that the OS is trying to do things
that doesn't make sense on this version of APIC - which is probably
necessary to do in some circumstances (I'm not that keyed up on
different APIC versions - but the fact that there is a write to a
read-only register is a pointer towards "OS doing things that it
shouldn't do", but it's also harmless to write to a read-only
register...)
Does this work besides the warning messages.
>
>
> But when I disable apic and acpi is on:
> (XEN) (GUEST: 26) Booting from Hard Disk...
> (XEN) (GUEST: 26) unsupported PCI BIOS function 0x0E
> (XEN) (GUEST: 26) int13_harddisk: function 15, unmapped
> device for ELDL=81
> (XEN) (GUEST: 26) *** int 15h function AX=E980, BX=00F2 not
> yet supported!
> (XEN) sh error: sh_page_fault__shadow_3_guest_3():
> disabled-APIC access: not
> supported
Yeah, that makes sense. If you install Windows with ACPI and APIC
enabled, you shouldn't attempt to run it without - Windows decides at
install-time which HAL and Kernel you need, and doesn't check again for
these features when it boots afterwards. It's not expected to change...
> (XEN) .domain_crash called from multi.c:3197
> (XEN) Domain 26 (vcpu#0) crashed on cpu#0:
> (XEN) ----[ Xen-3.0.3-rc3-1.2798.fc6 x86_64 debug=n Not
> tainted ]----
> (XEN) CPU: 0
> (XEN) RIP: 0008:[<00000000806e4312>]
> (XEN) RFLAGS: 0000000000010086 CONTEXT: hvm
> (XEN) rax: 00000000ffd04000 rbx: 0000000000000000 rcx:
> 00000000ffdff120
> (XEN) rdx: 00000000fec00000 rsi: 00000000ffd021e4 rdi:
> 0000000000000000
> (XEN) rbp: 0000000000060088 rsp: 000000000006006c r8:
> 0000000000000000
> (XEN) r9: 0000000000000000 r10: 0000000000000000 r11:
> 0000000000000000
> (XEN) r12: 0000000000000000 r13: 0000000000000000 r14:
> 0000000000000000
> (XEN) r15: 0000000000000000 cr0: 0000000080050033 cr4:
> 0000000000000671
> (XEN) cr3: 0000000000fe17a0 cr2: 0000000000000000
> (XEN) ds: 0023 es: 0023 fs: 0030 gs: 0000 ss: 0010 cs: 0008
>
>
>
> With acpi and apic off:
> (XEN) (GUEST: 28) Booting from Hard Disk...
> (XEN) (GUEST: 28) unsupported PCI BIOS function 0x0E
> (XEN) (GUEST: 28) int13_harddisk: function 15, unmapped
> device for ELDL=81
> (XEN) (file=x86_emulate.c, line=1152) Cannot emulate e8
> (XEN) (file=x86_emulate.c, line=1152) Cannot emulate 1e
> (XEN) domain_crash_sync called from vmx.c:2267
> (XEN) Domain 28 (vcpu#0) crashed on cpu#1:
> (XEN) ----[ Xen-3.0.3-rc3-1.2798.fc6 x86_64 debug=n Not
> tainted ]----
> (XEN) CPU: 1
> (XEN) RIP: 0008:[<00000000806d02e8>]
> (XEN) RFLAGS: 0000000000010246 CONTEXT: hvm
> (XEN) rax: 0000000080551b80 rbx: 000000000003f550 rcx:
> 00000000000000ff
> (XEN) rdx: 000000000000001f rsi: 0000000000000000 rdi:
> 00000000fffe0080
> (XEN) rbp: 000000000003f47c rsp: 000000000003f434 r8:
> 0000000000000000
> (XEN) r9: 0000000000000000 r10: 0000000000000000 r11:
> 0000000000000000
> (XEN) r12: 0000000000000000 r13: 0000000000000000 r14:
> 0000000000000000
> (XEN) r15: 0000000000000000 cr0: 0000000080050033 cr4:
> 0000000000000671
> (XEN) cr3: 0000000000fe17a0 cr2: 00000000fffe0080
> (XEN) ds: 0023 es: 0023 fs: 0030 gs: 0000 ss: 0010 cs: 0008
I have a different version of vmx.c than yours, so I don't know what
line this is, but I'd say it's a consequence of running a ACPI HAL on a
system that doesn't support ACPI (or APIC).
As above, this isn't expected to work.
>
>
> With acpi off and apic on I have thousand of:
> (XEN) (file=x86_emulate.c, line=1152) Cannot emulate 06
Opcode 06 is indeed not implemented in emulate.c - it's probably not
supposed to be either, and it's most likely a consequence of running an
ACPI HAL that is not suited for runing with ACPI off...
--
Mats
>
>
> My config:
> name = "winxpsp2"
> builder = "hvm"
> memory = "500"
> disk = [ 'file:/var/xen/machineWindows.img,ioemu:hda,w', ]
> vif = [ 'type=ioemu, mac=00:16:3e:25:da:76, bridge=xenbr0', ]
> uuid = "2f7344ee-4e83-633c-0b54-47278c3c7920"
> device_model = "/usr/lib64/xen/bin/qemu-dm"
> kernel = "/usr/lib/xen/boot/hvmloader"
> vnc=0
> vncunused=1
> apic=1 # I have tested combiansion of acpi apic and pae
> acpi=0
> pae=0
>
> vcpus=1
> serial = "pty" # enable serial console
> on_reboot = 'restart'
> on_crash = 'restart'
>
>
>
>
> A external remark: I have enable VT in the BIOD but it does
> not work after a
> simple reboot but after a shutdown it was OK.
>
> Thank for help
>
> _______________________________________________
> 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
|
Home