- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As some of you may have noticed, I have been awarded last summer with a Black Belt title, and I got a very nice notebook as a reward. It is a Sony VAIO VGN-FW190E.
Today I wanted to use Microsoft Virtual PC on it, and I realized in awe that the hardware virtualization support is disabled.
I used Everest, CPU-Z, CrystalCPUID and my own CPU info tool to verify that the P8600 actually does support VT which of course being high-end mobile 45nm part it does.
Being geeky I disassembled Virtual PC executable to check if perhaps detection doesn't work correctly and I found no flaws.
Then I consulted document order #253669 revision 29 (Intel 64 and IA-32 Architectures Software Developer's Manual Volume 3B - System Programming Guide) and in chapter 19.7 on page 156 I found that VT is controlled by MSR 0x3A bits 0, 1, and 2. I checked the contents of the MSR using CrystalCPUID MSR Editor tool and the value is 0x00000000 00000001, meaning that the VT has been disabled and the register locked.
After rebooting into BIOS I found no option to Enable/Disable VT. It is hardcoded as disabled.
I have spent two hours in chat with Sony Support. I got the following responses:
1. http://www.kb.sony.com/selfservice/documentLink.do?externalId=C381809
That KB article basically says that Intel VT is "currently" (since October 2008) not supported on VAIO notebooks.
2. Igor, as the Virtualization Technology is not supported, it is not possible to use the Hardware Virtualization.
In my opinion, this is giving Intel Corporation a bad name. I have Intel's latest and greatest mobile platform with not only VT but VT2 support which I cannot use simply because someone at Sony has been an incompetent cheapskate when they were configuring the BIOS modules.
3. This issue needs extensive communication. So, I suggest that you contact our Hotline Support team at 1-888-476-6972.
Well it is obvious that I can't make long distance call from Serbia and spend an hour listening to cheap elevator music until someone answers the phone and then spend another hour attempting to explain the technical nitty-gritty as I am being repeatedly told that "it is not supported".
4. BIOS updates will be released only if there are any known issues with the Computer.
Well, if this isn't a known issue then why it exists in their knowledge base? D'oh! Needless to say, BIOS is dated February 27th, 2008 so it probably doesn't even have recent microcode updates as well.
5. I suggest that you bookmark our Sony support site 'Drivers and Softwares' page to check for the latest updates.
Yeah, right. The only problem is that nowhere does it say on Sony's website "we are working on an update".
6. Igor, it is clearly mentioned that Sony VAIO computers do not currently support Virtualization Technology (VT).
Yes in the KB article dated October 27th, 2008.
No on the Sony Style website where the notebook has been ordered back in August 2008. Time travel not yet invented.
7. In this case, I suggest that you contact our Customer Information and Service Center to place and request. Dissatisfied customers and policy issues are handled by our Customer Information and Service Center.
Ok, so I will send an email, some developer will get it and all will be fine right? Bzzzt... Wrong!
8. Igor, I am sorry to inform you that, Telephone support is the only way to contact our Customer Information and Service Center.
Phone... again... this time I would need to call 1-239-768-7669 but I can't because...
9. In this case, you will be charged.
Well if I have to make an international call, isn't it obvious that I will be charged? D'oh!
Now, what this long (and hopefully at least a bit funny) rant tries to convey is that OEMs (not just Sony, other notebook manufacturers too) are damaging Intel's corporate image in this way.
How can I develop on Intel platform for Intel Platform using VT when I can't even turn it on?
I really need someone from Intel to help me with this issue.
Some manager on Intel Virtualization team who will pick up the phone, call a Sony representative, verbally wound his behind, rub some salt in, and demand a BIOS update A.S.A.P to be released to the customers. Or just politely ask -- whichever way works better.
Please folks, there is no one else who can resolve this!
Best regards,
Igor Levicki
Intel Black Belt
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Igor Levicki
As some of you may have noticed, I have been awarded last summer with a Black Belt title, and I got a very nice notebook as a reward. It is a Sony VAIO VGN-FW190E.
Today I wanted to use Microsoft Virtual PC on it, and I realized in awe that the hardware virtualization support is disabled.
I used Everest, CPU-Z, CrystalCPUID and my own CPU info tool to verify that the P8600 actually does support VT which of course being high-end mobile 45nm part it does.
Being geeky I disassembled Virtual PC executable to check if perhaps detection doesn't work correctly and I found no flaws.
Then I consulted document order #253669 revision 29 (Intel 64 and IA-32 Architectures Software Developer's Manual Volume 3B - System Programming Guide) and in chapter 19.7 on page 156 I found that VT is controlled by MSR 0x3A bits 0, 1, and 2. I checked the contents of the MSR using CrystalCPUID MSR Editor tool and the value is 0x00000000 00000001, meaning that the VT has been disabled and the register locked.
After rebooting into BIOS I found no option to Enable/Disable VT. It is hardcoded as disabled.
I have spent two hours in chat with Sony Support. I got the following responses:
1. http://www.kb.sony.com/selfservice/documentLink.do?externalId=C381809
That KB article basically says that Intel VT is "currently" (since October 2008) not supported on VAIO notebooks.
2. Igor, as the Virtualization Technology is not supported, it is not possible to use the Hardware Virtualization.
In my opinion, this is giving Intel Corporation a bad name. I have Intel's latest and greatest mobile platform with not only VT but VT2 support which I cannot use simply because someone at Sony has been an incompetent cheapskate when they were configuring the BIOS modules.
3. This issue needs extensive communication. So, I suggest that you contact our Hotline Support team at 1-888-476-6972.
Well it is obvious that I can't make long distance call from Serbia and spend an hour listening to cheap elevator music until someone answers the phone and then spend another hour attempting to explain the technical nitty-gritty as I am being repeatedly told that "it is not supported".
4. BIOS updates will be released only if there are any known issues with the Computer.
Well, if this isn't a known issue then why it exists in their knowledge base? D'oh! Needless to say, BIOS is dated February 27th, 2008 so it probably doesn't even have recent microcode updates as well.
5. I suggest that you bookmark our Sony support site 'Drivers and Softwares' page to check for the latest updates.
Yeah, right. The only problem is that nowhere does it say on Sony's website "we are working on an update".
6. Igor, it is clearly mentioned that Sony VAIO computers do not currently support Virtualization Technology (VT).
Yes in the KB article dated October 27th, 2008.
No on the Sony Style website where the notebook has been ordered back in August 2008. Time travel not yet invented.
7. In this case, I suggest that you contact our Customer Information and Service Center to place and request. Dissatisfied customers and policy issues are handled by our Customer Information and Service Center.
Ok, so I will send an email, some developer will get it and all will be fine right? Bzzzt... Wrong!
8. Igor, I am sorry to inform you that, Telephone support is the only way to contact our Customer Information and Service Center.
Phone... again... this time I would need to call 1-239-768-7669 but I can't because...
9. In this case, you will be charged.
Well if I have to make an international call, isn't it obvious that I will be charged? D'oh!
Now, what this long (and hopefully at least a bit funny) rant tries to convey is that OEMs (not just Sony, other notebook manufacturers too) are damaging Intel's corporate image in this way.
How can I develop on Intel platform for Intel Platform using VT when I can't even turn it on?
I really need someone from Intel to help me with this issue.
Some manager on Intel Virtualization team who will pick up the phone, call a Sony representative, verbally wound his behind, rub some salt in, and demand a BIOS update A.S.A.P to be released to the customers. Or just politely ask -- whichever way works better.
Please folks, there is no one else who can resolve this!
Best regards,
Igor Levicki
Intel Black Belt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
http://blog.durdle.com/archives/2008/09/03/sony-vaio-z-disabled-vt-virtualization-technology/
I am not the only one having this issue.
I found out that there is a way to work around this issue by editing NVRAM (CMOS) but the problem is that I don't know the right NVRAM token for my notebook model and BIOS version. If someone can get that information for me I would be gratefull.
EDIT: Unfortunately this works for Phoenix BIOS, not for AMI BIOS which I have. Back to square one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Now you see it - http://www.sony.com.sg/product/vgn-z26gn (specification tab)
Now you don't - http://www.sony.com.sg/microsite/vaio/products/vaio_z/product.html (my research and compared against Intel P8600 specs)
Quoting - Igor Levicki
http://blog.durdle.com/archives/2008/09/03/sony-vaio-z-disabled-vt-virtualization-technology/
I am not the only one having this issue.
I found out that there is a way to work around this issue by editing NVRAM (CMOS) but the problem is that I don't know the right NVRAM token for my notebook model and BIOS version. If someone can get that information for me I would be gratefull.
EDIT: Unfortunately this works for Phoenix BIOS, not for AMI BIOS which I have. Back to square one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A small update on my own progress since it seems that nobody wants to help me:
I have figured out that the notebook has APTIO BIOS which is actually UEFI, not legacy BIOS like I suspected earlier.
AMI Firmware Update Utility(APTIO) Ver.2.21.03 (afuwin.exe) can be used to save the current flash contents which is what I have done. After brief analysis I realized that the firmware is produced by InsydeSW which is confirmed by the following press release.
I will now exercise my fair use rights and attempt to reverse-engineer the firmware to figure out how to enable Intel VT.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Another update in quest for my missing Intel VT:
If you too are interested in extracting your Aptio UEFI BIOS image from your Sony VAIO notebook you can get this file (right-click, Save As).
IMPORTANT: Do not run the file itself or you may brick your notebook! Neither Intel nor I will accept responsibility if you make a mistake!
Extract the contents of the EP0000169871.exe using WinZIP or WinRAR and keep only afuwin.exe, amifldrv32.sys, and amifldrv64.sys.
To read the contents of the flash and save it to a file type the following command in your command prompt window:
afuwin backup.rom /O
NOTE: The option on the command line is capital letter O, not zero, and you need to do this as the Administrator or afuwin.exe will not be able to install driver and access the flash interface.
The program will read out the flash and save a file. It will also set your CPU fan to 100% as a side effect, and you will have to reboot to restore it to the normal level.
Now that you have the file, what can you do with it? Well, if you have AMIBCP for Aptio, you can do anything you like, but since the demo kit costs $800 at AMI's website you can only reverse engineer the file yourself just like I did.
IMPORTANT: Do not attempt to flash the BIOS with the file you got this way or by using this utility! That goes especially if you modified the file in any way. It won't work, and the result will be an extremely expensive brick with a Sony logo. Standard disclaimer applies here as well.
I have attached a small tool I wrote yesterday to extract the EFI PE executables from the BIOS image. Bear in mind that the tool is not extracting the exact PE images - they are good enough for disassembling and reverse-engineering though. Usage of the tool is self-explanatory, just run it to see the command line syntax.
When you run the tool, you will get approximately 15 PE images in the same folder. Look for the one with the number 0009, size of ~9.4 KB or with Unicode strings SmmBasesVariable, CpuS3Resume, Setup near the end of the file - that file is responsible for programming the MSR 0x3A and thus for disabling Intel VT.
My goal is to determine which NVRAM variable holds the Enable/Disable flag, not to patch the code itself since the patching cannot be done in reliable manner while NVRAM should be modifiable using some (un)documented EFI interface.
In Sony VAIO VGN-FW190E BIOS version R0250Y0, the offending WRMSR is located at FFFD5BB1 where you can see three values being pushed on the stack -- msr_high_bits, msr_low_bits, msr_number (0x3A) followed by the function call which contains the actual WRMSR instruction.
I would really appreciate any help I can get.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Another update in quest for my missing Intel VT:
If you too are interested in extracting your Aptio UEFI BIOS image from your Sony VAIO notebook you can get this file (right-click, Save As).
IMPORTANT: Do not run the file itself or you may brick your notebook! Neither Intel nor I will accept responsibility if you make a mistake!
Extract the contents of the EP0000169871.exe using WinZIP or WinRAR and keep only afuwin.exe, amifldrv32.sys, and amifldrv64.sys.
To read the contents of the flash and save it to a file type the following command in your command prompt window:
afuwin backup.rom /O
NOTE: The option on the command line is capital letter O, not zero, and you need to do this as the Administrator or afuwin.exe will not be able to install driver and access the flash interface.
The program will read out the flash and save a file. It will also set your CPU fan to 100% as a side effect, and you will have to reboot to restore it to the normal level.
Now that you have the file, what can you do with it? Well, if you have AMIBCP for Aptio, you can do anything you like, but since the demo kit costs $800 at AMI's website you can only reverse engineer the file yourself just like I did.
IMPORTANT: Do not attempt to flash the BIOS with the file you got this way or by using this utility! That goes especially if you modified the file in any way. It won't work, and the result will be an extremely expensive brick with a Sony logo. Standard disclaimer applies here as well.
I have attached a small tool I wrote yesterday to extract the EFI PE executables from the BIOS image. Bear in mind that the tool is not extracting the exact PE images - they are good enough for disassembling and reverse-engineering though. Usage of the tool is self-explanatory, just run it to see the command line syntax.
When you run the tool, you will get approximately 15 PE images in the same folder. Look for the one with the number 0009, size of ~9.4 KB or with Unicode strings SmmBasesVariable, CpuS3Resume, Setup near the end of the file - that file is responsible for programming the MSR 0x3A and thus for disabling Intel VT.
My goal is to determine which NVRAM variable holds the Enable/Disable flag, not to patch the code itself since the patching cannot be done in reliable manner while NVRAM should be modifiable using some (un)documented EFI interface.
In Sony VAIO VGN-FW190E BIOS version R0250Y0, the offending WRMSR is located at FFFD5BB1 where you can see three values being pushed on the stack -- msr_high_bits, msr_low_bits, msr_number (0x3A) followed by the function call which contains the actual WRMSR instruction.
I would really appreciate any help I can get.
Hi Igor -
I've forwared your concerns to the director of OEM enabling. I understand your frustration, but OEM's make the decision on what's in/what's out - based on a large set of parameters - like validation, market segment, cost, etc. I'll let you know what comes of it.
Thanks
Eric Sardella
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Igor -
I've forwared your concerns to the director of OEM enabling. I understand your frustration, but OEM's make the decision on what's in/what's out - based on a large set of parameters - like validation, market segment, cost, etc. I'll let you know what comes of it.
Thanks
Eric Sardella
Hello Eric!
Thanks for hearing me out, and I am sorry if it sounded a bit off-topic at the webinar, but I really felt it was worth your attention. I hope that the following arguments will convince you that Intel has to intervene:
People buy notebooks and prebuilt computers from OEMs based on the advertised specification.
Based on the specification available at the time of purchase on the OEM website, I was convinced that I would be able to use all the features the CPU has to offer. Unfortunately, that isn't possible.
Now, I don't mind if OEM choses to ship a notebook with VT disabled in BIOS, and with a disclaimer that they don't offer support for any issues you might have while using VT as long as they leave me the option to enable it.
In this particular case the notebook was a gift, so the money wasted on a feature which can't be used wasn't from my own pocket. However, if I bought it with my own money, and if I wanted a notebook without VT, then I would have chosen a less expensive CPU and saved some money in the process.
The main issue here is that conscious buyers who know which features they should expect from a particular SKU# are usually developers, and Intel is letting them down and leaving them at the mercy of OEMs.
Take a look at your own website:
http://processorfinder.intel.com/Details.aspx?sSpec=SLB3S
It is the CPU I have in my notebook. There is a disclaimer for EM64T and Execute Disable, but there is no disclaimer for Virtualization Technology.
Here you can read the product marketing specification (PDF) for my notebook - again no mention of the inability to use Virtualization Technology CPU feature. After all, it is a somewhat high-end notebook when you consider $1,799 price tag.
Finally, a Configure-To-Order page where it was ordered - again no mention that I won't be able to use Virtualization Technology.
As a developer, even though I cannot justify OEMs decision, I can at least understand that my inability to use VT isn't Intel's fault because after all the CPU does support the feature.
But tell me, what chance an Average Joe has at understanding and accepting that?
In the end they will turn to you because the OEM support will tell them the same lie they have told me - that the CPU doesn't support the feature. Moreover, Intel is the one getting money for an advertised feature customers cannot use. How will you handle that?
The current practice is deceiving to say the least, and as much as it may hurt the OEMs it will hurt the Intel Corporation as well.
So yesterday in a webinar when I saw "Faster Virtualization" on the slide I was really concerned. Intel is obviously investing a lot of effort into making and marketing of such a great feature which won't be able to reach the audience because of those narrow-minded men in the middle.
I believe that the control over CPU features has to be in the customer's hands. Intel got burnt once with the CPU serial number fiasco, and I was hoping that you have learned that lesson.
Finally, a suggestion on how to resolve the problem - since nowadays OEMs use mostly EFI based BIOS, may I suggest that Intel engineers write a unified CPU initialization EFI module which will be given to the OEMs for integration in the binary format so that they cannot enable/disable the features or hide the CPU related options from the end user? That module could also contain fresh CPU microcode updates and be a way to push those to the customers because OEMs have shown that they simply don't care about correcting errata. Let me know what you think about the idea.
Looking forward to hearing from you Eric!
Regards,
Igor Levicki
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I absoluteley agree with you. This is a shame for Sony and also for Intel. I also had no success enabling VT support on my Sony Vaio VGN-FW21M (European Version) as it's based on AMI BIOS. There are just workarounds for Phoenix BIOS.
I mean we may could enable it if we got an AMIBCP version with APTIO support (v4.06). Please have also a look at the latest posts on this thread. http://forum.notebookreview.com/showthread.php?p=4531271#post4531271
Regards
Guido
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I absoluteley agree with you. This is a shame for Sony and also for Intel. I also had no success enabling VT support on my Sony Vaio VGN-FW21M (European Version) as it's based on AMI BIOS. There are just workarounds for Phoenix BIOS.
I mean we may could enable it if we got an AMIBCP version with APTIO support (v4.06). Please have also a look at the latest posts on this thread. http://forum.notebookreview.com/showthread.php?p=4531271#post4531271
Regards
Guido
Guido,
Please contact me via MSN, Skype, or via my website http://www.levicki.net/ feedback form. I have some questions for you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just wanted to let you know I appreciate your endeavours enormously. I own an FW21E, was as surprised as you were when I found out VT was disabled. I contacted Sony about this to no avail. I do not posses the required technical skills to help you on this one, but I'll be watching this thread and the one on notebookreview.com.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just wanted to let you know I appreciate your endeavours enormously. I own an FW21E, was as surprised as you were when I found out VT was disabled. I contacted Sony about this to no avail. I do not posses the required technical skills to help you on this one, but I'll be watching this thread and the one on notebookreview.com.
Thanks!
Thanks for your support. I have been telling everyone at Intel that this is unacceptable and bad for business. I guess that more than 1500 views of this thread confirms it as a serious issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good news everyone!
After a long session of reverse-engineering I have managed to enable VT by patching the BIOS.

I am currently writing a generic patch which should work for all Sony notebooks with Aptio based EFI BIOS - stay tuned!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here is a patch for Aptio based Sony notebooks, but please read the whole article most carefully before attempting anything -- I won't be the one responsible if you brick your notebook:
HOWTO: Enable Intel VT on Sony VAIO notebook with AMI Aptio EFI BIOS- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here is a patch for Aptio based Sony notebooks, but please read the whole article most carefully before attempting anything -- I won't be the one responsible if you brick your notebook:
HOWTO: Enable Intel VT on Sony VAIO notebook with AMI Aptio EFI BIOSDear Igor,
I would like to ask you if you have found any solution, for Vaio notebooks with Phoenix BIOS, during your research. I have a VGN-NR498E and I would like to enable the VT flag. Even if I could install VirtualBox in Ubuntu 64, I know I have this feature and I can't use it...
Best regards,
Lucian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here is a patch for Aptio based Sony notebooks, but please read the whole article most carefully before attempting anything -- I won't be the one responsible if you brick your notebook:
HOWTO: Enable Intel VT on Sony VAIO notebook with AMI Aptio EFI BIOSKudos dude. Just, wow. Really. I hope I'll be able to use it when it's released!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Igor,
I would like to ask you if you have found any solution, for Vaio notebooks with Phoenix BIOS, during your research. I have a VGN-NR498E and I would like to enable the VT flag. Even if I could install VirtualBox in Ubuntu 64, I know I have this feature and I can't use it...
Best regards,
Lucian
http://forum.notebookreview.com/showthread.php?t=189228
http://www.wimsbios.com/phpBB2/topic9326-15.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you very much for your kind words. It is not the interest in this topic that I have lost, it is my faithfull companion and with it my strength, motivation, and will to go on after experiencing such a tragic loss first hand. It will surely take some time to pick myself up and continue with what I was doing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Since nobody wanted to help and to push this issue with Sony so that they release an official BIOS update which enables Intel VT I decided to roll up my sleeves and to help people who were in the same position as me -- they couldn't use a CPU feature they paid for.
I have finalized permanent Intel VT enable patch for Sony VAIO notebooks with AMI Aptio BIOS. You can get it from my website Downloads section. Read the enclosed README.TXT carefully before attempting to use it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Igor -
I've forwared your concerns to the director of OEM enabling. I understand your frustration, but OEM's make the decision on what's in/what's out - based on a large set of parameters - like validation, market segment, cost, etc. I'll let you know what comes of it.
Thanks
Eric Sardella
What I'd propose to "the industry" would be in such cases, to have (menu) sections marked as "not supported". This would make it clear to users, that if they {dis,en}able features, they may not get support for resulting problems, while at the same time it is left up to the users to decide what is important to them.
BTW: Companies often forget, that it is a good thing for them to not only focus on "the majority of users", but to enable "professionals/power users" as well, as they are the ones giving trusted opinions to friends and colleagues.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page