virtualbox.org

Host: Ubuntu Server 16.04.1 + xfce4 + xrdp
VirtualBox VM 5.1.12 r112440 linux.amd64 (Dec 20 2016 17:20:21)
HP ProDesk 400 G2 MINI without display, remote controled via rdp.

Guest FAIL (crash): Xubuntu 16.04.1, Kubuntu 16.10, Ubuntu 14.04.5
Guest OK: Ubuntu Server 16.04.1, Xubuntu 12.04.4 i386

The installation of the above mention guest OS crash after a few seconds, shortly after the color background is displayed on screen. It seems to have to do with the virtual display. I have made a VM on another machine. Installation of Xubuntu 16.04.1 went good (little graphics disturbance, workaround by F1 F7). I exported this VM and imported it on my machine. It crash shortly after start. However by start it as headless, it boots up and possible to see in preview. Via RDP (by VirtualBox) I can connect to it and use it. I have installed the Guest Additions. However it isn't possible to go into Settings - Display (wanted to change resolution), window shortly popup and disappears.

crash = the vm window disappeares and "Aborted" show in VirtualBox Manager.

I have tested to change some settings for the VM in VirtualBox Manager, but the same behaviour. However server Ubuntu (only text) works, so do also an old 32 bit Xubuntu (desktop).

I think the main problem is in my host. Maybe I have a unique combination of things that doesn't match. One special thing is that my host runs Ubuntu Server with XFCE4 to get graphics and it is remote controled via xrdp. I don't have any display nor keyboard attached to it.

Please, does anybody have any idea of what I can do to fix it?

Best regards,
Michael


PS. Last part of two logs...

Xubuntu 16.04.1 Start:
00:00:09.027635 NAT: DHCP offered IP address 10.0.2.15
00:00:09.074281 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners.
00:00:09.074307 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:09.074310 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:09.074312 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:09.080164 VBVA: InfoScreen: [0] @0,0 800x600, line 0xc80, BPP 32, flags 0x1
00:00:09.107054 AC97: Reset
00:00:09.107315 AC97: Reset

Ubuntu 14.04.5 Install:
00:00:38.531830 NAT: DHCP offered IP address 10.0.2.15
00:00:40.628781 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners.
00:00:40.628807 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:40.628811 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:40.628813 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:40.635763 VBVA: InfoScreen: [0] @0,0 800x600, line 0xc80, BPP 32, flags 0x1

Partial logs are not of great use. We need the whole log:

1. Start the VM. Not from a saved or paused state. Clean start.
2. Take the steps required to generate/observe the error. Record the error message. EXACTLY. Post a screenshot if you have to.
3. Shut down the VM (if it hasn't aborted by itself). Not saved, not paused. Completely shut down. If you can't shut it down by normal means, close the VM window and select "Power off".
4. Right-click on the VM in the VirtualBox Manager. Select "Show Log..."
5. Save it (just the first log), ZIP it and attach it in your response (see the "Upload attachment" tab below the reply form).

Thanks!

More details:
- Create a new VM, Linux, Ubuntu 64bit, default settings for all. - Start, select "xubuntu-16.04.1-desktop-amd64.iso"
- During a few seconds, things happens in the VM display (window). For example big text "Xubuntu 16.04" and four dots.
- Shortly after this: the VM window disappears!
- VirtualBox Manager show red sign and "Aborted"

Log file: //Michael

I have tested with your proposal, but still the same. Actually I have other settings from the beginning, but for this trouble report I used the default. One thing I normally change (for Ubuntu guest) is the networkcard. Since the default Intel card gives super slow network (atleast on my host at work), I used to change it to "PCnet-FAST III".

Now I need to tell something more that have happened, since I think it is related. As I wrote I have a guest that works, an old version Xubuntu 32bit. One thing with it was that I couldn't select the screen resolution I wanted (1200 heigth), not even after guest additions. Maybe this is because of previous attached monitor to host. However now I run with 1200 heigth, what happened! Well, I notice I have started it headless. I shutdown and started it normal (not headless)... it crash! Here is a log while started it headless and shutdown normal way: //Michael

I created and installed a WIndows XP VM. It started and run, in a VM window. I install the GuestAdditions. After this it crash shortly after start. The windows logo and a progress are shortly visible. Log file: However, it is possible to run it Headless.

//Michael

I connected monitor, keyboard and mouse to the host machine. Booted the host, login local and startx. Now it is possible to run Xubuntu 16.04 and also to create a new VM and install Xubuntu 16.04.1. The XP VM is also possible to run. All these run with normal Start (in VM window). So the problem seems to be related that I remote run the host with xrdp. The host is an Ubuntu Server with installed xfce4 to get graphics.

I also notice some other things with the host.
1) If I shutdown in the graphic user interface (remote via xrdp) the machine doesn't shutdown. I think only the remote xfce4 sessions is closed.
2) If an USB is inserted, it isn't mounted (permission reason I think). This if remote xrdp session. If running local on the machine, it works normal.

PS. When I was logged in local on host, I tested USB. It works to get USB sticks into the VMs. (I also learned that if the USB device is USB3, the VM needs to handle USB3) So most things seems to work, except the problem describe in this thread.

//Michael

I have now tested more. Using another (different) hardware, I have tested the following host OS:
Kubuntu 16.10 + VB 5.1.14 = OK
Xubuntu 16.04 + VB 5.1.12 = FAIL
Xubuntu 16.10 + VB 5.1.14 = OK
Xubuntu 16.04 + VB 5.1.14 = FAIL

I realize that a new version of VirtualBox have been released, so I have used a mixed of versions. It is also a change in xrdp in Ubuntu 16.10, compared to 16.04. In the newer it looks different and libxup.so (xorgxrdp) is used instead of libvnc.so (vnc).

Next step, I updated my machine (the original, that this thread started with). This result in 36 new packages, incl. VirtualBox 5.1.14 r112924. Result = FAIL, still the same problem. I tested to use libxup.so, but cannot login in (doesn't work).

So now we getting closer. It seems like a newer Ubuntu might fix the problem.

Now I install Ubuntu Server 16.10 on the new test hardware and did:
sudo apt update
sudo apt upgrade
reboot
sudo apt install xfce4 xrdp
sudo apt install build-essential dkms
sudo apt install libcurl3 libpython2.7 libsdl1.2debian libvpx3
sudo apt install libqt5core5a libqt5gui5 libqt5opengl5 libqt5printsupport5 libqt5widgets5 libqt5x11extras5
sudo dpkg -i virtualbox-5.1_5.1.14-112924-Ubuntu-yakkety_amd64.deb
reboot
login remote with rdp
-> OK

However this isn't a LTS version. So I'm not happy yet.

All the VMs that don't work, I can run them headless. Actually, normally I want to run them headless. I let VB supply me rdp service to them. So maybe I can live with this, or else it seems I need to use newer (non LTS) Ubuntu.

PS. Annoying that the "Device" menu isn't available for the headless VMs. I propose it should be added in the right click menu. ...and maybe "Take Screenshot...", I think it is possible to do on a headless VM.

//Michael

Yesterday one VM didn't run anymore, not accessable on the network. It's a Ubuntu Server running with a VM window. I connect to the host (it's the machine this thread started about) and notice that the VM window was hanging, no responce. I also notice that the VirtualBox Manager window was also dead. However two other VMs was still running (headless). Tried to get something to work again, but failed. Start kill virtualbox processes and I lost all VM's. ...now I'm worried. Is VirtualBox an instable product? ...or maybe this problem also have to do with the problem I have describe in this thread. I hope so and that this will never occur when running Ubuntu 16.10 (xorgxrdp) as the host.

//Michael