WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] OpenSuse 11 hvm domU: screen resolution up to 640x480

To: jim burns <jim_burn@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] OpenSuse 11 hvm domU: screen resolution up to 640x480
From: Flavio <fbcyborg@xxxxxxxxx>
Date: Wed, 16 Nov 2011 10:47:32 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx, "Fajar A. Nugraha" <list@xxxxxxxxx>
Delivery-date: Wed, 16 Nov 2011 01:51:27 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=zum2SWtKAlaHauuMDunRfK2kYo1CPqk7yR1u/55VsQ8=; b=f9JSKHtbznVWE1a0gD6nj6eX4YCFrbfQct2CbXOor1CO/okSFDNnWoUt+cuu3Gb7wf nm6SPAqIs6Ap/jOK3nToa/p3wOl496CgKtfQq0t2Lp4WEuHvLKNvUMQhW4/+iKII13nl Rpl6+FN8hB+NhtLNaiXozBztIXdrcCfl/YrWg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <2018795.uE019qUBdA@dell4550>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <7877809.94pu0BOf0I@dell4550> <CAP8Jb=qGoU_+37_L7ViMn8uFM8GHCTZEW2Q+ONHD49nKWemMJA@xxxxxxxxxxxxxx> <1652090.dmCdkglHEM@dell4550> <2018795.uE019qUBdA@dell4550>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 15 November 2011 23:20, jim burns <jim_burn@xxxxxxxxxxxxx> wrote:
> At any rate, it is a boot optimization routine, and the errors can
> be ignored without concern. From 'rpm -qi preload-kmp-default', the
> Description field says:
>
> This will work with preload hand in hand to make sure no unnecessary
> files are preload.
In my case it says:
package preload-kmp-default is not installed
Actually, even if I try to install it, there is no package for 3.0.1 kernel.

>
> and 'rpm -qi preload' says:
>
> Preload lists files to load into the system cache. This shortens system
> boot time if used correctly.
OK

> Yeah, no response from Fajar, yet. I'll repost the problem with a different
> Subject line tomorrow, if no one responds.
OK, maybe Fajar is very busy in this days. No pressure for him! :)

On 16 November 2011 00:45, jim burns <jim_burn@xxxxxxxxxxxxx> wrote:
>
> Hmm - I'm reading the man page for qemu, and came across this sub-option to
> the -vga type option:
>
>           std Standard VGA card with Bochs VBE extensions.  If your guest OS
>               supports the VESA 2.0 VBE extensions (e.g. Windows XP) and if
>               you want to use high resolution modes (>= 1280x1024x16) then
>               you should use this option.
>
> Since changing the network card driver worked, and vesa seems to not want to
> unload / hand off to cirrusfb, maybe we should try stdvga=1 again, but with
> videoram=32. (Actually, as an experiment, try videoram=8 and 16 also. Then
> check with lspci -vvv for the video device, and see if the size= field in the
> first Region line changes.)
OK, this is what I see right now (without any change):
stdvga=0 && videoram=16 && kernel 3.0.1
Region 0: Memory at f0000000 (32-bit, prefetchable) [size=32M]
Region 1: Memory at f3020000 (32-bit, non-prefetchable) [size=4K]
Max Resolution: 800x600

stdvga=1 && videoram=8 && kernel 3.0.1 (I noticed the domU is slightly faster)
Region 0: Memory at f1000000 (32-bit, prefetchable) [size=8M]
Expansion ROM at <unassigned> [disabled]
Max Resolution: 800x600

stdvga=1 && videoram=16 && kernel 3.0.1
Region 0: Memory at f0000000 (32-bit, prefetchable) [size=16M]
Expansion ROM at <unassigned> [disabled]
Max Resolution: 800x600

stdvga=1 && videoram=32 && kernel 3.0.1
Region 0: Memory at f0000000 (32-bit, prefetchable) [size=16M]
Expansion ROM at <unassigned> [disabled]
Max Resolution: 800x600

So, something changed for 8 and 16M! But I didn't understand what has
changed. Now the
"size" increases but the max resolution is still 800x600. At least I notice
a faster domU with these settings. Haven't we already tried to set different
videoram quantity in our previous attempt, without success? Maybe the
only attempt we did was for videoram=32.

Thanks a lot!

Flavio

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

<Prev in Thread] Current Thread [Next in Thread>