On Wed, Nov 20, 2013 at 12:55 PM, Bruno Lauzé wrote:
>
> Using jails, customers are uncomfortable with the fact documents can be
> accessed from the host with root access.Project VPS seems to isolate more the
> guest from the host but not as well as an hypervisor like bhyve. With an
> hyperviso
Hi Aryeh,
When I run the following script bhyveload exits normally but when bhyve
runs I get:
Error return from kevent change: Operation not supported by device
Hmmm, I've not seen that before. Are you able to do a build of bhyve
and run it in gdb ?
The script:
#!/bin/sh
ifconfig tap60
When I run the following script bhyveload exits normally but when bhyve
runs I get:
Error return from kevent change: Operation not supported by device
The script:
#!/bin/sh
ifconfig tap6000 destroy
ifconfig tap6000 create
ifconfig tap6000 up
sleep 5
ifconfig bridge0 addm tap6000 up
/usr/sbin/bh
On 11/20/13, 10:03 AM, Miroslav Lachman wrote:
Bruno Lauzé wrote:
Using jails, customers are uncomfortable with the fact documents
can be accessed from the host with root access.Project VPS seems to
isolate more the guest from the host but not as well as an
hypervisor like bhyve. With an hyp
Bruno Lauzé wrote:
Using jails, customers are uncomfortable with the fact documents can be
accessed from the host with root access.Project VPS seems to isolate more the
guest from the host but not as well as an hypervisor like bhyve. With an
hypervisor what the client have is private, as long
Using jails, customers are uncomfortable with the fact documents can be
accessed from the host with root access.Project VPS seems to isolate more the
guest from the host but not as well as an hypervisor like bhyve. With an
hypervisor what the client have is private, as long as the host can mana
