Re: Python 2 and test/vm/netbsd

[Alex Bennée]

Kamil Rytarowski <address@hidden> 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.

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.


--
Alex Bennée