Unable to import linux openSuse 12.1 VMs(linux doesnt work)

[nilsmoody]

Situation:
I've imported a linux machine to my virtual box (which runs perfectly on a other computer). Importing does work, machines are in the list and the vmdk-files + vbox-files were on there right places.

In the export-files which I've used are 3 different VMs:

- linux open Suse 12.1 (meant to be a server later)
- linux open Suse 12.1 (meant to be a client later)
- Windows 2000 (meant to be a samba client later)

Now to the problem: When I start my linux vm's after I've selected the normal bootoption (not the failsafe) a error appears.

As image:
imageshack.us/a/img140/3342/fehlermeldungx.jpg
(HINT: I couldn't post the link or the image because of the rule that I have to be a member of one day and I have to create atleast one post. So instead of (DOT) there has to be a normal dot without brackets.)


In words:

Code: Select all

doing fast boot
FATAL: Module ata_piix not found.
FATAL: Error running install command for ata_piix
Creating device nodes with udev
udevd[139]: failed to execute ' /etc/sysconfig/network/scripts/iful-sysctl' ' /etc/sysconfig/network/scripts/iful-sysctl lo -o hotplug': No such file or directory

resume device not found (ignoring)
Waiting for device /dev/disk/by-id/ata-VBOX_HARDDISK_VB1fa8c6b3-a1e2ebf6-part 1 to appear:
...........Could not find /dev/disk/by-id/ata-VBOX_HARDDISK_VB1fa8c6b3-a1e2ebf6-part1.
Want me to fall back to /dev/disk/by-id/ata-VBOX_HARDDISK_VB1fa8c6b3-a1e2ebf6-part1? (Y/n)

It doesn't matter if I press Y or N... Nothing happens. I can't boot my linux machines. Whats the matter? How to solve this problem? Which file is missing? (the linux machines had other paths on the other pc before) By the way, I'm a beginner and I could need additional declarations. Additionally my first language is not English either

Many thanks in advance,
Moody

[nilsmoody]

-

[Perryg]

The first error is due to it looking for a network adapter that has changed. Not unusual since the adapter probably has changed. You can fix that after the boot. The second error usually is because the Guest additions or some other CD was left in the virtual drive when exporting. If that is the case export again with the virtual drive clean. If the reason is because the UUID has changed you need to reply yes and wait it out. Depending on your system this could take a long time to first boot. Up to an hour.

[nilsmoody]

Thanks for the reply!

So the first error (network adapter) isn't the reason why I can't boot but the second error with a disk? I had no CD or any other disk in the (virtual) drive when exporting... Whats the matter now?

Perryg, holy crap average 13.70 posts per day!

[Perryg]

It appears you have removed some information from your posts so I can not go back and read to refresh my memory on the issue, so now it is impossible for me to continue that train of thought.

What version of VirtualBox were the guests created with? If it was version => 4.0 you can simply copy the entire guest/s folders to the new location and simply add them with the add function located in the Machine tab at the top of the VMM. If they have already been created in the new location you would need to remove/delete them first.

[nilsmoody]

It appears you have removed some information from your posts so I can not go back and read to refresh my memory on the issue, so now it is impossible for me to continue that train of thought.

I have just removed a message which just was posted to bump the thread. No real additional informations has been removed.

I'm using version 4.1.20 r80170. So this isn't possible then?

[Perryg]

Still this looks like the guest OS is not finding what it expects to see. More than likely it is using UUID instead of names to distinguish the HDD name in Grub. I would still try to simple copy the entire folder of each guest to the new location and use the VirtualBox add feature.