qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [RFC] Bug Day - June 1st, 2010
Date: Wed, 19 May 2010 08:32:11 -0500	[thread overview]
Message-ID: <4BF3E85B.4010809@codemonkey.ws> (raw)
In-Reply-To: <4BF3E577.8050005@msgid.tls.msk.ru>

On 05/19/2010 08:19 AM, Michael Tokarev wrote:
> Anthony Liguori wrote:
> []
>    
>> For the Bug Day, anything is interesting IMHO.  My main interest is to
>> get as many people involved in testing and bug fixing as possible.  If
>> folks are interested in testing specific things like unusual or older
>> OSes, I'm happy to see it!
>>      
> Well, interesting or not, but I for one don't know what to do with the
> results.  There were a thread on kvm@ about sigsegv in cirrus code when
> running winNT. The issue has been identified and appears to be fixed,
> as in, kvm process does not SIGSEGV anymore, but it does not work anyway,
> now printing:
>
>   BUG: kvm_dirty_pages_log_enable_slot: invalid parameters
>
> with garbled guest display.  Thanks goes to Stefano Stabellini for
> finding the SIGSEGV case, but unfortunately his hard work isn't quite
> useful since the behavour isn't very much different from the previous
> version... ;)
>    

File a bug in Launchpad.  Even if it isn't fixed immediately, at least 
that way it will not be lost.  Things are too easily lost on the mailing 
list.

Regards,

Anthony Liguori

> Also, thanks to Andre Przywara, whole winNT thing works but it requires
> -cpu qemu64,level=1 (or level=2 or =3), -- _not_ with default CPU.  This
> is also testing, but it's not obvious what to do witht the result...
>
> Thanks!
>
> /mjt
>
>    

  reply	other threads:[~2010-05-19 13:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18 22:38 [Qemu-devel] [RFC] Bug Day - June 1st, 2010 Anthony Liguori
2010-05-19  0:58 ` Natalia Portillo
2010-05-19  1:45   ` Jamie Lokier
2010-05-19  1:48     ` Natalia Portillo
2010-05-19 13:35       ` Anthony Liguori
2010-05-19 14:10         ` Natalia Portillo
2010-05-19 13:09     ` Anthony Liguori
2010-05-19 13:19       ` Michael Tokarev
2010-05-19 13:32         ` Anthony Liguori [this message]
2010-05-19 15:57         ` Jamie Lokier
2010-05-19 22:29         ` Andre Przywara
2010-05-19 22:30           ` Anthony Liguori
2010-05-20  5:58             ` Michael Tokarev
2010-05-20  7:15               ` Andre Przywara
2010-05-20 21:32                 ` Michael Tokarev
2010-05-19 14:06       ` Natalia Portillo
2010-05-20  7:43   ` Jes Sorensen
2010-05-19  5:04 ` Aurelien Jarno
2010-05-19 12:21   ` Miguel Di Ciurcio Filho
2010-05-19 13:34   ` Anthony Liguori
2010-05-20  7:50     ` Jes Sorensen
2010-05-19 14:52 ` Luiz Capitulino
2010-05-19 17:02   ` Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2010-05-19 14:17 Riccardo Magliocchetti

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=4BF3E85B.4010809@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).