virtualbox.org

Hi All,
I have installed virtual box on my Windows XP host and created a virtual machine using my existing VMWare vmdk files which are having RHEL 5 as guest operating system. While booting the OS on Virtual Box I am getting kernal panic with below mentioned error:

Volume Group "VolGroup00" not found
Unable to access resume device (/dev/VolGroup00/LogVol01)
mount: Could not found filesystem '/dev/root/'
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory
Kernel panic- not syncing : Attempted to kill init!

Any help or clue ?

Best Regards
Sunil Khatri

Here are a few tips on what to do before you try to move the vms.

Remove any vmware tools.
Shut down the vm (not paused or hibernated).

Now try to create a new vm linked to the existing virtual hard disk file. If you plan to to stay on VirtualBox, use clonevdi tool to convert the vmdk to a vdi file.

Hi all,
I've just updated my VBox to 3.2.10 on my Kubuntu 10.04 (kernel 2.6.32-25-generic-pae #44-Ubuntu SMP) and while trying to run a guest RHEL 5.2 x86, I've exactly the same error message above.
The kernel version of the guest is 2.6.18-92.el5.
I didn't migrate it from VMWare and it was working before the VBox upgrade.
Attached there's the VBox.log generated.

Let me know if you need other info.

Cheers,
Marco

I also experience the same problem while trying to RHEL guest OS. The only solution I've found to work for me, is to create the virtual machine with a 3.1.x version of VirtualBox and then I was able to run the newly created machine with VirtualBox 3.2.10. By "create the virtual machine", I mean just the runtime entry which creates a new ~/.VirtualBox/Machines/machine_name.xml, you can use an existing virtual disk (VDI), so long as the machine XML is generated by a 3.1.x version of VirtualBox. A diff of a machine XML generated by 3.1.x with one created by 3.2.10 shows quite a few differences, though I'm not exactly sure which one is causing RHEL to barf...

@bogeek, I see nothing in the log to indicate a VBox error. I see the VM starting up, then 50 minutes later a controlled shutdown.

I'm getting exactly the same error message with VirtualBox 3.2.10 and a CentOS 5 VMWare image (host OS: Windows 7). I've attached the log file.

meanderix wrote:...the log file.

Code: Select all

00:00:01.576 [/Devices/ahci/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:01.576   Format   <string>  = "VMDK" (cb=5)
00:00:01.576   Path     <string>  = "D:\Virtual Machines\sectronic-ipf\sectronic-ipf.vmdk" (cb=53)

its very likely that it was configured on VMware to be attached to some virtual (probably BusLogic) SCSI adapter, thus won't work on AHCI/SATA

you may add a virtual SCSI adapter in the machines storage settings and then attach the vmdk there ...

fixedwheel wrote:

meanderix wrote:...the log file.

Code: Select all

00:00:01.576 [/Devices/ahci/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:01.576   Format   <string>  = "VMDK" (cb=5)
00:00:01.576   Path     <string>  = "D:\Virtual Machines\sectronic-ipf\sectronic-ipf.vmdk" (cb=53)

its very likely that it was configured on VMware to be attached to some virtual (probably BusLogic) SCSI adapter, thus won't work on AHCI/SATA

you may add a virtual SCSI adapter in the machines storage settings and then attach the vmdk there ...

Thanks a lot -- it's working after adding the SCSI adapter and now I don't need to install VMWare!

Mattias

Hello fixedwheel,

I used your suggestion to solve this error and want to thank you for this. I almost installed the vmplayer to see if the files do work there ... thanks

-Ankur Jain

1. Poweroff the virtualbox
2. Settings=>Storage:
3. RemoveController xxx.vdi under Controller:SATA
4. AddHardDisk xxx.vdi under Controller:IDE
5. Start virtualbox
that is ok!