Debian Bug report logs - #685097
vgabios: Windows 8 guest stuck at 1024x768

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Romain Francoise <rfrancoise@debian.org>

To: submit@bugs.debian.org

Subject: vgabios: Windows 8 guest stuck at 1024x768

Date: Thu, 16 Aug 2012 20:30:15 +0200

Package: vgabios
Version: 0.7a-3
Severity: normal

Windows 8 in KVM using the 'std' vga driver doesn't offer any resolution
other than 1024x768, unlike Windows 7 which supports larger resolutions up
to 2560x1600.

Applying the following patch to vgabios fixes the issue for me:

 http://lists.xen.org/archives/html/xen-devel/2012-05/msg00260.html

(However, the patch may not be suitable for inclusion, I didn't test the
effects it has on other guests.)

-- 
Romain Francoise <rfrancoise@debian.org>
http://people.debian.org/~rfrancoise/

Message #10 received at 685097@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: Romain Francoise <rfrancoise@debian.org>, 685097@bugs.debian.org

Subject: Re: Bug#685097: vgabios: Windows 8 guest stuck at 1024x768

Date: Fri, 29 Nov 2013 20:25:07 +0400

Control: tag -1 + confirmed

16.08.2012 22:30, Romain Francoise wrote:
> Package: vgabios
> Version: 0.7a-3
> Severity: normal
> 
> Windows 8 in KVM using the 'std' vga driver doesn't offer any resolution
> other than 1024x768, unlike Windows 7 which supports larger resolutions up
> to 2560x1600.
> 
> Applying the following patch to vgabios fixes the issue for me:
> 
>  http://lists.xen.org/archives/html/xen-devel/2012-05/msg00260.html
> 
> (However, the patch may not be suitable for inclusion, I didn't test the
> effects it has on other guests.)

Hello.

Yesterday I uploaded a new version of qemu to unstable (1.7.0+dfsg-2) which
switched from bochs vgabios to "seavgabios", -- vga bios implementation
which is part of seabios package.

With this change, windows8 guest can change resolutions with -vga std just
fine.  Seavgabios is missing some popular resolutions (such as 1920x1024),
which hopefully will be fixed in the next seabios update, but it is anyway
much better than what we currently have with vgabios.

If this change will not have really bad effects (and I really hope it wont),
vgabios will not be used with qemu anymore.

That's JFYI, I'm not saying there's no bug in vgabios (and adding `confirmed'
tag while at it).

Besides, there's one prob with the patch you pointed to.  It is a part of a
larger patchset, all of which should be applied, not just one change (because
this one change is based on previous changes).  However, vgabios in xen is,
for some reason, quite a bit different from what we have in debian, so this
patchset does not apply and needs some tweaking.  But I don't know enough of
vgabios internals to be able to tweak it easily.

Thanks,

/mjt

Message #17 received at 685097@bugs.debian.org (full text, mbox, reply):

From: Romain Francoise <rfrancoise@debian.org>

To: Michael Tokarev <mjt@tls.msk.ru>

Cc: 685097@bugs.debian.org

Subject: Re: Bug#685097: vgabios: Windows 8 guest stuck at 1024x768

Date: Fri, 29 Nov 2013 18:01:13 +0100

Michael Tokarev <mjt@tls.msk.ru> writes:

> With this change, windows8 guest can change resolutions with -vga std
> just fine.

Yes, I can confirm that with this change a Windows 8.1 Enterprise guest
can use all traditional VESA modes. Note that I had to change back to
Cirrus, boot the guest, then change back to vgastd to make it work at
all, otherwise all I got was a garbled screen.

Also, as mentioned on IRC the resolution I need (1920x1080) is not
available but I added it manually, and it's good to know that it will
eventually be added to upstream seabios as well.

Thanks!

Cheers,
-- 
Romain Francoise <rfrancoise@debian.org>
http://people.debian.org/~rfrancoise/

Message #22 received at 685097-done@bugs.debian.org (full text, mbox, reply):

From: Romain Francoise <rfrancoise@debian.org>

To: 685097-done@bugs.debian.org

Subject: Closing

Date: Sun, 12 Sep 2021 10:22:57 +0200

This was fixed long ago, closing.

Send a report that this bug log contains spam.