Bug 296679 - openSuSE does not work with paravirtualized frame buffer
Summary: openSuSE does not work with paravirtualized frame buffer
Status: RESOLVED DUPLICATE of bug 285523
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: Xen (show other bugs)
Version: Alpha 7
Hardware: Other Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Clyde Griffin
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-01 22:13 UTC by Stephen Shaw
Modified: 2007-08-06 17:39 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen Shaw 2007-08-01 22:13:17 UTC 
Description:

openSuSE (paravirtualized guest) starts to boot and drops to a ncurses install.  The error message is this:

  Your computer does not fulfill all requirements for a graphical installation.     
  There is less than 96 MB memory or x server could not be started.


Steps to Reproduce:

install opensuse 10.3 alpha 7 as dom0 and try and install opensuse 10.3 alpha 7 as a domU

Comments:

This appears to be the same as bug #233847.
Comment 1 Charles Coffing 2007-08-02 17:19:11 UTC 
This is a regression compared to SLES 10 SP1, and it's very visible.  Bumping severity up.
Comment 2 Marcus Schaefer 2007-08-02 20:13:51 UTC 
reassigned to maintainer of yast2 startup scripts
Comment 3 Arvin Schnell 2007-08-03 12:24:58 UTC 
Reassigned to Xen responsible person. Bug #285523 indicates that
this is a problem of the Xen framebufer.
Comment 4 Charles Coffing 2007-08-03 15:32:57 UTC 
Framebuffer is working fine from Xen's point of view.  The openSUSE 10.3 VM comes up using the PVFB, but yast displays text.  So the PVFB driver is working fine.  The problem is that the installer does not opt to go graphical.

Again, this is the same problem that was solved in bug #233847, which from my understanding of the discussion in that bug, was ultimately a change in sax2.
Comment 5 Charles Coffing 2007-08-06 17:39:15 UTC 

*** This bug has been marked as a duplicate of bug 285523 ***