Re: Discuss the 4.1.8 release
Posted: 15. Mar 2012, 20:19
Follow up:NeBlackCat wrote:With all due respect, please read what I actually write. This is nothing to do with guests. My linux *host* won't run vbox any more (never mind run a guest), and all I did was upgrade to 4.1.8. Prior to that, it did. The previous version wasn't old. I also just upgraded to 4.1.10 and the problem remains. While I can't (as no-one can) guarantee that it isn't a system problem, I don't have problems running anything else, and didn't have a problem running Virtualbox before.mpack wrote:You say in your own earlier message that you don't know what version you upgraded from, which means you also can't say with any confidence that this is a new problem in v4.1.8 (or indeed that it's a problem in VirtualBox at all). This thread is for discussing new issues in v4.1.8 - and frankly it's even a little late for that, given that a new release is likely soon. As I said before, "Linux Guests" seems to me like the right place to discuss your problem with a Linux Guest.
I ran Synaptic and did a complete removal of 4.1.10. I then installed 4.0.16 from Synaptic, and that ran fine (ie. it didn't just appear then disappear from sight when run, didn't actually try to run a VM). Then did a complete removal of that. Then installed the 4.1.10 deb again.
It now doesn't disappear either, but I can't run a VM in it - if I create an "empty" (ie. no virtual hard disk) VM in the UI (which succeeds) and try to run it, I get the following error:
Code: Select all
Failed to open a session for the virtual machine FRED.
Failed to load VMMR0.r0 (VERR_SUPLIB_OWNER_NOT_ROOT)
Result code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}sudo chown root:root /usr
sudo chown root:root /usr/lib
And now the VM runs. For the life of me, I don't understand how this happened or what's going on.