Opened 7 years ago
Closed 6 years ago
#17788 closed defect (worksforme)
ubuntu installation stuck and only black screen is seen
Reported by: | bobythomas | Owned by: | |
---|---|---|---|
Component: | USB | Version: | VirtualBox 5.1.38 |
Keywords: | Ubuntu installation hung | Cc: | |
Guest type: | Linux | Host type: | Windows |
Description (last modified by )
Procedure:
- Installed VirtualBox-5.1.38-122592-Win on Winows10
- Then trying to install and bring up ubuntu-17.04-desktop-i386 as the guest OS
- iso image is selected
- Installation is hung
Additional info:
- Used VB 5.2 and ubuntu16.04, but same result.
- Both 3D & 2D accelerations are disabled
Logs: VBoxSVC logs show that
00:00:00.199921 Getting USB descriptor failed with error 31 00:00:00.246936 HostDnsMonitor: old information 00:00:00.246936 no server entries 00:00:00.246936 no domain set 00:00:00.246936 no search string entries 00:00:00.246936 HostDnsMonitor: new information 00:00:00.246936 server 1: 125.22.47.125 00:00:00.246936 server 2: 125.22.47.100 00:00:00.246936 no domain set 00:00:00.246936 no search string entries 00:00:00.246936 HostDnsMonitorProxy::notify 00:00:00.340339 SUPR0QueryVTCaps -> VERR_VMX_MSR_ALL_VMX_DISABLED 00:00:00.341322 VD: VDInit finished 00:00:00.342822 VirtualBox: object created 00:00:54.080488 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={b2547866-a0a1-4391-8b86-6952d82efaa0} aComponent={MachineWrap} aText={This machine does not have any snapshots}, preserve=false aResultDetail=0 00:01:31.660118 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={edba9d10-45d8-b440-1712-46ac0c9bc4c5} aComponent={ExtPackManagerWrap} aText={No extension pack by the name 'Oracle VM VirtualBox Extension Pack' was found}, preserve=false aResultDetail=0 00:01:32.039966 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={b2547866-a0a1-4391-8b86-6952d82efaa0} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0
Attachments (1)
Change History (7)
by , 7 years ago
Attachment: | VBoxSVC.log added |
---|
comment:1 by , 7 years ago
Just a friendly reminder; you remember the requirements in the new ticket page? They're actually listed before the ticket form, so I'm not sure how you missed it. I don't see any of them fulfilled, not even a VBox.log (the VBoxSVC.log is not required at this point)...
Attach a (full) log file ("Machine" menu/"Show Log" in the main VirtualBox Manager window) straight away to save time for you and for us. The log file contains a lot of useful information about both the host and the guest systems as well as information about what happened during a particular machine run. Please do not cut and paste it.
May I also suggest something? It's usually better and faster, if issues get first addressed in the VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. Plus there are a lot more eyes in the forums.
So, if you can, please open a new thread in the Linux Guests section of the forums. Please be sure to mention that you came from the bug tracker and include the ticket number.
comment:2 by , 6 years ago
Related discussion in the forums: https://forums.virtualbox.org/viewtopic.php?f=3&t=88398
comment:3 by , 6 years ago
Description: | modified (diff) |
---|
comment:4 by , 6 years ago
Description: | modified (diff) |
---|
comment:5 by , 6 years ago
According to a message by the OP in the forums, the problem was the unavailability of VT-x from the BIOS setting.
The issue has been resolved, the ticket can be closed.
comment:6 by , 6 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
logs