Q: Have I seen this crash appear and vanish by accident and is it still there with VMX flag not set? This uses the code that no more adds the VMX flag (and due to that doesn't enable it by default)
- qemu64 - nested can't be used - qemu64,vmx=on - nested can be used => Still Crashes! - kvm64 - nested can't be used - kvm64,vmx=on - nested can be used - does not crash So qemu64 has a deficiency (as intended by upstream) and is unable to run VMX. Our former change adding the full VMX just had it set vmx=on in cmdline and due to that exposed the bug quicker. We need to identify the bug in qemu64 OR use this chance to stop our qemu64 to be different. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868692 Title: default cpu (qemu64) no more capable of nesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1868692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
