All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, "Kamil Rytarowski" <n54@gmx.com>
Cc: "Fam Zheng" <fam@euphon.net>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Eduardo Habkost" <ehabkost@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Kamil Rytarowski" <kamil@netbsd.org>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Cleber Rosa" <crosa@redhat.com>, "Kevin Wolf" <kwolf@redhat.com>,
	"John Snow" <jsnow@redhat.com>
Subject: Re: Python 2 and test/vm/netbsd
Date: Wed, 16 Oct 2019 14:23:30 +0200	[thread overview]
Message-ID: <e9698ee5-81f1-4556-d446-1f7332021070@redhat.com> (raw)
In-Reply-To: <875zkp5534.fsf@linaro.org>

On 10/16/19 12:59 PM, Alex Bennée wrote:
> Kamil Rytarowski <n54@gmx.com> writes:
>> On 16.10.2019 08:11, Thomas Huth wrote:
>>> On 16/10/2019 05.00, Eduardo Habkost wrote:
>>>> On Tue, Sep 17, 2019 at 08:31:40PM -0300, Eduardo Habkost wrote:
>>>>> On Mon, Jul 01, 2019 at 07:25:27PM -0300, Eduardo Habkost wrote:
>>>>>> On Mon, Jun 10, 2019 at 01:58:50PM +0100, Peter Maydell wrote:
>>>> [...]
>>>>>>> The configure check also spits out deprecation warnings for
>>>>>>> the NetBSD/FreeBSD/OpenBSD tests/vm configurations. It would be nice
>>>>>>> to get those updated.
>>>>>>
>>>>>> CCing the test/vm maintainers.
>>>>>>
>>>>>> Fam, Alex, are you able to fix this and create new BSD VM images
>>>>>> with Python 3 available?  I thought the VM image configurations
>>>>>> were stored in the source tree, but they are downloaded from
>>>>>> download.patchew.org.
>>>>>
>>>>> Fam, Alex, can you help us on this?  Python 2 won't be supported
>>>>> anymore, so we need the VM images to be updated.
>>>>
>>>> Anyone?
>>>>
>>>> I'm about to submit patches to remove Python 2 support, and this
>>>> will break tests/vm/netbsd.
>>>>
>>>> I'm powerless to fix this issue, because the netbsd image is
>>>> hosted at download.patchew.org.
>>>
>>> Gerd had a patch to convert the netbsd VM script to ad hoc image
>>> creation, too:
>>>
>>> https://lists.gnu.org/archive/html/qemu-devel/2019-05/msg04459.html
>>>
>>> But there was a regression with the serial port between QEMU v3.0 and
>>> v4.x, so it was not included:
>>>
>>> https://lists.gnu.org/archive/html/qemu-devel/2019-05/msg06784.html
>>>
>>> I guess someone™ needs to bisect that regression, so we can fix that bug
>>> and finally include Gerd's patch...
>>>
>>>    Thomas
>>>
>>
>> Is this a regression in qemu? How to reproduce the problem? "make
>> vm-build-netbsd V=1" ?
> 
> You'll need to apply the patch from that series:
> 
>    tests/vm: netbsd autoinstall, using serial
> 
> (all the others got merged)
> 
>> I can have a look but I need to know exact specifics of the problem.

IIRC this is not a NetBSD specific issue, but the NetBSD image triggers 
the chardev bug reliably.

> Make sure you've cleared out any cached images. As was mentioned in the
> thread it seems to be a little host dependant - some host systems it was
> working and some it was not.


  parent reply	other threads:[~2019-10-16 12:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16  3:00 Python 2 and test/vm/netbsd (was Re: [Qemu-devel] [PULL 0/8] Python queue, 2019-06-07) Eduardo Habkost
2019-10-16  6:11 ` Python 2 and test/vm/netbsd Thomas Huth
2019-10-16  8:25   ` Kamil Rytarowski
2019-10-16 10:59     ` Alex Bennée
2019-10-16 11:02       ` Thomas Huth
2019-10-16 12:23       ` Philippe Mathieu-Daudé [this message]
2019-10-16 22:41   ` Eduardo Habkost
2019-10-17 22:05     ` Eduardo Habkost
2019-10-17 22:55       ` Eduardo Habkost
2019-10-18  7:13         ` Thomas Huth
2019-10-18 14:51           ` Eduardo Habkost
2019-10-18 10:44         ` Gerd Hoffmann
2019-10-18 14:29           ` Eduardo Habkost
2019-10-18 14:58             ` Philippe Mathieu-Daudé
2019-10-18 16:00               ` Samuel Thibault
2019-10-18 16:41                 ` Eduardo Habkost
2019-10-22 13:16                   ` Samuel Thibault
2019-10-22 13:05                     ` Kamil Rytarowski
2019-10-22 13:10                 ` Samuel Thibault

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=e9698ee5-81f1-4556-d446-1f7332021070@redhat.com \
    --to=philmd@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=fam@euphon.net \
    --cc=jsnow@redhat.com \
    --cc=kamil@netbsd.org \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=n54@gmx.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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.