Opened 8 years ago
Closed 8 years ago
#15721 closed defect (invalid)
Debian 8.5 amd64 guest on Windows 10 host problems -> invalid
| Reported by: | seymour | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.2 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
I made a fresh install of Debian 8.5 amd64 on VirtualBox 5.1.2 from a live CD. On starting up the guest, I encountered numerous issues. Host-N shows Guest Additions not detected, Guest OS type - KVM. Settings/Display on Linux says Unknown Display and I am unable to increase the screen resolution. Device/Insert Guest Additions offers VBOXADDITIONS_5.1.2_108956 but on running get Oops! There was a problem running this software. Unable to locate the program. Closing Virtual Machine, Send the Shutdown signal. Causes a blank screen and the guest hangs. I can only do a Power Off or a Save.
I prefer Debian because the distribution provides two years support.
I have been running Debian 7 on Vbox for several years with no major issues.
I have searched the internet on installing guest additions on Debian. It talks about build-essentials and module assistant which are now obsolete.
Seymour
Attachments (2)
Change History (4)
by , 8 years ago
| Attachment: | Debian 8.5 amd64-2016-08-01-14-45-26.log added |
|---|
by , 8 years ago
| Attachment: | Fedora workstation 64bit-2016-08-04-14-24-11.log added |
|---|
comment:1 by , 8 years ago
As an alternative I tried to create a Fedora workstation guest. According to host-N, the guest addition was not detected in Fedora. Furthermore the Fedora window did not respond to the keyboard or mouse.
The Virtualbox documentation mentions rcvboxadd. I could not find this executable in the Debian guest.
I installed linuxmint-18-cinnamon-64bit.iso and did not encounter any issues.
comment:2 by , 8 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
| Summary: | Debian 8.5 amd64 guest on Windows 10 host problems → Debian 8.5 amd64 guest on Windows 10 host problems -> invalid |
I'm sorry, but it looks to me like this is not a bug in VirtualBox, though I am having a bit of trouble understanding what is happening. Could you please ask about this on the forums? If people there decide it is a bug then you can still re-open the ticket. I think it might make sense to make a video recording of what you are doing, possibly with commentary (but make sure people can see any text in the machine on the video).
log file