virtualbox NS_ERROR_FAILURE (0x80004005)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
Yesterday my Virtualbox guests were still running. Today I get the following error for all guests (windows or Linux).
Failed to open a session for the virtual machine win10.
The VM session was closed before any attempt to power it on.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
I already tried to run sudo /sbin/vboxconfig, reinstalling from Software Manager, reinstalling following Cannot run virtual machines after upgrading virtualbox from 5.0 to 5.1 and upgrading to 5.2.12 r122591 and 5.2.14 r123301. The result was always the same.
My current kernel version is 4.15.0-24-generic #26-Ubuntu SMP.
$ VBoxManage list extpacks
Extension Packs: 1
Pack no. 0: Oracle VM VirtualBox Extension Pack
Version: 5.2.14
Revision: 123301
Edition:
Description: USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption, NVMe.
VRDE Module: VBoxVRDP
Usable: true
virtualbox 18.04
asked Jul 1 '18 at 8:34
mucluxmuclux
3,58011131
|
show 4 more comments
Yesterday my Virtualbox guests were still running. Today I get the following error for all guests (windows or Linux).
Failed to open a session for the virtual machine win10.
The VM session was closed before any attempt to power it on.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
I already tried to run sudo /sbin/vboxconfig, reinstalling from Software Manager, reinstalling following Cannot run virtual machines after upgrading virtualbox from 5.0 to 5.1 and upgrading to 5.2.12 r122591 and 5.2.14 r123301. The result was always the same.
My current kernel version is 4.15.0-24-generic #26-Ubuntu SMP.
$ VBoxManage list extpacks
Extension Packs: 1
Pack no. 0: Oracle VM VirtualBox Extension Pack
Version: 5.2.14
Revision: 123301
Edition:
Description: USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption, NVMe.
VRDE Module: VBoxVRDP
Usable: true
virtualbox 18.04
asked Jul 1 '18 at 8:34
mucluxmuclux
3,58011131
1
Looks like you need to (re-)install Guest Additions correctly.
– David Foerster
Jul 8 '18 at 19:57
@DavidFoerster To install the guest additions I would need a running guest system which I don't have.
– muclux
Jul 8 '18 at 20:09
Sorry, I meant the Virtualbox Extension Pack. That's what the answers to the linked question say anyway. ;-]
– David Foerster
Jul 8 '18 at 20:13
ok, I got the extension pack 5.2.14 from virtualbox.org and opened it (as suggested) with VirtualBox. How can I verify now that it is really installed - because the guest still don't start?
– muclux
Jul 8 '18 at 20:17
The VirtualBox management interface should show you. How or from where did you install VirtualBox btw? And what's the output ofdkms status?
– David Foerster
Jul 8 '18 at 20:21
|
show 4 more comments
Yesterday my Virtualbox guests were still running. Today I get the following error for all guests (windows or Linux).
Failed to open a session for the virtual machine win10.
The VM session was closed before any attempt to power it on.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
I already tried to run sudo /sbin/vboxconfig, reinstalling from Software Manager, reinstalling following Cannot run virtual machines after upgrading virtualbox from 5.0 to 5.1 and upgrading to 5.2.12 r122591 and 5.2.14 r123301. The result was always the same.
My current kernel version is 4.15.0-24-generic #26-Ubuntu SMP.
$ VBoxManage list extpacks
Extension Packs: 1
Pack no. 0: Oracle VM VirtualBox Extension Pack
Version: 5.2.14
Revision: 123301
Edition:
Description: USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption, NVMe.
VRDE Module: VBoxVRDP
Usable: true
virtualbox 18.04
asked Jul 1 '18 at 8:34
mucluxmuclux
3,58011131
Yesterday my Virtualbox guests were still running. Today I get the following error for all guests (windows or Linux).
Failed to open a session for the virtual machine win10.
The VM session was closed before any attempt to power it on.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
I already tried to run sudo /sbin/vboxconfig, reinstalling from Software Manager, reinstalling following Cannot run virtual machines after upgrading virtualbox from 5.0 to 5.1 and upgrading to 5.2.12 r122591 and 5.2.14 r123301. The result was always the same.
My current kernel version is 4.15.0-24-generic #26-Ubuntu SMP.
$ VBoxManage list extpacks
Extension Packs: 1
Pack no. 0: Oracle VM VirtualBox Extension Pack
Version: 5.2.14
Revision: 123301
Edition:
Description: USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption, NVMe.
VRDE Module: VBoxVRDP
Usable: true
virtualbox 18.04
virtualbox 18.04
asked Jul 1 '18 at 8:34
mucluxmuclux
3,58011131
asked Jul 1 '18 at 8:34
mucluxmuclux
3,58011131
edited Jul 8 '18 at 20:28
muclux
asked Jul 1 '18 at 8:34
mucluxmuclux
3,58011131
asked Jul 1 '18 at 8:34
mucluxmuclux
3,58011131
asked Jul 1 '18 at 8:34
mucluxmuclux
3,58011131
3,58011131
1
Looks like you need to (re-)install Guest Additions correctly.
– David Foerster
Jul 8 '18 at 19:57
@DavidFoerster To install the guest additions I would need a running guest system which I don't have.
– muclux
Jul 8 '18 at 20:09
Sorry, I meant the Virtualbox Extension Pack. That's what the answers to the linked question say anyway. ;-]
– David Foerster
Jul 8 '18 at 20:13
ok, I got the extension pack 5.2.14 from virtualbox.org and opened it (as suggested) with VirtualBox. How can I verify now that it is really installed - because the guest still don't start?
– muclux
Jul 8 '18 at 20:17
The VirtualBox management interface should show you. How or from where did you install VirtualBox btw? And what's the output ofdkms status?
– David Foerster
Jul 8 '18 at 20:21
|
show 4 more comments
1
Looks like you need to (re-)install Guest Additions correctly.
– David Foerster
Jul 8 '18 at 19:57
@DavidFoerster To install the guest additions I would need a running guest system which I don't have.
– muclux
Jul 8 '18 at 20:09
Sorry, I meant the Virtualbox Extension Pack. That's what the answers to the linked question say anyway. ;-]
– David Foerster
Jul 8 '18 at 20:13
ok, I got the extension pack 5.2.14 from virtualbox.org and opened it (as suggested) with VirtualBox. How can I verify now that it is really installed - because the guest still don't start?
– muclux
Jul 8 '18 at 20:17
The VirtualBox management interface should show you. How or from where did you install VirtualBox btw? And what's the output ofdkms status?
– David Foerster
Jul 8 '18 at 20:21
1
1
Looks like you need to (re-)install Guest Additions correctly.
– David Foerster
Jul 8 '18 at 19:57
Looks like you need to (re-)install Guest Additions correctly.
– David Foerster
Jul 8 '18 at 19:57
@DavidFoerster To install the guest additions I would need a running guest system which I don't have.
– muclux
Jul 8 '18 at 20:09
@DavidFoerster To install the guest additions I would need a running guest system which I don't have.
– muclux
Jul 8 '18 at 20:09
Sorry, I meant the Virtualbox Extension Pack. That's what the answers to the linked question say anyway. ;-]
– David Foerster
Jul 8 '18 at 20:13
Sorry, I meant the Virtualbox Extension Pack. That's what the answers to the linked question say anyway. ;-]
– David Foerster
Jul 8 '18 at 20:13
ok, I got the extension pack 5.2.14 from virtualbox.org and opened it (as suggested) with VirtualBox. How can I verify now that it is really installed - because the guest still don't start?
– muclux
Jul 8 '18 at 20:17
ok, I got the extension pack 5.2.14 from virtualbox.org and opened it (as suggested) with VirtualBox. How can I verify now that it is really installed - because the guest still don't start?
– muclux
Jul 8 '18 at 20:17
The VirtualBox management interface should show you. How or from where did you install VirtualBox btw? And what's the output of
dkms status?– David Foerster
Jul 8 '18 at 20:21
The VirtualBox management interface should show you. How or from where did you install VirtualBox btw? And what's the output of
dkms status?– David Foerster
Jul 8 '18 at 20:21
|
show 4 more comments
2 Answers
2
active
oldest
votes
After a long, friendly and fruitful chat with @DavidFoerster, it turned out that Microsoft and its weird update policy was the culprit!
David patiently guided me through the reinstallation of the VirtualBox packages from the Ubuntu repositories and check out the configuration (dkms, extension packages, etc.). At last, he asked me to try a new installation with a live ISO. It was then that I noticed that my "Default Machine Folder" defined in VirtualBox - File - Preferences - General was not usable. I knew that it was on a mounted NTFS used by the dualboot Win10 system. A closer look showed that at present it was mounted read-only, which prevented the virtual machines from starting (with a not very helpful error message).
As I recalled then, shortly after I had last successfully booted the VirtualBox guests, I had not only got Ubuntu updates, but I had also booted for the first time since long my native Win10 system. Apparently, Microsoft had then installed updates AND had reactivated the 'fast startup' option (which certainly had been deactivated before!) - so that later, back in Ubuntu, the NTFS file system was mounted in read-only mode, as Windows had not properly shut down.
Now that I have again deactivated the 'fast startup' option in Windows10, my guest systems are running again.
Thank you, David, for asking the right question which set me on the right track!
edited Jul 12 '18 at 6:10
mauliksompura
1054
answered Jul 8 '18 at 22:41
mucluxmuclux
3,58011131
add a comment |
I had similar issue on xubuntu 18.04 where my Virtualbox guests was to run windows 7. Although I had Virtualbox 5.2 installed previously that worked.
I made sure virtualbox-dkms was installed and by passing this command
dpkg -l | grep virtualbox-dkms
Then I purged it and and reinstalled only dkms
apt-get purge virtualbox-dkms && sudo apt-get install dkms
Then I run the command the suggested command to rebuild the kernel.
sudo /sbin/vboxconfig
This is what worked for me.
answered Apr 6 at 17:03
Ismail YushawIsmail Yushaw
1012217
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1051161%2fvirtualbox-ns-error-failure-0x80004005%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
After a long, friendly and fruitful chat with @DavidFoerster, it turned out that Microsoft and its weird update policy was the culprit!
David patiently guided me through the reinstallation of the VirtualBox packages from the Ubuntu repositories and check out the configuration (dkms, extension packages, etc.). At last, he asked me to try a new installation with a live ISO. It was then that I noticed that my "Default Machine Folder" defined in VirtualBox - File - Preferences - General was not usable. I knew that it was on a mounted NTFS used by the dualboot Win10 system. A closer look showed that at present it was mounted read-only, which prevented the virtual machines from starting (with a not very helpful error message).
As I recalled then, shortly after I had last successfully booted the VirtualBox guests, I had not only got Ubuntu updates, but I had also booted for the first time since long my native Win10 system. Apparently, Microsoft had then installed updates AND had reactivated the 'fast startup' option (which certainly had been deactivated before!) - so that later, back in Ubuntu, the NTFS file system was mounted in read-only mode, as Windows had not properly shut down.
Now that I have again deactivated the 'fast startup' option in Windows10, my guest systems are running again.
Thank you, David, for asking the right question which set me on the right track!
edited Jul 12 '18 at 6:10
mauliksompura
1054
answered Jul 8 '18 at 22:41
mucluxmuclux
3,58011131
add a comment |
After a long, friendly and fruitful chat with @DavidFoerster, it turned out that Microsoft and its weird update policy was the culprit!
David patiently guided me through the reinstallation of the VirtualBox packages from the Ubuntu repositories and check out the configuration (dkms, extension packages, etc.). At last, he asked me to try a new installation with a live ISO. It was then that I noticed that my "Default Machine Folder" defined in VirtualBox - File - Preferences - General was not usable. I knew that it was on a mounted NTFS used by the dualboot Win10 system. A closer look showed that at present it was mounted read-only, which prevented the virtual machines from starting (with a not very helpful error message).
As I recalled then, shortly after I had last successfully booted the VirtualBox guests, I had not only got Ubuntu updates, but I had also booted for the first time since long my native Win10 system. Apparently, Microsoft had then installed updates AND had reactivated the 'fast startup' option (which certainly had been deactivated before!) - so that later, back in Ubuntu, the NTFS file system was mounted in read-only mode, as Windows had not properly shut down.
Now that I have again deactivated the 'fast startup' option in Windows10, my guest systems are running again.
Thank you, David, for asking the right question which set me on the right track!
edited Jul 12 '18 at 6:10
mauliksompura
1054
answered Jul 8 '18 at 22:41
mucluxmuclux
3,58011131
add a comment |
After a long, friendly and fruitful chat with @DavidFoerster, it turned out that Microsoft and its weird update policy was the culprit!
David patiently guided me through the reinstallation of the VirtualBox packages from the Ubuntu repositories and check out the configuration (dkms, extension packages, etc.). At last, he asked me to try a new installation with a live ISO. It was then that I noticed that my "Default Machine Folder" defined in VirtualBox - File - Preferences - General was not usable. I knew that it was on a mounted NTFS used by the dualboot Win10 system. A closer look showed that at present it was mounted read-only, which prevented the virtual machines from starting (with a not very helpful error message).
As I recalled then, shortly after I had last successfully booted the VirtualBox guests, I had not only got Ubuntu updates, but I had also booted for the first time since long my native Win10 system. Apparently, Microsoft had then installed updates AND had reactivated the 'fast startup' option (which certainly had been deactivated before!) - so that later, back in Ubuntu, the NTFS file system was mounted in read-only mode, as Windows had not properly shut down.
Now that I have again deactivated the 'fast startup' option in Windows10, my guest systems are running again.
Thank you, David, for asking the right question which set me on the right track!
edited Jul 12 '18 at 6:10
mauliksompura
1054
answered Jul 8 '18 at 22:41
mucluxmuclux
3,58011131
After a long, friendly and fruitful chat with @DavidFoerster, it turned out that Microsoft and its weird update policy was the culprit!
David patiently guided me through the reinstallation of the VirtualBox packages from the Ubuntu repositories and check out the configuration (dkms, extension packages, etc.). At last, he asked me to try a new installation with a live ISO. It was then that I noticed that my "Default Machine Folder" defined in VirtualBox - File - Preferences - General was not usable. I knew that it was on a mounted NTFS used by the dualboot Win10 system. A closer look showed that at present it was mounted read-only, which prevented the virtual machines from starting (with a not very helpful error message).
As I recalled then, shortly after I had last successfully booted the VirtualBox guests, I had not only got Ubuntu updates, but I had also booted for the first time since long my native Win10 system. Apparently, Microsoft had then installed updates AND had reactivated the 'fast startup' option (which certainly had been deactivated before!) - so that later, back in Ubuntu, the NTFS file system was mounted in read-only mode, as Windows had not properly shut down.
Now that I have again deactivated the 'fast startup' option in Windows10, my guest systems are running again.
Thank you, David, for asking the right question which set me on the right track!
edited Jul 12 '18 at 6:10
mauliksompura
1054
answered Jul 8 '18 at 22:41
mucluxmuclux
3,58011131
edited Jul 12 '18 at 6:10
mauliksompura
1054
edited Jul 12 '18 at 6:10
mauliksompura
1054
edited Jul 12 '18 at 6:10
mauliksompura
1054
1054
answered Jul 8 '18 at 22:41
mucluxmuclux
3,58011131
answered Jul 8 '18 at 22:41
mucluxmuclux
3,58011131
answered Jul 8 '18 at 22:41
mucluxmuclux
3,58011131
3,58011131
add a comment |
add a comment |
I had similar issue on xubuntu 18.04 where my Virtualbox guests was to run windows 7. Although I had Virtualbox 5.2 installed previously that worked.
I made sure virtualbox-dkms was installed and by passing this command
dpkg -l | grep virtualbox-dkms
Then I purged it and and reinstalled only dkms
apt-get purge virtualbox-dkms && sudo apt-get install dkms
Then I run the command the suggested command to rebuild the kernel.
sudo /sbin/vboxconfig
This is what worked for me.
answered Apr 6 at 17:03
Ismail YushawIsmail Yushaw
1012217
add a comment |
I had similar issue on xubuntu 18.04 where my Virtualbox guests was to run windows 7. Although I had Virtualbox 5.2 installed previously that worked.
I made sure virtualbox-dkms was installed and by passing this command
dpkg -l | grep virtualbox-dkms
Then I purged it and and reinstalled only dkms
apt-get purge virtualbox-dkms && sudo apt-get install dkms
Then I run the command the suggested command to rebuild the kernel.
sudo /sbin/vboxconfig
This is what worked for me.
answered Apr 6 at 17:03
Ismail YushawIsmail Yushaw
1012217
add a comment |
I had similar issue on xubuntu 18.04 where my Virtualbox guests was to run windows 7. Although I had Virtualbox 5.2 installed previously that worked.
I made sure virtualbox-dkms was installed and by passing this command
dpkg -l | grep virtualbox-dkms
Then I purged it and and reinstalled only dkms
apt-get purge virtualbox-dkms && sudo apt-get install dkms
Then I run the command the suggested command to rebuild the kernel.
sudo /sbin/vboxconfig
This is what worked for me.
answered Apr 6 at 17:03
Ismail YushawIsmail Yushaw
1012217
I had similar issue on xubuntu 18.04 where my Virtualbox guests was to run windows 7. Although I had Virtualbox 5.2 installed previously that worked.
I made sure virtualbox-dkms was installed and by passing this command
dpkg -l | grep virtualbox-dkms
Then I purged it and and reinstalled only dkms
apt-get purge virtualbox-dkms && sudo apt-get install dkms
Then I run the command the suggested command to rebuild the kernel.
sudo /sbin/vboxconfig
This is what worked for me.
answered Apr 6 at 17:03
Ismail YushawIsmail Yushaw
1012217
answered Apr 6 at 17:03
Ismail YushawIsmail Yushaw
1012217
answered Apr 6 at 17:03
Ismail YushawIsmail Yushaw
1012217
answered Apr 6 at 17:03
Ismail YushawIsmail Yushaw
1012217
1012217
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1051161%2fvirtualbox-ns-error-failure-0x80004005%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Looks like you need to (re-)install Guest Additions correctly.
– David Foerster
Jul 8 '18 at 19:57
@DavidFoerster To install the guest additions I would need a running guest system which I don't have.
– muclux
Jul 8 '18 at 20:09
Sorry, I meant the Virtualbox Extension Pack. That's what the answers to the linked question say anyway. ;-]
– David Foerster
Jul 8 '18 at 20:13
ok, I got the extension pack 5.2.14 from virtualbox.org and opened it (as suggested) with VirtualBox. How can I verify now that it is really installed - because the guest still don't start?
– muclux
Jul 8 '18 at 20:17
The VirtualBox management interface should show you. How or from where did you install VirtualBox btw? And what's the output of
dkms status?– David Foerster
Jul 8 '18 at 20:21