Parallels Forums
> Archives > Parallels Desktop for Mac  
VT-X disabled by firmware update?  
  

VT-X disabled by firmware update?

Apr 6, 2006, 11:44 AM
#1  

elektroholunder
Junior Member


Join: Apr 2006
Posts: 8
VT-X disabled by firmware update?
Hi everybody,

I tried Workstation on my Core Duo Mac Mini; apart from what I think are probably beta issues (no full screen possible etc), everything works great - I'm definitely buying licenses when the release is out. If it's priced at 49,95 as the versions for the other host systems, it's a steal ..

But: after my trial I installed Boot Camp and did a native XP install; since the necessary firmware update, launching a VM brings up the message that VT-X is present but disabled.

Is it possible for me to reactivate VT-X in Open Firmware somehow, or is this a matter which must be solved by a new Workstation release?

Cheers,
Jan
Apr 6, 2006, 12:17 PM
#2  

anshar
Member


Join: Mar 2006
Posts: 81
It is really interesting question! If we list 3 available Macs in terms of VT-x support we will have following:

1. iMac - VT supported and enabled.
2. MacBook - VT supported and enabled.
3. Mac mini - VT supported but disabled.

Is it intention of Apple to reduce Mac mini functionality or just firmware bug - I don't know...

__________________
Best Regards,
anshar
Apr 6, 2006, 12:38 PM
#3  

elektroholunder
Junior Member


Join: Apr 2006
Posts: 8
As Boot Camp, the respective firmware and Workstation for OS X are all brand-spanking new, I wouldn't jump to any conclusions yet.

I'd say there is probably just a glitch in the combination of these three - at least I really, really hope so. Being able to use Minis in our corporate environment would so rock :)
Apr 6, 2006, 12:48 PM
#4  

daveschroeder
Member


Join: Apr 2006
Posts: 67
This has nothing to do with the firmware update.

VT is not enabled on any Intel-based Mac mini.
Apr 6, 2006, 12:56 PM
#5  

anshar
Member


Join: Mar 2006
Posts: 81
The question is it done intentionally or is it just a bug in firmware?

__________________
Best Regards,
anshar
Apr 6, 2006, 01:34 PM
#6  

daveschroeder
Member


Join: Apr 2006
Posts: 67
I've just been talking with an engineer at Apple, and the thinking right now is that it is unintentional and is a bug. I have passed his contact information on to the Parallels team.
Apr 6, 2006, 01:47 PM
#7  

elektroholunder
Junior Member


Join: Apr 2006
Posts: 8
Thanks Dave, that certainly is good news! So I'm waiting for the things to come from Apple in this regard.

On a different note: I haven't really worked with VMs before, and especially not on the Mac, so please forgive me if this is a stupid question, but: what is the best way to exchange files between VM and host - i.e., make office documents created in the VM available to OS X?
Apr 6, 2006, 02:01 PM
#8  

perdurabo
Junior Member


Join: Apr 2006
Posts: 16
Quote:
Originally Posted by elektroholunder
but: what is the best way to exchange files between VM and host - i.e., make office documents created in the VM available to OS X?
The VM environment grabs its own IP address on the LAN, so you can set up a Windows share on either/both OS X and/or Windows and share files that way.
Apr 7, 2006, 10:47 AM
#9  

DaveGee
Junior Member


Join: Apr 2006
Posts: 4
Quote:
Originally Posted by daveschroeder
I've just been talking with an engineer at Apple, and the thinking right now is that it is unintentional and is a bug. I have passed his contact information on to the Parallels team.
Dave,

For various reasons I just don't want to fork out the cash for a Core Duo iMac or Mac Book Pro (I'm really holding out for the desktop machines) but with all this bootcamp and even more sexy to me virtulazation (I'm not really a gamer so this is just up my ally) the mini was looking like a real option to bide-my-time. Like I said I'm not a hard core gamer by any stretch so I can pretty much forgive the built in graphics (not happy but I can deal) but when I read that VT was crippled / disabled and or in some way not available stopped me in my tracks.

I hated to think it was done 'just to be nasty' aka a pure and heartless marketing move without any cost savings associated with it but it was the first thing that jumped into my head. Sure save a few bucks not having an ATI chipset (gulp well okay) but no VT when it is working fine everywhere else... That I couldn't forgive Apple for.

Well anyway I'm glad to read what you posted and I and I'm sure many others are quite interested in hearing anything more you might find out.

Thanks for (pretty much) restoring my faith in Apple. :D

Dave
Apr 7, 2006, 11:57 AM
#10  

Scott Willsey
Senior Member


Join: Apr 2006
Posts: 174
Question for those with core duo minis who installed bootcamp and then found vt-x not working... is the firmware upgrade for bootcamp different than the firmware Update 1.0 that came out on the 6th or so?

The reason I ask is I have not installed bootcamp yet, but I have installed 10.4.6, I have installed firmware update 1.0, and I have installed the parallels workstation trial and I do have VT-x support working.

I was planning on doing bootcamp shortly but now I'm wondering.
Apr 7, 2006, 11:57 AM
#11  

waa
Junior Member


Join: Apr 2006
Posts: 1
Quote:
Originally Posted by daveschroeder
I've just been talking with an engineer at Apple, and the thinking right now is that it is unintentional and is a bug. I have passed his contact information on to the Parallels team.
How did you test if VT was enabled? I wrote a VT test program based on the Xen start-up routines and it indicates VT is not only present, but enabled.
Apr 7, 2006, 12:31 PM
#12  

daveschroeder
Member


Join: Apr 2006
Posts: 67
Quote:
Originally Posted by waa
How did you test if VT was enabled? I wrote a VT test program based on the Xen start-up routines and it indicates VT is not only present, but enabled.
One of the Parallels programmers has written a simple kext to demonstrate that VT is disabled/inaccessible on the Mac mini in firmware, and is in communication with Apple on the issue.

__________________
Dave Schroeder
University of Wisconsin - Madison
das@doit.wisc.edu
http://das.doit.wisc.edu
Apr 15, 2006, 10:45 PM
#13  

MacFanatic
Junior Member


Join: Apr 2006
Posts: 1
disabled firmware
Quote:
Originally Posted by anshar
The question is it done intentionally or is it just a bug in firmware?
I suspect the firmware in the Intel Mini has a disabled-on-purpose VT, just like the iBook, iMac, Mini, and eMac have only mirrored external monitor support. Apple disabled the extended desktop that is available on PowerMacs and PowerBooks, to differentiate between the consumer and professional lines. My 14" iBook does just fine with an extrnal monitor running at 1280x1024 while the 14" has a 1024x786 or nothing at all on it. The firmware was there, and could be turned on with unix. An enterprising programmer put together an Applescript hack that restored the settion, and I downloaded ScreenSpanningDoctor, ran the script, and everything works nicely.

I suspect if Apple has set the mini that way, it won't be long before someone figures out how to fix it!
Apr 16, 2006, 09:31 AM
#14  

NoBackUp
Member


Join: Apr 2006
Posts: 30
Quote:
Originally Posted by MacFanatic
I suspect the firmware in the Intel Mini has a disabled-on-purpose VT, just like the iBook, iMac, Mini, and eMac have only mirrored external monitor support. Apple disabled the extended desktop that is available on PowerMacs and PowerBooks, to differentiate between the consumer and professional lines. My 14" iBook does just fine with an extrnal monitor running at 1280x1024 while the 14" has a 1024x786 or nothing at all on it. The firmware was there, and could be turned on with unix. An enterprising programmer put together an Applescript hack that restored the settion, and I downloaded ScreenSpanningDoctor, ran the script, and everything works nicely.

I suspect if Apple has set the mini that way, it won't be long before someone figures out how to fix it!

what are people complaining about, i have 2 Mini's both updated and VT-x is working on Both, I even used the RECOVERY CD to downgrade one and reinstalled it again , same result ..

I even booted via Boot Camp into Native and use the Intel CPUID util...which also tells me that VT-X is available and supported...

Looks Like every one is trying to "Make" everyone else belive that this is an issue..

From My research and PHYSICAL testing I would say it ant an issue

or did I miss something ?
Apr 16, 2006, 12:11 PM
#15  

dr_lha
Junior Member


Join: Apr 2006
Posts: 18
Quote:
Originally Posted by NoBackUp
what are people complaining about, i have 2 Mini's both updated and VT-x is working on Both, I even used the RECOVERY CD to downgrade one and reinstalled it again , same result ..

I even booted via Boot Camp into Native and use the Intel CPUID util...which also tells me that VT-X is available and supported...

Looks Like every one is trying to "Make" everyone else belive that this is an issue..

From My research and PHYSICAL testing I would say it ant an issue

or did I miss something ?
You missed the fact that you're only talking about 2 machines, which clearly do not accurately represent experience of everyone with Minis out there. On my Mini the VT-x was disabled by default. I used the sleep trick and now I have VT-x running. There's clearly a bug in the firmware that disables it at boot-up. I've also tried both firmwares on the mini.

That said, I rarely reboot my machine, so having it work after a sleep basically means it works 99.99% of the time.
May 23, 2006, 12:24 PM
#16  

crchad
Junior Member


Join: May 2006
Posts: 3
Something Overlooked?
I found this thread after getting the VT-x disabled message when I started Parallels today. It worked yesterday (after first installing) without a message, as others have stated. I've tried the various sleep/pulling-the-plug etc tricks, without success.

There's a lot of talk about whether VT-x is enabled on different firmware/serial combinations. But isn't it overlooking the elephant in the room? Couldn't it simply be a bug, sorry a "feature", with Parallels that's causing it to be disabled, or reported as disabled?

Why did it work first time but give an error after the Mac is rebooted? I'd say there's two possible choices:
1. It didn't detect the setting was disabled the first time it ran.
2. It changed something that didn't manifest until after a reboot.
Does Parallels install/change anything that could related to the firmware settings?

Has anyone tried restoring a Mini (does this only happen to Minis?) from a backup or to a clean install... Then run the vtx-check pre and post installing Parallels to see what happens (can you restore the firmware too? - I don't know.)


Just a couple of thoughts.

Chris

P.S. Nice work Parallels people.
May 23, 2006, 12:29 PM
#17  
Andrew @ Parallels's Avatar

Andrew @ Parallels
Parallels Team


Join: Apr 2006
Posts: 1,557
This problem happened sometimes on Mac Minis some time ago. Now with the latest firmware and Mac OS updates it supposed to be fixed. Did you have installed the latest firmware and software updates?

__________________
Best Regards,
Andrew @ Parallels
May 23, 2006, 04:16 PM
#18  

crchad
Junior Member


Join: May 2006
Posts: 3
Yes I have the latest firmware. But I didn't install it until after the problem manifested. Could that be relevant?
May 23, 2006, 05:20 PM
#19  
Andrew @ Parallels's Avatar

Andrew @ Parallels
Parallels Team


Join: Apr 2006
Posts: 1,557
Hmm... I don't know really. We did reproduce Mac Mini VT-x lock issue in our labs and have opened the ticket in Apple support. Not long ago they told us that with latest updates it fails to reproduce. So we rechecked it in our labs again - it doesn't reproduced anymore with latest updates.

__________________
Best Regards,
Andrew @ Parallels
May 24, 2006, 09:25 AM
#20  

crchad
Junior Member


Join: May 2006
Posts: 3
Interesting...Today it's working ok again. I guess the firmware update and a couple of extra reboots did the trick.
 


Thread tools Display modes
Hybrid Mode