Re: [Xen-devel] BAR 0: cirrusfb load errors prevent hvm domu from getting resolutions above 800x600

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 21.11.11 at 01:01, jim burns <jim_burn@xxxxxxxxxxxxx> wrote:
> I meant is a BAR 0: error a commonly understood problem with common steps to 
> find and fix the *configuration* problem, not where can I tinker with kernel 
> code. I would think suse's 2.6.37.1-1.2-desktop kernel would work as is in an 
> hvm domain. Or should he be using a different suse kernel 'flavor'? (-
> default?) Although, since it doesn't work for his hand-compiled 3.1 either, 
> this looks more like a filesystem / sysconfig configuration problem.

Using any fb driver other than VESA and the DRM base ones is - afaik -
uncommon, if not unsupported.

> Actually, he is loading the xorg cirrus module. It loads two candidates - 
> vesa 
> & cirrus. Then it unloads vesa in favor of the better cirrus candidate. 
> Unfortunately, after running through all the possible modes, it only 
> accepts:
> 
> [    33.240] (--) CIRRUS(0): Virtual size is 800x600 (pitch 1024)
> [    33.240] (**) CIRRUS(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 
> 60.3 
> Hz
> [    33.240] (II) CIRRUS(0): Modeline "800x600"x60.3   40.00  800 840 968 
> 1056  
> 600 601 605 628 +hsync +vsync (37.9 kHz)
> [    33.240] (**) CIRRUS(0): *Default mode "800x600": 36.0 MHz, 35.2 kHz, 
> 56.2 
> Hz
> [    33.240] (II) CIRRUS(0): Modeline "800x600"x56.2   36.00  800 824 896 
> 1024  
> 600 601 603 625 +hsync +vsync (35.2 kHz)
> [    33.240] (**) CIRRUS(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 
> 59.9 
> Hz
> [    33.240] (II) CIRRUS(0): Modeline "640x480"x59.9   25.18  640 656 752 
> 800  
> 480 490 492 525 -hsync -vsync (31.5 kHz)
> [    33.240] (==) CIRRUS(0): DPI set to (96, 96)

That's something that may need looking at from the X side then. And
again, it may well be that 800x600 is all that's supposed to be
supported for a HVM guest here (i.e. anything beyond might be
considered a feature request rather than a bug, but it may also be
that all you need is some extension to the default monitor definition
[which admittedly shouldn't be really meaningful in a virtual environment]).

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel