Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Long story short, I have a Ubuntu 12.04 64-Bit Server setup as a virtual machine with VirtualBox (4.1.18). I migrated the guest machine from an AMD chipset (a gaming machine) to an Intel Xeon (server hardware with dual processor support) thinking that there wouldn't be any issues. Once I got the guest machine setup on the server, I started the guest machine only to find that it hangs at "Loading Initial Ramdisk".

I mounted the Ubuntu 12.04 64-Bit setup ISO to see if I could get in to see any logs, but get "Kernel requires x86-64 CPU, but only detects i686 CPU" when trying to boot off the ISO. Keep in mind that host OS on both source and destination machines are also Ubuntu 12.04 Server 64-Bit. This lead me to look into how the guest OS sees the CPU information within the virtual machine. I found that the CPU information looks exactly the same on the host as it does on the guest on the source machine.

Source CPU Info:

Processor - AMD Phenom™ II X4
Model - 925
Operating Mode 32 Bit - Yes
Operating Mode 64 Bit - Yes
Revision - C2
Base Speed (MHz) - 2800
Boost Speed (MHz)
Voltages - 0.850-1.425V 
Wattage - 95 W
AMD Virtualization Technology - Yes
L1 Cache Size (KB) - 128
L1 Cache Count - 4
L2 Cache Size (KB) - 512
L2 Cache Count - 4
L3 Cache Size (KB) - 6144
CMOS - 45nm SOI
Socket - AM3
AMD Business Class - No
Black Edition - No

Destination CPU Info:

3 Ghz Xeon - SL7ZF
Number of Cores - 1
Clock Speed - 3 GHz
L2 Cache - 2 MB
FSB Speed - 800 MHz
FSB Parity - Yes 
Instruction Set - 64-bit
Embedded Options Available - No
Lithography - 90 nm
Max TDP - 110 W
VID Voltage Range - 1.2875V-1.3875V
Physical Address Extensions - 32-bit
ECC Memory Supported - No
Processing Die Size - 135 mm2
Number of Processing Die Transistors - 169 million
Sockets Supported - PPGA604
Intel® Hyper-Threading Technology - No
Intel® Virtualization Technology (VT-x) - No
Intel® Trusted Execution Technology - No
Intel® 64 - Yes 
Idle States - Yes 

I found a similar question, but wasn't sure if this is applies to my situation. The destination cpu show to support 64-Bit instructions. On the other hand, I've also read that Intel's 64-Bit is not true 64-Bit.

Am I stuck rebuilding my guest VM from scratch?

share|improve this question
I think there should be no problem in running this VM on the new processor. Could you please boot again the guest without the "quiet" kernel option in order to have more details on what the problem is? (I might be wrong, but I assume that a linux kernel is loaded, while the problem may be earlier.) – eppesuig Apr 15 '13 at 15:12
@eppesuig I have to admit, I've been trying to figure out GRUB on the fly but I am having trouble. I think it might be worth mentioning that the volume is encrypted through LVM with LUKS. With that said, I believe initrd is being used. I'm still learning. – hydroparadise Apr 19 '13 at 14:50

Your problem may not be with the new processor but your vm's settings. The first machine with the amd processor has visualization support built into the processor and the second does not. There is an option in the settings for the virtual machine under system > Acceleration > ... for hardware acceleration which the Intel machine does not have.

enter image description here

"Intel® Virtualization Technology (VT-x) - No"
share|improve this answer
Unfortunately, this did not help :( – hydroparadise Apr 19 '13 at 14:46
maybe un-checking the option "PAE/NX" under the processor tab could help. – Joe May 1 '13 at 5:30

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.