Comment 2 for bug 650646

Everything was current and most up-to-date at time of install.
No Not an update, a fresh install - of everything including Ubuntu.
Not the first time using VirtualBox, and I dont believe the issue is
fixed. I could not find any info that worked and did not believe that
the format it was created had become obsolete.

tried the Vbox with Ubuntu then tried a download direct from Vbox.

I've been using Virtualbox for years but started using vmware because I
could not import the virtual machine created on Virtualbox. (windows XP
pro client and I'm using 64bit Ubuntu, but I believe I tried 32bit too)
I like vmware but for the sake of freedom I'd rather use VirtualBox.

I did a fresh install every few weeks and found that the VM that had
been built since would not import either (I had exported them, except
the 1st VM which was just copied)

No I have not tried this in the last 2 months as I got tired of
re-installing windows (I hate windows, but have to use it for some
client development).

On 11-01-27 10:41 PM, Flames_in_Paradise wrote:
> What Version of VirtualBox the VM was created in? What Version of
> VirtualBox are you trying to run the VM in?
>
> Was this a major update? Did you refer to Information given in the
> UserManual?
>
> -- You received this bug notification because you are a direct
> subscriber of the bug. https://bugs.launchpad.net/bugs/650646 Title:
> After first time install import fails to run Status in
> “virtualbox-ose” package in Ubuntu: New Bug description: First time
> install of VirtualBox ose or direct from virtualbox.org can import old
> hard drive but it wont run - does not register in xml? its a fresh
> ubuntu 10.04 (64bit) desktop install. then installed virtualbox ose
> tried to import a vm (windows xp) that was exported from ubuntu 9.xx
> the ovf and vmdk were an 'export' in april 2009. the 'import' appeared
> to work but when trying to run the vm got the error saying something
> about dkms - but it was installed the I got the error 'not in the
> media regitry' then I deleted that - created a new vm loaded the os it
> ran fine I deleted that Re-tried the original import - now that works
> fine too. My guess is that the registry file is not there after
> initial install and the import does not create it - could be wrong but
> whatever the 'New' does, import leaves out. PS the ubuntu non-ose from
> virtualbox.org does the same thing To unsubscribe from this bug, go
> to:
> https://bugs.launchpad.net/ubuntu/+source/virtualbox-ose/+bug/650646/+subscribe
>