On Tue, 2010年01月26日 at 14:30 -0500, David P. Quigley wrote:
> I have a small update on the problem. It does seem like it is tied to
> VT-D because I just turned it off in the bios and the dom0 manages to
> boot on top of xen and I can log in. Are there any options for VT-D that
> you would like me to try to help pin point the problem?
>
> Dave
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel 
So I've managed to get my dom0 booting on top of xen however now I'm
running into a problem where my domU is kernel oopsing on startup. The
traces I've gotten seem to be in the memory allocation functions.
Normally this is a sign of memory corruption. Considering this VM was
working perfectly with the 2.6.31.10 dom0 based on the Novell patches
and xen 4.0 I don't think it is the VM that is the problem (however I
can try starting it under kvm to be certain. Any suggestions on what I
can do to try to hunt down the memory corruption?
Dave
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel