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.
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 n
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
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
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,
