Ok, if I run the bhyve commands manually, then I get a serial console.
So something is just borked with vm-bhyve and its use of tmux. Whew.
(Now I don't know *what*, but that's at least progress in my diagnosis!)
___
freebsd-current@freebsd.org mailing
Ok, with debug=yes I see that it *is* running the VM -- but I have no
serial console? This may be operator error here, which is a big relief.
An update after I get back from the vet :). Thanks!
Sean.
___
freebsd-current@freebsd.org mailing list
https:
>Could you test with larger memory setup - instead of 512M, 1-2G?
I tried multiple vcpus and 1G of RAM; it made no difference (to either my
attempting to boot the system I built, or the ISO; just confirmed the ISO with
1G).
Sean.
___
freebsd-current@fre
Could you test with larger memory setup - instead of 512M, 1-2G?
rgds,
toomas
> On 16 Aug 2019, at 22:00, Sean Eric Fagan wrote:
>
>> I think vm-bhyve hides stderr output from bhyve by default, but there might
>> be a flag to make it display the stderr output. Can you try doing that to
>> see
>I think vm-bhyve hides stderr output from bhyve by default, but there might
>be a flag to make it display the stderr output. Can you try doing that to see
>if bhyve is reporting an error? Alternatively, can you see if the bhyve
>process is still running?
The log file from it is below. bhyve wa
On 8/15/19 9:21 AM, Sean Eric Fagan wrote:
> I get:
>
> Loading kernel...
> /boot/kernel/kernel text=0x16c493c data=0x1c8b38+0x819238
> syms=[0x8+0x180c18+0x8+0x19df0b]
> Loading configured modules...
> can't find '/boot/entropy'
> \
>
> Note that
I get:
Loading kernel...
/boot/kernel/kernel text=0x16c493c data=0x1c8b38+0x819238
syms=[0x8+0x180c18+0x8+0x19df0b]
Loading configured modules...
can't find '/boot/entropy'
\
Note that I am using vm-bhyve as a management & control wrapper, so that
