boot fail virtualbox Guest nach Kernel Update openSuSE-2019-2503

fwkuser · November 21, 2019, 12:19pm

Hallo zusammen,

nach Kernel Update: openSuSE-2019-2503 auf Host und Guest (VirtualBox)
bleibt der Guest beim booten hängen. (deadlock)

Guest’s älterer Versionen (Linux) oder (Windows, debian) laufen korrekt.

Jemand eine Idee dazu?

Host: openSuSE LEAP 15.0 / Guest OpenSuSE LEAP 15.0 (gleicher Versionsstand)

Kernel Update: openSuSE-2019-2503

VirtualBox Versionsstand Host.

Informationen zu Paket virtualbox:

Repository : openSUSE-Leap-15.0-Update
Name : virtualbox
Version : 6.0.12-lp150.4.39.1
Arch : x86_64
Anbieter : openSUSE
Installierte Größe : 38,1 MiB
Installiert : Ja
Status : aktuell
Quellpaket : virtualbox-6.0.12-lp150.4.39.1.src
Zusammenfassung : VirtualBox is an Emulator
Beschreibung :

Informationen zu Paket virtualbox-guest-desktop-icons:

Repository : openSUSE-Leap-15.0-Update
Name : virtualbox-guest-desktop-icons
Version : 6.0.12-lp150.4.39.1
Arch : noarch
Anbieter : openSUSE
Installierte Größe : 156,8 KiB
Installiert : Ja
Status : aktuell
Quellpaket : virtualbox-6.0.12-lp150.4.39.1.src
Zusammenfassung : Icons for guest desktop files
Beschreibung :
This package contains icons for guest desktop files that were created on the desktop.

Informationen zu Paket virtualbox-host-kmp-default:

Repository : openSUSE-Leap-15.0-Update
Name : virtualbox-host-kmp-default
Version : 6.0.10_k4.12.14_lp150.12.67-lp150.4.36.1
Arch : x86_64
Anbieter : openSUSE
Installierte Größe : 830,6 KiB
Installiert : Ja
Status : aktuell
Quellpaket : virtualbox-6.0.10-lp150.4.36.1.src
Zusammenfassung : Host kernel module for VirtualBox
Beschreibung :

Informationen zu Paket virtualbox-host-source:

Repository : openSUSE-Leap-15.0-Update
Name : virtualbox-host-source
Version : 6.0.12-lp150.4.39.1
Arch : noarch
Anbieter : openSUSE
Installierte Größe : 5,1 MiB
Installiert : Ja
Status : aktuell
Quellpaket : virtualbox-6.0.12-lp150.4.39.1.src
Zusammenfassung : Source files for virtualbox host kernel modules
Beschreibung :
Source files for virtualbox host kernel modules
These can be built for custom kernels using
sudo /sbin/vboxconfig

Informationen zu Paket virtualbox-qt:

Repository : openSUSE-Leap-15.0-Update
Name : virtualbox-qt
Version : 6.0.12-lp150.4.39.1
Arch : x86_64
Anbieter : openSUSE
Installierte Größe : 57,8 MiB
Installiert : Ja (automatisch)
Status : aktuell
Quellpaket : virtualbox-6.0.12-lp150.4.39.1.src
Zusammenfassung : Qt GUI part for virtualbox
Beschreibung :
This package contains the code for the GUI used to control VMs.

Informationen zu Paket virtualbox-kmp-default:

Repository : openSUSE-Leap-15.0-Update
Name : virtualbox-kmp-default
Version : 6.0.12_k4.12.14_lp150.12.70-lp150.4.39.1
Arch : x86_64
Anbieter : openSUSE
Installierte Größe : 1,6 MiB
Installiert : Ja (automatisch)
Status : aktuell
Quellpaket : virtualbox-6.0.12-lp150.4.39.1.src
Zusammenfassung : Kernel modules for VirtualBox
Beschreibung :

Sauerland · November 21, 2019, 6:26pm

This is the English Sub-Forum, so please post:

zypper lr -d

From Host:

zypper se -si kernel virtualbox

From Guest:

zypper se -si kernel virtualbox

And please use Code-Tags.

tsu2 · November 22, 2019, 3:40am

openSUSE 15.0 is expected to reach EOL any day or week now,
You should strongly consider upgrading all your 15.0 to 15.1 ASAP.
If a bug is found, I wouldn’t expect it to be fixed.

If you actually are experiencing a deadlock error,
You’ll need to inspect or post your bootlog to determine what actually happened just prior to the deadlock. Ordinarily, systemd is fairly good at avoiding deadlocks, so unless others report the same type of error, the problem is likely unique to your system.
An attempt to troubleshoot a boot problem might involve choosing an older kernel in your grub menu, and if that doesn’t work then if your root partition is BTRFS, booting an older snapshot before your upgrade. When you can boot, then you can then inspect the system log for prior (failed) boot attempts with a command like

journalctl -b -1

TSU

fwkuser · November 22, 2019, 10:42am

Hallo,

vielen Dank für euere Antwort.
Das Problem hatte ich schonmal nach einem Kernel update - vieleicht schon 1 Jahr her. Das wurde nach 3 Werktagen mit einem Kernel Patch behoben.
Leider weiss ich den Zeitpunkt noch das Ticket (nicht von mir) und das Datum nicht mehr.

nachfolgend schon mal die zypper Ausgaben:

HOST
zypper lr -d

| Alias | Name | Aktiviert | GPG-Überprüfung | Aktualisierung | Priorität | Typ | URI | Dienst

—±------------------------------------±----------------------------------------±----------±----------------±---------------±----------±-------±-------------------------------------------------------------------------------±------
1 | http-download.opensuse.org-3ba7ca83 | KDE:Qt5 | Ja | (r ) Ja | Ja | 99 | rpm-md | http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_Leap_15.0/ |
2 | http-download.opensuse.org-6d4f948c | games:tools | Nein | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/games:/tools/openSUSE_Leap_15.0/ |
3 | http-download.opensuse.org-c7be3f14 | KDE:Frameworks5 | Ja | (r ) Ja | Ja | 99 | rpm-md | http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Leap_15.0/ |
4 | http-download.opensuse.org-fd245be8 | games | Nein | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/games/openSUSE_Leap_15.0/ |
5 | openSUSE-Leap-15.0-1 | openSUSE-Leap-15.0-1 | Nein | ---- | ---- | 99 | rpm-md | hd:/?device=/dev/disk/by-id/usb-058f_6387_14112263005339-0:0-part2 |
6 | openSUSE_Leap_15.0 | packman | Ja | (r ) Ja | Ja | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.0/ |
7 | repo-debug | openSUSE-Leap-15.0-Debug | Nein | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/15.0/repo/oss/ |
8 | repo-debug-non-oss | openSUSE-Leap-15.0-Debug-Non-Oss | Nein | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/15.0/repo/non-oss/ |
9 | repo-debug-update | openSUSE-Leap-15.0-Update-Debug | Nein | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/15.0/oss/ |
10 | repo-debug-update-non-oss | openSUSE-Leap-15.0-Update-Debug-Non-Oss | Nein | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/15.0/non-oss/ |
11 | repo-non-oss | openSUSE-Leap-15.0-Non-Oss | Ja | (r ) Ja | Ja | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.0/repo/non-oss/ |
12 | repo-oss | openSUSE-Leap-15.0-Oss | Ja | (r ) Ja | Ja | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.0/repo/oss/ |
13 | repo-source | openSUSE-Leap-15.0-Source | Nein | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/15.0/repo/oss/ |
14 | repo-source-non-oss | openSUSE-Leap-15.0-Source-Non-Oss | Nein | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/15.0/repo/non-oss/ |
15 | repo-update | openSUSE-Leap-15.0-Update | Ja | (r ) Ja | Ja | 99 | rpm-md | http://download.opensuse.org/update/leap/15.0/oss/ |
16 | repo-update-non-oss | openSUSE-Leap-15.0-Update-Non-Oss | Ja | (r ) Ja | Ja | 99 | rpm-md | http://download.opensuse.org/update/leap/15.0/non-oss/ |
17 | teamviewer | TeamViewer - x86_64 | Ja | (r ) Ja | Nein | 99 | rpm-md | http://linux.teamviewer.com/yum/stable/main/binary-x86_64/ |
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
HOST
zypper se -si kernel virtualbox

Repository-Daten werden geladen…
Installierte Pakete werden gelesen…

Repository-Daten werden geladen…
Installierte Pakete werden gelesen…

dcurtisfra · November 22, 2019, 11:17am

@fwkuser:

AFAICS, the »last, final, update« Leap 15.0 VirtualBox versions all look OK but, please be aware that, the Leap 15.0 Kernel version may well have some issues with the 6.0.12 VirtualBox versions.

Leap 15.0 VirtualBox versions:

virtualbox: 6.0.12-lp150.4.39.1
virtualbox-kmp-default: 6.0.12_k4.12.14_lp150.12.70-lp150.4.39.1

Leap 15.1 VirtualBox versions:

virtualbox: 6.0.12-lp151.2.9.1
virtualbox-kmp-default: 6.0.12_k4.12.14_lp151.28.13-lp151.2.9.1

Having mentioned that, the last Leap 15.0 VirtualBox version should have passed the OpenQA at build time …
[HR][/HR]Assuming that, you’re committed to using Leap 15.0 for whatever reason, you may have to consider, rolling the VirtualBox version back to the previous Leap 15.0 one …
[HR][/HR]Viele Grüße aus Franken!

fwkuser · November 22, 2019, 11:20am

journalctl -b -1
Specifying boot ID or boot offset has no effect, no persistent journal was found.

I don’t know how I can get boot messages if the new Kernel 4.12.14-lp150.12.82.1 not running. By the Way - deadlock
If this Error not will be fixed, I must use the older Kernel 4.12.14-lp150.12.79.1 and later upgrade to LEAP 15.1.

fwkuser · November 22, 2019, 11:32am

dcurtisfra:

@fwkuser:

AFAICS, the »last, final, update« Leap 15.0 VirtualBox versions all look OK but, please be aware that, the Leap 15.0 Kernel version may well have some issues with the 6.0.12 VirtualBox versions.

Leap 15.0 VirtualBox versions:

virtualbox: 6.0.12-lp150.4.39.1

virtualbox-kmp-default: 6.0.12_k4.12.14_lp150.12.70-lp150.4.39.1

Leap 15.1 VirtualBox versions:

virtualbox: 6.0.12-lp151.2.9.1

virtualbox-kmp-default: 6.0.12_k4.12.14_lp151.28.13-lp151.2.9.1

Having mentioned that, the last Leap 15.0 VirtualBox version should have passed the OpenQA at build time …
[HR][/HR]Assuming that, you’re committed to using Leap 15.0 for whatever reason, you may have to consider, rolling the VirtualBox version back to the previous Leap 15.0 one …
[HR][/HR]Viele Grüße aus Franken!

Thank you for your Commends.

Viele Grüße aus NRW

tsu2 · November 22, 2019, 2:19pm

You should post any log or display output in

 tags which is the hash button in the web post editor tool.

Another way is to hit ESC on you keyboard during boot so that boot events are displayed and not hidden by the splashscreen, and then you can take a picture of the screen whenever and as often as you want (but definitely when the boot freezes).

Are you saying that the journalctl command given doesn't display anything at all?
It should display the bootlog of your immediately prior boot, and you you increment the number to display older bootlogs.

TSU

dcurtisfra · November 22, 2019, 6:59pm

Please try, with the user “root”:


journalctl --disk-usage
journalctl --this-boot
journalctl --dmesg
journalctl --list-boots

If the size of the Journal is excessive then, you’ll have to perform some house-keeping – assuming that, the Journal entries aren’t needed for any operational reason …

journalctl --vacuum-time=6months

dcurtisfra · November 25, 2019, 10:23am

@fwkuser:

I suspect that, we all forgot about the VirtualBox log files:

In the “Oracle VM VirtualBox Manager” – “Machine” – “Show Log” – filter for “warning” and “error”.

This Oracle VirtualBox blog entry may also be useful: <https://blogs.oracle.com/scoter/virtualbox-log-files-v2>.
There’s also some information in the manual: <Oracle® VM VirtualBox®.

The log file is called VBox.log and resides in the VM log file folder. Typically this will be a directory as follows:

$HOME/VirtualBox VMs/{machinename}/Logs

When starting a VM, the configuration file of the last run will be renamed to .1, up to .3. Sometimes when there is a problem, it is useful to have a look at the logs.

The Oracle VirtualBox manual is here: <https://www.virtualbox.org/manual/UserManual.html>.

Sauerland · November 25, 2019, 4:38pm

You should update your virtualbox-host-kmp:

i+ | virtualbox | Paket | 6.0.12-lp150.4.39.1 | x86_64 | openSUSE-Leap-15.0-Update
i+ | virtualbox-guest-desktop-icons | Paket | 6.0.12-lp150.4.39.1 | noarch | openSUSE-Leap-15.0-Update
i+ | virtualbox-host-kmp-default | Paket | 6.0.10_k4.12.14_lp150.12.67-lp150.4.36.1 | x86_64 | openSUSE-Leap-15.0-Update