You're running on KVM, which probably means you're using virtio. Have you set the 0x2 flag on the vio driver?
I experienced hangs on my KVM-hosted OpenBSD VMs until I read the vio(4) man page: http://man.openbsd.org/vio.4 "The *vio* driver provides support for the virtio(4) <http://man.openbsd.org/virtio.4> network interface provided by bhyve, KVM, QEMU, and VirtualBox. Setting the bit 0x2 in the flags disables the RingEventIndex feature. This can be tried as a workaround for possible bugs in host implementations of *vio* at the cost of slightly reduced performance." An example of how to do this: http://blather.michaelwlucas.com/archives/2083 On Tue, Jul 26, 2016 at 2:02 AM, Edd Barrett <e...@theunixzoo.co.uk> wrote: > Hi, > > This is very much off-topic, and a long shot. > > I have a VM hosted at Bytemark, which seems to have started freezing > about once a week. It stops responding to the network, and if I bring up > the console, I see the login prompt with a flashing cursor, but it is > not responsive to key-presses. > > I have a support ticket open, but we are not sure if it's an OpenBSD > problem, or something on their end. The VM is running 5.9-stable with > all patches applied. FWIW, Bytemark uses KVM + Qemu, so this question may > extend to ARP networks VMs too(?). > > Wondering if anyone else here is hosting on Bytemark (or ARP) and had a > similar issue, or even a workaround. > > Like I said, long shot. > > Cheers > > -- > Best Regards > Edd Barrett > > http://www.theunixzoo.co.uk > > -- andrew fabbro and...@fabbro.org
