Am 02.01.2014 22:12, schrieb Bernhard Voelker:
On 01/02/2014 02:20 PM, Wolfgang Rosenauer wrote:
I've updated a VM to Factory today and now it doesn't boot anymore in VirtualBox. The last thing I can see is "Loading initial ramdisk" and afterwards VirtualBox (4.3.6) switches into "Guru Meditation" and fails to boot further. Any ideas how to solve that?
I had this once, too. The reason was that I had a share on the host mounted via vboxfs via /etc/mtab, but the new VBox client modules first have to be re-compiled after a kernel update. The problem is that systemd has local-fs as a prerequisite for other targets and therefore hangs in an endless loop. I had to boot the VM from a CD image, mount the root file system, and remove the vboxfs share's entry from /etc/fstab.
hmm, not the issue here. But one problem seems to be that the initrd is not gzipped but only a cpio archive. I've gzipped it and tried again and the VBox issue is gone but now I get a kernel panic (not able to mount the root fs). My guess is that the initrd is just completely broken. A dracut issue? (I've noticed that Factory is using dracut now apparently.) Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org