Resending.... can anyone help?
Thanks
/Jd
jdsw <jdsw2002@yahoo.com> wrote: Hi
I tried using xen-3.0.3-testing.hg followed most of the stuff from
http://www.broermann.com/howto_amd_hvm.html
Still getting the same problem when I try to start WinXP domU. Same dmesg
message about ROMBIOS. I would appreciate any help getting this and related
issues resolved.
Q1 : Is the procedure ok (bit later in email) ? Do I need to do anything else ?
(One interesting thing is that the kernel version that I had installed using
yum, were 2.6.17-1.2187, while 3.0.3 testing.hg is got 2.6.16.29 !!! )
Additionaly I am seeing the following. These are put here as they might be
actual bugs or may help resolve the issue.
A .
during startup, Between xend starting and login prompt takes 2 min.!! I dont
know whats going on ?
some messages in dmesg
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 50
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 50, Value: 1
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 18
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 18, Value: 1
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 50
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 50, Value: 0
B
-- Now my network name resolution is not working. I can ping using IP addresses.
C
-- Xen is dropping 1GB memory of 4 GB!!! (see attached xm_dmesg)
Xen version 3.0.3-rc4 (root@) (gcc version 4.1.1 20060525 (Red Hat 4.1.1-1))
Thu Oct 12 22:58:53 PDT 2006
Latest ChangeSet: Thu Oct 12 19:09:08 2006 +0100 11758:946628333c31
(XEN) Command line: /xen.gz dom0_mem=768000
(XEN) WARNING: Only the first 4 GB of the physical memory map can be accessed
(XEN) by Xen in 32-bit mode. Truncating the memory map...
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009f800 (usable)
(XEN) 000000000009f800 - 00000000000a0000 (reserved)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000bbff0000 (usable)
(XEN) 00000000bbff0000 - 00000000bbff3000 (ACPI NVS)
(XEN) 00000000bbff3000 - 00000000bc000000 (ACPI data)
(XEN) 00000000f0000000 - 00000000f2000000 (reserved)
(XEN) 00000000fec00000 - 0000000100000000 (reserved)
(XEN) System RAM: 3007MB (3079740kB)
(XEN) Xen heap: 10MB (10376kB)(XEN) PAE disabled.
(XEN) found SMP MP-table at 000f5240
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 GBT ) @ 0x000f6bf0
(XEN) ACPI: RSDT (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0xbbff3000
(XEN) ACPI: FADT (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0xbbff3040
(XEN) ACPI: SSDT (v001 PTLTD POWERNOW 0x00000001 LTP 0x00000001) @ 0xbbff7a40
(XEN) ACPI: MCFG (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0xbbff7c80
(XEN) ACPI: MADT (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0xbbff79c0
(XEN) ACPI: DSDT (v001 GBT AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 15:11 APIC version 16
============ BUILD PROCEDURE ==================
# cd /usr/src/
# hg clone http://xenbits.xensource.com/xen-3.0.3-testing.hg
# cd xen-3.0-3testing.hg
# make world
# make install
# mkinitrd initrd.img-2.6.16.29-xen 2.6.16.29-xen
# ln -sf initrd.img-2.6.16.29-xen initrd.img-2.6-xen
--- disabled ASUS-ACPI
# make linux-2.6-xen-config CONFIGMODE=menuconfig
# make linux-2.6-xen-build
# make linux-2.6-xen-install
-- did the whole procedure twice.. once skipped this two
--- steps (removed and rebuilt, as mkinitrd was compalaining..
# rm initrd.img-2.6.16.29-xen
# mkinitrd initrd.img-2.6.16.29-xen 2.6.16.13-xen
I had to manually copy xen and grub from /usr/lib/python to
/usr/lib/python2.4/site-packages.
Added a new entry in the menu.lst under
grub.
title Fedora Core TEST (2.6.16.29-xen)
root (hd0,0)
kernel /xen.gz dom0_mem=768000
module /vmlinuz-2.6.16.29-xen ro root=/dev/VG_Fedora/LV2 rhgb quiet
module /initrd.img-2.6.16.29-xen
booted in Test kernel. And tried to create HVM winxp domu.
==============
Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:Re: [Xen-devel] RE:
[Xen-users] HVM WinXP dom crash On 9/10/06 8:19 pm, "jdsw"
<jdsw2002@yahoo.com> wrote:
ok.. I would not worry about the WRMSR warnings.
But how do I get pass the ROMBIOS problem ?
ccing devloper forum,in case someone knows about this particular issue.
The hvmloader binary is definitely out of sync with the Xen binary (hvmloaders
SVM hypercall interface is older than the Xen that you are running knows about).
This might be a misfeature of the FC5 packages, although I havent heard anyone
else report this problem.
If you want to play with the best-possible bits right now, particularly for HVM
guests, I recommend you download binary tarballs when we release 3.0.3-final in
a few days, or grab the xen-3.0.3-testing.hg repository and build it yourself.
Then youll know for sure that everything is in sync.
-- Keir
---------------------------------
Get your email and more, right on the new Yahoo.com
---------------------------------
Want to be your own boss? Learn how on Yahoo! Small Business.
--0-1252953307-1161020857=:79279
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Resending.... can anyone
help?<br><br>Thanks<br>/Jd<br><br><b><i>jdsw
<jdsw2002@yahoo.com></i></b> wrote:<blockquote
class="replbq" style="border-left: 2px solid rgb(16, 16, 255);
margin-left: 5px; padding-left: 5px;"> Hi<br> I tried
using <font face="Verdana, Helvetica, Arial"><span
style="font-size: 12px;">xen-3.0.3-testing.hg followed
most of the stuff from
<br>http://www.broermann.com/howto_amd_hvm.html<br>Still getting the
same problem when I try to start WinXP domU. Same dmesg message about
ROMBIOS. I would appreciate any help getting this and related issues
resolved.<br><br>Q1 : Is the procedure ok (bit later in
email) ? Do I need to do anything else ? (One interesting thing is that the
kernel version that I had installed using yum, were 2.6.<span
style="font-weight: bold;">17</span>-1.2187, while 3.0.3
testing.hg is got 2.6.<span style="font-weight:
bold;">16</span>.29 !!! )<br><br>Additionaly I am
seeing the following. These are put
here as they might be actual bugs or may help resolve the
issue.<br><br>A . <br> during startup, Between xend
starting and login prompt takes 2 min.!! I dont know whats
going on ?<br> some messages in dmesg
</span></font><font face="Verdana, Helvetica,
Arial"><span style="font-size:
12px;"></span></font><br><font face="Verdana,
Helvetica, Arial"><span style="font-size:
12px;">evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4,
Value: 50<br>evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code:
50, Value: 1<br>evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code:
0, Value: 0<br>evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code:
4, Value: 18<br>evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code:
18, Value: 1<br>evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code:
0, Value: 0<br>evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code:
4, Value: 50<br>evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code:
50,
Value: 0<br><br>B <br>-- Now my network name
resolution is not working. I can ping using IP
addresses.<br><br>C<br>-- Xen is dropping 1GB memory of 4
GB!!! (see attached xm_dmesg)<br> Xen version 3.0.3-rc4 (root@)
(gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)) Thu Oct 12 22:58:53 PDT
2006<br> Latest ChangeSet: Thu Oct 12 19:09:08 2006 +0100
11758:946628333c31<br><br>(XEN) Command line: /xen.gz
dom0_mem=768000<br>(XEN) WARNING: Only the first 4 GB of the physical
memory map can be
accessed<br>(XEN)
by Xen in 32-bit mode. Truncating the memory map...<br>(XEN) Physical RAM
map:<br>(XEN) 0000000000000000 - 000000000009f800
(usable)<br>(XEN) 000000000009f800 - 00000000000a0000
(reserved)<br>(XEN) 00000000000f0000 - 0000000000100000
(reserved)<br>(XEN) 0000000000100000 - 00000000bbff0000
(usable)<br>(XEN) 00000000bbff0000 - 00000000bbff3000 (ACPI
NVS)<br>(XEN)
00000000bbff3000 - 00000000bc000000 (ACPI data)<br>(XEN)
00000000f0000000 - 00000000f2000000 (reserved)<br>(XEN)
00000000fec00000 - 0000000100000000 (reserved)<br>(XEN) System RAM: 3007MB
(3079740kB)<br>(XEN) Xen heap: 10MB (10376kB)(XEN) PAE
disabled.<br>(XEN) found SMP MP-table at 000f5240<br>(XEN) DMI 2.3
present.<br>(XEN) Using APIC driver default<br>(XEN) ACPI: RSDP
(v000
GBT
) @ 0x000f6bf0<br>(XEN) ACPI: RSDT (v001 GBT
AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0xbbff3000<br>(XEN) ACPI: FADT
(v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @
0xbbff3040<br>(XEN) ACPI: SSDT (v001 PTLTD POWERNOW
0x00000001 LTP 0x00000001) @ 0xbbff7a40<br>(XEN) ACPI: MCFG
(v001 GBT AWRDACPI 0x42302e31 AWRD
0x01010101) @ 0xbbff7c80<br>(XEN) ACPI: MADT (v001
GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @
0xbbff79c0<br>(XEN) ACPI: DSDT (v001 GBT
AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000<br>(XEN) ACPI: Local
APIC address 0xfee00000<br>(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00]
enabled)<br>(XEN) Processor #0 15:11 APIC version
16<br><br><br>============ BUILD PROCEDURE
===================<br></span></font><pre># cd
/usr/src/<br># hg clone
http://xenbits.xensource.com/xen-3.0.3-testing.hg<br># cd
xen-3.0-3testing.hg<br># make world<br># make install<br>#
mkinitrd initrd.img-2.6.16.29-xen 2.6.16.29-xen<br># ln -sf
initrd.img-2.6.16.29-xen initrd.img-2.6-xen</pre><br>--- disabled
ASUS-ACPI<br><pre># make linux-2.6-xen-config
CONFIGMODE=menuconfig<br># make linux-2.6-xen-build<br># make
linux-2.6-xen-install<br><br>-- did the whole procedure twice.. once
skipped this two<br>--- steps (removed and rebuilt, as mkinitrd was
compalaining..<br># rm initrd.img-2.6.16.29-xen <br># mkinitrd
initrd.img-2.6.16.29-xen 2.6.16.13-xen<br><br>I had to manually
copy xen and grub from /usr/lib/python to
/usr/lib/python2.4/site-packages.<br>Added a new entry in the menu.lst
under<br> grub.<br><br>title Fedora Core TEST
(2.6.16.29-xen)<br> root (hd0,0)<br> kernel /xen.gz
dom0_mem=768000<br> module /vmlinuz-2.6.16.29-xen ro
root=/dev/VG_Fedora/LV2 rhgb quiet<br> module
/initrd.img-2.6.16.29-xen<br><br>booted in Test kernel. And tried to
create HVM winxp
domu.<br>===============<br><br></pre><br><b><i>Keir
Fraser <Keir.Fraser@cl.cam.ac.uk></i></b>
wrote:<blockquote class="replbq" style="border-left: 2px solid
rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><title>Re:
[Xen-devel] RE: [Xen-users] HVM WinXP dom crash</title> <font
face="Verdana, Helvetica, Arial"><span style="font-size:
12px;">On 9/10/06 8:19 pm, "jdsw"
<jdsw2002@yahoo.com> wrote:<br> <br>
</span></font><blockquote><font face="Verdana,
Helvetica, Arial"><span style="font-size: 12px;">ok.. I
would not worry about the WRMSR warnings.<br> But how do I get pass the
ROMBIOS problem ?<br> <br> ccing devloper forum,in case someone
knows about this particular issue.<br>
</span></font></blockquote><font face="Verdana,
Helvetica, Arial"><span style="font-size:
12px;"><br> The hvmloader binary is definitely out of sync with
the Xen binary (hvmloaders SVM hypercall interface is older than the Xen that
you are running knows about). This might be a misfeature of the FC5 packages,
although I havent heard anyone else report this problem.<br> <br>
If you want to play with the best-possible bits right now, particularly for HVM
guests, I recommend you download binary tarballs when we release 3.0.3-final in
a few days, or grab the xen-3.0.3-testing.hg repository and build it yourself.
Then youll know for sure that everything is in sync.<br> <br>
-- Keir<br>
</span></font> </blockquote><br><div>
</div><hr size="1">Get your email and more, right on the
<a
href="http://us.rd.yahoo.com/evt=42973/*http://www.yahoo.com/preview">
new Yahoo.com</a> </blockquote><br><p> 
<hr size=1>Want to be your own boss? Learn how on <a
href="http://us.rd.yahoo.com/evt=41244/*http://smallbusiness.yahoo.com/r-index">
Yahoo! Small Business.</a>
--0-1252953307-1161020857=:79279--
--===============0569192391=Content-Type: text/plain;
charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
--===============0569192391==--
If you¹re still getting the bad hypercall message when the hvmloader runs, and thus unable to run ROMBIOS, then your hvmloader binary is still out of date. Where did you get 3.0.3-testing from? If you built yourself you need to download an extra 16-bit compiler (bcc). The instructions for this are listed when you try to build the HVM firmware (which fails to build if that compiler is absent). Look at /usr/lib/xen/boot/hvmloader what¹s the timestamp on it? -- Keir On 16/10/06 6:47 pm, "jdsw" <jdsw2002@yahoo.com> wrote:> Resending.... can anyone help? > > Thanks > /Jd > > jdsw <jdsw2002@yahoo.com> wrote: >> Hi >> I tried using xen-3.0.3-testing.hg followed most of the stuff from >> http://www.broermann.com/howto_amd_hvm.html >> Still getting the same problem when I try to start WinXP domU. Same dmesg >> message about ROMBIOS. I would appreciate any help getting this and related >> issues resolved. >> >> Q1 : Is the procedure ok (bit later in email) ? Do I need to do anything >> else ? (One interesting thing is that the kernel version that I had installed >> using yum, were 2.6.17-1.2187, while 3.0.3 testing.hg is got 2.6.16.29 !!! ) >> >> Additionaly I am seeing the following. These are put here as they might be >> actual bugs or may help resolve the issue. >> >> A . >> during startup, Between xend starting and login prompt takes 2 min.!! I >> dont know whats going on ? >> some messages in dmesg >> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 50 >> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 50, Value: 1 >> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0 >> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 18 >> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 18, Value: 1 >> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0 >> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 50 >> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 50, Value: 0 >> >> B >> -- Now my network name resolution is not working. I can ping using IP >> addresses. >> >> C >> -- Xen is dropping 1GB memory of 4 GB!!! (see attached xm_dmesg) >> Xen version 3.0.3-rc4 (root@) (gcc version 4.1.1 20060525 (Red Hat >> 4.1.1-1)) Thu Oct 12 22:58:53 PDT 2006 >> Latest ChangeSet: Thu Oct 12 19:09:08 2006 +0100 11758:946628333c31 >> >> (XEN) Command line: /xen.gz dom0_mem=768000 >> (XEN) WARNING: Only the first 4 GB of the physical memory map can be accessed >> (XEN) by Xen in 32-bit mode. Truncating the memory map... >> (XEN) Physical RAM map: >> (XEN) 0000000000000000 - 000000000009f800 (usable) >> (XEN) 000000000009f800 - 00000000000a0000 (reserved) >> (XEN) 00000000000f0000 - 0000000000100000 (reserved) >> (XEN) 0000000000100000 - 00000000bbff0000 (usable) >> (XEN) 00000000bbff0000 - 00000000bbff3000 (ACPI NVS) >> (XEN) 00000000bbff3000 - 00000000bc000000 (ACPI data) >> (XEN) 00000000f0000000 - 00000000f2000000 (reserved) >> (XEN) 00000000fec00000 - 0000000100000000 (reserved) >> (XEN) System RAM: 3007MB (3079740kB) >> (XEN) Xen heap: 10MB (10376kB)(XEN) PAE disabled. >> (XEN) found SMP MP-table at 000f5240 >> (XEN) DMI 2.3 present. >> (XEN) Using APIC driver default >> (XEN) ACPI: RSDP (v000 GBT ) @ 0x000f6bf0 >> (XEN) ACPI: RSDT (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @ >> 0xbbff3000 >> (XEN) ACPI: FADT (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @ >> 0xbbff3040 >> (XEN) ACPI: SSDT (v001 PTLTD POWERNOW 0x00000001 LTP 0x00000001) @ >> 0xbbff7a40 >> (XEN) ACPI: MCFG (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @ >> 0xbbff7c80 >> (XEN) ACPI: MADT (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @ >> 0xbbff79c0 >> (XEN) ACPI: DSDT (v001 GBT AWRDACPI 0x00001000 MSFT 0x0100000c) @ >> 0x00000000 >> (XEN) ACPI: Local APIC address 0xfee00000 >> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) >> (XEN) Processor #0 15:11 APIC version 16 >> >> >> ============ BUILD PROCEDURE ==================>> # cd /usr/src/ >> # hg clone http://xenbits.xensource.com/xen-3.0.3-testing.hg >> # cd xen-3.0-3testing.hg >> # make world >> # make install >> # mkinitrd initrd.img-2.6.16.29-xen 2.6.16.29-xen >> # ln -sf initrd.img-2.6.16.29-xen initrd.img-2.6-xen >> >> --- disabled ASUS-ACPI >> # make linux-2.6-xen-config CONFIGMODE=menuconfig >> # make linux-2.6-xen-build >> # make linux-2.6-xen-install >> >> -- did the whole procedure twice.. once skipped this two >> --- steps (removed and rebuilt, as mkinitrd was >> compalaining.. >> # rm initrd.img-2.6.16.29-xen >> # mkinitrd initrd.img-2.6.16.29-xen 2.6.16.13-xen >> >> I had to manually copy xen and grub from /usr/lib/python to >> /usr/lib/python2.4/site-packages. >> Added a new entry in the menu.lst under >> grub. >> >> title Fedora Core TEST (2.6.16.29-xen) >> root (hd0,0) >> kernel /xen.gz dom0_mem=768000 >> module /vmlinuz-2.6.16.29-xen ro root=/dev/VG_Fedora/LV2 rhgb quiet >> module /initrd.img-2.6.16.29-xen >> >> booted in Test kernel. And tried to create HVM winxp domu. >> ==============>> >> >> Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote: >>> Re: [Xen-devel] RE: [Xen-users] HVM WinXP dom crash On 9/10/06 8:19 pm, >>> "jdsw" <jdsw2002@yahoo.com> wrote: >>> >>> >>>> ok.. I would not worry about the WRMSR warnings. >>>> But how do I get pass the ROMBIOS problem ? >>>> >>>> ccing devloper forum,in case someone knows about this particular issue. >>>> >>> >>> The hvmloader binary is definitely out of sync with the Xen binary >>> (hvmloader¹s SVM hypercall interface is older than the Xen that you are >>> running knows about). This might be a misfeature of the FC5 packages, >>> although I haven¹t heard anyone else report this problem. >>> >>> If you want to play with the best-possible bits right now, particularly for >>> HVM guests, I recommend you download binary tarballs when we release >>> 3.0.3-final in a few days, or grab the xen-3.0.3-testing.hg repository and >>> build it yourself. Then you¹ll know for sure that everything is in sync. >>> >>> -- Keir >>> >> >> >> >> Get your email and more, right on the new Yahoo.com >> <http://us.rd.yahoo.com/evt=42973/*http://www.yahoo.com/preview> > > > > > Want to be your own boss? Learn how on Yahoo! Small Business. > <http://us.rd.yahoo.com/evt=41244/*http://smallbusiness.yahoo.com/r-index>_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thanks Keir.
My hvmloader was old, got the dev86 package from http://www.cix.co.uk/~mayday
and rebuilt the things. Now I am passed that error.
btw, I had seen some traffic mentioning that there is no special need to build
HVM stuff on one of the mailing list, which apparently is not true.
My CDROM for windows is not bootable. Need to find the right CDROM and try it
out.
(Is there a way to kick of a windows program like setup.exe...?)
Still running in to most of other problems mentioned. I might repeat the whole
procedure soon and report result to the forum.
/Jd
Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
If youre still getting the bad hypercall message when the hvmloader runs, and
thus unable to run ROMBIOS, then your hvmloader binary is still out of date.
Where did you get 3.0.3-testing from? If you built yourself you need to download
an extra 16-bit compiler (bcc). The instructions for this are listed when you
try to build the HVM firmware (which fails to build if that compiler is absent).
Look at /usr/lib/xen/boot/hvmloader whats the timestamp on it?
-- Keir
On 16/10/06 6:47 pm, "jdsw" <jdsw2002@yahoo.com> wrote:
Resending.... can anyone help?
Thanks
/Jd
jdsw <jdsw2002@yahoo.com> wrote:
Hi
I tried using xen-3.0.3-testing.hg followed most of the stuff from
http://www.broermann.com/howto_amd_hvm.html
Still getting the same problem when I try to start WinXP domU. Same dmesg
message about ROMBIOS. I would appreciate any help getting this and related
issues resolved.
Q1 : Is the procedure ok (bit later in email) ? Do I need to do anything else ?
(One interesting thing is that the kernel version that I had installed using
yum, were 2.6.17-1.2187, while 3.0.3 testing.hg is got 2.6.16.29 !!! )
Additionaly I am seeing the following. These are put here as they might be
actual bugs or may help resolve the issue.
A .
during startup, Between xend starting and login prompt takes 2 min.!! I dont
know whats going on ?
some messages in dmesg
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 50
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 50, Value: 1
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 18
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 18, Value: 1
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 50
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 50, Value: 0
B
-- Now my network name resolution is not working. I can ping using IP addresses.
C
-- Xen is dropping 1GB memory of 4 GB!!! (see attached xm_dmesg)
Xen version 3.0.3-rc4 (root@) (gcc version 4.1.1 20060525 (Red Hat 4.1.1-1))
Thu Oct 12 22:58:53 PDT 2006
Latest ChangeSet: Thu Oct 12 19:09:08 2006 +0100 11758:946628333c31
(XEN) Command line: /xen.gz dom0_mem=768000
(XEN) WARNING: Only the first 4 GB of the physical memory map can be accessed
(XEN) by Xen in 32-bit mode. Truncating the memory map...
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009f800 (usable)
(XEN) 000000000009f800 - 00000000000a0000 (reserved)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000bbff0000 (usable)
(XEN) 00000000bbff0000 - 00000000bbff3000 (ACPI NVS)
(XEN) 00000000bbff3000 - 00000000bc000000 (ACPI data)
(XEN) 00000000f0000000 - 00000000f2000000 (reserved)
(XEN) 00000000fec00000 - 0000000100000000 (reserved)
(XEN) System RAM: 3007MB (3079740kB)
(XEN) Xen heap: 10MB (10376kB)(XEN) PAE disabled.
(XEN) found SMP MP-table at 000f5240
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 GBT ) @ 0x000f6bf0
(XEN) ACPI: RSDT (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0xbbff3000
(XEN) ACPI: FADT (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0xbbff3040
(XEN) ACPI: SSDT (v001 PTLTD POWERNOW 0x00000001 LTP 0x00000001) @ 0xbbff7a40
(XEN) ACPI: MCFG (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0xbbff7c80
(XEN) ACPI: MADT (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0xbbff79c0
(XEN) ACPI: DSDT (v001 GBT AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 15:11 APIC version 16
============ BUILD PROCEDURE ==================# cd /usr/src/
# hg clone http://xenbits.xensource.com/xen-3.0.3-testing.hg
# cd xen-3.0-3testing.hg
# make world
# make install
# mkinitrd initrd.img-2.6.16.29-xen 2.6.16.29-xen
# ln -sf initrd.img-2.6.16.29-xen initrd.img-2.6-xen
--- disabled ASUS-ACPI
# make linux-2.6-xen-config CONFIGMODE=menuconfig
# make linux-2.6-xen-build
# make linux-2.6-xen-install
-- did the whole procedure twice.. once skipped this two
--- steps (removed and rebuilt, as mkinitrd was
compalaining..
# rm initrd.img-2.6.16.29-xen
# mkinitrd initrd.img-2.6.16.29-xen 2.6.16.13-xen
I had to manually copy xen and grub from /usr/lib/python to
/usr/lib/python2.4/site-packages.
Added a new entry in the menu.lst under
grub.
title Fedora Core TEST (2.6.16.29-xen)
root (hd0,0)
kernel /xen.gz dom0_mem=768000
module /vmlinuz-2.6.16.29-xen ro root=/dev/VG_Fedora/LV2 rhgb quiet
module /initrd.img-2.6.16.29-xen
booted in Test kernel. And tried to create HVM winxp domu.
==============
Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
Re: [Xen-devel] RE: [Xen-users] HVM WinXP dom crash On 9/10/06 8:19 pm,
"jdsw" <jdsw2002@yahoo.com> wrote:
ok.. I would not worry about the WRMSR warnings.
But how do I get pass the ROMBIOS problem ?
ccing devloper forum,in case someone knows about this particular issue.
The hvmloader binary is definitely out of sync with the Xen binary (hvmloaders
SVM hypercall interface is older than the Xen that you are running knows about).
This might be a misfeature of the FC5 packages, although I havent heard anyone
else report this problem.
If you want to play with the best-possible bits right now, particularly for HVM
guests, I recommend you download binary tarballs when we release 3.0.3-final in
a few days, or grab the xen-3.0.3-testing.hg repository and build it yourself.
Then youll know for sure that everything is in sync.
-- Keir
---------------------------------
Get your email and more, right on the new Yahoo.com
<http://us.rd.yahoo.com/evt=42973/*http://www.yahoo.com/preview>
---------------------------------
Want to be your own boss? Learn how on Yahoo! Small Business.
<http://us.rd.yahoo.com/evt=41244/*http://smallbusiness.yahoo.com/r-index>
---------------------------------
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates
starting at 1¢/min.
--0-1328966363-1161192183=:69450
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
<div>Thanks Keir.</div> <div> </div>
<div>My hvmloader was old, got the dev86 package from <A
href="http://www.cix.co.uk/~mayday">http://www.cix.co.uk/~mayday</A>
and rebuilt the things. Now I am passed that error. </div>
<div> </div> <div>btw, I had seen some traffic
mentioning that there is no special need to build HVM stuff on one of the
mailing list, which apparently is not true.</div>
<div> </div> <div>My CDROM for windows is not
bootable. Need to find the right CDROM and try it out.</div>
<div>(Is there a way to kick of a windows program like
setup.exe...?)</div> <div> </div> <div>Still
running in to most of other problems mentioned. I might repeat the whole
procedure soon and report result to the forum.</div>
<div> </div> <div>/Jd</div>
<div><BR><BR><B><I>Keir Fraser
<Keir.Fraser@cl.cam.ac.uk></I></B> wrote:</div>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px;
BORDER-LEFT: #1010ff 2px solid"><FONT
face="Verdana, Helvetica, Arial"><SPAN style="FONT-SIZE:
12px">If youre still getting the bad hypercall message when the
hvmloader runs, and thus unable to run ROMBIOS, then your hvmloader binary is
still out of date. Where did you get 3.0.3-testing from? If you built yourself
you need to download an extra 16-bit compiler (bcc). The instructions for this
are listed when you try to build the HVM firmware (which fails to build if that
compiler is absent). Look at /usr/lib/xen/boot/hvmloader whats the timestamp
on it?<BR><BR> -- Keir<BR><BR>On 16/10/06 6:47
pm, "jdsw" <jdsw2002@yahoo.com>
wrote:<BR><BR></SPAN></FONT> <BLOCKQUOTE><FONT
face="Verdana, Helvetica, Arial"><SPAN style="FONT-SIZE:
12px">Resending.... can anyone
help?<BR><BR>Thanks<BR>/Jd<BR><BR><B><I>jdsw
<jdsw2002@yahoo.com></I></B>
wrote:<BR></SPAN></FONT> <BLOCKQUOTE><FONT
face="Verdana, Helvetica, Arial"><SPAN style="FONT-SIZE:
12px">Hi<BR> I tried using xen-3.0.3-testing.hg
followed most of the stuff from <BR><A
href="http://www.broermann.com/howto_amd_hvm.html">http://www.broermann.com/howto_amd_hvm.html</A><BR>Still
getting the same problem when I try to start WinXP domU. Same dmesg
message about ROMBIOS. I would appreciate any help getting this and related
issues resolved.<BR><BR>Q1 : Is the procedure ok (bit
later in email) ? Do I need to do anything else ? (One interesting thing is that
the kernel version that I had installed using yum, were 2.6.17-1.2187, while
3.0.3 testing.hg is got 2.6.16.29 !!! )<BR><BR>Additionaly I am
seeing the following. These are put here as they might be actual bugs or may
help resolve the issue.<BR><BR>A . <BR> during
startup, Between xend starting and login prompt takes 2 min.!!
I dont know whats going on ?<BR> some
messages in dmesg <BR>evbug.c: Event. Dev:
isa0060/serio0/input0, Type: 4, Code: 4, Value: 50<BR>evbug.c: Event. Dev:
isa0060/serio0/input0, Type: 1,
Code: 50, Value: 1<BR>evbug.c: Event. Dev: isa0060/serio0/input0, Type:
0, Code: 0, Value: 0<BR>evbug.c: Event. Dev: isa0060/serio0/input0, Type:
4, Code: 4, Value: 18<BR>evbug.c: Event. Dev: isa0060/serio0/input0, Type:
1, Code: 18, Value: 1<BR>evbug.c: Event. Dev: isa0060/serio0/input0, Type:
0, Code: 0, Value: 0<BR>evbug.c: Event. Dev: isa0060/serio0/input0, Type:
4, Code: 4, Value: 50<BR>evbug.c: Event. Dev: isa0060/serio0/input0, Type:
1, Code: 50, Value: 0<BR><BR>B <BR>-- Now my network
name resolution is not working. I can ping using IP
addresses.<BR><BR>C<BR>-- Xen is dropping 1GB memory of 4
GB!!! (see attached xm_dmesg)<BR> Xen version 3.0.3-rc4
(root@) (gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)) Thu Oct 12
22:58:53 PDT 2006<BR> Latest ChangeSet: Thu Oct 12 19:09:08 2006
+0100 11758:946628333c31<BR><BR>(XEN) Command line: /xen.gz
dom0_mem=768000<BR>(XEN) WARNING: Only the first 4 GB of the physical
memory map can be accessed<BR>(XEN)
by
Xen in 32-bit mode. Truncating the memory map...<BR>(XEN) Physical RAM
map:<BR>(XEN) 0000000000000000 - 000000000009f800
(usable)<BR>(XEN) 000000000009f800 - 00000000000a0000
(reserved)<BR>(XEN) 00000000000f0000 - 0000000000100000
(reserved)<BR>(XEN) 0000000000100000 - 00000000bbff0000
(usable)<BR>(XEN) 00000000bbff0000 - 00000000bbff3000 (ACPI
NVS)<BR>(XEN) 00000000bbff3000 - 00000000bc000000 (ACPI
data)<BR>(XEN) 00000000f0000000 - 00000000f2000000
(reserved)<BR>(XEN) 00000000fec00000 - 0000000100000000
(reserved)<BR>(XEN) System RAM: 3007MB (3079740kB)<BR>(XEN) Xen
heap: 10MB (10376kB)(XEN) PAE disabled.<BR>(XEN) found SMP
MP-table at 000f5240<BR>(XEN) DMI 2.3 present.<BR>(XEN) Using APIC
driver default<BR>(XEN) ACPI: RSDP (v000 GBT
)
@ 0x000f6bf0<BR>(XEN) ACPI: RSDT (v001 GBT
AWRDACPI 0x42302e31 AWRD 0x01010101) @
0xbbff3000<BR>(XEN) ACPI: FADT (v001 GBT
AWRDACPI 0x42302e31 AWRD 0x01010101) @
0xbbff3040<BR>(XEN) ACPI: SSDT (v001 PTLTD POWERNOW 0x00000001
LTP 0x00000001) @ 0xbbff7a40<BR>(XEN) ACPI: MCFG (v001 GBT
AWRDACPI 0x42302e31 AWRD 0x01010101) @
0xbbff7c80<BR>(XEN) ACPI: MADT (v001 GBT
AWRDACPI 0x42302e31 AWRD 0x01010101) @
0xbbff79c0<BR>(XEN) ACPI: DSDT (v001 GBT
AWRDACPI 0x00001000 MSFT 0x0100000c) @
0x00000000<BR>(XEN) ACPI: Local APIC address
0xfee00000<BR>(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00]
enabled)<BR>(XEN) Processor #0 15:11 APIC version
16<BR><BR><BR>=========== BUILD PROCEDURE
===================<BR># cd /usr/src/<BR># hg clone <A
href="http://xenbits.xensource.com/xen-3.0.3-testing.hg">http://xenbits.xensource.com/xen-3.0.3-testing.hg</A><BR>#
cd xen-3.0-3testing.hg<BR># make world<BR># make install<BR>#
mkinitrd initrd.img-2.6.16.29-xen 2.6.16.29-xen<BR># ln -sf
initrd.img-2.6.16.29-xen initrd.img-2.6-xen<BR><BR>--- disabled
ASUS-ACPI<BR># make linux-2.6-xen-config CONFIGMODE=menuconfig<BR>#
make linux-2.6-xen-build<BR># make
linux-2.6-xen-install<BR><BR>-- did the whole procedure twice.. once
skipped this two<BR>--- steps (removed and rebuilt, as mkinitrd
was<BR> compalaining..<BR># rm initrd.img-2.6.16.29-xen
<BR># mkinitrd initrd.img-2.6.16.29-xen
2.6.16.13-xen<BR><BR>I had to manually copy xen and grub
from /usr/lib/python to /usr/lib/python2.4/site-packages.<BR>Added a new
entry in the menu.lst under<BR> grub.<BR><BR>title
Fedora Core TEST
(2.6.16.29-xen)<BR> root
(hd0,0)<BR> kernel
/xen.gz
dom0_mem=768000<BR> module
/vmlinuz-2.6.16.29-xen ro root=/dev/VG_Fedora/LV2 rhgb
quiet<BR> module
/initrd.img-2.6.16.29-xen<BR><BR>booted in Test kernel. And tried to
create HVM winxp
domu.<BR>===============<BR><BR><BR><B><I>Keir
Fraser <Keir.Fraser@cl.cam.ac.uk></I></B>
wrote:<BR></SPAN></FONT> <BLOCKQUOTE><FONT
face="Verdana, Helvetica, Arial"><SPAN style="FONT-SIZE:
12px">Re: [Xen-devel] RE: [Xen-users] HVM WinXP dom crash
On 9/10/06 8:19 pm, "jdsw"
<jdsw2002@yahoo.com>
wrote:<BR> <BR> <BR></SPAN></FONT>
<BLOCKQUOTE><FONT face="Verdana, Helvetica,
Arial"><SPAN style="FONT-SIZE: 12px">ok.. I would not
worry about the WRMSR warnings.<BR> But how do I get pass the
ROMBIOS problem
?<BR> <BR> ccing devloper forum,in case someone
knows about this particular
issue.<BR> <BR></SPAN></FONT></BLOCKQUOTE><FONT
face="Verdana, Helvetica, Arial"><SPAN style="FONT-SIZE:
12px"><BR> The hvmloader binary is definitely out of sync
with the Xen binary (hvmloaders SVM hypercall interface is older than the Xen
that you are running knows about). This might be a misfeature of the FC5
packages, although I havent heard anyone else report this
problem.<BR> <BR> If you want to play with the
best-possible bits right now, particularly for HVM guests, I recommend you
download binary tarballs when we release 3.0.3-final in a few days, or grab the
xen-3.0.3-testing.hg repository and build it yourself. Then youll know for sure
that everything is in sync.<BR> <BR> --
Keir<BR> <BR></SPAN></FONT></BLOCKQUOTE><FONT
face="Verdana, Helvetica, Arial"><SPAN style="FONT-SIZE:
12px"><BR> <BR>
<HR
align=center width="100%" SIZE=1> Get your email and more, right
on the new Yahoo.com <A
href="http://us.rd.yahoo.com/evt=42973/*http://www.yahoo.com/preview"><http://us.rd.yahoo.com/evt=42973/*http://www.yahoo.com/preview></A>
<BR></SPAN></FONT></BLOCKQUOTE><FONT
face="Verdana, Helvetica, Arial"><SPAN style="FONT-SIZE:
12px"><BR><BR> <BR> <HR align=center
width="100%" SIZE=1> Want to be your own boss? Learn how on
Yahoo! Small Business. <A
href="http://us.rd.yahoo.com/evt=41244/*http://smallbusiness.yahoo.com/r-index"><http://us.rd.yahoo.com/evt=41244/*http://smallbusiness.yahoo.com/r-index></A>
<BR></SPAN></FONT></BLOCKQUOTE><FONT
face="Verdana, Helvetica, Arial"><SPAN style="FONT-SIZE:
12px"><BR></SPAN></FONT></BLOCKQUOTE><BR><p> 
<hr size=1>Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone
calls. <a
href="http://us.rd.yahoo.com/mail_us/taglines/postman7/*http://us.rd.yahoo.com/evt=39666/*http://messenger.yahoo.com">
Great rates starting at 1¢/min.
--0-1328966363-1161192183=:69450--
--===============1823192586=Content-Type: text/plain;
charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
--===============1823192586==--