@Sander - Thanks a million for the link, I had come across it before but then couldn't find my way back to it. I have to say I am a little confused though. The version of VBox mentioned in the bug report/documentation is v3.1.0 and the error/defect is marked as fixed. I am however running v3.2.8 so does this bug even apply? From the documentation it would appear that the issue is KVM however the last statement does not clarify exactly what the problem is and how Oracle/VBox plan to address it in the future:
1. 3.0 and before had a bug that ignored the AMD-V in-use bit set by either KVM or buggy BIOSes
2. 3.1 corrected this to prevent complete system reboots when using other hypervisors at the same time (read Windows 7 XP compatibility mode or KVM for that matter)
The fact that KVM refused to work, just by being installed and not even active, with any other hypervisor for many years until Dec. last year IS NOT OUR FAULT.
- Is this bug still an issue in the latest version of VBox (v3.2.
- Will removing KVM from a Linux Host resolve this issue?
- You mentioned "for many years until Dec. Last year" - Does this mean that VBox and KVM now play nice together or how are we to interpret this?
- Can you tell me if Oracle is willing to leave the laxy dazy workaround of using an environment variable as a permanent solution to a serious problem?