This has happened a couple more times in the past two days, always with a 32bit windows 10 guest running. This time though, I just left the system a bit longer to see what would happen. First, only a few windows on the desktop (plasma) became unresponsive, then eventually they all froze with the exception of the mouse pointer. Then after about 1 or 2 minutes, the mouse pointer froze as well and the caps lock began flashing indicating a kernel panic. I powered off the computer and rebooted. Here is the log from before the freeze up to when I rebooted:
Aug 08 21:03:16 precision plasmashell: QXcbConnection: XCB error: 2 (BadValue), sequence: 58225, resource id: 67108869, major code: 142 (Unknown), minor code: 3
Aug 08 21:04:06 precision plasmashell: QXcbConnection: XCB error: 2 (BadValue), sequence: 59222, resource id: 44040197, major code: 142 (Unknown), minor code: 3
Aug 08 21:05:17 precision plasmashell: QXcbConnection: XCB error: 2 (BadValue), sequence: 59618, resource id: 81788945, major code: 142 (Unknown), minor code: 3
-- Reboot --
As you can see, there were no logs about anything other than the XCB connection prior to the kernel panic. Then, immediately after rebooting, I went to the logs to see if there was anything useful, and it froze again. This time, the only thing open was a Konsole window. This is the second time it has happened with exactly this same order of events. The last time I attempted to check the logs, it caused a system freeze also, but only after experiencing the first freeze with he VM running.
Here are the logs from the second freeze:
Aug 08 21:10:50 precision sudo: me : TTY=pts/0 ; PWD=/home/me ; USER=root ; COMMAND=/usr/bin/journalctl --since 10 minutes ago
Aug 08 21:10:50 precision sudo: pam_unix(sudo:session): session opened for user root by me(uid=0)
-- Reboot --
Again, as you can see, some really useful stuff… The only difference with the second freeze is that it wasn’t a kernel panic like the first one. Subsequent boot is fine, no freezes so far.
Anyone have some ideas what would be causing a kernal panic with a 32bit guest OS in KVM? I have not noticed a freeze any other time, and I can leave my laptop on all day and it’s fine as long as I don’t fire up that VM. I even thought maybe there was something weird with that installation so I reinstalled it…same problem. 64bit guest OSes seem to run fine. Could this be a problem with windows 10 32bit? Is there a specific CPU architecture I should try for the guest, maybe?