Partial boot up and stops

English Virtualization
1

Hi::slight_smile:

Host-Windows XP, Guest-OpenSuse 12.3, VirtualBox 4.2.18, Acer laptop.

After reading several online tutorals about guest additions, I decided to open a terminal and I entered the following commands:

sudo zypper install gcc make automake autoconf kernel-source

sudo sh VBoxLinuxAdditions.run

The download and installs lasted for maybe an hour. I rebooted and all went well. Later a popup appeared on OpenSuse desktop asking if I wanted to add updates. I agreed. After completed, I rebooted again and that is when during the booting process it suddenly stopped. Please see Susepaste that I am sending.

SUSE Paste

2

Apparently the graphics driver cannot be loaded.
Maybe the updates included a newer kernel?
In this case you would have to reinstall the guest additions.

But I never had a need to install them in the first place. OpenSUSE does include virtualbox-guest-x11 and virtualbox-guest-tools by default anyway…
Maybe it’s sufficient to re-install those packages (and virtualbox-guest-kmp-desktop)?

3

Does OpenSuse 12.3 also do automatic updates also? Just install the guest and no other installations required? There is so much misleading info that says to download guest additions. Even in the Linux online manual it says to do apt-get, guest additions, and many other things. Where does this information appear, so that in future I don’t go on a wild goose chase again. Are you also saying that after I reinstall the guest, that I should re-install these same packages that have caused this problem? I am not sure I am understanding? :\ Would it be sufficient to just do a command “suse virtualbox-guest-kmp-desktop” and not install those other packages that seem to be corrupted. I remember that when they were downloading an error occurred and I was asked to send a report and I agreed but it was so long and sent me to another link, etc…too much. I just canceled the report.

4

What do you mean with that?
By default openSUSE does not install updates automatically. It just shows you that there are updates available.
You have to initiate the installation manually, but the updater can be configured to that automatically as well.

Just install the guest and no other installations required?

Correct, openSUSE installs the guest additions automatically.

There is so much misleading info that says to download guest additions. Even in the Linux online manual it says to do apt-get, guest additions, and many other things. Where does this information appear, so that in future I don’t go on a wild goose chase again.

Well, if it mentions apt-get, it’s most likely intended for Debian or Ubuntu… :wink:

Are you also saying that after I reinstall the guest, that I should re-install these same packages that have caused this problem? I am not sure I am understanding? :\

If you re-install openSUSE those guest packages should get installed automatically, so no further action necessary.

Would it be sufficient to just do a command “suse virtualbox-guest-kmp-desktop” and not install those other packages that seem to be corrupted.

First check with “uname -a” which kernel you are using. If not kernel-desktop, you have to replace the “desktop” in the following command appropriately.
You can re-install the included guest additions with:

sudo zypper in -f virtualbox-guest-kmp-desktop virtualbox-guest-x11 virtualbox-guest-tools

But you should uninstall the files created by VBoxLinuxAdditions.run first:

sudo sh ./VBoxLinuxAdditions.run uninstall

And no, you don’t have to install VBoxLinuxAdditions.run on an openSUSE guest, the guest additions are already included.

If it still doesn’t start afterwards, you should remove the file /etc/X11/xorg.conf if present. (maybe
VBoxLinuxAdditions.run creates this?)

You can of course install the guest additions using “VBoxLinuxAdditions.run” like explained in the manual (there is a section especially for openSUSE), but it’s not necessary. And you should remove the openSUSE packages first in that case.

5

Thank you, I appreciate your help. For now, I will “remove” the guest from VB since all I have now is a black screen. I will then reinstall from DVD again, from scratch. That way “VBoxLinuxAdditions.run” and any other packages will all be removed and I know that all is clean from problems. After this next install, I like your idea that I should not add anything. At that time I will also check "“uname -a” to see if I have the kernel-desktop. Wish me luck.:slight_smile:

6

IIANM you must specifically enable the PAE extension in your VM’s settings to get kernel-desktop in VirtualBox, I don’t think PAE is enabled by default.
And without PAE, kernel-default will get installed, because kernel-desktop (and kernel-pae of course) would not work.

But that shouldn’t really matter for you. You would just have to know which one you are in fact using if you want to manually install packaged kernel modules like virtualbox-guest-kmp (and as I said, the correct one should get installed automatically).

7

I found the location of enable PAE and will attempt to enable it immediately after I create the VM guest in VB and “before” I click “installation” button of Guest. Reason being, is that during the installation, the default kernel pops up and installs automatically. At that point, I think it is too late to enable PAE, correct?

8

Yes, for the installation it would be to late then. But you could always install a different kernel afterwards as well.

I just don’t understand why you bother about that now. You should be fine with kernel-default as well (at least if you don’t want to add more than 4GB RAM to your VM).

9

On 2013-11-01 20:36, jimhebert wrote:
>
> Thank you, I appreciate your help. For now, I will “remove” the guest
> from VB since all I have now is a black screen. I will then reinstall
> from DVD again, from scratch. That way “VBoxLinuxAdditions.run” and any
> other packages will all be removed and I know that all is clean from
> problems. After this next install, I like your idea that I should not
> add anything. At that time I will also check "“uname -a” to see if I
> have the kernel-desktop. Wish me luck.:slight_smile:

You have to be careful about what documentation you read. It may be
intended for other distros, and there maybe big differences. Some times
substantial. Also, Linux can evolve faster than Windows, so what a
document said two years ago may be obsolete.

Better read things from the opensuse.org site - and if you have doubts,
just ask us :wink:

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

10

On 2013-11-01 20:56, wolfi323 wrote:
> IIANM you must specifically enable the PAE extension in your VM’s
> settings to get kernel-desktop in VirtualBox, I don’t think PAE is
> enabled by default.
> And without PAE, kernel-default will get installed, because
> kernel-desktop (and kernel-pae of course) would not work.

IIRC, his host machine is Windows XP - would it support that?

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

11

I’ve got the guest installed and running OK. Should I "enable PAE " which is in VB, system, processor?

12

Yes, if his CPU supports it, of course.

13

You have to decide that yourself.
From the VirtualBox manual:

In addition, the **"Enable PAE/NX"**
setting determines whether the PAE and NX capabilities of the host CPU
will be exposed to the virtual machine. PAE stands for "Physical Address
Extension". Normally, if enabled and supported by the operating system,
then even a 32-bit x86 CPU can access more than 4 GB of RAM. This is
made possible by adding another 4 bits to memory addresses, so that with
36 bits, up to 64 GB can be addressed. Some operating systems (such as
Ubuntu Server) require PAE support from the CPU and cannot be run in a
virtual machine without it.

openSUSE does work without PAE enabled as you already noticed.
But if you enable it now after the installation, you also have to install a different kernel (kernel-desktop or kernel-pae) to make use of PAE. kernel-default does not know anything about PAE.

The main point for PAE is to make use of more than 4 GB RAM as I already mentioned. If you don’t want that, there’s no need to turn it on.

Oh, and this only applies to a 32bit guest. If you’re running a 64bit guest, it doesn’t matter anyway, since the 64bit architecture has 64bit addresses and can therefore address much more than 4GB.

14

Thank you… I will run it without PAE…Another problem I have had concerns copy and paste from host to guest and vice versa. Should I open another thread? Maybe this is a VB forum question? I have both VB and guest clipboards in bidirectional and in drag’n drop. I have googled this topic and tried many ways. Nothing works.

15

I got copy/paste working now…