Re: Bhyve guest boot error, Buffer I/O error on dev vda1, logical block 0, lost async page write

Rajil Saraswat wrote this message on Mon, Aug 27, 2018 at 17:42 -0500: > On 08/27/2018 11:50 AM, Pete Wright wrote: > > > > > > On 8/26/18 10:07 PM, Sami Halabi wrote: > >> Hi, > >> IIRC pool shouldn't be above 90% used otherwise bad things happen.. > >> but at > >> 69% > >> Can someone explain

Re: on bhyve statistics

>> Currently, bhyve does not expose any of these statistics. All the stats > available through bhyvectl --get-stats seem to be coming from the VMM, > not from the userspace emulation. >That is correct, byhvectl is a diagnostics tool for getting information from the kernel/vmm module. bhyvectl pro

Re: Bhyve guest boot error, Buffer I/O error on dev vda1, logical block 0, lost async page write

On 08/27/2018 11:50 AM, Pete Wright wrote: > > > On 8/26/18 10:07 PM, Sami Halabi wrote: >> Hi, >> IIRC pool shouldn't be above 90% used otherwise bad things happen.. >> but at >> 69% >> Can someone explain thid please? > > it's possible the filesystem was heavily fragmented?  seems suspicious

[Bug 229167] [Hyper-V] [Jun 19, 2018] Recently FreeBSD VM panics during boot-up, especially with Mellanox VF configured

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229167 --- Comment #32 from Dexuan Cui --- (In reply to Andriy Gapon from comment #31) Unluckily I still can't reproduce the issue recently. :-( I created the Marketplace 11.1 VM on Azure, and can't reproduce the issue: FreeBSD decui-bsd111 11.

Re: Bhyve guest boot error, Buffer I/O error on dev vda1, logical block 0, lost async page write

On 8/26/18 10:07 PM, Sami Halabi wrote: Hi, IIRC pool shouldn't be above 90% used otherwise bad things happen.. but at 69% Can someone explain thid please? it's possible the filesystem was heavily fragmented?  seems suspicious - did scrubbing your pool find any errors? -pete -- Pete W

Re: Query regarding tutorials (Please have a quick read of me!)

Thanks for the feedback! Indeed I quite like the errors too when I see other people, its nice when its not to 'rehearsed' feels more natural :) On Mon, 27 Aug 2018 at 16:14, Tommi Pernila wrote: > Hi Paul, > > thanks for the videos, they are looking great. > > some feedback: > Do keep the small

Re: Query regarding tutorials (Please have a quick read of me!)

Hi Paul, thanks for the videos, they are looking great. some feedback: Do keep the small mistakes like typoes or similar in the video. It's always interesting to see how people correct the errors. In the first video the left side of the terminal was slightly cut out. Not too much though. In the

Re: on bhyve statistics

> Hi list, > > I'm currently looking at getting the libvirt prometheus exporter[1] to > work with libvirt+bhyve. In its current state this doesn't work because > at least one of the API calls exposed by libvirt isn't implemented by > the libvirt bhyve driver - so I started looking at implementing

Re: Query regarding tutorials (Please have a quick read of me!)

Heya all part 2 'windows server 2016' is ready: https://www.youtube.com/watch?v=tHIWdoNXGec On Sat, 25 Aug 2018 at 09:55, Paul Webster wrote: > Hey all, > > A while ago I created a youtube channel to start doing video example > versions of the FreeBSD documentation, I have decided that this wee

Re: on bhyve statistics

On 27.08.2018 16:34, Marcelo Araujo wrote: > Hi Fabian, > > 2018-08-27 22:14 GMT+08:00 Fabian Freyer > >: [...] > - are the stats in struct bhyvestats {...} stats exposed or used in any >   non-obvious way? > > > They are most used inside bhyver

Re: on bhyve statistics

Hi Fabian, 2018-08-27 22:14 GMT+08:00 Fabian Freyer : > Hi list, > > I'm currently looking at getting the libvirt prometheus exporter[1] to > work with libvirt+bhyve. In its current state this doesn't work because > at least one of the API calls exposed by libvirt isn't implemented by > the libv

on bhyve statistics

Hi list, I'm currently looking at getting the libvirt prometheus exporter[1] to work with libvirt+bhyve. In its current state this doesn't work because at least one of the API calls exposed by libvirt isn't implemented by the libvirt bhyve driver - so I started looking at implementing it. The fir