Date: Thu, 27 Feb 2014 23:45:18 -0800 From: "Rudy (bulk)" <crapsh@monkeybrains.net> To: Peter Grehan <grehan@freebsd.org> Cc: freebsd-virtualization@freebsd.org Subject: [SOLVED] Re: lazy bhyve doesn't boot until I conenct to console Message-ID: <53103E8E.80709@monkeybrains.net> In-Reply-To: <531035FD.4030704@freebsd.org> References: <5310346B.4000001@monkeybrains.net> <531035FD.4030704@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/27/14, 11:08 PM, Peter Grehan wrote:
> Hi Rudy,
>
>
>> I'm seeing something odd... I am running this command:
>>
>> bhyve -c 4 -m 2048M -H -P -A -s 0:0,hostbridge -s 1:0,lpc -s
>> 2,virtio-net,tap1 -s 3,virtio-blk,/dev/zvol/data/vm1 -l com1,/dev/nmdm1A
>> vm1
>> but I the VM is being lazy...
>
> A number of people have reported this, and looking at it, I think
> it's a bug in bhyve.
>
> nmdm attempts to simulate modem control (not quite correctly - run
> back-back cu's to see some of the behaviour), but also bhyve doesn't
> open the device non-blocking. This results in the open() syscall
> waiting for simulated carrier-detect to arrive, which doesn't happen
> until the other end of the nmdm is opened.
>
I have a fix: echo into the nmdm after booting VM.
Added this line to bhyve.rc
echo >> ${bhyve_nmdmBdev}
Rudy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53103E8E.80709>