All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Natalia Portillo <claunia@claunia.com>
Cc: Anthony Liguori <aliguori@linux.vnet.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	kvm-devel <kvm@vger.kernel.org>
Subject: Re: [RFC] Bug Day - June 1st, 2010
Date: Wed, 19 May 2010 08:35:46 -0500	[thread overview]
Message-ID: <4BF3E932.3010807@codemonkey.ws> (raw)
In-Reply-To: <37D5F493-E4BD-420E-A782-78F18E749DB6@claunia.com>

[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]

On 05/18/2010 08:48 PM, Natalia Portillo wrote:
>
> El 19/05/2010, a las 02:45, Jamie Lokier escribió:
>
>> Natalia Portillo wrote:
>>> Hi,
>>>
>>>> - We'll try to migrate as many confirmable bugs from the Source 
>>>> Forge tracker to Launchpad.
>>> I think that part of the bug day should also include retesting OSes 
>>> that appear in OS Support List as having bug and confirming if the 
>>> bug is still present and if it's in Launchpad or not.
>>
>> There have been reports of several legacy OSes being unable to install
>> or boot in the newer qemu while working in the older one.  They're
>> probably not in the "OS Support List" though.  Are they effectively
>> uninteresting for the purpose of the 0.13 release?
> There are a couple of.
>
> The majority of them are because SeaBIOS not behaving like real 
> hardware should and must do.
>
> If you know any OS that's not in the OS Support List and is broken 
> please commit.

If something is broken, please file a bug against it.  The OS Support 
List is a very useful resource but we still need bugs to actually work 
on fixing the problems.

Regards,

Anthony Liguori

>
>> Unfortunately I doubt I will have time to participate in the Bug Day.
>>
>> Thanks,
>> -- Jamie
>>
>


[-- Attachment #2: Type: text/html, Size: 2348 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Natalia Portillo <claunia@claunia.com>
Cc: Anthony Liguori <aliguori@linux.vnet.ibm.com>,
	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:35:46 -0500	[thread overview]
Message-ID: <4BF3E932.3010807@codemonkey.ws> (raw)
In-Reply-To: <37D5F493-E4BD-420E-A782-78F18E749DB6@claunia.com>

[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]

On 05/18/2010 08:48 PM, Natalia Portillo wrote:
>
> El 19/05/2010, a las 02:45, Jamie Lokier escribió:
>
>> Natalia Portillo wrote:
>>> Hi,
>>>
>>>> - We'll try to migrate as many confirmable bugs from the Source 
>>>> Forge tracker to Launchpad.
>>> I think that part of the bug day should also include retesting OSes 
>>> that appear in OS Support List as having bug and confirming if the 
>>> bug is still present and if it's in Launchpad or not.
>>
>> There have been reports of several legacy OSes being unable to install
>> or boot in the newer qemu while working in the older one.  They're
>> probably not in the "OS Support List" though.  Are they effectively
>> uninteresting for the purpose of the 0.13 release?
> There are a couple of.
>
> The majority of them are because SeaBIOS not behaving like real 
> hardware should and must do.
>
> If you know any OS that's not in the OS Support List and is broken 
> please commit.

If something is broken, please file a bug against it.  The OS Support 
List is a very useful resource but we still need bugs to actually work 
on fixing the problems.

Regards,

Anthony Liguori

>
>> Unfortunately I doubt I will have time to participate in the Bug Day.
>>
>> Thanks,
>> -- Jamie
>>
>


[-- Attachment #2: Type: text/html, Size: 2348 bytes --]

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

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18 22:38 [RFC] Bug Day - June 1st, 2010 Anthony Liguori
2010-05-18 22:38 ` [Qemu-devel] " 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  1:48       ` [Qemu-devel] " Natalia Portillo
2010-05-19 13:35       ` Anthony Liguori [this message]
2010-05-19 13:35         ` Anthony Liguori
2010-05-19 14:10         ` Natalia Portillo
2010-05-19 14:10           ` Natalia Portillo
2010-05-19 13:09     ` Anthony Liguori
2010-05-19 13:09       ` [Qemu-devel] " Anthony Liguori
2010-05-19 13:19       ` Michael Tokarev
2010-05-19 13:19         ` Michael Tokarev
2010-05-19 13:32         ` Anthony Liguori
2010-05-19 13:32           ` Anthony Liguori
2010-05-19 15:57         ` Jamie Lokier
2010-05-19 15:57           ` Jamie Lokier
2010-05-19 22:29         ` Andre Przywara
2010-05-19 22:29           ` Andre Przywara
2010-05-19 22:30           ` Anthony Liguori
2010-05-19 22:30             ` Anthony Liguori
2010-05-20  5:58             ` Michael Tokarev
2010-05-20  7:15               ` Andre Przywara
2010-05-20  7:15                 ` Andre Przywara
2010-05-20 21:32                 ` Michael Tokarev
2010-05-20 21:32                   ` Michael Tokarev
2010-05-19 14:06       ` Natalia Portillo
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-20  7:50       ` Jes Sorensen
2010-05-19 14:52 ` Luiz Capitulino
2010-05-19 17:02   ` Anthony Liguori

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=4BF3E932.3010807@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=claunia@claunia.com \
    --cc=kvm@vger.kernel.org \
    --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 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.