VT-X disabled by firmware update?

[elektroholunder]

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

[anshar]

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...

[elektroholunder]

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 :)

[daveschroeder]

This has nothing to do with the firmware update.

VT is not enabled on any Intel-based Mac mini.

[anshar]

The question is it done intentionally or is it just a bug in firmware?

[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.

[elektroholunder]

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?

[perdurabo]

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.

[elektroholunder]

Thanks! That sounds like a smooth solution my users certainly could accept.

[daveschroeder]

Thanks! That sounds like a smooth solution my users certainly could accept.

You'll also be able to share a folder/volume from the Mac environment into the Parallels environment using the Parallels tools.

[elektroholunder]

Perfect; that is exactly what I initially hoped for. Exciting times - I'm really looking forward to the next release(s).

[DaveGee]

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

[Scott Willsey]

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.

[waa]

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.

[elektroholunder]

@Scott: good question; my firmware download (MacMiniFirmwareUpdater.dmg) is from Tuesday 4th, size 1.562.706 Bytes, MD5 1404b34a75d591e72e645c41a8af71cf - is yours different?

[furfurfur]

Hi guys

Just wanted to mention that I bought a mini yesterday (1.66 Duo / 1GB) and all I've done is update to 10.4.6 and installed Parallels - I haven't installed any new firmware for Boot Camp or otherwise.

I get the message from Parallels that VT is disabled in the BIOS.

Cheers
James

[Scott Willsey]

James, that can't be true or it wouldn't be working for me. Try updating your firmware with Apple's recent firmware update. Maybe Parallels was working with a pre-updated firmware. This firmware's only been out a few days.

[Scott Willsey]

@Scott: good question; my firmware download (MacMiniFirmwareUpdater.dmg) is from Tuesday 4th, size 1.562.706 Bytes, MD5 1404b34a75d591e72e645c41a8af71cf - is yours different?

Not sure how to check the MD5 hash but the date and file size are right.

[daveschroeder]

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.

[Scott Willsey]

Dave,

How do you explain when I run parallels that it shows VT-x enabled on my core duo mini, and that xp runs quite fast (faster than expected) under it?

I'm wondering if the Parallels test wasn't against the original mini firmware and not the update that came out on the 4th.

Either that or they haven't tried it on a core duo, only a core solo? I don't know, I'm guessing, but it's working for me.

[daveschroeder]

Dave,

How do you explain when I run parallels that it shows VT-x enabled on my core duo mini, and that xp runs quite fast (faster than expected) under it?

I'm wondering if the Parallels test wasn't against the original mini firmware and not the update that came out on the 4th.

Either that or they haven't tried it on a core duo, only a core solo? I don't know, I'm guessing, but it's working for me.

I think there may be more issues at play here, and if VT being disabled on some minis is indeed an oversight, it wouldn't be surprising to me if some mini production was not affected by this issue. I'll post more information as I receive it. I think, as you say, there has also been some confusion surrounding Duo versus Solo.

[daveschroeder]

Here is the source for a kernel extension that can test whether VT-x is present on the processor and whether or not it can be used:

http://das.doit.wisc.edu/misc/vtx-check.zip

To use:

- Unpack the archive
- Go into the vtx-check directory and type "make" (requires that the Developer Tools have been installed)
- Load the kext with "sudo kextload MacOS/vtxcheck.kext"
- Look at "dmesg" for details; you should see a message indicating whether or not VT-x can be used on your system

It would be good if people could try this with their Mac mini and report back WITH YOUR SERIAL NUMBER:

Confirmed working:

- iMac (Core Duo) (all models)
- MacBook Pro (Core Duo) (all models)

- Mac mini (Core Duo) (firmware: MM11.0055.B02, serial: YM60935SU39)
- Mac mini (Core Duo) (firmware: MM11.0055.B02, serial: YM608JEJxxx)
- Mac mini (Core Duo) (firmware: MM11.004B.B00, serial: YM608RPVxxx)
- Mac mini (Core Duo) (firmware: MM11.0055.B02, serial: YM610237U39)

Confirmed NOT working:

- Mac mini (Core Duo) (firmware: MM11.004B.B00, serial: YM608QS0U36)
- Mac mini (Core Duo) (firmware: MM11.0055.B02, serial: YM608QS0U36)
- Mac mini (Core Duo) (firmware: MM11.004B.B00, serial: YM6092JZVJN)
- Mac mini (Core Duo) (firmware: MM11.0055.B02, serial: YM6092JZVJN)
- Mac mini (Core Duo) (firmware: MM11.004B.B00, serial: YM610237U39)
- Mac mini (Core Duo) (firmware: MM11.0055.B02, serial: YM6087PJU36)
- Mac mini (Core Duo) (firmware: MM11.0055.B02, serial: YM608R0VU36)


To be tested:

- Mac mini (Core Duo) before Mac mini (early 2006) Firmware Update 1.0 (firmware: MM11.004B.B00)
- Mac mini (Core Duo) after Mac mini (early 2006) Firmware Update 1.0 (firmware MM11.0055.B02)
- Mac mini (Core Solo) before Mac mini (early 2006) Firmware Update 1.0 (firmware MM11.004B.B00)
- Mac mini (Core Solo) after Mac mini (early 2006) Firmware Update 1.0 (firmware MM11.0055.B02)

Thanks!

UPDATE:

It's looking like it's not as clear cut as models here, since we have at least one person with a Mac mini Core Duo that DOES have VT enabled. I'm guessing it was an issue that got caught, and newer Core Duo Mac minis have VT enabled.

[Scott Willsey]

Dave, thanks for the efforts on this issue. I can't do a before/after scenario but I can verify that the test gives the expected results on my post Firmware Updater 1.0 update. I'll do that tonight (late) when I get home.

[enchiladas_verdes]

To be tested:
- Mac mini (Core Duo) after Mac mini (early 2006) Firmware Update 1.0

Dave, I ran this on my Intel Core Duo 1.66 Mini and got the following:

"VT-x is supported (reported by CPUID) and can be used"

I have Firmware Update 1.0 installed and my Boot ROM Version is listed as MM11.0055.B02.

[daveschroeder]

Dave, I ran this on my Intel Core Duo 1.66 Mini and got the following:

"VT-x is supported (reported by CPUID) and can be used"

I have Firmware Update 1.0 installed and my Boot ROM Version is listed as MM11.0055.B02.

That's really interesting, because I just ran it against a Mac mini (Core Duo) with MM11.0055.B02 (for those not paying attention, that's the recent firmware update), and it is definitely NOT enabled.

I think it's going to come down to certain ranges of Mac minis. We're going to have to start looking at serial numbers too. This one was YM608QS0U36. What is your serial?

[metfoo]

I just got my mini core duo 2 days ago. If you have a working model, how old is it? Are the newest ones enabled or are the oldest ones enabled?

[tobyg]

That's really interesting, because I just ran it against a Mac mini (Core Duo) with MM11.0055.B02 (for those not paying attention, that's the recent firmware update), and it is definitely NOT enabled.

I think it's going to come down to certain ranges of Mac minis. We're going to have to start looking at serial numbers too. This one was YM608QS0U36. What is your serial?

What about running something as simple as this

sysctl machdep.cpu.features

from terminal?

You should get an output like this. I get the same output from both my Intel iMac and Intel Mac Mini.

machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM SSE3 MON VMX EST TM2 TPR

As far as I am aware, VMX is the virtualization. Do the mac mini's that are not working with the virtualization show VMX?

Just FYI, my mac mini works fine and states VT-x is supported when running the kext.

Mine has been updated with the newest firmware (1.0.0) for bootcamp support.

Core Duo 1.66 Mac Mini
Boot ROM version: MM11.0055.B02
Serial Number: YM608JEJxxx (last 3 digits left off)
SMC Version : 1.3f2

[Chris]

I have a Mac mini Core Duo that reports VT-x is available, but Parallels says it CANNOT USE use it, as it's been disabled by the BIOS??

My machine:
Boot ROM Version: MM11.0055.B02
Serial Number: YM60935SU39

I did update my firmware on the 6th.

vtxcheck reported: VT-x is supported (reported by CPUID) and can be used

Chris

[tobyg]

I have a Mac mini Core Duo that reports VT-x is available, but Parallels says it CANNOT USE use it, as it's been disabled by the BIOS??

My machine:
Boot ROM Version: MM11.0055.B02
Serial Number: YM60935SU39

I did update my firmware on the 6th.

vtxcheck reported: VT-x is supported (reported by CPUID) and can be used

Chris

I should note mine also states its supported, and Parallels runs fine with VT-x. When the VM is running and if I do an Parallels Workstation->About Parallels Workstation it states "Virtualization mode: Intel VT-x"

That means it's running I would think. Virtual machine seems quite fast even on my mini.

[Chris]

Okay guys... here's something interesting:

Ever since I loaded the vtxcheck.kext and then unloaded it, now when I run Parallels it SUCCESSFULLY detects VT-x support on my Mac mini Core Duo!

I'm using build 1658.24 of Parallels. About to reboot and see if it stops working again, until I load and unload the vtxcheck kext.

Could there be a bad build of Parallels floating around out there?

Chris

[STim]

Just a quick note...

1. Any known to us MacTel has VT-capable CPU
2. VT can be locked or unlocked by corresponding BIOS controls.
3. If VT is locked by BIOS, the CPU info will still show that it's VT-capable.
4. But since VT is locked, it can never be used until unlocked.

We're now getting in contact with Apple to clear things out. Please be patient. I'm sure very soon PW will run in VT mode on any MacTels :)

[furfurfur]

Guys

As I said before - Mini Core Duo 1.66 purchased yesterday from London. No firmware updates applied by me. Serial number YM6092JZVJN:

VT-x is supported (reported by CPUID), but locked in MSR and can't be used

Cheers

James

[daveschroeder]

machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM SSE3 MON VMX EST TM2 TPR

As far as I am aware, VMX is the virtualization. Do the mac mini's that are not working with the virtualization show VMX?

Yes, Mac minis that are not working do still show VMX as a CPU feature.

[Chris]

My Mac mini Core Duo now works fine- even across a cold reboot. I haven't changed anything else- all I did was go to work today.

Yesterday, every time I started the VM in Parallels I got a "VT-x available but disabled by the BIOS" message. Today, when I got home, I couldn't wait to try the vtx-check kernel extension to try to diagnose the problem. I tried it, and it reported VT-x was available AND enabled. I unloaded it again, just to be safe.

I tried Parallels again- This time, it is able to use VT-x just fine!! It seems to work now. I thought maybe the MSR was "tickled" the right way by the kext, so I tried shutting down and cold booting, to see if my Mac mini reverted back to the old state. It didn't, which is very odd.

Something seems flaky here... but i'm happy for now that it works. Good news for all you other Mac mini owners out there- might be something simple.

[furfurfur]

OK - updated to new Firmware 1.0 and the vtx-check util reports the same thing

VT-x is supported (reported by CPUID), but locked in MSR and can't be used

Cheers

James

[anshar]

All this so weird...

[mikeward]

Here is the source for a kernel extension that can test whether VT-x is present on the processor and whether or not it can be used:

http://das.doit.wisc.edu/misc/vtx-check.zip

To use:

- Unpack the archive
- Go into the vtx-check directory and type "make" (requires that the Developer Tools have been installed)
- Load the kext with "sudo kextload MacOS/vtxcheck.kext"
- Look at "dmesg" for details; you should see a message indicating whether or not VT-x can be used on your system

It would be good if people could try this with their Mac mini and report back WITH YOUR SERIAL NUMBER:

Confirmed working:

- iMac (Core Duo) (all models)
- MacBook Pro (Core Duo) (all models)

- Mac mini (Core Duo) (firmware: MM11.0055.B02, serial: YM60935SU39)
- Mac mini (Core Duo) (firmware: MM11.0055.B02, serial: YM608JEJxxx)

Confirmed NOT working:

- Mac mini (Core Duo) (firmware: MM11.004B.B00, serial: YM608QS0U36)
- Mac mini (Core Duo) (firmware: MM11.0055.B02, serial: YM608QS0U36)
- Mac mini (Core Duo) (firmware: MM11.004B.B00, serial: YM6092JZVJN)
- Mac mini (Core Duo) (firmware: MM11.0055.B02, serial: YM6092JZVJN)

To be tested:

- Mac mini (Core Duo) before Mac mini (early 2006) Firmware Update 1.0 (firmware: MM11.004B.B00)
- Mac mini (Core Duo) after Mac mini (early 2006) Firmware Update 1.0 (firmware MM11.0055.B02)
- Mac mini (Core Solo) before Mac mini (early 2006) Firmware Update 1.0 (firmware MM11.004B.B00)
- Mac mini (Core Solo) after Mac mini (early 2006) Firmware Update 1.0 (firmware MM11.0055.B02)

Thanks!

UPDATE:

It's looking like it's not as clear cut as models here, since we have at least one person with a Mac mini Core Duo that DOES have VT enabled. I'm guessing it was an issue that got caught, and newer Core Duo Mac minis have VT enabled.


Machine Name: Mac mini
Machine Model: Macmini1,1
CPU Type: Intel Core Duo
Number Of Cores: 2
CPU Speed: 1.66 GHz
L2 Cache (shared): 2 MB
Memory: 1 GB
Bus Speed: 667 MHz
Boot ROM Version: MM11.004B.B00
Serial Number: YM610237U39
SMC Version: 1.3f2

Parallels Workstation Hypervisor started.
Parallels Workstation VMM Main driver started.
USBF: 2160.684 [0x2770e00] (Reset) USB Generic Hub @ 2 (0x1d100000)
VT-x is supported (reported by CPUID), but locked in MSR and can't be used

[Scott Willsey]

Machine Name: Mac mini
Machine Model: Macmini1,1
CPU Type: Intel Core Duo
Number Of Cores: 2
CPU Speed: 1.66 GHz
L2 Cache (shared): 2 MB
Memory: 2 GB
Bus Speed: 667 MHz
Boot ROM Version: MM11.0055.B02
Serial Number: YM608RPVxxx
SMC Version: 1.3f2

VT-x works for me in Parallels and has since the beginning. I already had the bios update installed when I first installed Parallels.

I have been told that early Yonah didn't have VT-x enabled but that later Yonah processors did, however, I don't know if this is fact or fiction and the serial numbers of those that work and those that don't are all over the place. Furthermore, seeing that some people were able to go from VT-x disabled to enabled makes me wonder even more about that theory.

By the way, go to this page:

http://www.chipmunk.nl/klantenservice/applemodel.html

And enter your serial number. You'll get the date and location of manufacture:


Serial number: YM608RPVxxx
Model: Mxxxx Mac mini Intel Core duo 1.66GHz
Factory: YM (China (Hon Hai = Foxconn) Configured in Czech Republic?)code_to_number: RPV - UV3340W8MRT

Production year: 2006
Production week: 08 (February)
Production number: 29711 (within this week)

[mikeward]

Machine Name: Mac mini
Machine Model: Macmini1,1
CPU Type: Intel Core Duo
Number Of Cores: 2
CPU Speed: 1.66 GHz
L2 Cache (shared): 2 MB
Memory: 1 GB
Bus Speed: 667 MHz
Boot ROM Version: MM11.004B.B00
Serial Number: YM610237U39
SMC Version: 1.3f2

Parallels Workstation Hypervisor started.
Parallels Workstation VMM Main driver started.
USBF: 2160.684 [0x2770e00] (Reset) USB Generic Hub @ 2 (0x1d100000)
VT-x is supported (reported by CPUID), but locked in MSR and can't be used

Have just installed the firmware update... and reinstalled parallels...

vtxcheck.kext reports

Parallels Workstation Hypervisor started.
Parallels Workstation VMM Main driver started.
VT-x is supported (reported by CPUID) and can be used

so it seems the firmware update enables VT-x on the mac mini core duo.
(well mine at least, circa march 06)

however parallels seems to crash and take the wole system with it which makes it unusable at the moment.

mike

[thingi]

kextload: MacOS/vtxcheck.kext loaded successfully
Mini:~/Desktop/vtx-check thingi$ sudo dmesg
hi mem tramps at 0xffe00000
PAE enabled
standard timeslicing quantum is 10000 us
vm_page_bootstrap: 509278 free pages
mig_table_max_displ = 71
Enabling XMM register save/restore and SSE/SSE2 opcodes
89 prelinked modules
ACPI CA 20051117 [debug level=0 layer=0]
AppleACPICPU: ProcessorApicId=0 LocalApicId=0 Enabled
AppleACPICPU: ProcessorApicId=1 LocalApicId=1 Enabled
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.

using 5194 buffer headers and 4096 cluster IO buffer headers
Enabling XMM register save/restore and SSE/SSE2 opcodes
IOAPIC: Version 0x20 Vectors 0:23
Started CPU 01
ACPI: System State [S0 S3 S4 S5] (S3)
Security auditing service present
BSM auditing present
disabled
rooting via boot-uuid from /chosen: 079B5DB5-BC66-4BBD-8AA6-3C33691B2701
Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
FireWire (OHCI) Lucent ID 5811 PCI now active, GUID 0016cbfffe5346ec; max speed s400.
Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleAHCI/AppleAHCIPort@2/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/ST98823AS Media/IOGUIDPartitionScheme/Customer@2
BSD root: disk0s2, major 14, minor 2
CSRHIDTransitionDriver::probe:
CSRHIDTransitionDriver::start before command
CSRHIDTransitionDriver::stop
IOBluetoothHCIController::start Idle Timer Stopped
Jettisoning kernel linker.
Resetting IOCatalogue.
Matching service count = 4
Matching service count = 4
Matching service count = 4
Matching service count = 4
Matching service count = 4
Previous Shutdown Cause: 3
mac 10.3 phy 6.1 radio 10.2
IPv6 packet filtering initialized, default to accept, logging disabled
yukonosx: Ethernet address 00:16:cb:a2:0c:1a
AirPort_Athr5424: Ethernet address 00:14:51:ee:bc:25
display: Not usable
[HCIController][setupHardware] AFH Is Supported
[IOAppleBluetoothHIDDriver][init] IOBluetoothHIDDriver 1.1.4
[IOBluetoothHIDDriver][init] IOBluetoothHIDDriver 1.1.4
[IOAppleBluetoothHIDDriver][handleStart][00-0a-95-43-77-c6] Done.
(42: SystemStarter)tfp: failed on 0:
(42: SystemStarter)tfp: failed on 0:
(42: SystemStarter)tfp: failed on 0:
(42: SystemStarter)tfp: failed on 0:
Parallels Workstation Hypervisor started.
[IOAppleBluetoothHIDDriver][waitForHandshake][00-0a-95-43-77-c6] Unsuccessful Handshake: e00002c2
Parallels Workstation VMM Main driver started.
(65: coreservicesd)tfp: failed on 0:
(65: coreservicesd)tfp: failed on 0:
(65: coreservicesd)tfp: failed on 0:
VT-x is supported (reported by CPUID) and can be used
VT-x is supported (reported by CPUID) and can be used
(65: coreservicesd)tfp: failed on 0:
netsmb_dev: loaded
en1 duplicate IP address 10.0.1.253 sent from address 00:14:51:ee:bc:25
AppleRAID: terminating set "RAID Set" (70C233E9-5FC3-4C70-AF18-2489CC76612C).
VT-x is supported (reported by CPUID) and can be used

This is on a mac mini and Parallels no longer gives the error message when vt-x is enabled :-)

thingi

[ingomar]

For the record:
Serial YM6087PJU36
ROM: MM11.0055.B02
Prod: Wk8/2006
vtx-check reports VT-x is supported (reported by CPUID), but locked in MSR and can't be used

[roscoe13]

I should note mine also states its supported, and Parallels runs fine with VT-x. When the VM is running and if I do an Parallels Workstation->About Parallels Workstation it states "Virtualization mode: Intel VT-x"

That means it's running I would think. Virtual machine seems quite fast even on my mini.

on my core duo mini, with MM11.0055.B02, SN YM608R0VU36, vtx-check gives me "VT-x is supported (reported by CPUID) and can be used", but Parallels Workstation->About Parallels Workstation gives me "Virtualization mode: Software mode 0"

Of course, I can't get it to boot from a real CD or a CD image, so it's all kind of meaningless to me at this point anyway...

Using build 1658.24

Peace

[djyod]

Here is the source for a kernel extension that can test whether VT-x is present on the processor and whether or not it can be used:

http://das.doit.wisc.edu/misc/vtx-check.zip

To use:

- Unpack the archive
- Go into the vtx-check directory and type "make" (requires that the Developer Tools have been installed)
- Load the kext with "sudo kextload MacOS/vtxcheck.kext"
- Look at "dmesg" for details; you should see a message indicating whether or not VT-x can be used on your system

It would be good if people could try this with their Mac mini and report back WITH YOUR SERIAL NUMBER:

Confirmed working:

- iMac (Core Duo) (all models)
- MacBook Pro (Core Duo) (all models)

- Mac mini (Core Duo) (firmware: MM11.0055.B02, serial: YM60935SU39)
- Mac mini (Core Duo) (firmware: MM11.0055.B02, serial: YM608JEJxxx)

Confirmed NOT working:

- Mac mini (Core Duo) (firmware: MM11.004B.B00, serial: YM608QS0U36)
- Mac mini (Core Duo) (firmware: MM11.0055.B02, serial: YM608QS0U36)
- Mac mini (Core Duo) (firmware: MM11.004B.B00, serial: YM6092JZVJN)
- Mac mini (Core Duo) (firmware: MM11.0055.B02, serial: YM6092JZVJN)

To be tested:

- Mac mini (Core Duo) before Mac mini (early 2006) Firmware Update 1.0 (firmware: MM11.004B.B00)
- Mac mini (Core Duo) after Mac mini (early 2006) Firmware Update 1.0 (firmware MM11.0055.B02)
- Mac mini (Core Solo) before Mac mini (early 2006) Firmware Update 1.0 (firmware MM11.004B.B00)
- Mac mini (Core Solo) after Mac mini (early 2006) Firmware Update 1.0 (firmware MM11.0055.B02)

Thanks!

UPDATE:

It's looking like it's not as clear cut as models here, since we have at least one person with a Mac mini Core Duo that DOES have VT enabled. I'm guessing it was an issue that got caught, and newer Core Duo Mac minis have VT enabled.

Would it possible to give some detail directions on using this test? I am relatively new to the Mac sene and would love a detailed step by step......

Thanks for all the effort!

[NoBackUp]

So PVm states

License information:
Status:
---
Product ID:
00005-00013361-0004
Validity period:
April 6, 2006 - May 6, 2006
Primary OS(es):
Mac OS X
Terminal Services:
no

Virtualization mode: Intel VT-x
Remote client off
session:

(But Had to start the Guest OS to Get This !!!)


And About this mac..

Machine Name: Mac mini
Machine Model: Macmini1,1
CPU Type: Intel Core Duo
Number Of Cores: 2
CPU Speed: 1.66 GHz
L2 Cache (shared): 2 MB
Memory: 1.25 GB
Bus Speed: 667 MHz
Boot ROM Version: MM11.0055.B02
Serial Number: YM608G~~~~~
SMC Version: 1.3f2

If I use BootCamp/XP-Native i was using a tool from Intel (http://www.intel.com/support/processors/tools/piu/sb/CS-014921.htm


and it reports..


Intel(R) Processor Identification Utility
Version: 2.8.20060328
Time Stamp: 2006/04/09 01:10:54
Number of processors in system: 1
Current processor: #1
Processor Name: Intel(R) Core(TM) Duo CPU T2300 @ 1.66GHz
Type: 0
Family: 6
Model: E
Stepping: 8
Revision: 39
L1 Instruction Cache: 32 KB
L1 Data Cache: 32 KB
L2 Cache: 2 MB
Packaging: µFCPGA/µFCBGA
EIST: Yes
MMX(TM): Yes
SIMD: Yes
SIMD2: Yes
SIMD3: Yes
Enhanced Halt State: No
Execute Disable Bit: Yes
Hyper-Threading Technology: No
Intel(R) Extended Memory 64 Technology: No
Intel(R) Virtualization Technology: Yes
Expected Processor Frequency: 1.66 GHz
Reported Processor Frequency: 1.66 GHz
Expected System Bus Frequency: 667 MHz
Reported System Bus Frequency: 667 MHz
************************************************** ***********

so where do we go from here ?

[gnujon]

Hi,

When I tried Beta 1 of Parallels Workstation on my Core Duo Mac Mini yesterday, I was getting that error message stating that the CPU supports VT-x but that it has been disabled in the system BIOS.

Today I downloaded Beta 2 (build 1658.30 8-Apr-2006) and now I no longer get the error message and the VT-x mode seems to be working.

In the about box I see this:
Virtualization mode: Intel VT-x

And your vtx-check kext gives me this:
VT-x is supported (reported by CPUID) and can be used

Here are the details of my system:

Machine Name: Mac mini
Machine Model: Macmini1,1
CPU Type: Intel Core Duo
Number Of Cores: 2
CPU Speed: 1.66 GHz
L2 Cache (shared): 2 MB
Memory: 512 MB
Bus Speed: 667 MHz
Boot ROM Version: MM11.0055.B02
Serial Number: YM608KNPU36
SMC Version: 1.3f2

Thanks.

[djyod]

So when you install Beta 2, is it a complete new reinstall and do you have to reinstall windows again or does it just do an update to Workstation?

Thanks,

[Scott Willsey]

It's an update. Just download the dmg, run the package installer, and have fun.

[pojo]

What is weird, is that the first time I ran 2.1 beta2, it didn't show that warning that VT wasn't enabled. But then it crashed (hard, got a nice gray screen informing me to reboot) and after that it gave me the error message each time I wanted to use it.

Anyway, I ran the little test program and it says that it's not enabled, so you can add this to your list :(

Confirmed NOT working:
- Mac mini (Core Duo) (firmware: MM11.004B.B00, serial: YM609081U39)
- Mac mini (Core Duo) (firmware: MM11.0055.B02, serial: YM609081U39)

[Alf]

Hi:

Installed the beta yesterday, 2.1.1658.24 April 4

Also my mini is:

Machine Name: Mac mini
Machine Model: Macmini1,1
CPU Type: Intel Core Duo
Number Of Cores: 2
CPU Speed: 1.66 GHz
L2 Cache (shared): 2 MB
Memory: 1 GB
Bus Speed: 667 MHz
Boot ROM Version: MM11.0055.B02
Serial Number: YM60849AU36
SMC Version: 1.3f2

Before I started the download for Parallels, I did 10.4.6 update and new Firmware BIOS update from apple.

All day yesterday, beta was working but got VT-x is disabled.

This morning did a shutdown by mistake with Parallels running, First startup gave me a gray screen and second startup booted fine, now VT-x is working fine.

Very strange behaviour, but happy that its working ok.

I notice missing features and some minor annoyance bugs, but overall I love it. Thanks very much, the forum is a wealth of info, thanks again.

There is a pre-order website, $39, I just ordered! Now want to buy a new imac, ha!

Alf

[whomikejones]

Not working here, FYI:

Serial: YM608HV8U36
Boot ROM: MM11.0055.B02

[pojo]

This is *very* odd. Yesterday, when I ran vtx-check, it stated that vtx was disabled. Now, for some reason, it's enabled???

The only difference that I can see in dmesg is this:

Parallels Workstation Hypervisor started.
Parallels Workstation VMM Main driver started.
System Sleep
Enabling XMM register save/restore and SSE/SSE2 opcodes
Started CPU 01
System Wake
USB caused wake event (EHCI)
AppleYukon - en0 link active, 1000-Mbit, full duplex, symmetric flow control enabled
VT-x is supported (reported by CPUID) and can be used

Does making the mini sleep and then wake up again enable VT-x? I'm installing Ubuntu right now and it seems to be working fine. Parallels reports that it is using virtualization too.

--pojo

[jase]

Does making the mini sleep and then wake up again enable VT-x? I'm installing Ubuntu right now and it seems to be working fine. Parallels reports that it is using virtualization too.

--pojo

Great catch!

I just put mine to sleep, and after waking it up, I can confirm that I'm seeing the same results you are. VT-x was locked in MSR on my Mini, but after sleeping, it's reported as working both with vtx-check and Parallels. :D

[aplnub]

10.4.6
Firmware Update
PW 2.1.1658.30 Beta

No VT-x hardware support message.

intel Mini s/n: YM608SHMU36

The sleep trick does not work and I can't get it to recognize a ISO image or my CD/DVD drive.

[daveschroeder]

Ok, this is really strange...VT is now enabled on a Mac mini it *wasn't* previously enabled on, and this was without doing any sleep tricks. In fact, I now can't get it to report that it's *disabled*. I can't see any rhyme or reason as to why this could be happening...

[metfoo]

with beta 1, i was enabled. With beta 2, i was software only. I will try the sleep trick at home

[dusty]

Just found this thread.

Did the firmware update before trying for the first time yesterday to run parellels on my mini dual core. At first I was locked. Then I went to sleep for the first time and afterwords, I now have
VT-x is supported (reported by CPUID) and can be used.

??

[CraigF]

This is the craziest thread ever.

I wish I had a Core Duo Mini just to try this on. :p

[ctrl+alt+del]

well, on my Mini, i installed directly beta 2. The Mini is brand new, and the Firmware Updater says it does not need any update.

Anyway, XP runs fine in Parallels, and the VT was enabled (well, i guess it was as Parallels did not say anything). Then i had two computer hangs in a row trying to insert a CD in the drive while running the VM (the second one beeing a short black screen followed by a direct restart.

Since then, i have this VT disabled message showing (and vtx-check tells me it's indeed disabled).

ROM : MM11.004B.B00
Serial : YM6092U4U36
Version SMC : 1.3f2

[Todd Woodward]

Apr 11 11:40:41 administrators-computer kernel[0]: VT-x is supported (reported by CPUID), but locked in MSR and can't be used

Machine Name: Mac mini
Machine Model: Macmini1,1
CPU Type: Intel Core Duo
Number Of Cores: 2
CPU Speed: 1.66 GHz
L2 Cache (shared): 2 MB
Memory: 512 MB
Bus Speed: 667 MHz
Boot ROM Version: MM11.0055.B02
Serial Number: YM6098B3U36

[mattham]

Well I can also account to the strange things going on.

Mac MINI core duo 1.66
ym6133p2u36
10.4.6
latest firmware & beta 2
(all DL yesterday - brand new mini)

When I first installed Parallels I got the "not supported" notice but went ahead and installed anyway - then found & read this thread.

I let my mac go to sleep & woke it up. Still got the "not supported" warning on startup but noticed that it was using VT-x when windows got up & running. then it became very unstable & crashed my mini (total reset - no kernel panic or any thing) I gave up & went to bed (4am :-D - I left the mac running).
When i woke it up this morning & tried it - no "disabled" warning - booted straight into windows & is running stable.

Hope this helps (although i'm sure it wont)

Matt :-)

PS with the sleep thing - I first tried putting it to sleep with the power button & this didn't seem to make any difference, it wasnt until I let it go to sleep by itself that things started to happen.

[aplnub]

So, what is the official word from Parallels on this at this point? Surely they are looking into this?

I will let my mac go to sleep on it's own tomorrow and give that shot. There is still hope!!

[JakePratt]

mattham, my experience is much like yours. I have seen VT both on and off. One time was after a hard crash. Since then, it now only wants to do Software Mode 2....whatever that is.

[metfoo]

so what are the different modes?

I have software mode 0

[Andrew @ Parallels]

Hi All!

Thank you very much for helping us with this issue! We are filed a bug about Intel VT-x behavior on Mac Minis on bugreport.apple.com and we will keep you posted about its status.

[Jasper]

Just tried a little experiment....

bought a new mac mini and upgraded it to 10.4.6 through Software update, installed Parallels Beta 2, and set up my XP session. Vt-x mode was off all through this. Updated firmware, tried the sleep trick, still running in software.

Then I fired up my XP session in Parallels, waited until XP had fully loaded and had no disk activity, then I yanked the power cable from the mini. After powering up and going back into my XP session, I now have VT-x running!

caveat emptor, YMMV, I am not responsible for damage to your Mac, etc.

[n4khq]

Solo core mac Mini. 1 GB memory. I moved a MacBook pro image (winxp folder) and VT-x was working. Did an 10.4.6 update and sometime after the update, I start getting the message Firmware lockout of VT-x. XP was much slower.

Needed a bigger drive so I reinstalled on the MBP and copied the winxp folder to the mini mac. I now have VT-x working again.

[dunn.hatani]

Machine Name: Mac mini
Machine Model: Macmini1,1
CPU Type: Intel Core Solo
Number Of Cores: 1
CPU Speed: 1.5 GHz
Memory: 512 MB
Bus Speed: 667 MHz
Boot ROM Version: MM11.0055.B02
Serial Number: YM61204PU38
SMC Version: 1.3f2
L2 Cache: 2 MB

I started with PW 2.1 beta 1 before the firmware update but after 10.4.6..."VT-x is supported (reported by CPUID), but locked in MSR and can't be used" were results from VTX-check. I got the same results after the firmware update. I just installed beta 2 last night and paralles said that it was still using software 0 I think. Just installed beta3 just now. I wasn't thinking because I wastrying to install beta3 while xp installer was running in the VM. Needless to say I got the gray crash message saying that I need to restart my computer. So I did and then re-ran the beta3 installer. I was reading the forums when XP installer was going again so I went to the apple menu and put my machine to sleep. When it woke up I ran vtx-check and it reports enabled vt-x. Of course I didn't check before I put the machine to sleep. Anyway I hope this helps. I've got a feeling that it might have something to do with specific serials.
Nathan

[Dez]

installed Parallels Beta 2, and set up my XP session. Vt-x mode was off all through this. Updated firmware, tried the sleep trick, still running in software.

Then I fired up my XP session in Parallels, waited until XP had fully loaded and had no disk activity, then I yanked the power cable from the mini. After powering up and going back into my XP session, I now have VT-x running!

This worked for me, too! I think my timeline is something like this:

beta 1, worked with VT-X on [empirically; I didn't know then to look to make sure, but subsequently when I knew it was off, it was slower, so I'm going to assume that at this point it was on]
tried to install beta 2. The installer went into an infinite loop, and was cramming my system.log with messages like the below at an alarming rate, so I had to force quite the installer:
Apr 9 11:42:11 imini kernel[0]: Error:Unsupported il() call (0xc0105401) to hypervisor (hypervisor.c:122)
Apr 9 11:42:11 imini kernel[0]: Error:Unsupported ioctl() call (0xc0105401) to hypervisor (hypervisor.c:122)
Apr 9 11:42:11 imini kernel[0]: ctl() call (0xc0105401) to hypervisor (hypervisor.c:122)
Apr 9 11:42:11 imini kernel[0]: or:Unsupported ioctl() call (0xc0105401) to hypervisor (hypervisor.c:122)
Apr 9 11:42:11 imini kernel[0]: or:Unsupported ioctl() call (0xc0105401) to hypervisor (hypervisor.c:122)
Apr 9 11:42:11 imini kernel[0]: Error:Unsupported ioctl() call (0xc0105) to hypervisor (hypervisor.c:122)
Apr 9 11:42:11 imini kernel[0]: Error:Unsupported ioctl() call (0xc0101) to hypervisor (hypervisor.c:122)
Apr 9 11:42:11 imini kernel[0]: Error:Unsupported ioctl() call (0xc0105401) to hypisor (hypervisor.c:122)
Apr 9 11:42:11 imini kernel[0]: Error:Unsupport)ll (0xc0105401) to hypervisor (hypervisor.c:122)
Apr 9 11:42:11 imini kernel[0]: Error:Unsupported ioctl() call (0xc0105401) to hyvisor (hypervisor.c:122)
Apr 9 11:42:11 imini kernel[0]: Error:Unsupported ioctl() call (0xc0105401) to hypervisor (hypervisor.c:122)
retrying a few times got similar problems, so I removed all references to Parallels, and installed again. This time it went without a hitch
my initial attempts to run beta 2 were met with various crashes; panics; hung system; spontaneous reboot. Eventually I got it running smoothly. At this point I noticed it was obviously slower than beta 1 [albeit still perfectly fast enough for my requirements]. I had noticed the 'VT-X disabled by BIOS' message, but I assumed that that was just a new message for beta 2... after all, I figured why would something in the BIOS suddenly not work!
eventually came to the conclusion that it wasn't just a new message, and installed the Mac mini firmware upgrade, expecting that to make VT-X work, and of course it didn't
installed beta 3, thinking maybe that will fix it, but of course that didn't either. Then I found this forum!
I shutdown the VM, then Parallels and all other apps, and pulled the powercord, and indeed VT-X is now functioning again, and performance is back to how it was when I first tried beta 1

I am speculating, but I wonder if the crashes I had with beta 2 caused VT-X to be disabled somehow, and that the Mac's firmware is not correctly resetting it, even after a soft restart. I would think that just shutting down and pulling power then would have also worked, rather than risking pulling the power while the Mac is still running.

[Djoh]

Is there anyone here who got the Parallels Workstation to run natively (with u-processor support) on a miniMac w/ Core Solo? (even if you had to use the weird tricks)

I ask simply because I want the cheapest Windows-on-Mac system. As some people had mentioned before, restarting just to use one or two Windows apps sounds really irritating, this software sounds like it is really good when it's got u-proc. support! I was even considering looking for one of those old "Orange-PC" cards for my G4 tower to make Virtual PC run faster!

Thanks in advance for any responses.

[Scott Willsey]

Is there anyone here who got the Parallels Workstation to run natively (with u-processor support) on a miniMac w/ Core Solo? (even if you had to use the weird tricks)


I don't think the Core Solo supports VT-x. I believe only the dual core cpus do. Also there's some confusion based on what you read where that the Yonah based Core Duo is not supposed to support VT-x, but it clearly does, or at least some steppings of it do. Certainly Merom based Core Duo cpus will, and in my experience the current Core Duo does as well.

[n4khq]

Is there anyone here who got the Parallels Workstation to run natively (with u-processor support) on a miniMac w/ Core Solo? (even if you had to use the weird tricks)

Thanks in advance for any responses.

I have gotten VT-x working several times but after an upgrade on panic I lose it. Three time I have copied the image from my MBP and it start working on the Core Solo.

[Scott Willsey]

I have gotten VT-x working several times but after an upgrade on panic I lose it. Three time I have copied the image from my MBP and it start working on the Core Solo.

Hmm. So much for my theory. I dug around on Intel's web site and found a spec sheet for both Core Duo and Core Solo and it mentions Intel Virtualization without distinguishing between the two so I guess Core Solo supports it.

[mattham]

i presume you guys have seen this thread

http://forum.parallels.com/thread577.html

Matt

[MacFanatic]

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!

[NoBackUp]

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 ?

[dr_lha]

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.

[NoBackUp]

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.

No Sir I think you are missing the point... I tried to MAKE my maschines report that VT-X was disabled :confused:

Thas why I redid the whole firmware issue.. to try and force it :eek:

How come its disabled by defualt on yours but iI cant get 2 other maschines to do the same...

How come I cant get mines to do what yours does although I tried it on 2 maschines bought 3 weeks apart on 2 different contents.. :cool:

I can boot both maschines and install the whole thing from scratch and it works...

I can boot it into native and the intel software tells me its enabled...

If my maschine and yours show different results, I boot mines with naked OS X (10.4.6) and it works, then as the OS & Parralles & the Firmware are the same... then somthing OTHER than the firmware is a miss here... pure logic..

So what else do you have loaded on your maschine ? (startup items, additional software) partiotions, os's) perhaps we should rule out everything else before calling wolf .. :)

[Djoh]

Don't forget there's LOTS of people whose miniMacs aren't working with VT-x support until they do one of these tricks, and the firmware has fixed it for people. It doesn't seem like there's much question about it being the firmware thing, mate. That, and it's not All miniMacs, just a seemingly random bunch of them. If yours works, then just let it work! You just happen to be quite lucky in having TWO machines without the firmware problem!

[NoBackUp]

Hi Djoh,

Thats why I am trying to get to the bottom of this as I have 2 Boxes and they dont have this issue

In Such situations its a good idea to try and find out what is different on the Boxes, including looking at

What OS's are installed
What OS patches are loaded
Do they Have Bottcamp installed
Did they have XOM Installed


Who did they find out if VT-X is enabled (PVM, or someother thing)..

Just writing here to the Par - Team its broken.. withouth giving them something to be getting on with ant real helpfull same as people just Jumping on the Band wagon "The Firmware..."

[dr_lha]

No Sir I think you are missing the point... I tried to MAKE my maschines report that VT-X was disabled :confused:

Thas why I redid the whole firmware issue.. to try and force it :eek:

How come its disabled by defualt on yours but iI cant get 2 other maschines to do the same...

How come I cant get mines to do what yours does although I tried it on 2 maschines bought 3 weeks apart on 2 different contents.. :cool:

I can boot both maschines and install the whole thing from scratch and it works...

I can boot it into native and the intel software tells me its enabled...

If my maschine and yours show different results, I boot mines with naked OS X (10.4.6) and it works, then as the OS & Parralles & the Firmware are the same... then somthing OTHER than the firmware is a miss here... pure logic..

So what else do you have loaded on your maschine ? (startup items, additional software) partiotions, os's) perhaps we should rule out everything else before calling wolf .. :)

Well I have a mini Core Solo if that helps. However I don't believe that people on here have been reporting 100% sucess with the Core Duo and 100% failure with the mini Core Solo. It comes back to the point that 2 machines does not a accurate sample make, regardless of what you tried to force them to do.

[NoBackUp]

Then correct me if I am wrong BUT the Core Solo does not support VT-X, according to the featurs list on the Intel web page, therefore its not a FIRWARE issue preventing VT-X from being enabled (Core Solo) its the Processor it's self...

http://www.intel.com/products/processor_number/proc_info_table.pdf

Page 3 ... it states that the Core Solo DOES NOT support VT-X...

So I dont really understand how you or the others can expect it to work in the First place, I have read here that PVM then uses a software emulation to "Share" the single core...

So me thinks if on Core Solo's that PVM is reporting that VT-X is enabled sometimes that its self is the "BUG" and not the maschine..

and that the TRICKS people are using are infact just causing this BUG to surface

[Andrew @ Parallels]

Please check VT detection utility posted in this thread by Dave Shroeder (http://forum.parallels.com/thread85-3.html). It includes sources and it is very simple:

1. It checks VT-x feature in CPUID.
2. It checks is it unlocked in IA32_FEATURE_CONTROL MSR.

So far we can see that 1) reports that VT-x existed on all known Mac Minis (including Core Solo). At the same time 2) is random - on some Mac boxes it is locked on some unlocked. And it could be changed using some tricks (like sleep trick posted here).

It looks like boot code on Mini could lock VT-x in some random situations.

[NoBackUp]

Andrew,

Hiow can it exist if INTEL states that it does not on the CORE-SOLO ?

[Andrew @ Parallels]

NoBackUp,

We will investigate this issue and keep your informed.

[Scott Willsey]

Andrew,

Hiow can it exist if INTEL states that it does not on the CORE-SOLO ?

Intel's web site is a little confusing on this. Awhile back, I dug around on Intel's web site and found a spec sheet for both Core Duo and Core Solo and it mentions Intel Virtualization without distinguishing between the two. However now I can't figure out where I found it.

[fibtastic]

root@mactv:~/Desktop/vtx-check#kextload MacOS/vtxcheck.kext
kextload: extension /Users/billm/Desktop/vtx-check/MacOS/vtxcheck.kext is not authentic (check ownership and permissions)

everything is root:wheel 755 on a core duo mac mini. What am I doing wrong?

[dr_lha]

NoBackup and presumably Intel are wrong about the Core Solo not supporting VT-x.

"VT-x is supported (reported by CPUID) and can be used".

On a Mac mini Core Solo 1.5Ghz with MM11.0055.B02 firmware and G8610XXXXXX serial number.

[Djoh]

Dr_lha:
Right, that's exactly why I asked in the first place, it sounded like both Solos and Duos support the function and Intel disabling it seems to mean locking it through the firmware (although it looks like it didn't get locked in All the releases), which has been proven to be easily circumvented. [also, note that the "Intel Core Solo" in that data sheet posted above runs at 1.66GHz, not the same u-proc. as in the miniMac w/Core Solo]
However, the fact that it takes a trick to get it working correctly on half of the miniMacs is enough, I'm sure, to achieve the intended goal of getting people who want full Windows support to buy a higher-end mac. On the other hand, Apple says nothing about the miniMacs not fully supporting Windows via the Intel u-proc, so it may be more likely that it is a mistake (or that they locked a bunch and then changed their minds...)

Either way, I'm buying myself the cheapest Dual-OS option available on the market today: The Mac Mini Core Solo w/ Parallel's Workstation.

[stompbox]

I have a Core Solo and believe me, it does support VT. In fact, right from the beginning, this software informed me it was supported but locked by firmware. After running the "hack" it was enabled and there is a vast difference between the software-only mode (before) and the hardware mode (after running hack).

It's a very, very cool machine now. Remember, you can also pop out the CPU and put in a dual core after the price drop in May.

[NoBackUp]

NoBackup and presumably Intel are wrong about the Core Solo not supporting VT-x.

"VT-x is supported (reported by CPUID) and can be used".

On a Mac mini Core Solo 1.5Ghz with MM11.0055.B02 firmware and G8610XXXXXX serial number.


You are a Joke.. Intel is wrong its thier CPU..falls off chair... what a dum a...

Its thier docs that say no !!!...

[Djoh]

I just bought a MiniMac Solo, specifically for running Parallel's Workstation & Windows XP.

It works great, supports VT-X, all is well! I updated all software & firmware (v. 1.0.1 Mac Mini Firmware Updater) before installing anything at all. So I actually didn't need any hacks or tricks (just lucky?).

I posted a screenshot of it somewhere on this forum, click my username and check my other posts if you're interested.

Relax, Mr. Backup, it's just a computer...

[keirnna]

VT-x is supported (reported by CPUID) and can be used

Hardware Overview:

Machine Name: Mac mini
Machine Model: Macmini1,1
CPU Type: Intel Core Duo
Number Of Cores: 2
CPU Speed: 1.66 GHz
L2 Cache (shared): 2 MB
Memory: 2 GB
Bus Speed: 667 MHz
Boot ROM Version: MM11.0055.B02
Serial Number: YM608LJ6U36
SMC Version: 1.3f2

[mettmann]

Hello -

do we have any status from apple on this issue?

by the way - thanks Dave for the code - I'm a complete noob to compiling, Developer Tools is already loaded on my duo core mini - I just need to know how to "make" the checker run within Xcode.. (yep, step by step)

any help would be appreciated!

[keirnna]

Hello -

do we have any status from apple on this issue?

by the way - thanks Dave for the code - I'm a complete noob to compiling, Developer Tools is already loaded on my duo core mini - I just need to know how to "make" the checker run within Xcode.. (yep, step by step)

any help would be appreciated!

These are step by step already, but let me try to clairify...

Here is the source for a kernel extension that can test whether VT-x is present on the processor and whether or not it can be used:

http://das.doit.wisc.edu/misc/vtx-check.zip

To use:

- Unpack the archive
- Go into the vtx-check directory and type "make" (requires that the Developer Tools have been installed)
- Load the kext with "sudo kextload MacOS/vtxcheck.kext"
- Look at "dmesg" for details; you should see a message indicating whether or not VT-x can be used on your system

It would be good if people could try this with their Mac mini and report back WITH YOUR SERIAL NUMBER:

Download the file
double click the file to unzip it with stuff it (have the file on your desktop)
now open the terminal via: Applications>Utilities>Terminal
Type exactly like this:
cd Desktop/vtx-check/
make
sudo kextload MacOS/vtxcheck.kext
sudo dmesg

[mettmann]

Thanks!

I presumed that I needed to click on the unzipped vtx content (which then opened up the Xcode app..)

worked great - here's my info..
(already updated firmware to 1.01)

Hardware Overview:

Machine Name: Mac mini
Machine Model: Macmini1,1
CPU Type: Intel Core Duo
Number Of Cores: 2
CPU Speed: 1.66 GHz
L2 Cache (shared): 2 MB
Memory: 1 GB
Bus Speed: 667 MHz
Boot ROM Version: MM11.0055.B03
Serial Number: YM6141KNU39
SMC Version: 1.3f2
VT-x is supported (reported by CPUID) and can be used

[iocomposer]

Out of curiosity, what is the affect of PW running without VT-x enabled? Is it a significant speed dump?

[James Wu]

Out of curiosity, what is the affect of PW running without VT-x enabled? Is it a significant speed dump?

Yes. I'd say 75-80% slower.

James

[thebryceman]

Today I changed the network connection on my Mini Core Duo from Airport to Ethernet and noticed that VT-X became enabled again!!!

The Mac Mini was plugged into Ethernet a few days ago and VT-X was working. It seems VT-X became disabled (pop up error on Parallels startup) yesterday when I turned on and changed to an Airport connection (unplugging the ethernet cable too). This happened both before and after the latest Apple Firmware update.

I will try again tomorrow and report... I have not done any other hacks or changes. Can others confirm this?

[keirnna]

Today I changed the network connection on my Mini Core Duo from Airport to Ethernet and noticed that VT-X became enabled again!!!

The Mac Mini was plugged into Ethernet a few days ago and VT-X was working. It seems VT-X became disabled (pop up error on Parallels startup) yesterday when I turned on and changed to an Airport connection (unplugging the ethernet cable too). This happened both before and after the latest Apple Firmware update.

I will try again tomorrow and report... I have not done any other hacks or changes. Can others confirm this?

My VT-X works and I connect via Airport Extreme...

[James Wu]

Yes. I'd say 75-80% slower.

James

Doh!

I meant to say the speed at which it runs without hardware support is about 75-80% of what what the speed would be with hardware support, which would make it 20-25% slower...

James

[iocomposer]

- Go into the vtx-check directory and type "make" (requires that the Developer Tools have been installed)

Is there an easier way to determine if VT-x is enabled without having to install Developer Tools?

[crchad]

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.

[Andrew @ Parallels]

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?

[crchad]

Yes I have the latest firmware. But I didn't install it until after the problem manifested. Could that be relevant?

[Andrew @ Parallels]

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.

[crchad]

Interesting...Today it's working ok again. I guess the firmware update and a couple of extra reboots did the trick.

[thorsten]

Hardware Overview:

Machine Name: Mac mini
Machine Model: Macmini1,1
CPU Type: Intel Core Duo
Number Of Cores: 2
CPU Speed: 1.66 GHz
L2 Cache (shared): 2 MB
Memory: 1.25 GB
Bus Speed: 667 MHz
Boot ROM Version: MM11.004B.B00
Serial Number: YM6094QPU36
SMC Version: 1.3f4

daveschroeder's test returned the following:
VT-x is supported (reported by CPUID), but locked in MSR and can't be used

[spride]

Mac Mini Cored Duo 1.66 GHz
Boot Rom MM11.0048.800
Serial # G86221VTU39
SMC version 1.3f4


VT-x is supported (reported by CPUID), but locked in MSR and can't be used
(100: coreservicesd)tfp: failed on 0:

[eon]

I've been monitoring this thread for about a month, since I got my Mac Mini and started using Parallels, and I've yet to be able to get Parallels working in VT-X mode. I've got the latest firmware, I've tried the "sleep" trick, I've done everything except the trick described in another thread.

My Mac Mini info is as follows:
Machine Name: Mac mini
Machine Model: Macmini1,1
CPU Type: Intel Core Duo
Number Of Cores: 2
CPU Speed: 1.66 GHz
L2 Cache (shared): 2 MB
Memory: 2 GB
Bus Speed: 667 MHz
Boot ROM Version: MM11.0055.B03
Serial Number: G86167Q2U36
SMC Version: 1.3f4

The output from dmseg is as follows:
Parallels Workstation Hypervisor started.
Parallels Workstation VMM Main driver started.
com_parallels_kext_Pvsvnic: Ethernet address 00:01:23:45:67:89
netsmb_dev: loaded
smbfs_smb_qfsattr: (fyi) share 'NTFS', attr 0x700ff, maxfilename 255
smbfs_smb_qfsattr: (fyi) share 'NTFS', attr 0x700ff, maxfilename 255
VT-x is supported (reported by CPUID), but locked in MSR and can't be used

This hasn't been a huge issue for me, as Parallels is still running Windows faster on my Mac than it was on my desktop PC, so it's been very usable. I just hate knowing that there's more out there and I can't get to it....

-Eriq

[Andrew @ Parallels]

Thanks for reporting eon - we will investigate this.

BTW: Did you check About->More info->Virtualization mode? Did show Software mode when VM is running?

[cybermice]

I also had a problem with VT-x not being enabled (Mac Mini Core Duo received & updated the day 10.4.7 came out). Part of the update was the Mac mini SMC Firmware Update.

I installed Parallels after the updates and restart and got the following message every time:

Your CPU supports Intel Virtualization Technology (VT-x) but it is currently disabled (locked by firmware). Virtual machine will be started without VT-x support (in software virtualization mode).

I noticed that the default Parallels folder (inside Applications) was locked. Hmm. I copied Parallels to the desktop and ran it from there. Same thing.

When I ran it earlier this evening... from the Parallels folder... no message.

Could it have somehing to do with permissions? I haven't looked around to see if the Parallels folder should be locked, but haven't done anything else relating to Parallels since the initial Mac Mini update and Parallels install.

Just a thought. Haven't repaired permissions yet...

[Scott.M.]

I've had all the problems with the mac-mini not supporting virtualisation until i went to

http://www.apple.com/support/downloads/macminiearly2006smcfirmwareupdate.html

and manually updated the firmware regardless, software update not telling me to install the update.

My mini was purchased in June, however the Early 2006 update worked fine.

[cybermice]

After adding a KVM switch to my setup, I started up Parallels only to find that the problem returned. Repairing permissions had no effect. Changing the permissions of the Parallels folder to what most applications are set to... had no effect. Bummer...

[echinoderm]

Just FYI to file under it didn't work, but now it does for VT-x on the Mac Mini.

I bought my Mini in March. Have been keeping it up to date and following Parallels to look for the GA launch. It happened, I bought it, and here's whats happened since last Friday.

1) Went to Software Update and updated everything to current. 10.4.7, iTunes, QT...then restarted.
2) Installed Parallels and immediately got the dreaded 'locked in firmware' VT-x message every time I started up a VM.
3) Looked around on this forum and saw the recent post about the 1.0.1 upgrade and the SMC firmware update. I checked Info and had the following:

Machine Name: Mac mini
Machine Model: Macmini1,1
CPU Type: Intel Core Duo
Number Of Cores: 2
CPU Speed: 1.66 GHz
L2 Cache (shared): 2 MB
Memory: 2 GB
Bus Speed: 667 MHz
Boot ROM Version: MM11.004B.B00
Serial Number: YM6120BTU39
SMC Version: 1.3f4

4) Since the SMC was up to date, I then went out and got the early 2006 1.0.1 firmware update and applied it.
5) After the power on that applied the firmware, still no go. VT-x was disabled when starting my WinXP VM per the warning message.
6) Shut down, then powered up again. VT-x still disabled.
7) At this point, I went to bed, leaving the Mini up. Sleep mode kicked in, and in the morning I woke her up and bingo! VT-x was working! No warning message. Here's the way I look now:

Machine Name: Mac mini
Machine Model: Macmini1,1
CPU Type: Intel Core Duo
Number Of Cores: 2
CPU Speed: 1.66 GHz
L2 Cache (shared): 2 MB
Memory: 2 GB
Bus Speed: 667 MHz
Boot ROM Version: MM11.0055.B03
Serial Number: YM6120BTU39
SMC Version: 1.3f4

Confirmed thru the Parallels app he also thought VT-x was working.

Don't know if the above helps anyone, but a couple of observations.

- The SMC firmware went on via Software Update a while ago (month or two ago...)
- The 1.0.1 firmware did not, and only after I went and got it and applied it yesterday.
- I've seen people talk about Sleep mode...since that seemed to be involved here, I wonder if it isn't in the equation somehow.

[cybermice]

Thanks! It worked for myself as well.

It's amazing how these things are so much like people. All it needed to work correctly was a little nap...

[echinoderm]

Excellent! Glad it helped!

:D

[cybermice]

After my success with Parallels, I tried to install the Boot Camp Beta. After all, I had what I thought was a completely updated Mini (including the Mac mini SMC Firmware Update). However...

... when I tried to run the Boot Camp Assistant Beta, I was informed that my firmware was out of date. Apparently, the ROM was out of date (this is what the "1.0.1" update is all about). Now that the 2nd *firmware* update is out of the way, Windows is being installed...

I'll have to see what effect this has on Parallels. I did set my Mini to never sleep in Preferences. I wonder if this is what was wrong (at least for the ROMs that I didn't know were out of date).

I'll have to see if I can NOT put it to sleep occasionally and get away with it.

[eon]

Thanks for reporting eon - we will investigate this.

BTW: Did you check About->More info->Virtualization mode? Did show Software mode when VM is running?

Yep, About->More Info->Virtualization Mode shows "Software Mode 2"

Otherwise, the product has been running very well. I'm impressed that it's actually running Windows and the few Windows apps I have to run better than my Dell desktop that I had been using.

Now if I could just get this pesky virtualization mode thing cleared up...

-Eriq

[cybermice]

This may sound strange, but have you run the Boot Camp Assistant Beta?

I know you're using Parallels, but I didn't find out that my Boot ROMs were out of date until I ran the program. My SMC firmware was up-to-date and listed in the Installed Updates section of Software Update. The Boot Camp Assistant Beta told me my firmware (Boot ROMs?) were out of date and when I updated the Boot ROMs, the Boot Camp Assistant Beta was able to run. I haven't had a problem with Parallels since.

Mac mini (early 2006) SMC Firmware Update [shows in Software Update]:
http://www.apple.com/support/downloads/macminiearly2006smcfirmwareupdate.html

Mac mini (early 2006) Firmware Update 1.0.1 [does NOT show in Software Update]:
http://www.apple.com/support/downloads/macminiearly2006firmwareupdate101.html

[mikeg]

I just got a Macmini and updated to 10.4.7 and the firmware to 1.3F4, loaded Parallels and get the VT-x disabled message...then no boot disk.

Sorry I paid my $50 up front...

[cybermice]

Select the 1st item in the Apple menu (About This Mac)

Click on the More Info... button

Is the Boot ROM version MM11.0055.B03?

If not, visit the following URL to read about the new Boot ROM version you may need:

http://www.apple.com/support/downloads/macminiearly2006firmwareupdate101.html

You can't tell if you have the updated Boot ROMs by using Software Update

Let me know whether or not this works for you

Cheers!

[ts77]

I tried that, upgraded the firmware and I still get the same error-message (vt-x included but disabled by bios) as before :(.

[mikeg]

Played around some more and found a way to get Windows XP Home installed and working, though I still get the firmware disabled message.

For others trying this here is what I did:

I restarted the process setting up a Win XP install this time, with no unusual settings other than defaults in the wizard. I set the boot to go from CDROM first rather than HD. Saved settings. Inserted the XP Home (Upgrade) CD. Clicked the green start triangle, and this time it started the install. At some point it asks to have you insert a valid Win 95 or Win 98 install disk (since this was an XP Home Upgrade disk). I needed to take control of the cursor (Ctrl-Alt) and used the disk icon at the lower part of the window to disconnect the CDROM. I could then see it on the desktop and eject it. I then inserted a Win 95 Install disk, and used that same icon to Connect it, clicked on the windows install window, and told it to proceed. Well that didn't work since it somehow didn't recognize my Win 95 Install disk that came with Virtual PC. So I proceeded to eject that one and inserted a Win 98 Upgrade disk and it accepted that. It then proceeded to nicely install XP Home. The time it projected was much more than it actually took...about 3x faster. After shutting down win xp, I then updated the VM to have more memory and to boot from HD first...saved then restarted with no issues. I used the Windows display control panel to set my screen size to a larger 1280x960. All seems to be functional, so I guess my next step is to find a virus program cheaply before this thing gets infected...heard the life is only 20 minutes without a windoz condom.

Just a start, but I am very impressed I got this far!

[kdawg]

I just want to chime in as well. When I first got my Mini and installed Parallels and WXP everything was working fine. Then the next day I got the VT-x error (capable but disabled in firmware). I had at this point updated everything with the Apple Software Update menu. However it did not update the firmware to v1.0.1 (MM11.0055.B03) so I downloaded that and installed it. Nothing, still says VT-x is disabled.

For the record the serial number of my Mini is G86180ZEU36 and the SMC firmware is 1.3f4.
WXP is XP Home (SP2) with all applicable Windows updates applied to that as well.

So is this an Apple thing or a Parallels thing? Anyone?

[cybermice]

Since updating my SMC firmware and Boot ROM, I haven't had a problem with the VT-x error. HOWEVER, I also now put my Mini to sleep at least 1x per day. Maybe the combination of new firmware AND sleep does the trick.

To check whether Parallels is in VT-x mode:

Parallels Desktop: About Parallels Desktop: More Info...
Virtualization Mode: Intel VT-x [if VT-x is working]

[kdawg]

I just want to chime in as well. When I first got my Mini and installed Parallels and WXP everything was working fine. Then the next day I got the VT-x error (capable but disabled in firmware). I had at this point updated everything with the Apple Software Update menu. However it did not update the firmware to v1.0.1 (MM11.0055.B03) so I downloaded that and installed it. Nothing, still says VT-x is disabled.

For the record the serial number of my Mini is G86180ZEU36 and the SMC firmware is 1.3f4.
WXP is XP Home (SP2) with all applicable Windows updates applied to that as well.

So is this an Apple thing or a Parallels thing? Anyone?


VT-x is working now but I haven't changed anything since my last post. What I did do, because I noticed some people mention it, is unplug my Mini for about 5 minutes to drain the power. Now Parallels Desktop for Mac seems to be working with VT-x, before and after sleep. Just wanted to pass it along. I'm thinking that after updating the Mini's firmware with v1.0.1 (MM11.0055.B03) you need to unplug it after for it to really take effect. Although Apple's firmware doesn't require you to unplug it.

[Calaban]

Had the same problems as previous mentioned here. Virtualization was enabled after install and then after reboot had software emulation. Followed this method:
http://forum.parallels.com/thread577.html
Problem solved! :)

Thanks Joshua for software patch and monoclast for the great instructions! :D

[monoclast]

I've seen a bunch of instructions here for doing this; but all of them seemed to leave out one or two crucial details. So I'll try to provide those who need it a more complete list of steps to get this done. Please refer to this thread for complete instructions showing how to enable VT-x permanently on your Intel Mac:

http://forums.parallels.com/thread3273.html (http://forums.parallels.com/thread3273.html)

[bergeron76]

I just experienced this _exact_ error on my Mac MINI (boot rom: MM11.004B.B00). I just upgraded my Ram from 512 to 2GB (for the purpose of running Parallels!). I just booted it up (without the cover on), and I got this VT-X error. At first, I was thinking this error was related to the RAM that I just installed, or that it was related to modifying my Mac Mini.

However - Last night, I disabled power save on it and this is the first time I've run Parallels since then. So it could be caused by disabling power save (entirely/Never) on the Mini.

Does this shed any light on things? Is there a fix for this?

[cybermice]

I had a very similar experience. I updated the SMC firmware & Boot ROMs and still had a problem. I may have had one of the two Energy Saver options set to something other than Never. Now, I still put my Mac Mini to sleep, but I do so manually. I leave both of the options in the panel on Never.

In summary:

1) SMC firmware update; 2) Boot ROM update; 3) Energy Saver panel set to Never; 4) Set the Mac Mini to sleep every day

[bergeron76]

I just got my mini a few weeks ago. It's boot rom version: MM11.004B.B00; smc version 1.3f4.

VT-x is supported (reported by CPUID), but locked in MSR and can't be used

macmini:/tmp/vtx-check root# sysctl machdep.cpu.features
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM SSE3 MON VMX EST TM2 TPR

[cybermice]

Your Boot ROM appears to be out of date:
http://www.apple.com/support/downloads/macminiearly2006firmwareupdate101.html
Current is MM11.0055.B03. I suggest updating to the latest version.

Also, you may want to change the Energy Saver panel settings to Never and put the Mini to sleep when not in use.

[adamjroth]

I was having the same problem with my Mac Pro -- then I put it to sleep (click the blue apple, 'Sleep'). Wake it up. Restart windows, and VTx is enabled.

[hchen]

- Mac mini (Core Solo) after Mac mini (late 2006) Firmware Update 1.x (firmware MM11_0055_08B)