Re: [SOLVED] Re: lazy bhyve doesn't boot until I conenct to console

[Peter Grehan]

Hi Roman,


   Fixed in r262884

 ...

Do you plan to MFC that? The original commit set MFC to 3 weeks and now
more than 4 weeks passed since. That would be a very useful fix to have
in STABLE.


 Yes - there should be a large set of MFCs soon; just getting together 
the list of what will be done.


later,

Peter.

___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: [SOLVED] Re: lazy bhyve doesn't boot until I conenct to console

[Roman Bogorodskiy]

  Peter Grehan wrote:

> >>> 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.
> 
>   Fixed in r262884

Hi Peter,

Do you plan to MFC that? The original commit set MFC to 3 weeks and now
more than 4 weeks passed since. That would be a very useful fix to have
in STABLE.

Thanks,

Roman Bogorodskiy


pgpt5CDTqkcxg.pgp
Description: PGP signature

Re: [SOLVED] Re: lazy bhyve doesn't boot until I conenct to console

[Peter Grehan]

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.


 Fixed in r262884

later,

Peter.

___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

[SOLVED] Re: lazy bhyve doesn't boot until I conenct to console

[Rudy (bulk)]

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
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"