[SOLVED] VM from Ubuntu hosts don't run under Mac OS x

[konze]

Hello,

I have the following problem, I've created a VM under Ubuntu (host) with Ubuntu Server (guest). Yesterday I tried to move this VM to my MacBook (host) (1. Method: I copied the *.vdi, 2. Method: I copied the whole VM folder, 3. Method: I used 'export appliance'). When I want to start this Ubuntu Server (Guest) on my MacBook everything seems fine, but the boot process looks completely different (graphic fallback mode...), The biggest problem is that the Ubuntu Server (guest) cant retrieve an IP (I in my opinion the VM doesn't find a networkcard).
I also installed a new VM on my MacBook (host) with Ubuntu Server (guest) and this one runs without any errors.

I hope you can help my

Best regards

konze

[stefan.becker]

VBOX version and guest additions must be the same version.

[konze]

VBOX version and guest additions must be the same version.

I've created the VM under Ubuntu (host) with 4.1.3 but I've updated VirtualBox to 4.2.4 this morning. There are no guest additions on my VM. What is the right way to move/copy VMs form one host to another one?

[mpack]

The only officially supported way to move VMs between hosts is via the appliance route, but I wouldn't recommend it.

Personally, I would just copy the VM folder, and correct the resource names in the .vbox xml manually, before adding the VM.

If that's too hard, build a new VM around the old VDI. Of course that won't work if you use snapshots, but no sane person does, hence that won't be a problem.

[konze]

just copy the VM folder, and correct the resource names in the .vbox xml manually, before adding the VM.

Which resources?

build a new VM around the old VDI.

This doesn't work, when Ubuntu Server boots (guest) it can't retrieve an IP.

[Perryg]

just copy the VM folder, and correct the resource names in the .vbox xml manually, before adding the VM.

Which resources?

build a new VM around the old VDI.

This doesn't work, when Ubuntu Server boots (guest) it can't retrieve an IP.

This usually happens when you change the MAC address in Linux.
You need to edit the /etc/udev/rules.d/70-persistent-net.rules or you can delete the rules and Linux will configure it on the next boot

[konze]

You need to edit the /etc/udev/rules.d/70-persistent-net.rules or you can delete the rules and Linux will configure it on the next boot

Thanks to all, now it runs perfectly.

[SOLVED]