Hi Stuart, I had a similar issue on Proxmox /KVM the issue doesnt affect linux guests / windows guests on a KVM Box
It doesnt affect OpenBSD running on Older versions of KVM / Linux Kernel (4.x) it would appear to be a compatibility issue between an openBSD guest and the virtual hardware (virtual timers) as presented by newer KVM boxes http://openbsd-archive.7691.n7.nabble.com/Performance-issues-as-KVM-guest-td334612.html as Stuart Henderson pointed out kernel pre-emption timer disabling worked for us and would probably help you... that said the Kernel Patch as mentioned by Kaptaniks sounds interesting and may be a more permanent fix (on my to do list to try ...) Thanks Tom Smyth On 19 June 2018 at 21:09, Stuart Longland <[email protected]> wrote: > On 20/06/18 00:21, Leo Unglaub wrote: >> Hi, >> i have searched the list archive and found some similar reports but none >> of them found a solution for the problem. (at least not the threads i >> have found) >> >> I run some OpenBSD 6.3 instances in a virtual environment. The host is >> some unknown Linux distribution with qemu on it. After the data center >> updated there kernels and also qemu my virtual OpenBSD instances startet >> to freeze randomly but almost always during login. They freeze up so >> hard that i cannot drop into a debugger or get any output whatsoever. >> There is not even a core dump, nothing. Just for testing purposes i >> installed a 6.2 as well and did syspatch on it just to see if the error >> happens there as well and it does. I have added a dmesg on the bottom of >> the email. > > I had a problem like this as well, this was about the time I was > battling rl0 issues on an old industrial PC, so thought it might've been > something else causing the issues. > > With the exception of the border router, all my other OpenBSD instances > are virtual machines. Updating the VMs to 6.3 proved to be quite an > adventure as the kernel would randomly freeze up. `virt-manager` would > show the virtual processor spinning at 100% CPU, `top` on the host would > show qemu-system-x86_64 consuming 100% CPU. > > One spot it'd freeze up (in the installer) is creating /dev nodes, and > sometimes when re-linking the kernel. Very rarely, it will freeze up on > the production install. > > None of the Linux guests are affected, it's just OpenBSD. I've seen it > in 6.1, 6.2 and 6.3. (They were 6.1 VMs; did the update to 6.2 then to > 6.3.) > > Due to resets during install, one of my routers complains (the > "insecurity" report from cron) about permissions and ownership on /dev > nodes as a result. It's on my TO-DO list to clean this up. > > https://www.mail-archive.com/[email protected]/msg161846.html was posted > as a response to me trying to find a work-around until such time as I > could investigate it further. > > If it happens again, I wonder if it's worth breaking into the QEMU > monitor and seeing where the CPU registers are pointed and to inspect > the RAM on the VM to figure out where in the kernel OpenBSD is spinning? > (Although trying to figure out where in the kernel a particular hex > dump of machine code came from will be "fun".) > > Regards, > -- > Stuart Longland (aka Redhatter, VK4MSL) > > I haven't lost my mind... > ...it's backed up on a tape somewhere. > -- Kindest regards, Tom Smyth Mobile: +353 87 6193172 The information contained in this E-mail is intended only for the confidential use of the named recipient. If the reader of this message is not the intended recipient or the person responsible for delivering it to the recipient, you are hereby notified that you have received this communication in error and that any review, dissemination or copying of this communication is strictly prohibited. If you have received this in error, please notify the sender immediately by telephone at the number above and erase the message You are requested to carry out your own virus check before opening any attachment.
