Re: Bhyve storage improvements (was: Several bhyve quirks)

On 06.04.2015 23:38, Alexander Motin wrote: >> I had some time to try it out today, but I'm still having issues: > > I've just made experiment alike to your with making bhyve to work on top > of GEOM device instead of preferable "dev" mode of ZVOL. And I indeed > reproduced the problem. But the pr

Re: Bhyve storage improvements (was: Several bhyve quirks)

Hi, Julian. > I had some time to try it out today, but I'm still having issues: I've just made experiment alike to your with making bhyve to work on top of GEOM device instead of preferable "dev" mode of ZVOL. And I indeed reproduced the problem. But the problem that I see is not related to the b

Re: Bhyve storage improvements (was: Several bhyve quirks)

On 2015-03-27 09:46:50 +, Alexander Motin said: [snip] Also both virtio-blk and ahci-hd drivers now report to guest logical and physical block sizes of underlying storage, that allow guests properly align partitions and I/Os for best compatibility and performance. Hi Alexander, In a prev

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: Bhyve storage improvements (was: Several bhyve quirks)

On Mar 27, 2015, at 10:47 AM, John Nielsen wrote: > On Mar 27, 2015, at 3:46 AM, Alexander Motin wrote: > >>> I've always assumed virtio driver > emulated driver so it didn't occur >>> to me to try ahci-hd. >> >> I've just merged to FreeBSD stable/10 branch set of bhyve changes that >> should

Re: Bhyve storage improvements (was: Several bhyve quirks)

On Mar 27, 2015, at 3:46 AM, Alexander Motin wrote: >> I've always assumed virtio driver > emulated driver so it didn't occur >> to me to try ahci-hd. > > I've just merged to FreeBSD stable/10 branch set of bhyve changes that > should significantly improve situation in the storage area. > > vir

Bhyve storage improvements (was: Several bhyve quirks)

> I've always assumed virtio driver > emulated driver so it didn't occur > to me to try ahci-hd. I've just merged to FreeBSD stable/10 branch set of bhyve changes that should significantly improve situation in the storage area. virtio-blk driver was fixed to work asynchronously and not block virt

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.

Several bhyve quirks

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 both the host and guests are set to US/Pacific (currently PDT). I thought