Bug 939432

(In reply to Vadim Krevs from comment #0)

> How is anyone expected to test this if it does not install in virtualbox ...

There are more hypervisors available than Virtualbox - for example, KVM works very well

(In reply to Richard Brown from comment #1)
> (In reply to Vadim Krevs from comment #0)
> 
> > How is anyone expected to test this if it does not install in virtualbox ...
> 
> There are more hypervisors available than Virtualbox - for example, KVM
> works very well

Virtualbox is very popular, that's all I am saying. I'll give KVM a go. 

P.S.: Is this a policy decision not support Oracle's virtualbox? I recall wanting to try Tumbleweed some time ago when the discussions about Leap started, and it had the same problem with Virtualbox.

(In reply to Vadim Krevs from comment #2)
> 
> P.S.: Is this a policy decision not support Oracle's virtualbox? I recall
> wanting to try Tumbleweed some time ago when the discussions about Leap
> started, and it had the same problem with Virtualbox.

Not a policy decision. this bug could certainly be valid. As I refuse to do anything with Virtualbox I'm afraid I can't reproduce it, so I can't confirm this bug, and won't be doing anything to fix it, but hopefully someone else will :)

(In reply to Vadim Krevs from comment #2)
> (In reply to Richard Brown from comment #1)
> > (In reply to Vadim Krevs from comment #0)
> > 
> > > How is anyone expected to test this if it does not install in virtualbox ...
> > 
> > There are more hypervisors available than Virtualbox - for example, KVM
> > works very well
> 
> Virtualbox is very popular, that's all I am saying. I'll give KVM a go. 
> 
> P.S.: Is this a policy decision not support Oracle's virtualbox? I recall
> wanting to try Tumbleweed some time ago when the discussions about Leap
> started, and it had the same problem with Virtualbox.

Well SLES is not supported in virtualbox yet it seems to work fine there, TW works in virtualbox fine for me as well, I have seen some users reporting similar issues, if I recall correctly changing graphics settings in virtualbox helped (enable/disable 3D acceleration, etc).

Well, I've attempted to install KVM via YAST, and default network bridge creation seems to have failed and now Network Settings does not start anymore.

https://bugzilla.opensuse.org/show_bug.cgi?id=939438

I have just installed Leap into virtualbox and it works mostly fine (apart from missing vbox guest addons in leap).

(In reply to Martin Pluskal from comment #6)
> I have just installed Leap into virtualbox and it works mostly fine (apart
> from missing vbox guest addons in leap).

Could you attach the .vbox file for your vm image?

Created attachment 641987 [details]
vbox config

sure, enjoy

Thanks. The only differences I can see are:

* your host is Windows, mine is openSUSE 13.2. No
* your guest is configured to use 4 processors, mine 2
* your guest is configured to use 4GB RAM, mine 1GB
* your guest uses virtio-net network card, mine - Intel Pro 1000/MT desktop.

I've tried all the above except the first - no Windows pc in sight in my home - but it made no difference.

Can you please attach installation logs?
You can do it e.g. with booting with DVD and disk image and then in DVD rescue system mount disk and grab logs from there ( content of /var/log/YaST2/ should be enough

tgz of Contents of /var/log from the vdi disk image is at the link below. Xorg.log.0 - presumably corresponding to the first boot attempt - is full of errors.

https://drive.google.com/open?id=0B9obXDcgwWMHLUxFcHBGNE9HeHM

Stefan, could you please have a look.

[    17.468] (EE) systemd-logind: failed to get session: PID 936 does not belong to any known session

Known issue related to systemd-logind. Still investigated.

[    17.658] (EE) Failed to load module "vboxvideo" (module does not exist, 0)

vboxvideo X driver no available on the system. Not sure why. Is virtualbox-guest-x11 package installed?

[    17.665] (EE) open /dev/dri/card0: No such file or directory

fallback to modeseting fails for some reason.

[    17.683] (EE) AIGLX: reverting to software rendering

That's because of the fallback to fbdev driver.

(In reply to Stefan Dirsch from comment #13)
> [    17.468] (EE) systemd-logind: failed to get session: PID 936 does not
> belong to any known session
> 
> Known issue related to systemd-logind. Still investigated.
> 
> [    17.658] (EE) Failed to load module "vboxvideo" (module does not exist,
> 0)
> 
> vboxvideo X driver no available on the system. Not sure why. Is
> virtualbox-guest-x11 package installed?

Could you please check.

> 
> [    17.665] (EE) open /dev/dri/card0: No such file or directory
> 
> fallback to modeseting fails for some reason.
> 
> [    17.683] (EE) AIGLX: reverting to software rendering
> 
> That's because of the fallback to fbdev driver.

(In reply to Gabriele Mohr from comment #14)
> (In reply to Stefan Dirsch from comment #13)
> > [    17.468] (EE) systemd-logind: failed to get session: PID 936 does not
> > belong to any known session
> > 
> > Known issue related to systemd-logind. Still investigated.
> > 
> > [    17.658] (EE) Failed to load module "vboxvideo" (module does not exist,
> > 0)
> > 
> > vboxvideo X driver no available on the system. Not sure why. Is
> > virtualbox-guest-x11 package installed?
> 
> Could you please check.
> 
> > 
> > [    17.665] (EE) open /dev/dri/card0: No such file or directory
> > 
> > fallback to modeseting fails for some reason.
> > 
> > [    17.683] (EE) AIGLX: reverting to software rendering
> > 
> > That's because of the fallback to fbdev driver.

No, virtualbox-guest-X11 does not appear to have been installed as part of Leap's installation under virtualbox.

The fbdev driver cannot be used any more as there is nothing giving it the permissions to access /dev/fb when the Xserver is run as non-root.
the virtualbox X11 driver is not used as it is not installed. It looks like it isn't installed because the virualbox guest-kmp isn't installed. This is most likely not installed as it isn't built for the currently shipped kernel.
This may be a dependency issue which I'm currently trying to find out.

The dependencies look oll right more or less.
There are some things missing which we normally do for drm KMPs, however I don't think they are responsible for the fact that the virtualbox guest-kmp doesn't match the kernel.
I've added the pieces we are using for drm for reference in:
https://build.opensuse.org/package/show/home:eeich:branches:Virtualization/virtualbox
I'm not sure what would be required to have a virtualbox-guest-kmp-default that matches kernel-default in 
http://download.opensuse.org/distribution/leap/42.1-Current/repo/oss

Maybe Coolo can help here ...

Changing component and assigning to bug owner of VirtualBox.

Just tried installing Leap from the updated iso (build 46) - openSUSE-42.1-DVD-x86_64-Build0046-Media.iso - and it worked without any issues.

So looks like the issue is fixed and Leap is testable in virtualbox.

Great so we can close the bug.

Installation openSUSE-42.1-DVD-x86_64-Build0043-Media.iso into a VirtualBox VM is OK. I agree that this bug should be closed.