Switching type and bitness is not processed correctly

[Daniel U. Thibault]

I cloned a 32-bit Red Hat VM and then switched the clone to Ubuntu 64-bit. To my great surprise, the VM would not boot (on an empty disk with an installation DVD attached) because it detected an i686.

I fixed this by switching it to Ubuntu 32-bit, closing the Settings dialog, then switching it again to Ubuntu 64-bit.

It seems when you switch the type and bitness at once, the bitness change is missed.

[Frank Mehnert]

What bitness has your host, 32-bit or 64-bit?

[Daniel U. Thibault]

Replying to frank:

What bitness has your host, 32-bit or 64-bit?

64-bit. Shouldn't this be irrelevant?

[Frank Mehnert]

I asked to be 100% sure when trying to reproduce your problem. I did the following:

1. Created a 32-bit VM (Linux / Red Hat (32-bit)), default settings.
2. VBoxManage showvminfo VM_NAME | grep "Long Mode" returned off.
3. Switched the OS type of this VM to Red Hat (64-bit)
4. VBoxManage showvminfo VM_NAME | grep "Long Mode" returned on.

I even did the same experiement with cloning a VM with the 32-bit OS type set. After I set the OS type to 64-bit, Long Mode (which is required to start a 64-bit guest) is enabled.

Therefore I would like to know an exact reproduction scenario for your problem.

[Daniel U. Thibault]

Well, this is bizarre. Even though I did reproduce the problem before posting the bug report, now I can't seem to reproduce it anymore.

[Frank Mehnert]

Please reopen when you can provide a reproduction scenario.