AMD-V

[fafster]

I have a HP dx2250 PC with an AMD X2 5000+ processor. I'm certain that this comes with AMD hardware virtualisation, but I can't find any way to turn it on in the BIOS. It's not on by default because neither Virtual PC nor Xen can detect it, though I have used a little utility to confirm that the CPU does have the capabilities.

 

The machine uses a MS7297 ROM, so I'm thinking if this BIOS doesn't support the option I might possibly be able to use another one.

 

Any ideas?

 

Cheers.

[PeterW]

What stepping is the CPU? Not all Athlon 64 x2's have Pacifica tech in them, try running cpu-z to get the stepping. If you can confirm the CPU has it then its worth seeing if there are any BIOS updates to enable it. Its an MSI mainboard by the sounds of it but you will have to get any updates via HP.

[Geoff]

I also have a HP dx2250 AMD PC as my desktop machine. I can tell you definitively that mine does have the pacifica hardware virtualisation. You can tell by looking at /proc/cpuinfo:

 

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 107
model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
stepping        : 1
cpu MHz         : 1000.000
cache size      : 512 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm extapic cr8legacy 3dnowprefetch ts fid vid ttp tm stc 100mhzsteps
bogomips        : 1996.63
clflush size    : 64

processor       : 1
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 107
model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
stepping        : 1
cpu MHz         : 1000.000
cache size      : 512 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm extapic cr8legacy 3dnowprefetch ts fid vid ttp tm stc 100mhzsteps
bogomips        : 1996.63
clflush size    : 64

 

The CPU flag for pacifica is "svm" (Intel vanderpool equivelent is "vmx").

[fafster]

It has a stepping of 1, if that's any use?

[fafster]

Where would I find the CPU flag using XP? The CPU codename is Brisbane.

[PeterW]

If its Brisbane your CPU is capable.

[fafster]

Bloody HP and their stupid BIOS.

 

I'll have to see if MSI have BIOS downloads available too.

[Geoff]

Where would I find the CPU flag using XP? The CPU codename is Brisbane.

 

Download the AMD CPUID software.

 

http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_9706,00.html

[PeterW]

Bloody HP and their stupid BIOS.

 

I'll have to see if MSI have BIOS downloads available too.

 

Don't bother its a unique board/bios to HP.

[fafster]

Don't bother its a unique board/bios to HP.

 

Any reason in particular? I found this:

 

http://www.pctechbytes.net/forums/showthread.php?p=64655

[john]

The boards may be made by MSI for HP and look similar to a MSI model but there not and custom made and hacked for HP so don't try an MSI BIOS as it may break it and render it useless

[PeterW]

As already mentioned even if you do find any other MS-7297 bios files it is strongly advised not to attempt to flash to them as MS-7297 is a general moel number and will have mnay different ERP revisions some of them could be drastically different and even use different size bios roms.

 

The best think to do would be to work out what the differnece is between your system and Geoff's as his seems to be enabled and working.

[Geoff]

The best think to do would be to work out what the differnece is between your system and Geoff's as his seems to be enabled and working.

 

The obvious answer is that I'm using Linux. Linux doesn't use the bios once it's booted up.

[fafster]

Would installing XenServer onto the machine solve the problem then? If it's available but not enabled, would Xen be able to switch it on?

[fafster]

Never mind, it seems that HP lock the registers that allow you to enable AMD-V after boot. I guess they're basically stopping anyone using a beefy workstation to run VMs and forcing them to pay the extra for a 'proper' server.

 

I think I'll put together my own test machine....

[Geoff]

Unless your running Linux ;-)