RE: dom0 issues with switching from X to console orstarting X

RE: dom0 issues with switching from X to console orstarting X

[Dugger, Donald D]

Jan-

If you are running fully virtualized guests then Jun Nakajima fixed a
problem that was put into the Xen unstable tree this morning that was
probably affecting you.  The page table entry for page 0 was getting
corrupted after the first fully virtualized guest ran, causing problems
for X.  I'd try the latest Xen unstable tree and see if that fixes your
problem.

--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Donald.D.Dugger@intel.com
Ph: (303)440-1368 

>-----Original Message-----
>From: xen-devel-bounces@lists.xensource.com 
>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Jan Beulich
>Sent: Wednesday, May 31, 2006 10:05 AM
>To: xen-devel@lists.xensource.com
>Subject: [Xen-devel] dom0 issues with switching from X to 
>console orstarting X
>
>We are seeing a number of machines that (simply running dom0) 
>either fail to start X (for reasons other than the machine
>in native mode only working via the frame buffer driver) or 
>fail to switch from (or back to) X to one of the consoles.
>This normally looks like a hang, though at least in some cases 
>it's only X apparently sitting in an endless loop. From
>looking at data so far obtained from these systems this 
>appears to be an issue with accessing the video BIOS, in either
>not being to properly run this in vm86 mode (on 32 bits) or 
>under emulation (on 64 bits). Has anyone seen similar
>behavior and possibly knows more about this?
>
>Thanks, Jan
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>

RE: dom0 issues with switching from X to console orstarting X

[Jan Beulich]

No - as said in the original description, we see this with solely running dom0. Jan

>>> "Dugger, Donald D" <donald.d.dugger@intel.com> 01.06.06 00:57 >>>
Jan-

If you are running fully virtualized guests then Jun Nakajima fixed a
problem that was put into the Xen unstable tree this morning that was
probably affecting you.  The page table entry for page 0 was getting
corrupted after the first fully virtualized guest ran, causing problems
for X.  I'd try the latest Xen unstable tree and see if that fixes your
problem.

--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Donald.D.Dugger@intel.com 
Ph: (303)440-1368 

>-----Original Message-----
>From: xen-devel-bounces@lists.xensource.com 
>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Jan Beulich
>Sent: Wednesday, May 31, 2006 10:05 AM
>To: xen-devel@lists.xensource.com 
>Subject: [Xen-devel] dom0 issues with switching from X to 
>console orstarting X
>
>We are seeing a number of machines that (simply running dom0) 
>either fail to start X (for reasons other than the machine
>in native mode only working via the frame buffer driver) or 
>fail to switch from (or back to) X to one of the consoles.
>This normally looks like a hang, though at least in some cases 
>it's only X apparently sitting in an endless loop. From
>looking at data so far obtained from these systems this 
>appears to be an issue with accessing the video BIOS, in either
>not being to properly run this in vm86 mode (on 32 bits) or 
>under emulation (on 64 bits). Has anyone seen similar
>behavior and possibly knows more about this?
>
>Thanks, Jan
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com 
>http://lists.xensource.com/xen-devel 
>

Xen on ARM

[Philip Reames]

Hey all,
    I was wondering if anyone out there knew of any work to port Xen to ARM? 
Has there been anything done on this so far?

Thanks,
Philip Reames