"CPU doesn't support long mode" error message

[Adam Vande More]

On Wed, Oct 12, 2011 at 7:39 PM, Daevid Vincent <daevid at daevid.com> wrote:

> Sorry, of course I agree. I hit “reply” thinking that the list was setup
> like every other normal list I’m on, and would reply back to the list, but
> apparently it’s not, and you have to hit “reply all” instead. **sigh******
>
> ** **
>
> What I’ve done just now is re-create a “FreeBSD_64” VM and pointed it at my
> existing .vdi and it does load (although networking is not working at the
> moment, but it’s at least encouraging!)****
>
> ** **
>
> Couldn’t I have just change the .vbox file to say…****
>
> <Machine uuid="{e23be440-6afa-48ad-8643-538a2fc1ffb6}" name="VZ_Dev"
> OSType="FreeBSD_64"  ?? Or is there more to it than that?****
>
>
Yes, you've gotten the cause.  I don't know if Vbox keeps some mapping other
than the .vbox file, but the general way of doing it is

"VBoxManage modifyvm <vmname> --ostype <ostype>"

You can list os types with:

"VBoxManage list ostypes"

And find almost everything you'll need to know about it here:

http://www.virtualbox.org/manual/ch08.html

-- 
Adam Vande More