From: Gerd Hoffmann <kraxel@redhat.com>
To: Vitaly Chipounov <vitaly@cyberhaven.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] hw/display/virtio-vga: made vga memory size configurable
Date: Wed, 17 Mar 2021 07:45:03 +0100 [thread overview]
Message-ID: <20210317064503.wj7zgpvztnps6jck@sirius.home.kraxel.org> (raw)
In-Reply-To: <CACjSjctXNbdX=Kiu6oQ+R6c2nee4mYm0oO0HWS207AWz864ouw@mail.gmail.com>
On Tue, Mar 16, 2021 at 08:51:21PM +0100, Vitaly Chipounov wrote:
> On Mon, Mar 15, 2021 at 4:24 PM Gerd Hoffmann <kraxel@redhat.com> wrote:
> >
> > On Mon, Mar 15, 2021 at 12:29:16PM +0100, Vitaly Chipounov wrote:
> > > On Mon, Mar 15, 2021 at 8:21 AM Gerd Hoffmann <kraxel@redhat.com> wrote:
> > > >
> > > > If your guest has no virtio driver use stdvga instead of running
> > > > virtio-vga permanently in vga compatibility mode.
> > >
> > > I tried -device VGA,vgamem_mb=32. I did not see any resolution above
> > > 1080p on a Windows 10 guest.
> >
> > Try "-device VGA,vgamem_mb=32,edid=off". Windows seems to not like our
> > edid block for some reason.
> >
>
> This worked, thanks for the tip. Regarding the patch, I can resubmit
> it with an amended commit message if people think it's still better to
> have a configurable memory size here.
Given that the vram is used for vga compatibility only and not used any
more once the virtio-gpu driver initialized the device I don't think
this should be configurable.
take care,
Gerd
prev parent reply other threads:[~2021-03-17 6:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 12:23 [PATCH] hw/display/virtio-vga: made vga memory size configurable vitaly
2021-03-14 12:45 ` BALATON Zoltan
2021-03-14 12:50 ` Vitaly Chipounov
2021-03-15 7:21 ` Gerd Hoffmann
2021-03-15 11:29 ` Vitaly Chipounov
2021-03-15 15:24 ` Gerd Hoffmann
2021-03-16 19:51 ` Vitaly Chipounov
2021-03-17 6:45 ` Gerd Hoffmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210317064503.wj7zgpvztnps6jck@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vitaly@cyberhaven.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).