On Wed, Oct 16, 2019 at 08:11:57AM +0200, 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
The URL above has this error:
con recv: x: Exitqqqqqqqqqqqqqqqqqqqqqqqqqj
con recv: To be able to use the network, we need answers to the
following:Network media type
con send: <enter>
con recv: : qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk Perform autoconfiguration?
>a: Yes b: Noqqqqqqqqqqqqqqqqq
console: *** read timeout ***
console: waiting for: 'a: Yes'
console: line buffer:
con recv: qqqqqqqqqqqqqqj
I believe that problem was solved in v4, because v4 was reading
the serial output 1 byte at a time.
The issue that caused the netbsd patch to be dropped was:
https://lore.kernel.org/qemu-devel/cafeaca8k9qja9ie-kwiaphr0fy_2zg7jrx5uv4aassjxcss...@mail.gmail.com/
Possibly this is the same issue we saw at:
https://lore.kernel.org/qemu-devel/20190607034214.gb22...@habkost.net/
The test script must either close the console socket, or keep
reading from it. Otherwise, the QEMU VCPU threads might get
stuck waiting for the chardev to be writeable.
--
Eduardo
