Opened 10 years ago
Closed 10 years ago
#14406 closed defect (invalid)
Guest Ubuntu 15.04 (64 bit) Graphic Driver crashes -> probably guest out of disk space
Reported by: | Aweman | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.0.0 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Windows |
Description
Because I habe two other issues (#14385 and #14405) with Ubuntu on Windows 10 Pro (64 bit) I reinstalled it about 10 times.
Three times, after the installation process has completed, after the first Restart (which always crashes), the installation was corrupted because of a Graphic Driver error even with Testbuild 5.0.1-101957 with AVX turned off.
See the behaviour in this video: https://www.dropbox.com/s/yyj4spvbqjzv5et/Ubuntu%2015.04%20Display%20Crash.webm?dl=0
Attachments (6)
Change History (26)
by , 10 years ago
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Sorry but I reinstalled it already and with this installation I don't have the problem
comment:3 by , 10 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Summary: | Guest Ubuntu 15.04 (64 bit) Graphic Driver crashes → Guest Ubuntu 15.04 (64 bit) Graphic Driver crashes -> no longer reproducible |
I'm sure if there is something I need to fix then someone else will notice. Thanks for letting me know.
comment:4 by , 10 years ago
Ok I installed it two more times to recreate the bug and now I can provide you with the log files
by , 10 years ago
Attachment: | Xorg.0.log1 added |
---|
by , 10 years ago
Attachment: | Xorg.0.log2 added |
---|
comment:5 by , 10 years ago
Could you please describe in detail how you did the installation? The X.Org log files show that the VirtualBox Additions video driver is not correctly installed.
comment:6 by , 10 years ago
I didn't install any driver, because it crashes within the first restart, after the Ubuntu Setup has completed
comment:7 by , 10 years ago
The request for a detailed description of the installation still stands though. Thanks.
comment:8 by , 10 years ago
Resolution: | obsolete |
---|---|
Status: | closed → reopened |
I mounted "ubuntu-15.04-desktop-amd64.iso" and made a clean installation through the Setup GUI. At the end of the setup process I restarted the VM and then it didn't boot up, instead the issue described showed up
comment:9 by , 10 years ago
Did you choose any non-default options at any point during the installation process, either while creating the machine or during the guest installation? I.e. accepting when the installed machine asks you if you want to install guest drivers from the Ubuntu repositories? Your detailed description of the installation was somewhat short: since I and many other people have done what you describe without the crashes you are seeing I would be interested to know what is different in your case.
comment:10 by , 10 years ago
I have installed it about 14 times, 4 installations showed the issue
I made the following changes to the Default Profile of the VM:
- Base memory to 2048 MB
- Boot Order: deactivated Floppy and moved it to third position
- Set processors to 2
- Set video memory to 64 MB
- Removed Controller IDE
- Added a optical drive to SATA where I mounted the iso
then I set: VBoxManage setextradata "Ubuntu 15.04" VBoxInternal/CPUM/IsaExts/AVX 0
During the Ubuntu Setup, the only non default option I selected was during second step: "Download updates while installing"
comment:11 by , 10 years ago
So far unable to reproduce. Trying to think what else I can do here. Could you attach the logs from /var/log/lightdm on the guest when this is happening if you can get at them, or as soon after as possible (perhaps reboot to safe mode)? And does this occurs, does it always occur again if you stop the guest and restart?
comment:12 by , 10 years ago
So far unable to reproduce. Could you also disable 'AVX2', 'XSAVE', 'SSE4.1', 'SSE4.2' and 'AESNI' in the same way as you disabled 'AVX' to see if that makes any difference?
VBoxManage setextradata "Ubuntu 15.04" "VBoxInternal/CPUM/IsaExts/AVX2" 0 VBoxManage setextradata "Ubuntu 15.04" "VBoxInternal/CPUM/IsaExts/XSAVE" 0 VBoxManage setextradata "Ubuntu 15.04" "VBoxInternal/CPUM/IsaExts/SSE4.1" 0 VBoxManage setextradata "Ubuntu 15.04" "VBoxInternal/CPUM/IsaExts/SSE4.2" 0 VBoxManage setextradata "Ubuntu 15.04" "VBoxInternal/CPUM/IsaExts/AESNI" 0
comment:13 by , 10 years ago
It does always occur when the guest starts.
I disabled 'AVX2', 'XSAVE', 'SSE4.1', 'SSE4.2' and 'AESNI' but it doesn't change the issue
by , 10 years ago
Attachment: | lightdm.log.old added |
---|
by , 10 years ago
Attachment: | x-0.log.old added |
---|
by , 10 years ago
Attachment: | x-0-greeter.log.old added |
---|
comment:14 by , 10 years ago
The third of those log files just says: "Error writing X authority: Failed to write X authority /var/lib/lightdm/.Xauthority: No space left on device". Could it really just be that your virtual disk is full?
comment:15 by , 10 years ago
I also saw the "No space left on device" message in the log file, but there are are 2 GB left of free space on the Virtual Harddrive!?
comment:16 by , 10 years ago
I have to ask though: can you still reproduce this if you add another few GB to the drive size? Of course, that does not explain why you see this and no one else (that I am aware of - perhaps a bit of searching would be a good thing to do) does.
comment:17 by , 10 years ago
One report found so far - may or may not be related: http://iswwwup.com/t/adc869520c22/13-04-lightdm-crashing-black-screen-flashing-cursor.html
comment:18 by , 10 years ago
http://askubuntu.com/questions/223501/ubuntu-gets-stuck-in-a-login-loop
Might be worth asking the lightdm people:
comment:19 by , 10 years ago
Ok I resized the *.vdi file and then Gparted the Partitions, now I have 4 GB of free space and it works. Weird!
Thank you
comment:20 by , 10 years ago
Resolution: | → invalid |
---|---|
Status: | reopened → closed |
Summary: | Guest Ubuntu 15.04 (64 bit) Graphic Driver crashes -> no longer reproducible → Guest Ubuntu 15.04 (64 bit) Graphic Driver crashes -> probably guest out of disk space |
Thank you for your patience. Perhaps someone was reporting free space wrong to someone else, or something was getting allocated and then removed again before your check - free space is a more difficult concept than it sometimes seems... Still strange that no one else is reporting this, but whatever.
Could you please attach /var/log/Xorg.* from the guest? Thanks.