Enable hardware virtualization on basic BIOSes


Recommended Posts

I recently got a new notebook - a Sony VGN-FZ280E ... it's a pretty decent machine sporting a T7250 800mhz C2D, 2GB RAM, 250GB HD, 15.4" widescreen and best of all a Blu-ray burner all for $1100 flat Canadian.

Anyways, I decided to run a virtual machine on this sytem since it's the most powerful one in the house right now (yeah I know I'm behind the times). I prefer MS's Virtual PC 2007 because it's free. After fiddling around with the options I come by the Hardware virtualization option but it's disabled and forces me to use software virtualization. Now I thought the CPU is capable of doing hardware virtualization and thought it was a glitch in virtual PC.

Now I remember building my girlfriend's quad-core system last summer and remembered a bios setting to enable/disable it. I checked the BIOS settings for my notebook and there's nothing listed in there. All I get are options for the date/time, power management and boot options. After doing much research I came across the VMWare forums and landed on this thread.

Seems like Sony and I'm sure a few other OEMs out there disables this option for consumer based products thinking that no one would use it. I ended up following instructions on that thread and enabled VT/Vanderpool/virtualizaion by changing the value of a single register in my bios. Simply put, all you'd do is boot to dos, dump register values in a text file, changed a register in the dump then updated the registers back in the bios.

If anyone is interested here's what I did for my system:

Download symcmos.exe from http://www.filewatcher.com/b/ftp/ftp.supermicro.com/utility.0.0.html

Please remember to do this in a DOS (boot to DOS).

TO DUMP CURRENT REGISTERS:

symcmos -v2 -lcmos.sav

TO MODIFY REGISTERS:

Open cmos.sav in text a editor and change the register of your model from 0 to 1

SONY MODEL	  BIOS VERSION	REGISTER
==========	  ============	========
SZ1XP						   reg 0399
GN-SZ370		R0096N0		 reg 0399
VGN-AR21S	   R200J6		  reg 0195
VGN-AR51SU	  R1050J8		 reg 027f
vgn-FE890	   R0200J3		 reg 0195
VGN-AR670	   R1050J8		 reg 027f
VGN-FZ21M					   reg 02CD
VGN-FZ180E	  R0050J7		 reg 02D3
VGN-FZ11ZR	  R0050J7		 reg 02D3
VGN-FZ280E	  R1120J7		 reg 02CD**

TO UPDATE REGISTERS:
symcmos -v2 -ucmos.sav

Completey power down the system after updating the registers then boot back up.
HOPEFULLY the system starts and it's enabled.

** I guessed this register based on the FZ12M model on that list because it was very similar to my system and took a chance at temporarily bricking the laptop (resetting the cmos can be done by removing the cmos battery). Needless to say, I'm now happy with the hardware virtualization on my system. I hope this helps other people in a similar situation that I was in.

Keep in mind that the tool that was used is for phoenix bioses and your mileage may vary with different models and manufacturers. Good luck!

Edited by warwagon
  • 6 months later...
  • 4 weeks later...

Hello there,

I don't know what you mean, You say:

change the register of your model from 0 to 1

What do i need to do? I don't understand.

I have a Vaio FZ21Z and I want to enable hardware virtualization. I found elswhere the settings for my model:

VGN-FZ21Z R1120J7 reg 02CD.

So do I change it to 12CD?

Thanks

  • 9 months later...
  • 5 weeks later...

i added my vaio laptop VGN-FE770G R0174J3 reg 0195

:D

SONY MODEL BIOS VERSION REGISTER

========== ============ ========

SZ1XP reg 0399

GN-SZ370 R0096N0 reg 0399

VGN-AR21S R200J6 reg 0195

VGN-AR51SU R1050J8 reg 027f

vgn-FE890 R0200J3 reg 0195

VGN-AR670 R1050J8 reg 027f

VGN-FZ21M reg 02CD

VGN-FZ180E R0050J7 reg 02D3

VGN-FZ11ZR R0050J7 reg 02D3

VGN-FZ280E R1120J7 reg 02CD**

VGN-FE770G R0174J3 reg 0195

  • 1 month later...
  • 3 weeks later...

it is very easy to enable Virtualization in Sony Vaio FE models really:

1)wou need a usb stick with a large capacity 3-4 Gb (small ones do not work unfortynatelly)

2) format it with hewllet packard usb disk storafe tool (select option create a dos startup disk-any dos version is good)

3) copy to usb stick symcmos.exe

4) reboot from the stick (change bios settings and REMOVE internal disk from the boot sequence by pressing X or else will never boot from the stick)

5)whe you will be on dos write: symcmos -v2 -lcmos.txt .this will create a cmos.text file with bios settings

6) restore boot sequence and start your windows. then edit line 0195 from 0 to 1 to the text file to usb stick

7) reboot from usb stick

8) when in dos write: symcmos -v2 -ucmos.txt .this updates register no 195 to 1 (virtyalization enabled)

9) when done SHUT DOWN you pc (NOT REBOOT must be shut down to restore bios settings)

10) check that VT is enabled with havtool.exe from microsoft. must be OK!

  • 4 months later...

I recently got a new notebook - a Sony VGN-FZ280E ... it's a pretty decent machine sporting a T7250 800mhz C2D, 2GB RAM, 250GB HD, 15.4" widescreen and best of all a Blu-ray burner all for $1100 flat Canadian.

Anyways, I decided to run a virtual machine on this sytem since it's the most powerful one in the house right now (yeah I know I'm behind the times). I prefer MS's Virtual PC 2007 because it's free. After fiddling around with the options I come by the Hardware virtualization option but it's disabled and forces me to use software virtualization. Now I thought the CPU is capable of doing hardware virtualization and thought it was a glitch in virtual PC.

Now I remember building my girlfriend's quad-core system last summer and remembered a bios setting to enable/disable it. I checked the BIOS settings for my notebook and there's nothing listed in there. All I get are options for the date/time, power management and boot options. After doing much research I came across the VMWare forums and landed on this thread.

Seems like Sony and I'm sure a few other OEMs out there disables this option for consumer based products thinking that no one would use it. I ended up following instructions on that thread and enabled VT/Vanderpool/virtualizaion by changing the value of a single register in my bios. Simply put, all you'd do is boot to dos, dump register values in a text file, changed a register in the dump then updated the registers back in the bios.

If anyone is interested here's what I did for my system:

Download symcmos.exe from http://www.filewatcher.com/b/ftp/ftp.supermicro.com/utility.0.0.html

Please remember to do this in a DOS (boot to DOS).

TO DUMP CURRENT REGISTERS:

symcmos -v2 -lcmos.sav

TO MODIFY REGISTERS:

Open cmos.sav in text a editor and change the register of your model from 0 to 1

SONY MODEL	  BIOS VERSION	REGISTER
==========	  ============	========
SZ1XP						   reg 0399
GN-SZ370		R0096N0		 reg 0399
VGN-AR21S	   R200J6		  reg 0195
VGN-AR51SU	  R1050J8		 reg 027f
vgn-FE890	   R0200J3		 reg 0195
VGN-AR670	   R1050J8		 reg 027f
VGN-FZ21M					   reg 02CD
VGN-FZ180E	  R0050J7		 reg 02D3
VGN-FZ11ZR	  R0050J7		 reg 02D3
VGN-FZ280E	  R1120J7		 reg 02CD**

TO UPDATE REGISTERS:
symcmos -v2 -ucmos.sav

Completey power down the system after updating the registers then boot back up.
HOPEFULLY the system starts and it's enabled.

** I guessed this register based on the FZ12M model on that list because it was very similar to my system and took a chance at temporarily bricking the laptop (resetting the cmos can be done by removing the cmos battery). Needless to say, I'm now happy with the hardware virtualization on my system. I hope this helps other people in a similar situation that I was in.

Keep in mind that the tool that was used is for phoenix bioses and your mileage may vary with different models and manufacturers. Good luck!

hey,,,....i don't get all those codes..

where do itype them> i really want to run mac os. plz help!

  • 2 weeks later...
  • 1 month later...

i added my vaio laptop VGN-FE770G R0174J3 reg 0195

:D

SONY MODEL BIOS VERSION REGISTER

========== ============ ========

SZ1XP reg 0399

GN-SZ370 R0096N0 reg 0399

VGN-AR21S R200J6 reg 0195

VGN-AR51SU R1050J8 reg 027f

vgn-FE890 R0200J3 reg 0195

VGN-AR670 R1050J8 reg 027f

VGN-FZ21M reg 02CD

VGN-FZ180E R0050J7 reg 02D3

VGN-FZ11ZR R0050J7 reg 02D3

VGN-FZ280E R1120J7 reg 02CD**

VGN-FE770G R0174J3 reg 0195

I also have the same laptop. the vgn-fe770g.

Does anyone know the register to enable AHCI?

Holy continuous thread resurrection, Batman!

Unfortunately you can't just set a register to turn on AHCI - it's a complete set of instructions and usually a 3rd party controller (such as Intel AHCI BIOS - independent of the main BIOS). You won't be able to turn it on that easily if it's non existent.

Holy continuous thread resurrection, Batman!

Unfortunately you can't just set a register to turn on AHCI - it's a complete set of instructions and usually a 3rd party controller (such as Intel AHCI BIOS - independent of the main BIOS). You won't be able to turn it on that easily if it's non existent.

Oh, I see.

Then I would like to know why at this place... ---> http://forum.notebookreview.com/sony/189228-how-enable-intel-vt-ahci-napa-santa-rosa-platform-phoenix-bios-vaio-laptop.html

They seem to have enabled it with only one register. Am I wrong?

I am guessing that those computers have the 3rd party controller you're talking about and my laptop doesn't?

I'm confused...

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • AltSendme 0.4.2 is out.
    • Simple answer is yes, you will still get the Windows updates and as long as browser is up to date, you will be good. Only thing secure boot does is protect you against boot level threats and make it harder to install other OS's. I've been looking into this pretty thoroughly lately myself as wifes computer has secure boot disabled plus my other, older computers that run Linux, don't have secure boot enabled. Have seen all kinds of questions about this on the Linux Mint and MX Linux forums. Just don't suddenly enable secure boot now.
    • How many other companies will follow Ford's lead? Or, have they already gotten lazy and become enslaved to AI--and now can't figure out how to get out of that mess.
    • Why would any self-respecting intelligent person follow any recommendation by Donald's GOP administration? With almost two years of fabrications, deceit, and blatantly illegal behavior, why believe them now? They had best be gone after the November 2026 election, so we'll wait and see.
    • AltSendme 0.4.2 by Razvan Serea AltSendme is a minimal, cross-platform application designed for fast, secure, and private peer-to-peer file transfers. It allows users to send files or entire directories directly between devices without relying on cloud servers, accounts, or any personal information. Everything is encrypted end-to-end using modern protocols like QUIC and TLS 1.3, ensuring both strong security and low-latency performance. Transfers are verified with BLAKE3 for data integrity, and interrupted downloads automatically resume, making the experience reliable even on unstable connections. You can transfer anything—images, videos, documents, and more. Integrity checks are performed on both ends, so your files are automatically verified for correctness during both sending and receiving. AltSendme works seamlessly across local networks or long-distance links, capable of saturating multi-gigabit connections for extremely fast delivery. With built-in NAT traversal and encrypted relay fallback, it connects devices almost anywhere. The app integrates with the Sendme CLI and will soon support mobile and web platforms. Fully free and open-source, AltSendme offers a lightweight, privacy-first alternative to traditional cloud-based services, removing size limits, upload costs, and unnecessary data exposure. AltSendme 0.4.1 changelog: Release Highlights Self-hosted relays: Run your own iroh relay so transfers don't rely on public infrastructure. Includes a full deployment template in deploy/relay/ with Docker Compose for a VPS and configuration examples for production use. Fly.io support: One-click deploy template for Fly.io, including a quick-start config (fly.dev.toml) for testing without a custom domain, plus production setup with Let's Encrypt and your own hostname. Relay settings UI: New Settings → Network panel to choose how AltSendme connects: automatic public relays, custom self-hosted URLs (with optional auth token), or disabled. Test connections, verify latency, and see live relay status in the footer. Disable relays: Turn off relay servers entirely when you only need same-network transfers (e.g. LAN). Direct connections only. No relay hop required when devices can reach each other. Android graduates from beta: Android is now part of the regular release cycle alongside desktop. APKs ship with each version (universal, arm64, and armv7). Other improvements Private relay access control via shared auth token Relay fallback notifications when a custom relay is unreachable Broadcast mode toggle in sharing settings Android release build fixes (split-per-ABI APKs, universal APK preservation) UI polish: mobile safe-area insets, dropzone layout, transfer progress animation Bug fixes for minification-related serialization issues and system tray icon loading What's Changed feat(relay): add relay status functionality and settings UI (a120cdf) feat(relay): implement custom relay server configuration and verification (51276c7) feat(relay): add configuration for private relay access and enhance observability features (48fbabf) feat(relay): enhance relay URL validation, display connection status (d4fffa0) feat(relay): add RelayChangeGuard component and enhance relay-related translations (16ba514) feat(broadcast): add toggle setting for broadcast mode in sharing UI (ca6d977) fix(relay): correct QUIC discovery port, pin image, templatize fly.dev (52a2ba5) fix: More broken serialization due to minification (67491a9) fix(android): preserve true universal APK across per-ABI builds (e9f256f) fix(ui): conditional safe-area insets padding on mobile (1182f0e) refactor(transfer): CircularRing component animation fix (944572b) chore(android): drop x86 and x86_64 release APKs, keep universal+arm64+armv7 (34ada0b) AltSendme 0.4.2 release highlight: Modern Debian & Ubuntu support. The .deb package now declares compatible dependency alternatives (libayatana-appindicator3-1, libgtk-3-0t64) alongside the older Ubuntu 22.04 names, so it installs cleanly on Debian and Ubuntu 24.04+. Fixed settings sidebar header being covered by the custom title bar on Linux. What's Changed #172 Fixed #168 Addressed feat(tauri): support for modern debian (80f548d) fix(setting-sidebar): linux-only custom title bar covering nav header (fb55c9d) Download: AltSendme 0.4.2 | ARM64 | ~9.0 MB (Open Source) Download: AltSendme for MacOS | Android Links: AltSendme Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      494
    2. 2
      +Edouard
      225
    3. 3
      PsYcHoKiLLa
      149
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!