From: Pelle <Pelle-5JapdU7xTciEVqv0pETR8A@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
mrintegrity-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: -std-vga causes crash
Date: Thu, 30 Aug 2007 08:15:35 +0200 [thread overview]
Message-ID: <46D66087.20804@quicknet.nl> (raw)
In-Reply-To: <46D6109B.20503-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
No, I'm not,
changing to
/usr/local/bin/qemu-system-x86_64
fixes it, Tnx!
Avi Kivity wrote:
> Pelle wrote:
>
>> The message that this should be fixed was reason for me to test it
>> again, and it fails miserably, even on kvm-36
>> I checked with "modinfo kvm-intel" that i am in fact using kvm-36,
>> processor is a core 2 duo 6300
>>
>> $ /usr/local/bin/qemu -hda winXP.img -hdb vdisk.img -m 256 -soundhw
>> es1370 -std-vga
>>
>> kvm: get_dirty_pages returned -2
>>
>>
>
> Are you sure you're using the qemu binary from kvm-36? The fix was in
> userspace, not kernel.
>
> Try /usr/local/bin/qemu-system-x86_64.
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-08-30 6:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 11:51 -std-vga causes crash mrintegrity
2007-08-29 2:19 ` Izik Eidus
[not found] ` <1188353996.3215.1.camel-siXIhNkUrCXckEVJwWePHtCfPAL7FxvL@public.gmane.org>
2007-08-29 12:51 ` Pelle
[not found] ` <46D56BDC.5050200-5JapdU7xTciEVqv0pETR8A@public.gmane.org>
2007-08-30 0:34 ` Avi Kivity
[not found] ` <46D6109B.20503-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-30 6:15 ` Pelle [this message]
2007-08-29 13:21 ` mrintegrity
2007-08-30 0:35 ` Avi Kivity
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=46D66087.20804@quicknet.nl \
--to=pelle-5japdu7xtcievqv0petr8a@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mrintegrity-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox