Re: Several bhyve quirks

On 28 March 2015 at 10:49, Neel Natu wrote: > > This is fixed in HEAD where the RTC device model defaults to 24-hour time. > >> >> suggests that I'm on the right track, but it doesn't explain the off-by-one >> nor

Re: Several bhyve quirks

Hi Julian, On Wed, Mar 25, 2015 at 2:24 AM, Julian Hsiao wrote: > Hi, > > I'm running bhyve on 10.1, mostly with OpenBSD (5.7) guests, and I ran into > a few strange issues: > > 1. The guest RTC is several hours off every time I start bhyve. The host > RTC is set to UTC, and /etc/localtime on bo

Re: Several bhyve quirks

Hi Julian, Thank you for your explanation and tips, Peter. I just tried changing virtio-blk -> ahci-hd and preliminary results are good. And now you've mentioned it, I do recall seeing slightly less performance degradation on guests with 2 vCPUs vs. ones with just one. Glad to hear that :)

Re: Several bhyve quirks

On 2015-03-25 15:44:35 +, Peter Grehan said: In 10.1, virtio-blk i/o is done sychronously in the context of the guest vCPU exit. If it's a single vCPU guest, or the virtio-net interrupt happens to be delivered to that vCPU, performance will suffer. A workaround is to use ahci-hd for the dis

Re: Several bhyve quirks

Hi Julian, I'll let Neel take care of the time questions. 3. Even moderate guest disk I/O completely kills guest network performance. For example, whenever security(8) (security(7) in FreeBSD) runs, guest network throughput drops from 150+ Mbps to ~20 Mbps, and jitter from ping jumps from <0.