All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: QEMU devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	KVM mailing list <kvm@vger.kernel.org>,
	Kevin Wolf <kwolf@redhat.com>, Cleber Rosa <crosa@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [1.0 release work] Fix regressions found on recent KVM autotest qemu master 'sanity' jobs
Date: Fri, 04 Nov 2011 15:02:35 -0200	[thread overview]
Message-ID: <4EB41AAB.6050505@redhat.com> (raw)
In-Reply-To: <4EB4193E.5080108@codemonkey.ws>

On Fri 04 Nov 2011 02:56:30 PM BRST, Anthony Liguori wrote:
> On 11/04/2011 11:40 AM, Lucas Meneghel Rodrigues wrote:
>> Hi guys,
>>
>> As we understand that qemu is approaching 1.0, we think it's a good 
>> idea to
>> share the issues we have been seeing on recent qemu.git sanity jobs:
>>
>> 1) Some condition is consistently making a RHEL 6.1 linux guest not 
>> able to
>> bring up the network interface, causing login failures for all linux 
>> guest
>> tests. This very same guest install works perfectly on qemu-kvm, RHEL 
>> 5 and RHEL 6.
>
> Can you file a bug report with specific information about how the 
> guest is being launched? Specifically, what NIC are we talking about? 
> Do other types of guests work?

Ok, I will. Just FYI, it's a virtio nic. As on sanity jobs we only test 
RHEL 6.1 64 bit and Windows 7 SP1 64 bit, and Windows is blocked due to 
the other bug mentioned, I still have no idea whether other guests do 
work.


WARNING: multiple messages have this Message-ID (diff)
From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	KVM mailing list <kvm@vger.kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	QEMU devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>,
	Cleber Rosa <crosa@redhat.com>
Subject: Re: [Qemu-devel] [1.0 release work] Fix regressions found on recent KVM autotest qemu master 'sanity' jobs
Date: Fri, 04 Nov 2011 15:02:35 -0200	[thread overview]
Message-ID: <4EB41AAB.6050505@redhat.com> (raw)
In-Reply-To: <4EB4193E.5080108@codemonkey.ws>

On Fri 04 Nov 2011 02:56:30 PM BRST, Anthony Liguori wrote:
> On 11/04/2011 11:40 AM, Lucas Meneghel Rodrigues wrote:
>> Hi guys,
>>
>> As we understand that qemu is approaching 1.0, we think it's a good 
>> idea to
>> share the issues we have been seeing on recent qemu.git sanity jobs:
>>
>> 1) Some condition is consistently making a RHEL 6.1 linux guest not 
>> able to
>> bring up the network interface, causing login failures for all linux 
>> guest
>> tests. This very same guest install works perfectly on qemu-kvm, RHEL 
>> 5 and RHEL 6.
>
> Can you file a bug report with specific information about how the 
> guest is being launched? Specifically, what NIC are we talking about? 
> Do other types of guests work?

Ok, I will. Just FYI, it's a virtio nic. As on sanity jobs we only test 
RHEL 6.1 64 bit and Windows 7 SP1 64 bit, and Windows is blocked due to 
the other bug mentioned, I still have no idea whether other guests do 
work.

  reply	other threads:[~2011-11-04 17:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-04 16:40 [1.0 release work] Fix regressions found on recent KVM autotest qemu master 'sanity' jobs Lucas Meneghel Rodrigues
2011-11-04 16:40 ` [Qemu-devel] " Lucas Meneghel Rodrigues
2011-11-04 16:50 ` Kevin Wolf
2011-11-04 16:50   ` [Qemu-devel] " Kevin Wolf
2011-11-04 16:52   ` Lucas Meneghel Rodrigues
2011-11-04 16:52     ` [Qemu-devel] " Lucas Meneghel Rodrigues
2011-11-04 16:56 ` Anthony Liguori
2011-11-04 16:56   ` [Qemu-devel] " Anthony Liguori
2011-11-04 17:02   ` Lucas Meneghel Rodrigues [this message]
2011-11-04 17:02     ` Lucas Meneghel Rodrigues
2011-11-04 17:53   ` Lucas Meneghel Rodrigues

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=4EB41AAB.6050505@redhat.com \
    --to=lmr@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    --cc=mtosatti@redhat.com \
    --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.