Opened 16 years ago
Closed 15 years ago
#3203 closed defect (fixed)
Opensuse 11.1 fail bootup with Virtualbox 2.1.2 with gdmdisplay error -> unable to reproduce, possibly fixed in SVN
Reported by: | aven | Owned by: | |
---|---|---|---|
Component: | GUI | Version: | VirtualBox 2.1.2 |
Keywords: | gdmdisplay | Cc: | |
Guest type: | Linux | Host type: | Linux |
Description
I have used Virtualbox 2.1 before when I installed Opensuse 11.1 on a Ubuntu 8.10 host but I uninstalled the Opensuse install after a while. I upgraded to Virtualbox 2.1.2 and tried to reinstall Opensuse again, it started to have this gdmdisplay error.
No matter if it was with KDE or Gnome or a different host machine like Windows Vista, it gave a gdmdisplay error at startup. It did not have this error in the previous version but, Opensuse booted up fine in failsafe mode for some reason.
Attachments (2)
Change History (19)
follow-up: 2 comment:1 by , 16 years ago
follow-up: 3 comment:2 by , 16 years ago
Replying to michael:
Was this with or without hardware virtualisation? Could you please attach a log from a run of the VM?
I enabled 3D acceleration. I have a athlon xp 2200+ with a via/s3 integrated video.
Can you please tell me how I can make a log?
comment:3 by , 16 years ago
comment:4 by , 16 years ago
Summary: | Opensuse 11.1 fail bootup with Virtualbox 2.1.2 with gdmdisplay error → Opensuse 11.1 fail bootup with Virtualbox 2.1.2 with gdmdisplay error -> unable to reproduce, possibly fixed in SVN |
---|
I was unable to reproduce this using the current development version. I tried the following: creating a new 32bit openSUSE VM with the default settings and without hardware virtualistation, host Ubuntu 8.10 64bit. I installed openSUSE from the 11.1 installation DVD, using the defaults (except for the location, where I chose Germany) and with Gnome as a desktop choice. The installation completed successfully, including the final start of the installed system. The only difference I see is that you used a 32bit host. If you can see any important differences, please point them out, otherwise I will assume that your issue has been fixed since 2.1.2 was released.
comment:5 by , 16 years ago
The problem actually arose from the release of 2.1.2 and the weird thing was that, even in both kde or in gnome, the gdmdisplay didn't work for some reason.
In the installation, I didn't actually go with default install. I made all the partitions into 1 large one with no swap or anything. I made it autologin(if that makes any difference) and I turned up the number of colors allowed to be displayed from 16 bit to 24 bit. Everything else should not really have been touched. If it doesn't work, I'll write detailed instructions of what I did exactly. BTW, I turned floppy mount off in virtualbox, enabled cd mounting and usb as well as 3d acceleration of graphics(but that doesn't seemed to have mattered).
comment:6 by , 16 years ago
How did you turn up the number of colours? And no, the 3D acceleration shouldn't be relevant, since you didn't install Additions and it is not yet supported in the Linux additions anyway.
comment:7 by , 16 years ago
The step in the configurations, I did not use auto configurations and I changed the number of colors to display in hardware configurations section.
comment:8 by , 16 years ago
Two questions: 1) did you take a look in the Xorg log (/var/log/Xorg.0.log) to see if it contained any information? 2) if you set up a second VM, does this still occur? I have a suspicion that this is an X.Org configuration issue rather than a VirtualBox one.
comment:9 by , 16 years ago
for question 1, which xorg.log are you talking about, the opensuse guest or the host.
I installed ubuntu as guest and it works flawlessly on both my windows vista host and on my ubuntu host. its just that opensuse doesn't work on either for some reason.
comment:10 by , 16 years ago
I meant Xorg.0.log on the openSUSE guest, and whether you can reproduce this issue if you install another openSUSE guest.
comment:11 by , 16 years ago
Its kinda strange but, I was able to consistently reproduce the issue many times with every opensuse reinstall. Do you require the exact setup I did from configuring Vbox all the way to what I configured and did with opensuse install? I think the problem was triggered with something I did with opensuse as guest. The weird thing is that when opensuse is started, it starts booting in console rather than with a gui even from the start. I never had these problems with the same settings before.
When I tried to view the Xorg log (/var/log/Xorg.0.log) but that file was not found and and when other than that, any command like it gave something like a gtk error "open cannot be displayed"
comment:12 by , 16 years ago
Perhaps you should try giving me detailed instructions. So far I have completely failed to reproduce this.
comment:13 by , 16 years ago
This was the only method I used to encounter this error, I have not tried a default install without customisations.
comment:15 by , 16 years ago
I am using 3.0.2 this time. After installation, the screen is just blank when right when it gets past the boot menu. Same configs as last time too.
comment:16 by , 15 years ago
I have openSUSE 11.1 guests running perfectly here.
Host: Windows 7, x64, Core 2 Q6600, VBox 3.0.10 (and 3.1.0-BETA1). VT-x = on.
Guests: openSUSE 11.1 (32+64bit, SMP) inc. Guest Additions, Network and Sound. (except 3D).
Maybe it is related to software virtualization, need to check.
-Technologov
comment:17 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please reopen if this problem is reproducible with VBox 3.1.8. In that case attach a VBox.log file of such a VM session.
Was this with or without hardware virtualisation? Could you please attach a log from a run of the VM?