Trouble using current under qemu

[Julio Merino]

Hello,

I have a NetBSD/amd64 -current VM under VMware Fusion under which I'm
trying to run anita with qemu (1.3.0) for testing purposes. Things are
not working well:

Under qemu, I can see the NetBSD bootloader showing up. If I let the
bootloader time out and start the boot process by itself, the load of
the kernel gets stuck to the point where it never asks for a second
floppy disk. If I hit enter explicitly at the bootloader, then the
kernel boots up fine and then gets stuck later after vmt0 attempts to
initialize.

This happens with anita and outside of anita if I run the installation
image with qemu.

Any ideas? Has anyone else seen this?

Thanks,

--
Julio Merino / @jmmv

[Paul Goyette]

I've seen similar, and it seems to be an issue with qemu. See the
thread at

http://mail-index.netbsd.org/pkgsrc-users/2013/03/02/msg017785.html


The expectation is it would work if you go back to earlier version of
qemu (version 1.2.0nb2 should be good).



-------------------------------------------------------------------------
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
| Kernel Developer | | pgoyette at netbsd.org |
-------------------------------------------------------------------------

[Julio Merino]

On Fri, Mar 8, 2013 at 5:43 PM, Paul Goyette <pa...@whooppee.com> wrote:
>
> I've seen similar, and it seems to be an issue with qemu. See the thread at
>
> http://mail-index.netbsd.org/pkgsrc-users/2013/03/02/msg017785.html
>
>
> The expectation is it would work if you go back to earlier version of qemu
> (version 1.2.0nb2 should be good).

That did the trick. Thanks!

[Izumi Tsutsui]

Paul Goyette wrote:

> On Fri, 8 Mar 2013, Julio Merino wrote:

:

> > I have a NetBSD/amd64 -current VM under VMware Fusion under which I'm
> > trying to run anita with qemu (1.3.0) for testing purposes. Things are
> > not working well:
> >
> > Under qemu, I can see the NetBSD bootloader showing up. If I let the
> > bootloader time out and start the boot process by itself, the load of
> > the kernel gets stuck to the point where it never asks for a second
> > floppy disk. If I hit enter explicitly at the bootloader, then the
> > kernel boots up fine and then gets stuck later after vmt0 attempts to
> > initialize.
> >
> > This happens with anita and outside of anita if I run the installation
> > image with qemu.
> >
> > Any ideas? Has anyone else seen this?
>
> I've seen similar, and it seems to be an issue with qemu. See the
> thread at
>
> http://mail-index.netbsd.org/pkgsrc-users/2013/03/02/msg017785.html
>
>
> The expectation is it would work if you go back to earlier version of
> qemu (version 1.2.0nb2 should be good).

With qemu-1.3.1 NetBSD/i386 6.0.1 seems to work. (not on 1.3.0)
Does anyone else try qemu-1.3.1?

If qemu-1.3.1 actually contains fixes for NetBSD 6.x,
we should probably update pkgsrc/emulators/qemu to 1.3.1
even during freeze. (no PLIST change is required)

---
Izumi Tsutsui

[Andreas Gustafsson]

Izumi Tsutsui wrote:
> With qemu-1.3.1 NetBSD/i386 6.0.1 seems to work. (not on 1.3.0)
> Does anyone else try qemu-1.3.1?

I have not tried any recent qemu 1.x releases, but I have been running
automated tests of daily builds of the qemu git mainline. So far, I
have run into five different regressions that have broken NetBSD/i386
guests one way or another:

https://bugs.launchpad.net/qemu/+bug/897771
https://bugs.launchpad.net/qemu/+bug/1089996
https://bugs.launchpad.net/qemu/+bug/1091241
https://bugs.launchpad.net/qemu/+bug/1127369
https://bugs.launchpad.net/qemu/+bug/1154328

At least bug 1154328 still exists on the mainline, and I have received
no response to the bug report. Bug 1127369 is probably also still
unfixed, but I can no longer test it in an automated way because of
1154328.

I don't know which of the 1.x releases are affected by which of these
bugs, if any, but I would guess most of them are affected by at least
one.
--
Andreas Gustafsson, gs...@NetBSD.org

[Izumi Tsutsui]

gson@ wrote:

> Izumi Tsutsui wrote:
> > With qemu-1.3.1 NetBSD/i386 6.0.1 seems to work. (not on 1.3.0)
> > Does anyone else try qemu-1.3.1?
>
> I have not tried any recent qemu 1.x releases, but I have been running
> automated tests of daily builds of the qemu git mainline. So far, I
> have run into five different regressions that have broken NetBSD/i386
> guests one way or another:

(snip)

> I don't know which of the 1.x releases are affected by which of these
> bugs, if any, but I would guess most of them are affected by at least
> one.

I have not tried the latest qemu-1.4.0, but anyway I've commmitted
qemu-1.3.1 to pkgsrc (with approval from wiz@) so that forthcoming
2013Q1 will have working (even if it might still have bugs triggered
by atf) one for NetBSD/i386 6.0.1 guests.

---
Izumi Tsutsui

[Mayuresh]

On Sat, Mar 30, 2013 at 01:22:56AM +0900, Izumi Tsutsui wrote:
> I have not tried the latest qemu-1.4.0, but anyway I've commmitted
> qemu-1.3.1 to pkgsrc (with approval from wiz@) so that forthcoming
> 2013Q1 will have working (even if it might still have bugs triggered
> by atf) one for NetBSD/i386 6.0.1 guests.

I am using qemu 1.2.0 on NetBSD 6.0 i386 host and Arch Linux guest.

I was not able to upgrade to 1.3.0 due to some issue:
http://mail-index.netbsd.org/netbsd-users/2013/02/19/msg012511.html

With 1.3.1, Arch Linux hangs during booting. So not able to use it as
well.

(Sorry, I reverted to 1.2.0. Don't recollect exact state where it was
getting hung. I don't think I saw any error messages etc.)


Do I need 6.0.1 or anything higher for qemu 1.3.1 to work?

Mayuresh

[Izumi Tsutsui]

> Do I need 6.0.1 or anything higher for qemu 1.3.1 to work?

I doubt it.

Just 1.3.1 works better than 1.3.0, and still has some issue.
NetBSD guest with virtio block device still causes qemu hangup.
(not sure if it's NetBSD host specific or not though)

---
Izumi Tsutsui