Try in /boot/loader.conf of the VM : console=userboot or after beastie drop to loader OK promot and try : set console=userboot I think 11.x should fall back to userboot in bhyve if vidconsole of comconsole were set. (This is assuming non-EFI booting - using bhyveloader ). -- David P. Discher https://davidpdischer.com/ 408.368.3725 • dpd_at_dpdtech.com > On Jun 14, 2018, at 2:49 PM, tech-lists <tech-lists_at_zyxst.net> wrote: > > Hello list, > > context is freebsd-12 r317212 host and freebsd-11-stable r333924 guest > > I run this freebsd instance in screen. I start it like this: > > vmrun.sh -c 4 -m 8192M -t tap3 -d fbsd-guest.img fbsd-guest > > It starts, I get the daemon screen, then this: > > /boot/kernel/kernel text=0x70572d data=0xa5648+0x340ac0 syms=[0x8+0xc0c78+0x8+0xde421] > /boot/entropy size=0x1000 > Booting... > Unhandled ps2 mouse command 0xe1 > > and that's it. The guest loads, is functional, I can ssh into it, etc. > > Other freebsd-11 VMs started in the exact same way on the same server give the expected messages scrolling up when the VM starts. Why is this VM different and how can I fix? There was a time when the messages were displayed, then one day they didn't. > > I've built/installed a new world/kernel on this VM to no effect. > > thanks, > -- > J. > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:16 UTC