From: Niels Berglund <niels.berglund@gmail.com>
To: kvm@vger.kernel.org
Subject: Re: kvm-76 --std-vga problem
Date: Mon, 6 Oct 2008 07:35:04 +0000 (UTC) [thread overview]
Message-ID: <loom.20081006T073052-649@post.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0810061140490.7389@q66.ta.eth
duck <duck <at> roaming.ath.cx> writes:
> Michael Malone wrote:
[snip
> Glauber Costa replied:
[snip]
> > This is a band aid, but proves the general idea. Can you
> > confirm that it fixes the problem for you ?
>
> When I apply glommer's abovementioned band aid patch and use -std-vga then
> the problem is different, but not fixed. I no longer see the
> kvm_create_phys_mem error, nor the set_vram_mapping error, but the:
>
> kvm: get_dirty_pages returned -2
> kvm: get_dirty_pages returned -2
> kvm: get_dirty_pages returned -2
> kvm: get_dirty_pages returned -2
> kvm: get_dirty_pages returned -2
> ...zillions of this line...
>
> still appears.
I'm seeing the same issue as duck above, i.e the get_dirty_pages issue still
exist aftr having applied the patch. For me it's not a showstopper though, I
just run kvm without the -std-vga flag for the time being.
Niels
next prev parent reply other threads:[~2008-10-06 7:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 0:52 kvm-76 --std-vga problem duck
2008-10-06 7:35 ` Niels Berglund [this message]
2008-10-06 16:16 ` Glauber Costa
-- strict thread matches above, loose matches on Subject: below --
2008-09-28 21:44 Michael Malone
2008-09-29 12:37 ` Martin Maurer
2008-09-29 12:50 ` Brian Jackson
2008-09-29 17:29 ` Glauber Costa
2008-09-29 18:08 ` Glauber Costa
2008-10-01 7:47 ` Avi Kivity
2008-10-01 19:52 ` Michael Malone
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=loom.20081006T073052-649@post.gmane.org \
--to=niels.berglund@gmail.com \
--cc=kvm@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.