[opensuse-factory] Factory currently does not boot in VirtualBox
Hi, 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? Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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
Hi, tried once again to run Factory in a VirtualBox VM after applying the latest Factory packages. Still does not boot for me. Can anyone confirm that Factory currently boots correctly on VirtualBox 4.3 (or not)? It doesn't for me and I have no idea if it's because of a broken ramdisk or kernel. I have no spare bare metal just to run Factory. Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/31/2014 07:05 AM, Wolfgang Rosenauer wrote:
Hi,
tried once again to run Factory in a VirtualBox VM after applying the latest Factory packages. Still does not boot for me.
Can anyone confirm that Factory currently boots correctly on VirtualBox 4.3 (or not)? It doesn't for me and I have no idea if it's because of a broken ramdisk or kernel. I have no spare bare metal just to run Factory.
I just tried to boot Build 0808 KDE Live iso from Factory in a VB VM. The iso image was connected to a virtual drive as usual; however the boot code was unable to see it. The problem seems to be in the Factory image as that same VM could boot other iso images. I am using VirtualBox 4.3.6. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Bernhard Voelker -
Larry Finger -
Wolfgang Rosenauer