FS#35162 - [systemd] Upgrade of Systemd to 203-2 Causes Kernel Panic in 3.8.11-1-ARCH when running Virtualbox

Attached to Project: Community Packages
Opened by Melvin Lim (nivlenn) - Thursday, 09 May 2013, 01:48 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 09 May 2013, 11:34 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After systemd was upgraded to version 203-2 and rebooted, everything was fine until the execution of virtualbox which result in freezing up the OS. A force reboot causes the following error to show:

run-init: /sbin/init: Exec format error
[ ] Kernel panic - not syncing: Attempted to kill init!

Additional info:
* package version(s)

systemd-203-2
systemd-sysvcompat-203-2
virtualbox-4.2.12-2


Steps to reproduce:

- Install the packages as mentioned above
- Created a VM and ran with the command VBoxSDL --startvm XXX
- System hangs
This task depends upon

Closed by  Dave Reisner (falconindy)
Thursday, 09 May 2013, 11:34 GMT
Reason for closing:  Upstream
Additional comments about closing:  Standard vbox problems. Not a systemd bug.
Comment by Dave Reisner (falconindy) - Thursday, 09 May 2013, 11:32 GMT
Forcing a reboot will not universally cause init to be a zero byte file. You happened to upgrade systemd and were unlucky with whatever FS you use not sync'ing the data.

Not sure how this is a systemd bug. Vbox modules are known to be garbage.

Loading...