Changes between Initial Version and Version 1 of Ticket #19593, comment 13
- Timestamp:
- Jul 2, 2020 8:02:40 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #19593, comment 13
initial v1 5 5 I do have auto capture keyboard enabled, but that was because I had been having problems with VMs not responding to keyboard input and I *thought* perhaps this might help. What would happen is that, intermittently, a guest would not respond to keyboard input (but mouse worked fine in guest) and I would have to switch from full screen mode to windowed mode and then back to full screen so that I could input keys again in the guest. I may not fully understand the meaning of this option, but I thought it worth a try. 6 6 7 My host is Devuan Ascii (2.1) on Vbox 6.1 , though I had the same keyboard problem in 6.0 (I don't recall this in 5.x however). I run about 6 or so guests on an 8-core AMD FX cpu. Most VMs only get 1 vcpu allocated to them.7 My host is Devuan Ascii (2.1) on Vbox 6.1.10 (all guests have updated GAs), though I had the same keyboard problem in 6.0 (I don't recall this in 5.x however). I run about 6 or so guests on an 8-core AMD FX cpu. Most VMs only get 1 vcpu allocated to them. 8 8 9 9 If you feel this is a different issue, please feel free to move this comment to a different ticket. But please do not cancel it altogether. This *might* be related to the current issue; the symptoms are very similar even if the cause slightly different. Either way, this is a Vbox problem and deserves proper treatment. BTW, I discovered this ticket only by googling for a kernel message which has appeared several times in the past day or so on the host. (The message was "VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)"). I am happy to supply additional information.
