Opened 10 years ago
Closed 8 years ago
#13688 closed defect (obsolete)
Second VB guest does not start
Reported by: | shinguz | Owned by: | |
---|---|---|---|
Component: | VMM | Version: | VirtualBox 4.3.20 |
Keywords: | guest, start, fail | Cc: | |
Guest type: | Linux | Host type: | Linux |
Description (last modified by )
Since a while (I think since I have upgraded to Ubuntu 14.04) I am not able to start more than 1 VB at the same time any more. The first one starts and works perfectly but when I want to start the second one it fails.
This is reproducesable at any time at will. Please let me know what additional information you want/need.
Error Message:
Failed to open a session for the virtual machine CentOS 6.5 Test2.
No error info.
Result Code: NS_ERROR_CALL_FAILED (0x800706BE) Component: ProgressProxy Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913} Version 4.3.20 r96996 Linux laptop4 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty
Differences between first and second VB:
Test1
00:00:00.525040 SUP: Loaded VBoxDDR0.r0 (/usr/lib/virtualbox/VBoxDDR0.r0) at 0xffffffffa0a9c020 - ModuleInit at 0000000000000000 and ModuleTerm at 0000000000000000 00:00:00.525816 SUP: Loaded VBoxDD2R0.r0 (/usr/lib/virtualbox/VBoxDD2R0.r0) at 0xffffffffa01f8020 - ModuleInit at 0000000000000000 and ModuleTerm at 0000000000000000
Test2
00:00:00.560737 SUP: Opened VBoxDDR0.r0 (/usr/lib/virtualbox/VBoxDDR0.r0) at 0xffffffffa0a9c020. 00:00:00.560862 SUP: Opened VBoxDD2R0.r0 (/usr/lib/virtualbox/VBoxDD2R0.r0) at 0xffffffffa01f8020.
Attachments (2)
Change History (4)
by , 10 years ago
Attachment: | Test1_VBox.log added |
---|
comment:1 by , 10 years ago
Description: | modified (diff) |
---|---|
priority: | blocker → major |
Please attach the complete VBox.log file of boths VMs.
comment:2 by , 8 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Looks like the second VM crashed somewhere. Please reopen if still relevant with a recent VirtualBox release.
Log of the first working VB.