Hi all,
I have a CentOS 5.5 box running Xen 3.0.3 under which I run several
Windows 2003 Enterprise solutions.
Now, after doing a software upgrade last Friday, I restarted the CentOS box.
After the restart, one of my Windows installations refuses to run.
I see a brief startup-screen finding disk(s) and then I get a black
screen with this message:
"Attempting to load x64 Operating system, however, this system does not
have the APIC configured."
Now, I have apic configured, and the image contains a 32 bit version of
2003 server, not 64 bits. All other images I have run just fine.
The troubled image ran fine also, prior to update/reboot.
Is there any reason why I''m getting this message? Is there anything I
can do?
Hope somebody can help me with thius.
Cheers,
-Morten
Here is the config for the hvm:
name = "VarnerTest"
uuid = "bb2d31aa-d32a-daf0-75ae-a092934236a2"
maxmem = 1032
memory = 1032
vcpus = 1
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
boot = "c"
pae = 1
acpi = 1
apic = 1
localtime = 1
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
device_model = "/usr/lib64/xen/bin/qemu-dm"
usbdevice = "tablet"
sdl = 0
vnc = 1
vncunused = 1
keymap = "no"
disk = [ "file:/var/lib/xen/images/VarnerTest.img,hda,w",
",hdc:cdrom,r" ]
vif = [ "mac=00:16:3e:46:ed:52,bridge=xenbr1" ]
serial = "pty"
And here is dmesg:
__ __ _____ _ ____ _ ___ _ _ _____ _ _
____
\ \/ /___ _ __ |___ / / | |___ \ / |/ _ \| || | |___ / / | ___| |
___|
\ // _ \ \047_ \ |_ \ | | __) |__| | (_) | || |_ |_ \ | | / _
\ |___ \
/ \ __/ | | | ___) || |_ / __/|__| |\__, |__ _| ___) || || __/
|___) |
/_/\_\___|_| |_| |____(_)_(_)_____| |_| /_/
|_|(_)____(_)_(_)___|_|____/
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.1.2-194.3.1.el5 (mockbuild@centos.org) (gcc version 4.1.2
20080704 (Red Hat 4.1.2-48)) Thu May 13 12:59:18 EDT 2010
Latest ChangeSet: unavailable
(XEN) Command line:
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN) EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN) Found 1 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009cc00 (usable)
(XEN) 000000000009cc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000007fec0000 (usable)
(XEN) 000000007fec0000 - 000000007fecb000 (ACPI data)
(XEN) 000000007fecb000 - 000000007fece000 (ACPI NVS)
(XEN) 000000007fece000 - 0000000080000000 (reserved)
(XEN) 00000000e0000000 - 00000000e4000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec10000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ffb00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000280000000 (usable)
(XEN) System RAM: 8190MB (8386928kB)
(XEN) Xen heap: 13MB (13680kB)
(XEN) Domain heap initialised: DMA width 32 bits
(XEN) Processor #0 6:15 APIC version 20
(XEN) Processor #1 6:15 APIC version 20
(XEN) Processor #2 6:15 APIC version 20
(XEN) Processor #3 6:15 APIC version 20
(XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2394.052 MHz processor.
(XEN) HVM: VMX enabled
(XEN) VMX: MSR intercept bitmap enabled
(XEN) I/O virtualisation disabled
(XEN) CPU0: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz stepping 0b
(XEN) Booting processor 1/1 eip 90000
(XEN) CPU1: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz stepping 0b
(XEN) Booting processor 2/2 eip 90000
(XEN) CPU2: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz stepping 0b
(XEN) Booting processor 3/3 eip 90000
(XEN) CPU3: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz stepping 0b
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) Platform timer overflows in 2 jiffies.
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 4 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0xffffffff80200000 memsz=0x2f3d70
(XEN) elf_parse_binary: phdr: paddr=0xffffffff804f3d80 memsz=0x14c510
(XEN) elf_parse_binary: phdr: paddr=0xffffffff80641000 memsz=0xc08
(XEN) elf_parse_binary: phdr: paddr=0xffffffff80642000 memsz=0x11becc
(XEN) elf_parse_binary: memory: 0xffffffff80200000 -> 0xffffffff8075decc
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0xffffffff80000000
(XEN) elf_xen_parse_note: ENTRY = 0xffffffff80200000
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff80206000
(XEN) elf_xen_parse_note: FEATURES
"writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_addr_calc_check: addresses:
(XEN) virt_base = 0xffffffff80000000
(XEN) elf_paddr_offset = 0xffffffff80000000
(XEN) virt_offset = 0x0
(XEN) virt_kstart = 0xffffffff80200000
(XEN) virt_kend = 0xffffffff8075decc
(XEN) virt_entry = 0xffffffff80200000
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 ->
0xffffffff8075decc
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000272000000->0000000274000000 (1937315 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff80200000->ffffffff8075decc
(XEN) Init. ramdisk: ffffffff8075e000->ffffffff81007400
(XEN) Phys-Mach map: ffffffff81008000->ffffffff81edfd18
(XEN) Start info: ffffffff81ee0000->ffffffff81ee049c
(XEN) Page tables: ffffffff81ee1000->ffffffff81ef4000
(XEN) Boot stack: ffffffff81ef4000->ffffffff81ef5000
(XEN) TOTAL: ffffffff80000000->ffffffff82000000
(XEN) ENTRY ADDRESS: ffffffff80200000
(XEN) Dom0 has maximum 4 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xffffffff80200000 -> 0xffffffff804f3d70
(XEN) elf_load_binary: phdr 1 at 0xffffffff804f3d80 -> 0xffffffff80640290
(XEN) elf_load_binary: phdr 2 at 0xffffffff80641000 -> 0xffffffff80641c08
(XEN) elf_load_binary: phdr 3 at 0xffffffff80642000 -> 0xffffffff8067f0a8
(XEN) Initrd len 0x8a9400, start at 0xffffffff8075e000
(XEN) Scrubbing Free RAM: ...done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times to
switch input to Xen).
(XEN) Freed 112kB init memory.
(XEN) mtrr: type mismatch for de000000,400000 old: uncachable new:
write-combining
(XEN) mtrr: type mismatch for de000000,1000000 old: uncachable new:
write-combining
(XEN) mtrr: type mismatch for de000000,400000 old: uncachable new:
write-combining
(XEN) mtrr: type mismatch for de000000,1000000 old: uncachable new:
write-combining
--
---------------------
Morten Rønseth
Chief System Architect
t: +47 22 93 25 58
---------------------
Rayon Visual Concepts
Blindernveien 5
NO-0361 Oslo
t: +47 22 93 25 55
<http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=blindernveien5,+0361+oslo,+norway&sll=37.0625,-95.677068&sspn=44.47475,61.787109&ie=UTF8&hq=&hnear=Blindernveien+5,+0361+Oslo,+Norway&t=h&z=16>
www.rayon.no <http://www.rayon.no>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
in your config i see this: device_model = "/usr/lib64/xen/bin/qemu-dm" you actual use 64 qemu, is domU is 32 bit you must use 32 bit if i not wrong Morten Rønseth-2 wrote:> > Hi all, > > > I have a CentOS 5.5 box running Xen 3.0.3 under which I run several > Windows 2003 Enterprise solutions. > Now, after doing a software upgrade last Friday, I restarted the CentOS > box. > After the restart, one of my Windows installations refuses to run. > > I see a brief startup-screen finding disk(s) and then I get a black > screen with this message: > > "Attempting to load x64 Operating system, however, this system does not > have the APIC configured." > > Now, I have apic configured, and the image contains a 32 bit version of > 2003 server, not 64 bits. All other images I have run just fine. > The troubled image ran fine also, prior to update/reboot. > > Is there any reason why I''m getting this message? Is there anything I > can do? > > > Hope somebody can help me with thius. > > > Cheers, > > > -Morten > > > Here is the config for the hvm: > > name = "VarnerTest" > uuid = "bb2d31aa-d32a-daf0-75ae-a092934236a2" > maxmem = 1032 > memory = 1032 > vcpus = 1 > builder = "hvm" > kernel = "/usr/lib/xen/boot/hvmloader" > boot = "c" > pae = 1 > acpi = 1 > apic = 1 > localtime = 1 > on_poweroff = "destroy" > on_reboot = "restart" > on_crash = "restart" > device_model = "/usr/lib64/xen/bin/qemu-dm" > usbdevice = "tablet" > sdl = 0 > vnc = 1 > vncunused = 1 > keymap = "no" > disk = [ "file:/var/lib/xen/images/VarnerTest.img,hda,w", ",hdc:cdrom,r" ] > vif = [ "mac=00:16:3e:46:ed:52,bridge=xenbr1" ] > serial = "pty" > > > And here is dmesg: > > __ __ _____ _ ____ _ ___ _ _ _____ _ _ > ____ > \ \/ /___ _ __ |___ / / | |___ \ / |/ _ \| || | |___ / / | ___| | > ___| > \ // _ \ \047_ \ |_ \ | | __) |__| | (_) | || |_ |_ \ | | / _ > \ |___ \ > / \ __/ | | | ___) || |_ / __/|__| |\__, |__ _| ___) || || __/ > |___) | > /_/\_\___|_| |_| |____(_)_(_)_____| |_| /_/ > |_|(_)____(_)_(_)___|_|____/ > > > http://www.cl.cam.ac.uk/netos/xen > University of Cambridge Computer Laboratory > > Xen version 3.1.2-194.3.1.el5 (mockbuild@centos.org) (gcc version 4.1.2 > 20080704 (Red Hat 4.1.2-48)) Thu May 13 12:59:18 EDT 2010 > Latest ChangeSet: unavailable > > (XEN) Command line: > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds > (XEN) EDID info not retrieved because no DDC retrieval method detected > (XEN) Disc information: > (XEN) Found 1 MBR signatures > (XEN) Found 1 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 000000000009cc00 (usable) > (XEN) 000000000009cc00 - 00000000000a0000 (reserved) > (XEN) 00000000000e4000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 000000007fec0000 (usable) > (XEN) 000000007fec0000 - 000000007fecb000 (ACPI data) > (XEN) 000000007fecb000 - 000000007fece000 (ACPI NVS) > (XEN) 000000007fece000 - 0000000080000000 (reserved) > (XEN) 00000000e0000000 - 00000000e4000000 (reserved) > (XEN) 00000000fec00000 - 00000000fec10000 (reserved) > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > (XEN) 00000000ffb00000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 0000000280000000 (usable) > (XEN) System RAM: 8190MB (8386928kB) > (XEN) Xen heap: 13MB (13680kB) > (XEN) Domain heap initialised: DMA width 32 bits > (XEN) Processor #0 6:15 APIC version 20 > (XEN) Processor #1 6:15 APIC version 20 > (XEN) Processor #2 6:15 APIC version 20 > (XEN) Processor #3 6:15 APIC version 20 > (XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23 > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Detected 2394.052 MHz processor. > (XEN) HVM: VMX enabled > (XEN) VMX: MSR intercept bitmap enabled > (XEN) I/O virtualisation disabled > (XEN) CPU0: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz stepping 0b > (XEN) Booting processor 1/1 eip 90000 > (XEN) CPU1: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz stepping 0b > (XEN) Booting processor 2/2 eip 90000 > (XEN) CPU2: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz stepping 0b > (XEN) Booting processor 3/3 eip 90000 > (XEN) CPU3: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz stepping 0b > (XEN) Total of 4 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using new ACK method > (XEN) Platform timer overflows in 2 jiffies. > (XEN) Platform timer is 1.193MHz PIT > (XEN) Brought up 4 CPUs > (XEN) *** LOADING DOMAIN 0 *** > (XEN) elf_parse_binary: phdr: paddr=0xffffffff80200000 memsz=0x2f3d70 > (XEN) elf_parse_binary: phdr: paddr=0xffffffff804f3d80 memsz=0x14c510 > (XEN) elf_parse_binary: phdr: paddr=0xffffffff80641000 memsz=0xc08 > (XEN) elf_parse_binary: phdr: paddr=0xffffffff80642000 memsz=0x11becc > (XEN) elf_parse_binary: memory: 0xffffffff80200000 -> 0xffffffff8075decc > (XEN) elf_xen_parse_note: GUEST_OS = "linux" > (XEN) elf_xen_parse_note: GUEST_VERSION = "2.6" > (XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0" > (XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000 > (XEN) elf_xen_parse_note: PADDR_OFFSET = 0xffffffff80000000 > (XEN) elf_xen_parse_note: ENTRY = 0xffffffff80200000 > (XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff80206000 > (XEN) elf_xen_parse_note: FEATURES > "writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel" > (XEN) elf_xen_parse_note: LOADER = "generic" > (XEN) elf_xen_addr_calc_check: addresses: > (XEN) virt_base = 0xffffffff80000000 > (XEN) elf_paddr_offset = 0xffffffff80000000 > (XEN) virt_offset = 0x0 > (XEN) virt_kstart = 0xffffffff80200000 > (XEN) virt_kend = 0xffffffff8075decc > (XEN) virt_entry = 0xffffffff80200000 > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> > 0xffffffff8075decc > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000272000000->0000000274000000 (1937315 pages > to be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff80200000->ffffffff8075decc > (XEN) Init. ramdisk: ffffffff8075e000->ffffffff81007400 > (XEN) Phys-Mach map: ffffffff81008000->ffffffff81edfd18 > (XEN) Start info: ffffffff81ee0000->ffffffff81ee049c > (XEN) Page tables: ffffffff81ee1000->ffffffff81ef4000 > (XEN) Boot stack: ffffffff81ef4000->ffffffff81ef5000 > (XEN) TOTAL: ffffffff80000000->ffffffff82000000 > (XEN) ENTRY ADDRESS: ffffffff80200000 > (XEN) Dom0 has maximum 4 VCPUs > (XEN) elf_load_binary: phdr 0 at 0xffffffff80200000 -> 0xffffffff804f3d70 > (XEN) elf_load_binary: phdr 1 at 0xffffffff804f3d80 -> 0xffffffff80640290 > (XEN) elf_load_binary: phdr 2 at 0xffffffff80641000 -> 0xffffffff80641c08 > (XEN) elf_load_binary: phdr 3 at 0xffffffff80642000 -> 0xffffffff8067f0a8 > (XEN) Initrd len 0x8a9400, start at 0xffffffff8075e000 > (XEN) Scrubbing Free RAM: ...done. > (XEN) Xen trace buffers: disabled > (XEN) Std. Loglevel: Errors and warnings > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > (XEN) Xen is relinquishing VGA console. > (XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times to > switch input to Xen). > (XEN) Freed 112kB init memory. > (XEN) mtrr: type mismatch for de000000,400000 old: uncachable new: > write-combining > (XEN) mtrr: type mismatch for de000000,1000000 old: uncachable new: > write-combining > (XEN) mtrr: type mismatch for de000000,400000 old: uncachable new: > write-combining > (XEN) mtrr: type mismatch for de000000,1000000 old: uncachable new: > write-combining > > > -- > --------------------- > Morten Rønseth > Chief System Architect > t: +47 22 93 25 58 > --------------------- > Rayon Visual Concepts > Blindernveien 5 > NO-0361 Oslo > t: +47 22 93 25 55 > <http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=blindernveien5,+0361+oslo,+norway&sll=37.0625,-95.677068&sspn=44.47475,61.787109&ie=UTF8&hq=&hnear=Blindernveien+5,+0361+Oslo,+Norway&t=h&z=16> > www.rayon.no <http://www.rayon.no> > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- View this message in context: http://old.nabble.com/Xen-thinks-32-bit-windows-is-64-bit...-tp28946660p28946738.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2010-Jun-21 10:00 UTC
Re: [Xen-users] Xen thinks 32 bit windows is 64 bit...
On Mon, Jun 21, 2010 at 4:50 PM, Fantu <fantonifabio@tiscali.it> wrote:> > in your config i see this: > device_model = "/usr/lib64/xen/bin/qemu-dm" > you actual use 64 qemu, is domU is 32 bit you must use 32 bit if i not wrongThat shouldn''t be it. I use device_model = ''/usr/lib64/xen/bin/qemu-dm'' kernel = "/usr/lib/xen/boot/hvmloader" on all my HVM domUs, whether 32 or 64bit.> Morten Rønseth-2 wrote: >> "Attempting to load x64 Operating system, however, this system does not >> have the APIC configured." >> >> Now, I have apic configured, and the image contains a 32 bit version of >> 2003 server, not 64 bits. All other images I have run just fine. >> The troubled image ran fine also, prior to update/reboot.I never had that error message. At this point the best I can suggest is : (1) setup another Xen box with the version of Xen/kernel-xen that you had before you upgrade, and copy your domU image there. To be frank, I doubt even that would work, but at least that''s something you can try. (2) Setup a fresh Windows 2003 32bit, witch similar domU config file, on your upgraded box. Test #1 will confirm whether or not the disk image is actually OK. Test #2 will confirm whether the upgraded Xen can run 32bit HVM domUs correctly. My GUESS is that something happens on your domU side. Perhaps someone installed another program which modifies the disk''s MBR? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Morten Rønseth
2010-Jun-21 10:03 UTC
Re: [Xen-users] Xen thinks 32 bit windows is 64 bit...
Hi, The weird thing is that the config file hasn''t changed at all - and, all the other virt. servers run the same way. Cheers, -Morten On 21.06.10 11.50, Fantu wrote:> in your config i see this: > device_model = "/usr/lib64/xen/bin/qemu-dm" > you actual use 64 qemu, is domU is 32 bit you must use 32 bit if i not wrong > > > Morten Rønseth-2 wrote: > >> Hi all, >> >> >> I have a CentOS 5.5 box running Xen 3.0.3 under which I run several >> Windows 2003 Enterprise solutions. >> Now, after doing a software upgrade last Friday, I restarted the CentOS >> box. >> After the restart, one of my Windows installations refuses to run. >> >> I see a brief startup-screen finding disk(s) and then I get a black >> screen with this message: >> >> "Attempting to load x64 Operating system, however, this system does not >> have the APIC configured." >> >> Now, I have apic configured, and the image contains a 32 bit version of >> 2003 server, not 64 bits. All other images I have run just fine. >> The troubled image ran fine also, prior to update/reboot. >> >> Is there any reason why I''m getting this message? Is there anything I >> can do? >> >> >> Hope somebody can help me with thius. >> >> >> Cheers, >> >> >> -Morten >> >> >> Here is the config for the hvm: >> >> name = "VarnerTest" >> uuid = "bb2d31aa-d32a-daf0-75ae-a092934236a2" >> maxmem = 1032 >> memory = 1032 >> vcpus = 1 >> builder = "hvm" >> kernel = "/usr/lib/xen/boot/hvmloader" >> boot = "c" >> pae = 1 >> acpi = 1 >> apic = 1 >> localtime = 1 >> on_poweroff = "destroy" >> on_reboot = "restart" >> on_crash = "restart" >> device_model = "/usr/lib64/xen/bin/qemu-dm" >> usbdevice = "tablet" >> sdl = 0 >> vnc = 1 >> vncunused = 1 >> keymap = "no" >> disk = [ "file:/var/lib/xen/images/VarnerTest.img,hda,w", ",hdc:cdrom,r" ] >> vif = [ "mac=00:16:3e:46:ed:52,bridge=xenbr1" ] >> serial = "pty" >> >> >> And here is dmesg: >> >> __ __ _____ _ ____ _ ___ _ _ _____ _ _ >> ____ >> \ \/ /___ _ __ |___ / / | |___ \ / |/ _ \| || | |___ / / | ___| | >> ___| >> \ // _ \ \047_ \ |_ \ | | __) |__| | (_) | || |_ |_ \ | | / _ >> \ |___ \ >> / \ __/ | | | ___) || |_ / __/|__| |\__, |__ _| ___) || || __/ >> |___) | >> /_/\_\___|_| |_| |____(_)_(_)_____| |_| /_/ >> |_|(_)____(_)_(_)___|_|____/ >> >> >> http://www.cl.cam.ac.uk/netos/xen >> University of Cambridge Computer Laboratory >> >> Xen version 3.1.2-194.3.1.el5 (mockbuild@centos.org) (gcc version 4.1.2 >> 20080704 (Red Hat 4.1.2-48)) Thu May 13 12:59:18 EDT 2010 >> Latest ChangeSet: unavailable >> >> (XEN) Command line: >> (XEN) Video information: >> (XEN) VGA is text mode 80x25, font 8x16 >> (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds >> (XEN) EDID info not retrieved because no DDC retrieval method detected >> (XEN) Disc information: >> (XEN) Found 1 MBR signatures >> (XEN) Found 1 EDD information structures >> (XEN) Xen-e820 RAM map: >> (XEN) 0000000000000000 - 000000000009cc00 (usable) >> (XEN) 000000000009cc00 - 00000000000a0000 (reserved) >> (XEN) 00000000000e4000 - 0000000000100000 (reserved) >> (XEN) 0000000000100000 - 000000007fec0000 (usable) >> (XEN) 000000007fec0000 - 000000007fecb000 (ACPI data) >> (XEN) 000000007fecb000 - 000000007fece000 (ACPI NVS) >> (XEN) 000000007fece000 - 0000000080000000 (reserved) >> (XEN) 00000000e0000000 - 00000000e4000000 (reserved) >> (XEN) 00000000fec00000 - 00000000fec10000 (reserved) >> (XEN) 00000000fee00000 - 00000000fee01000 (reserved) >> (XEN) 00000000ffb00000 - 0000000100000000 (reserved) >> (XEN) 0000000100000000 - 0000000280000000 (usable) >> (XEN) System RAM: 8190MB (8386928kB) >> (XEN) Xen heap: 13MB (13680kB) >> (XEN) Domain heap initialised: DMA width 32 bits >> (XEN) Processor #0 6:15 APIC version 20 >> (XEN) Processor #1 6:15 APIC version 20 >> (XEN) Processor #2 6:15 APIC version 20 >> (XEN) Processor #3 6:15 APIC version 20 >> (XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23 >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs >> (XEN) Using scheduler: SMP Credit Scheduler (credit) >> (XEN) Detected 2394.052 MHz processor. >> (XEN) HVM: VMX enabled >> (XEN) VMX: MSR intercept bitmap enabled >> (XEN) I/O virtualisation disabled >> (XEN) CPU0: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz stepping 0b >> (XEN) Booting processor 1/1 eip 90000 >> (XEN) CPU1: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz stepping 0b >> (XEN) Booting processor 2/2 eip 90000 >> (XEN) CPU2: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz stepping 0b >> (XEN) Booting processor 3/3 eip 90000 >> (XEN) CPU3: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz stepping 0b >> (XEN) Total of 4 processors activated. >> (XEN) ENABLING IO-APIC IRQs >> (XEN) -> Using new ACK method >> (XEN) Platform timer overflows in 2 jiffies. >> (XEN) Platform timer is 1.193MHz PIT >> (XEN) Brought up 4 CPUs >> (XEN) *** LOADING DOMAIN 0 *** >> (XEN) elf_parse_binary: phdr: paddr=0xffffffff80200000 memsz=0x2f3d70 >> (XEN) elf_parse_binary: phdr: paddr=0xffffffff804f3d80 memsz=0x14c510 >> (XEN) elf_parse_binary: phdr: paddr=0xffffffff80641000 memsz=0xc08 >> (XEN) elf_parse_binary: phdr: paddr=0xffffffff80642000 memsz=0x11becc >> (XEN) elf_parse_binary: memory: 0xffffffff80200000 -> 0xffffffff8075decc >> (XEN) elf_xen_parse_note: GUEST_OS = "linux" >> (XEN) elf_xen_parse_note: GUEST_VERSION = "2.6" >> (XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0" >> (XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000 >> (XEN) elf_xen_parse_note: PADDR_OFFSET = 0xffffffff80000000 >> (XEN) elf_xen_parse_note: ENTRY = 0xffffffff80200000 >> (XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff80206000 >> (XEN) elf_xen_parse_note: FEATURES >> "writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel" >> (XEN) elf_xen_parse_note: LOADER = "generic" >> (XEN) elf_xen_addr_calc_check: addresses: >> (XEN) virt_base = 0xffffffff80000000 >> (XEN) elf_paddr_offset = 0xffffffff80000000 >> (XEN) virt_offset = 0x0 >> (XEN) virt_kstart = 0xffffffff80200000 >> (XEN) virt_kend = 0xffffffff8075decc >> (XEN) virt_entry = 0xffffffff80200000 >> (XEN) Xen kernel: 64-bit, lsb, compat32 >> (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> >> 0xffffffff8075decc >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >> (XEN) Dom0 alloc.: 0000000272000000->0000000274000000 (1937315 pages >> to be allocated) >> (XEN) VIRTUAL MEMORY ARRANGEMENT: >> (XEN) Loaded kernel: ffffffff80200000->ffffffff8075decc >> (XEN) Init. ramdisk: ffffffff8075e000->ffffffff81007400 >> (XEN) Phys-Mach map: ffffffff81008000->ffffffff81edfd18 >> (XEN) Start info: ffffffff81ee0000->ffffffff81ee049c >> (XEN) Page tables: ffffffff81ee1000->ffffffff81ef4000 >> (XEN) Boot stack: ffffffff81ef4000->ffffffff81ef5000 >> (XEN) TOTAL: ffffffff80000000->ffffffff82000000 >> (XEN) ENTRY ADDRESS: ffffffff80200000 >> (XEN) Dom0 has maximum 4 VCPUs >> (XEN) elf_load_binary: phdr 0 at 0xffffffff80200000 -> 0xffffffff804f3d70 >> (XEN) elf_load_binary: phdr 1 at 0xffffffff804f3d80 -> 0xffffffff80640290 >> (XEN) elf_load_binary: phdr 2 at 0xffffffff80641000 -> 0xffffffff80641c08 >> (XEN) elf_load_binary: phdr 3 at 0xffffffff80642000 -> 0xffffffff8067f0a8 >> (XEN) Initrd len 0x8a9400, start at 0xffffffff8075e000 >> (XEN) Scrubbing Free RAM: ...done. >> (XEN) Xen trace buffers: disabled >> (XEN) Std. Loglevel: Errors and warnings >> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) >> (XEN) Xen is relinquishing VGA console. >> (XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times to >> switch input to Xen). >> (XEN) Freed 112kB init memory. >> (XEN) mtrr: type mismatch for de000000,400000 old: uncachable new: >> write-combining >> (XEN) mtrr: type mismatch for de000000,1000000 old: uncachable new: >> write-combining >> (XEN) mtrr: type mismatch for de000000,400000 old: uncachable new: >> write-combining >> (XEN) mtrr: type mismatch for de000000,1000000 old: uncachable new: >> write-combining >> >> >> -- >> --------------------- >> Morten Rønseth >> Chief System Architect >> t: +47 22 93 25 58 >> --------------------- >> Rayon Visual Concepts >> Blindernveien 5 >> NO-0361 Oslo >> t: +47 22 93 25 55 >> <http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=blindernveien5,+0361+oslo,+norway&sll=37.0625,-95.677068&sspn=44.47475,61.787109&ie=UTF8&hq=&hnear=Blindernveien+5,+0361+Oslo,+Norway&t=h&z=16> >> www.rayon.no <http://www.rayon.no> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> >-- --------------------- Morten Rønseth Chief System Architect t: +47 22 93 25 58 --------------------- Rayon Visual Concepts Blindernveien 5 NO-0361 Oslo t: +47 22 93 25 55 <http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=blindernveien5,+0361+oslo,+norway&sll=37.0625,-95.677068&sspn=44.47475,61.787109&ie=UTF8&hq=&hnear=Blindernveien+5,+0361+Oslo,+Norway&t=h&z=16> www.rayon.no <http://www.rayon.no> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Morten Rønseth
2010-Jun-21 10:10 UTC
Re: [Xen-users] Xen thinks 32 bit windows is 64 bit...
Hi, I''m inclined to agree with this. All other images run fine, they all come out of the same windows installation disk. What are my options if the MBR is altered in some way? I''m now trying to copy the image to my Mac and mount it there to salvage content. Cheers, -Morten On 21.06.10 12.00, Fajar A. Nugraha wrote:> On Mon, Jun 21, 2010 at 4:50 PM, Fantu <fantonifabio@tiscali.it> wrote: > >> in your config i see this: >> device_model = "/usr/lib64/xen/bin/qemu-dm" >> you actual use 64 qemu, is domU is 32 bit you must use 32 bit if i not wrong >> > That shouldn''t be it. I use > > device_model = ''/usr/lib64/xen/bin/qemu-dm'' > kernel = "/usr/lib/xen/boot/hvmloader" > > on all my HVM domUs, whether 32 or 64bit. > > >> Morten Rønseth-2 wrote: >> >>> "Attempting to load x64 Operating system, however, this system does not >>> have the APIC configured." >>> >>> Now, I have apic configured, and the image contains a 32 bit version of >>> 2003 server, not 64 bits. All other images I have run just fine. >>> The troubled image ran fine also, prior to update/reboot. >>> > I never had that error message. At this point the best I can suggest is : > (1) setup another Xen box with the version of Xen/kernel-xen that you > had before you upgrade, and copy your domU image there. To be frank, I > doubt even that would work, but at least that''s something you can try. > (2) Setup a fresh Windows 2003 32bit, witch similar domU config file, > on your upgraded box. > > Test #1 will confirm whether or not the disk image is actually OK. > Test #2 will confirm whether the upgraded Xen can run 32bit HVM domUs correctly. > > My GUESS is that something happens on your domU side. Perhaps someone > installed another program which modifies the disk''s MBR? > >-- --------------------- Morten Rønseth Chief System Architect t: +47 22 93 25 58 --------------------- Rayon Visual Concepts Blindernveien 5 NO-0361 Oslo t: +47 22 93 25 55 <http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=blindernveien5,+0361+oslo,+norway&sll=37.0625,-95.677068&sspn=44.47475,61.787109&ie=UTF8&hq=&hnear=Blindernveien+5,+0361+Oslo,+Norway&t=h&z=16> www.rayon.no <http://www.rayon.no> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > I have a CentOS 5.5 box running Xen 3.0.3 under which I run several Windows > 2003 Enterprise solutions. > Now, after doing a software upgrade last Friday, I restarted the CentOS box. > After the restart, one of my Windows installations refuses to run. > > I see a brief startup-screen finding disk(s) and then I get a black screen > with this message: > > "Attempting to load x64 Operating system, however, this system does not have > the APIC configured." > > Now, I have apic configured, and the image contains a 32 bit version of 2003 > server, not 64 bits. All other images I have run just fine. > The troubled image ran fine also, prior to update/reboot. > > Is there any reason why I'm getting this message? Is there anything I can do? >You don't have a 64 bit iso loaded into the domain config or something do you? James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users