Hi
Trying to get WinXP HVM to install as domU on AMD. Got latest Xen Kernel and
Xen package (NOT unstable or debug).
When start, a window pops up for few seconds.. then it dies and another one
comes up... and it disappears too. (Xen is trying to restart and giving up
because the restart happens in 2 seconds..) It seems DomU is not able to
read/understand something from Cirrus VGABIOS.
Any ideas on getting this to work ? Do I need to change some bios setting ?
Please see details below.
Thanks
/Jd
OS :
-----
Linux 2.6.17-1.2187_FC5xen0 #1 SMP Mon Sep 11 02:05:21 EDT 2006 i686 athlon
i386 GNU/Linux
Xen :
-----
xen-3.0.2-3.FC5
------ config ------
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 500
name = "WinXP"
vif = [ ''type=ioemu, bridge=xenbr0'' ]
disk = [ ''phy:/dev/VG_PL1/winxp,ioemu:hda,w'' ]
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
cdrom=''/dev/hda''
boot=''d''
sdl=1
vnc=0
vncviewer=0
stdvga=0
serial=''pty''
ne2000=0
---------------------------
xm dmesg
======bunch of lines... similar to below line....
(XEN) (file=traps.c, line=1385) Domain attempted WRMSR c0010041 from
00000001:00000e0e to 00000190:00010e02.
(XEN) (file=traps.c, line=1385) Domain attempted WRMSR c0010041 from
00000001:00000e0e to 00000190:00010e02.
and then...
(XEN) (file=hvm.c, line=196) Allocated port 4 for hvm.
(XEN) (GUEST: 1) HVM Loader
(XEN) (GUEST: 1) Loading ROMBIOS ...
(XEN) (GUEST: 1) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 1) SVM go ...
(XEN) (file=hvm.c, line=385) HVM vcpu 1:0 did a bad hypercall 1480936960.
(XEN) (GUEST: 1) Failed to invoke ROMBIOS
(XEN) Guest shutdown exit
(XEN) domain_crash_sync called from svm.c:2999
(XEN) Domain 1 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 0
(XEN) EIP: 0000:[<00100039>]
(XEN) EFLAGS: 00000246 CONTEXT: hvm
(XEN) eax: 00000000 ebx: 00000000 ecx: 00129ae8 edx: 000000e9
(XEN) esi: 00000000 edi: 00000000 ebp: 00129ae8 esp: 00129ae8
(XEN) cr0: 0005003b cr3: 00000000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: 0000
=
---------------------------------
How low will we go? Check out Yahoo! Messengers low PC-to-Phone call rates.
--0-1143968988-1160267422=:30269
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Hi<br> Trying to get WinXP HVM to install as domU on
AMD. Got latest Xen Kernel and Xen package (NOT unstable or debug).
<br><br>When start, a window pops up for few seconds..
then it dies and another one comes up... and it disappears too. (Xen is trying
to restart and giving up because the restart happens in 2 seconds..) It seems
DomU is not able to read/understand something from Cirrus VGABIOS.
<br><br> Any ideas on getting this to work ? Do
I need to change some bios setting ?<br> Please see
details below.<br>Thanks<br>/Jd<br><br><br>OS
:<br>-----<br>Linux 2.6.17-1.2187_FC5xen0 #1 SMP Mon Sep
11 02:05:21 EDT 2006 i686 athlon i386 GNU/Linux<br>Xen
:<br>-----<br>xen-3.0.2-3.FC5<br><br>------ config
------<br>import os, re<br>arch = os.uname()[4]<br>if
re.search(''64'', arch):<br>
arch_libdir =
''lib64''<br>else:<br>
arch_libdir = ''lib''<br>kernel
"/usr/lib/xen/boot/hvmloader"<br>builder=''hvm''<br>memory
= 500<br>name = "WinXP"<br>vif = [ ''type=ioemu,
bridge=xenbr0'' ]<br>disk = [
''phy:/dev/VG_PL1/winxp,ioemu:hda,w'' ]<br>device_model =
''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''<br>cdrom=''/dev/hda''<br>boot=''d''<br>sdl=1<br>vnc=0<br>vncviewer=0<br>stdvga=0<br>serial=''pty''<br>ne2000=0<br>---------------------------<br><br>xm
dmesg <br>=======<br>bunch of lines... similar to below
line....<br><br>(XEN) (file=traps.c, line=1385) Domain attempted
WRMSR c0010041 from 00000001:00000e0e to 00000190:00010e02.<br>(XEN)
(file=traps.c, line=1385) Domain attempted WRMSR c0010041 from 00000001:00000e0e
to 00000190:00010e02.<br><br>and then... <br><br>(XEN)
(file=hvm.c, line=196) Allocated port 4 for hvm.<br>(XEN) (GUEST: 1) HVM
Loader<br>(XEN) (GUEST: 1) Loading ROMBIOS ...<br>(XEN) (GUEST: 1)
Loading Cirrus VGABIOS ...<br>(XEN) (GUEST: 1) SVM go ...<br>(XEN)
(file=hvm.c, line=385) HVM vcpu 1:0 did a bad hypercall
1480936960.<br>(XEN) (GUEST: 1) Failed to invoke ROMBIOS<br>(XEN)
Guest shutdown exit<br>(XEN) domain_crash_sync called from
svm.c:2999<br>(XEN) Domain 1 (vcpu#0) crashed on cpu#0:<br>(XEN)
----[ Xen-3.0-unstable Not tainted
]----<br>(XEN) CPU: 0<br>(XEN)
EIP:
0000:[<00100039>]<br>(XEN) EFLAGS:
00000246 CONTEXT: hvm<br>(XEN) eax:
00000000 ebx: 00000000 ecx:
00129ae8 edx: 000000e9<br>(XEN) esi:
00000000 edi: 00000000 ebp:
00129ae8 esp: 00129ae8<br>(XEN) cr0:
0005003b cr3: 00000000<br>(XEN) ds:
0000 es: 0000 fs:
0000 gs: 0000 ss:
0000 cs:
0000<br>==<br><br><br><br><p> 
<hr size=1>How low will we go? Check out Yahoo! Messengers low <a
href="http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com">
PC-to-Phone call rates.
--0-1143968988-1160267422=:30269--
--===============1005680109=Content-Type: text/plain;
charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
--===============1005680109==--
--- sending again-- (seems did not reach the list last time)
Hi
Trying to get WinXP HVM to install as domU on AMD. Got latest Xen Kernel and
Xen package (NOT unstable or debug).
When start, a window pops up for few seconds.. then it dies and another one
comes up... and it disappears too. (Xen is trying to restart and giving up
because the restart happens in 2 seconds..) It seems DomU is not able to
read/understand something from Cirrus VGABIOS.
Any ideas on getting this to work ? Do I need to change some bios setting ?
Please see details below.
Thanks
/Jd
OS :
-----
Linux 2.6.17-1.2187_FC5xen0 #1 SMP Mon Sep 11 02:05:21 EDT 2006 i686 athlon
i386 GNU/Linux
Xen :
-----
xen-3.0.2-3.FC5
------ config ------
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 500
name = "WinXP"
vif = [ ''type=ioemu, bridge=xenbr0'' ]
disk = [ ''phy:/dev/VG_PL1/winxp,ioemu:hda,w'' ]
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
cdrom=''/dev/hda''
boot=''d''
sdl=1
vnc=0
vncviewer=0
stdvga=0
serial=''pty''
ne2000=0
---------------------------
xm dmesg
======bunch of lines... similar to below line....
(XEN) (file=traps.c, line=1385) Domain attempted WRMSR c0010041 from
00000001:00000e0e to 00000190:00010e02.
(XEN) (file=traps.c, line=1385) Domain attempted WRMSR c0010041 from
00000001:00000e0e to 00000190:00010e02.
and then...
(XEN) (file=hvm.c, line=196) Allocated port 4 for hvm.
(XEN) (GUEST: 1) HVM Loader
(XEN) (GUEST: 1) Loading ROMBIOS ...
(XEN) (GUEST: 1) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 1) SVM go ...
(XEN) (file=hvm.c, line=385) HVM vcpu 1:0 did a bad hypercall 1480936960.
(XEN) (GUEST: 1) Failed to invoke ROMBIOS
(XEN) Guest shutdown exit
(XEN) domain_crash_sync called from svm.c:2999
(XEN) Domain 1 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 0
(XEN) EIP: 0000:[<00100039>]
(XEN) EFLAGS: 00000246 CONTEXT: hvm
(XEN) eax: 00000000 ebx: 00000000 ecx: 00129ae8 edx: 000000e9
(XEN) esi: 00000000 edi: 00000000 ebp: 00129ae8 esp: 00129ae8
(XEN) cr0: 0005003b cr3: 00000000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: 0000
=
---------------------------------
How low will we go? Check out Yahoo! Messengers low PC-to-Phone call rates.
---------------------------------
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates
starting at 1¢/min.
--0-1402156010-1160270883=:68177
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
<blockquote class="replbq" style="border-left: 2px solid
rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">--- sending
again-- (seems did not reach the list last time)<br>Hi<br>
Trying to get WinXP HVM to install as domU on AMD. Got latest Xen
Kernel and Xen package (NOT unstable or debug). <br><br>When start,
a window pops up for few seconds.. then it dies and another one comes
up... and it disappears too. (Xen is trying to restart and giving up because the
restart happens in 2 seconds..) It seems DomU is not able to read/understand
something from Cirrus VGABIOS.
<br><br> Any ideas on getting this to work ? Do
I need to change some bios setting ?<br> Please see
details below.<br>Thanks<br>/Jd<br><br><br>OS
:<br>-----<br>Linux 2.6.17-1.2187_FC5xen0 #1 SMP Mon Sep
11 02:05:21 EDT 2006 i686 athlon i386 GNU/Linux<br>Xen
:<br>-----<br>xen-3.0.2-3.FC5<br><br>------ config
------<br>import os, re<br>arch os.uname()[4]<br>if
re.search(''64'', arch):<br>
arch_libdir =
''lib64''<br>else:<br>
arch_libdir = ''lib''<br>kernel =
"/usr/lib/xen/boot/hvmloader"<br>builder=''hvm''<br>memory
= 500<br>name = "WinXP"<br>vif = [ ''type=ioemu,
bridge=xenbr0'' ]<br>disk = [
''phy:/dev/VG_PL1/winxp,ioemu:hda,w'' ]<br>device_model =
''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''<br>cdrom=''/dev/hda''<br>boot=''d''<br>sdl=1<br>vnc=0<br>vncviewer=0<br>stdvga=0<br>serial=''pty''<br>ne2000=0<br>---------------------------<br><br>xm
dmesg <br>=======<br>bunch of lines... similar to below
line....<br><br>(XEN) (file=traps.c, line=1385) Domain attempted
WRMSR c0010041 from 00000001:00000e0e to 00000190:00010e02.<br>(XEN)
(file=traps.c, line=1385) Domain attempted WRMSR c0010041 from 00000001:00000e0e
to 00000190:00010e02.<br><br>and then... <br><br>(XEN)
(file=hvm.c, line=196) Allocated port 4 for hvm.<br>(XEN) (GUEST: 1) HVM
Loader<br>(XEN) (GUEST: 1) Loading ROMBIOS ...<br>(XEN)
(GUEST: 1) Loading Cirrus VGABIOS ...<br>(XEN) (GUEST: 1) SVM go
...<br>(XEN) (file=hvm.c, line=385) HVM vcpu 1:0 did a bad hypercall
1480936960.<br>(XEN) (GUEST: 1) Failed to invoke ROMBIOS<br>(XEN)
Guest shutdown exit<br>(XEN) domain_crash_sync called from
svm.c:2999<br>(XEN) Domain 1 (vcpu#0) crashed on cpu#0:<br>(XEN)
----[ Xen-3.0-unstable Not tainted
]----<br>(XEN) CPU: 0<br>(XEN)
EIP:
0000:[<00100039>]<br>(XEN) EFLAGS:
00000246 CONTEXT: hvm<br>(XEN) eax:
00000000 ebx: 00000000 ecx:
00129ae8 edx: 000000e9<br>(XEN) esi:
00000000 edi: 00000000 ebp:
00129ae8 esp: 00129ae8<br>(XEN) cr0:
0005003b cr3: 00000000<br>(XEN) ds:
0000 es: 0000 fs:
0000 gs: 0000 ss:
0000 cs:
0000<br>==<br><br><br><br><div>
</div><hr size="1">How low will we go? Check out Yahoo!
Messengers low <a
href="http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com">
PC-to-Phone call rates.</a></blockquote><a
href="http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com"><br></a><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-1402156010-1160270883=:68177--
--===============1756017317=Content-Type: text/plain;
charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
--===============1756017317==--
On 10/8/06, jd_jedi@users.sourceforge.net <jdsw2002@yahoo.com> wrote:> Hi > Trying to get WinXP HVM to install as domU on AMD. Got latest Xen Kernel > and Xen package (NOT unstable or debug).I have no good experience with 3.0.2, also. Maybe you try 3.0.3-testing and see if it gets better... Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
________________________________
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of
jd_jedi@users.sourceforge.net
Sent: 08 October 2006 01:30
To: xen-users@lists.xensource.com
Subject: [Xen-users] HVM WinXP dom crash
Hi
Trying to get WinXP HVM to install as domU on AMD. Got latest
Xen Kernel and Xen package (NOT unstable or debug).
When start, a window pops up for few seconds.. then it dies and
another one comes up... and it disappears too. (Xen is trying to restart
and giving up because the restart happens in 2 seconds..) It seems DomU
is not able to read/understand something from Cirrus VGABIOS.
Any ideas on getting this to work ? Do I need to change some
bios setting ?
Please see details below.
Thanks
/Jd
OS :
-----
Linux 2.6.17-1.2187_FC5xen0 #1 SMP Mon Sep 11 02:05:21 EDT 2006
i686 athlon i386 GNU/Linux
Xen :
-----
xen-3.0.2-3.FC5
------ config ------
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 500
name = "WinXP"
vif = [ ''type=ioemu, bridge=xenbr0'' ]
disk = [ ''phy:/dev/VG_PL1/winxp,ioemu:hda,w'' ]
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
cdrom=''/dev/hda''
boot=''d''
sdl=1
vnc=0
vncviewer=0
stdvga=0
serial=''pty''
ne2000=0
---------------------------
xm dmesg
====== bunch of lines... similar to below line....
(XEN) (file=traps.c, line=1385) Domain attempted WRMSR c0010041
from 00000001:00000e0e to 00000190:00010e02.
(XEN) (file=traps.c, line=1385) Domain attempted WRMSR c0010041
from 00000001:00000e0e to 00000190:00010e02.
Completely harmless warnings. Explanation: This is the powernow driver
(or something else accessing PowerNow! registers) - it''s being ignored,
so I wouldn''t worry about it - there is a patch that adds those
MSR''s to
the msr-white-list in traps.c, but for all intents and purposes, it''s
only going to slow your processor down (from 11x to 5x multiplier, if I
read the tables and binaries right) if it were successfull in writing
the register - which may be useful if this is a laptop, but otherwise I
wouldn''t worry about it. If you don''t want to see these
things, I''d
suggest you remove the PowerNow! driver from Dom0.
and then...
(XEN) (file=hvm.c, line=196) Allocated port 4 for hvm.
(XEN) (GUEST: 1) HVM Loader
(XEN) (GUEST: 1) Loading ROMBIOS ...
(XEN) (GUEST: 1) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 1) SVM go ...
(XEN) (file=hvm.c, line=385) HVM vcpu 1:0 did a bad hypercall
1480936960.
(XEN) (GUEST: 1) Failed to invoke ROMBIOS
This is wrong and why things aren''t working. I''m not sure if
it''s
because your ROMBIOS is build incorrectly or something else...
Bad hypercall is definitely not right here - it seems like the BIOS and
the Hypervisor are disagreeing on how to "boot" the machine. Since it
fails, the system shuts down, which isn''t really a crash -
it''s a
failure with a "controlled emergency landing".
--
Mats
(XEN) Guest shutdown exit
(XEN) domain_crash_sync called from svm.c:2999
(XEN) Domain 1 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 0
(XEN) EIP: 0000:[<00100039>]
(XEN) EFLAGS: 00000246 CONTEXT: hvm
(XEN) eax: 00000000 ebx: 00000000 ecx: 00129ae8 edx:
000000e9
(XEN) esi: 00000000 edi: 00000000 ebp: 00129ae8 esp:
00129ae8
(XEN) cr0: 0005003b cr3: 00000000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs:
0000
=
________________________________
How low will we go? Check out Yahoo! Messenger''s low PC-to-Phone
call rates.
<http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.co
m/evt=39663/*http://voice.yahoo.com>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
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.
/Jd
"Petersson, Mats" <Mats.Petersson@amd.com> wrote:
---------------------------------
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of
jd_jedi@users.sourceforge.net
Sent: 08 October 2006 01:30
To: xen-users@lists.xensource.com
Subject: [Xen-users] HVM WinXP dom crash
Hi
Trying to get WinXP HVM to install as domU on AMD. Got latest Xen Kernel
and Xen package (NOT unstable or debug).
When start, a window pops up for few seconds.. then it dies and another one
comes up... and it disappears too. (Xen is trying to restart and giving up
because the restart happens in 2 seconds..) It seems DomU is not able to
read/understand something from Cirrus VGABIOS.
Any ideas on getting this to work ? Do I need to change some bios setting
?
Please see details below.
Thanks
/Jd
OS :
-----
Linux 2.6.17-1.2187_FC5xen0 #1 SMP Mon Sep 11 02:05:21 EDT 2006 i686 athlon
i386 GNU/Linux
Xen :
-----
xen-3.0.2-3.FC5
------ config ------
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 500
name = "WinXP"
vif = [ ''type=ioemu, bridge=xenbr0'' ]
disk = [ ''phy:/dev/VG_PL1/winxp,ioemu:hda,w'' ]
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
cdrom=''/dev/hda''
boot=''d''
sdl=1
vnc=0
vncviewer=0
stdvga=0
serial=''pty''
ne2000=0
---------------------------
xm dmesg
======bunch of lines... similar to below line....
(XEN) (file=traps.c, line=1385) Domain attempted WRMSR c0010041 from
00000001:00000e0e to 00000190:00010e02.
(XEN) (file=traps.c, line=1385) Domain attempted WRMSR c0010041 from
00000001:00000e0e to 00000190:00010e02.
Completely harmless warnings. Explanation: This is the powernow driver (or
something else accessing PowerNow! registers) - it''s being ignored, so
I wouldn''t worry about it - there is a patch that adds those
MSR''s to the msr-white-list in traps.c, but for all intents and
purposes, it''s only going to slow your processor down (from 11x to 5x
multiplier, if I read the tables and binaries right) if it were successfull in
writing the register - which may be useful if this is a laptop, but otherwise I
wouldn''t worry about it. If you don''t want to see these
things, I''d suggest you remove the PowerNow! driver from Dom0.
and then...
(XEN) (file=hvm.c, line=196) Allocated port 4 for hvm.
(XEN) (GUEST: 1) HVM Loader
(XEN) (GUEST: 1) Loading ROMBIOS ...
(XEN) (GUEST: 1) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 1) SVM go ...
(XEN) (file=hvm.c, line=385) HVM vcpu 1:0 did a bad hypercall 1480936960.
(XEN) (GUEST: 1) Failed to invoke ROMBIOS
This is wrong and why things aren''t working. I''m not sure if
it''s because your ROMBIOS is build incorrectly or something else...
Bad hypercall is definitely not right here - it seems like the BIOS and the
Hypervisor are disagreeing on how to "boot" the machine. Since it
fails, the system shuts down, which isn''t really a crash -
it''s a failure with a "controlled emergency landing".
--
Mats
(XEN) Guest shutdown exit
(XEN) domain_crash_sync called from svm.c:2999
(XEN) Domain 1 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 0
(XEN) EIP: 0000:[<00100039>]
(XEN) EFLAGS: 00000246 CONTEXT: hvm
(XEN) eax: 00000000 ebx: 00000000 ecx: 00129ae8 edx: 000000e9
(XEN) esi: 00000000 edi: 00000000 ebp: 00129ae8 esp: 00129ae8
(XEN) cr0: 0005003b cr3: 00000000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: 0000
=
---------------------------------
How low will we go? Check out Yahoo! Messengers low PC-to-Phone call
rates._______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
---------------------------------
Get your email and more, right on the new Yahoo.com
--0-753737649-1160421591=:50434
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
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>/Jd<br><br><br><b><i>"Petersson,
Mats" <Mats.Petersson@amd.com></i></b>
wrote:<blockquote class="replbq" style="border-left: 2px solid
rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> <meta
http-equiv="Content-Type" content="text/html;
charset=us-ascii"> <meta content="MSHTML 6.00.2900.2963"
name="GENERATOR"> <div dir="ltr"
align="left"><font color="#0000ff"
face="Arial"
size="2"></font> </div><br>
<blockquote style="border-left: 2px solid rgb(0, 0, 255); padding-left:
5px; margin-left: 5px; margin-right: 0px;"> <div
class="OutlookMessageHeader" dir="ltr"
align="left" lang="en-us"> <hr
tabindex="-1"> <font face="Tahoma"
size="2"><b>From:</b>
xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] <b>On Behalf Of
</b>jd_jedi@users.sourceforge.net<br><b>Sent:</b> 08
October 2006 01:30<br><b>To:</b>
xen-users@lists.xensource.com<br><b>Subject:</b>
[Xen-users] HVM WinXP dom crash<br></font><br></div>
<div></div> <div>Hi<br> Trying to get WinXP
HVM to install as domU on AMD. Got latest Xen Kernel and Xen
package (NOT unstable or debug). <br><br>When start, a window
pops up for few seconds.. then it dies and another one comes up...
and it disappears too. (Xen is trying to restart and giving up because the
restart happens in 2 seconds..) It seems DomU is not able to read/understand
something from Cirrus VGABIOS.
<br><br> Any ideas on getting this to work ?
Do I need to change some bios setting ?<br> Please
see details below.<br>Thanks<br>/Jd<br><br><br>OS
:<br>-----<br>Linux 2.6.17-1.2187_FC5xen0 #1 SMP Mon Sep
11 02:05:21 EDT 2006 i686 athlon i386 GNU/Linux<br>Xen
:<br>-----<br>xen-3.0.2-3.FC5<br><br>------ config
------<br>import os, re<br>arch = os.uname()[4]<br>if
re.search(''64'', arch):<br>
arch_libdir =
''lib64''<br>else:<br>
arch_libdir = ''lib''<br>kernel =
"/usr/lib/xen/boot/hvmloader"<br>builder=''hvm''<br>memory
= 500<br>name = "WinXP"<br>vif = [
''type=ioemu, bridge=xenbr0'' ]<br>disk = [
''phy:/dev/VG_PL1/winxp,ioemu:hda,w'' ]<br>device_model =
''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''<br>cdrom=''/dev/hda''<br>boot=''d''<br>sdl=1<br>vnc=0<br>vncviewer=0<br>stdvga=0<br>serial=''pty''<br>ne2000=0<br>---------------------------<br><br>xm
dmesg <br>=======<br>bunch of lines... similar to below
line....<br><br>(XEN) (file=traps.c, line=1385) Domain attempted
WRMSR c0010041 from 00000001:00000e0e to 00000190:00010e02.<br>(XEN)
(file=traps.c, line=1385) Domain attempted WRMSR c0010041 from
00000001:00000e0e to 00000190:00010e02.<span
class="382592009-09102006"><font
color="#0000ff" face="Arial"
size="2"> </font></span></div>
<div><span
class="382592009-09102006"></span> </div></blockquote>
<div><span class="382592009-09102006"><font
color="#0000ff" face="Arial"
size="2">Completely harmless warnings. Explanation: This is the
powernow driver (or something else accessing PowerNow! registers) -
it''s being ignored, so I wouldn''t worry about it -
there is a patch that adds those MSR''s to the msr-white-list in
traps.c, but for all intents and purposes, it''s only going to slow
your processor down (from 11x to 5x multiplier, if I read the tables
and binaries right) if it were successfull in writing the register -
which may be useful if this is a laptop, but otherwise I wouldn''t worry
about it. If you don''t want to see these things, I''d suggest
you remove the PowerNow! driver from Dom0.
</font></span></div> <blockquote style="border-left:
2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px;
margin-right: 0px;"> <div><span
class="382592009-09102006"><font color="#0000ff"
face="Arial"
size="2"></font></span> </div>
<div><span
class="382592009-09102006"> </span><br>and
then... <br><br>(XEN) (file=hvm.c, line=196) Allocated port 4 for
hvm.<br>(XEN) (GUEST: 1) HVM Loader<br>(XEN) (GUEST: 1) Loading
ROMBIOS ...<br>(XEN) (GUEST: 1) Loading Cirrus VGABIOS
...<br>(XEN) (GUEST: 1) SVM go ...<br>(XEN) (file=hvm.c,
line=385) HVM vcpu 1:0 did a bad hypercall 1480936960.<br>(XEN) (GUEST: 1)
Failed to invoke ROMBIOS<span
class="382592009-09102006"><font color="#0000ff"
face="Arial"
size="2"> </font></span></div>
<div><span
class="382592009-09102006"></span> </div></blockquote>
<div><span class="382592009-09102006"><font
color="#0000ff" face="Arial" size="2">This is
wrong and why things aren''t working. I''m not sure if
it''s because your ROMBIOS is build incorrectly or something else...
</font></span></div> <div><span
class="382592009-09102006"><font color="#0000ff"
face="Arial"
size="2"></font></span> </div>
<div><span class="382592009-09102006"><font
color="#0000ff" face="Arial" size="2">Bad
hypercall is definitely not right here - it seems like the BIOS and the
Hypervisor are disagreeing on how to "boot" the machine. Since it
fails, the system shuts down, which isn''t really a crash -
it''s a failure with a "controlled emergency landing".
</font></span></div> <div><span
class="382592009-09102006"><font color="#0000ff"
face="Arial"
size="2"></font></span> </div>
<div><span class="382592009-09102006"><font
color="#0000ff" face="Arial"
size="2">--</font></span></div>
<div><span class="382592009-09102006"><font
color="#0000ff" face="Arial"
size="2">Mats</font></span></div> <blockquote
style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px;
margin-left: 5px; margin-right: 0px;"> <div><span
class="382592009-09102006"> </span><br>(XEN)
Guest shutdown
exit<br>(XEN) domain_crash_sync called from svm.c:2999<span
class="382592009-09102006"><font color="#0000ff"
face="Arial"
size="2"> </font></span><span
class="382592009-09102006"> </span><br>(XEN)
Domain 1 (vcpu#0) crashed on cpu#0:<br>(XEN) ----[
Xen-3.0-unstable Not tainted
]----<br>(XEN) CPU: 0<br>(XEN)
EIP:
0000:[<00100039>]<br>(XEN) EFLAGS:
00000246 CONTEXT: hvm<br>(XEN) eax:
00000000 ebx: 00000000 ecx:
00129ae8 edx: 000000e9<br>(XEN) esi:
00000000 edi: 00000000 ebp:
00129ae8 esp: 00129ae8<br>(XEN) cr0:
0005003b cr3: 00000000<br>(XEN) ds:
0000 es: 0000 fs:
0000 gs: 0000 ss:
0000 cs:
0000<br>==<br><br><br><br></div>
<div> </div><hr size="1"> How low will we go?
Check out Yahoo! Messengers low <a
href="http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com">PC-to-Phone
call
rates.</a></blockquote>_______________________________________________<br>Xen-users
mailing
list<br>Xen-users@lists.xensource.com<br>http://lists.xensource.com/xen-users</blockquote><br><p> 
<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>
--0-753737649-1160421591=:50434--
--===============0374556361=Content-Type: text/plain;
charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
--===============0374556361==--
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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
--0-107763791-1160724814=:56377
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
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
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><p> 
<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>
--0-107763791-1160724814=:56377--
--===============2051573388=Content-Type: text/plain;
charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
--===============2051573388==--