iTunes 9.1 crashes on XP SP3 running on hosts w/o VT-x

[Ralph Schmieder]

Since a couple of versions, current iTunes versions crash shortly after starting on XP running within VirtualBox. This seems to be related to the fact that VT-x is not available on the host system. According to ​this forum post it can be replicated. My machine is Linux based and does not have VT-x available, iTunes crashes. The OP has it running on Windows and it shows the same behavior.

[Ralph Schmieder]

VBox.log

[Steve MacLaren]

I am running 3.2.4 r62467 with VT-x enabled (AMD-64 X2 processor). Since I upgraded from 3.1.6 using the same XP SP3 VM, I also cannot get iTunes 9.1 to start. How do I know if VT-x is actually functioning in my VM?

[Steve MacLaren]

Update: I just noticed the following line in my log: 00:00:01.044 HWACCM: No VT-x or AMD-V CPU extension found. Reason VERR_SVM_DISABLED So, I guess VT-x is no longer working in 3.2.4?

[Steve MacLaren]

One more update: Found the setting on my motherboard's bios for Virtualization. It was disabled, so I enabled it. Now I no longer get the "No VT-x or AMD-V CPU extension found" message, and iTunes 9.1 works again. Hope this helps-

[BelowSky]

@scram69 Actually no, that does not help. The report is specifically about NON VT-x system.
For example, you cannot run iTunes 9.1 with an AMD64 3700+ processor.

Please note, iTunes 9.1 runs without a problem on VMWare Player v3.
So, the problem is VirtualBox related, not iTunes related.

[Steve MacLaren]

Replying to BelowSky:

@scram69 Actually no, that does not help. The report is specifically about NON VT-x system.
For example, you cannot run iTunes 9.1 with an AMD64 3700+ processor.

Yes, I understand it is an issue for non-VT-x systems. My point was that it is not enough just to be using a VT-x capable processor; one must also ensure that the motherboard BIOS supports and is configured for hardware virtualization.

Please note, iTunes 9.1 runs without a problem on VMWare Player v3.
So, the problem is VirtualBox related, not iTunes related.

Actually, that's not correct. The reason I switched to VirtualBox was that iTunes would consistently lock up my XP vmware VM running on ubuntu host.

[BelowSky]

My config is different than yours. I use Windows 7 32bit host and Windows XP SP3 guest.

Maybe that's why VMWare and iTunes run flawlessly in my end. I have used that combination to update the firmware of my iPhone from v3.1.2 to v3.1.3 without a glitch.

[Matt]

I have an Intel Core2 Duo E7300 that doesn't have VT-x. I am getting this same issue. iTunes just crashes on startup with Virtualbox 3.2.4. I was able to get iTunes 9.0.0.70 to work, but anything newer than that crashes.

I'm considering downgrading my version of Virtualbox until this is fixed, but I'm not sure if that will help or just cause more issues.

[Matt]

I tried with 9.2 that just came out and that has the same issue. Hopefully VirtualBox will fix it.

[Marc Harter]

I am experience the same issue (and its more pressing since iOS4 requires 9.2), but I don't know if my system supports VT-x or not, I have it checked in the config but doesn't seem to help, anyway I can find out? (running Ubuntu 10.04 - VBox 3.2.4)

[Kurt Beyers]

Suffering from the same issue, the latest iTunes version I've managed to install on Window XP SP3 32bit is 9.0.2.25. The host OS is Ubuntu 10.04.

Upgraded yesterday the iPhone to IOS4, so I'm eager for a solution / workaround as well. I've enabled the Virtualization in the BIOS of my Compaq 6710b laptop too, but this didn't work?

[Luca]

Same issue for me

VBox 3.1.8 iTunes 9.2 (iPhone iOS 4) XP SP3 No VT-x capable processor

[krsoulsby]

Now that this issue will start to prevent users from upgrading to iOS4 on their iPhones is it possible to increase the priority.

BTW I am having the same problems with any version of itunes over 9.0 with windows 7 running on 3.2.4 VirtualBox and I also do not have a VT-x capable processor

I have tried 9.1 and 9.2 same crash on startup

I have heard that VMWare Player may work, will be trying this soon

[Marc Harter]

Works now for me. I did have a VT-x enabled machine but it wasn't turned on in the BOIS. After turning it on I had no probs loading iTunes.

[Kurt Beyers]

Replying to wavded:

Works now for me. I did have a VT-x enabled machine but it wasn't turned on in the BOIS.

After turning it on I had no probs loading iTunes.

I'm pretty sure I've tried this already, but just gave it another shot:

-Virtualization is enabled in BIOS

-VT-x enabled

-flagged 'Enabled Nested paging' as well

After starting my XP, I've installed an update of .Net and of java. I know I shouldn't have changed multiple parameters, but I thought it wouldn't matter any way.

However now the installation of iTunes 9.2 succeeded and so thus the management of the iPhone in iTunes. Got myself finally an IOS4 backup.

Hope this information is interesting to find the root cause of the problem.

[Matt]

@Kurbey The thing that fixed it for you was probably the enabling it in BIOS.

The issue is iTunes not working without VT-x enabled, which if you don't have a VT-x processor you can't enable it.

[Marc Harter]

Replying to Kurbey:

However now the installation of iTunes 9.2 succeeded and so thus the management of the iPhone in iTunes. Got myself finally an IOS4 backup.

Yeah even though iTunes started working, the firmware upgrade failed and I can't get at the device anymore in restore mode... (sounds like another bug for a different ticket)

[cyounkins]

Change the priority on this to "major".

[Kurt Beyers]

Replying to Matt Harrison:

@Kurbey The thing that fixed it for you was probably the enabling it in BIOS.

The issue is iTunes not working without VT-x enabled, which if you don't have a VT-x processor you can't enable it.

@Matt The virtualization was enabled already in the BIOS during previous attempts.

The only difference at the Virtualbox side was choosing the option 'Enable Nested Paging' as well. But if I hold my mouse above the 'V'-button in the system tray, the pop-up tells that only VT-x is enabled, nested paging is still shown as being disabled.

[Ralph Schmieder]

Replying to cyounkins:

Change the priority on this to "major".

Even though I opened the ticket it's not possible for me to change the priority. This needs to be done by some Oracle guy. And I don't know how to bring this to their attention...

[Frank Mehnert]

Changing the priority of a ticket is only allowed for members of the developers team and this by intension.

[Warwick McNaughton]

Replying to krsoulsby:

Now that this issue will start to prevent users from upgrading to iOS4 on their iPhones is it possible to increase the priority.

BTW I am having the same problems with any version of itunes over 9.0 with windows 7 running on 3.2.4 VirtualBox and I also do not have a VT-x capable processor

I have tried 9.1 and 9.2 same crash on startup

I have heard that VMWare Player may work, will be trying this soon

Tried VMWare Player and seems to work OK:

(i) in Virtualbox I exported virtual machine as an appliance (did not need to select legacy version)

(ii) used ovf tool (need to download from VMware) to change the ovf file to vmx file

• had to make manual changes to ovf file before this would work, see
  

​http://communities.vmware.com/thread/248989 and
​http://communities.vmware.com/thread/214231?tstart=30

(iii)from memory my changes to the ovf file were

• change .mf file to .mf_old (so didn't recognise it)
  
• for sound card section used <Item ovf:required="false">
  
• used <vssd:VirtualSystemType>vmx-07,vmx-06</vssd:VirtualSystemType>

(iv)was then able to open the export from Virtualbox in VMware Player and continue with iTunes where I left off

(v) I needed to experiment with memory settings for best result

(vi) I could not upgrade to iOS4 without errors. I have a 3G iPhone and a lot of people with 3G iphones are having problems: ​http://discussions.apple.com/forum.jspa?forumID=1274

(vii) eventually upgraded using the method in this thread: ​http://discussions.apple.com/thread.jspa?threadID=2473150&tstart=0 Basically back up then restore.

However, even though the OS was upgraded I did not get all my data. Now doing a sync with iTunes to reinstall missing bits. Indications are this is working.

I like Virtualbox and would like to come back to it once it is fixed. Not sure of the return path just yet.

Hope this helps someone.

[martinrs]

In my case I have a problem with iTunes 9.2 starting by flashing an error dialog and quitting right away. The message flashes too fast to read anything, but it seems to indicate something to do with component missing or not properly installed.

I have AMD-V enabled from BIOS and have AMD CPU with SVM, but VirtualBox 3.2.4 will not detect it (icon is greyed out.) I definitely know my desktop (Asus M2AVM with AMD 64x2 5200+) has AMD-V and BIOS is enabled.

I tested iTunes 9.0.2.25 and that works fine without AMD-V being detected.

I'm afraid there may be 2 issues: VirtualBox doesn't detect AMD-V for my PC, and iTunes from 9.1 has issues with non-detected VT-x/AMD-V.

[martinrs]

Ok, I was able to solve the issue of not detecting AMD-V from ticket#5639 and #6310. iTunes 9.2 is now working fine with VT-x/AMD-V on. Sorry this doesn't solve the original ticket though.

[Mohammad Alkahtani]

I have the same problem I attached the log Win7-2010-06-30-11-44-38.log The host is ubuntu 10.4 and the guset windows 7 ultimate 32-bit on Toshiba Labtop (Satellite Pro U400-185) when I debuge itune.exe on Visual Studio I get this error "Unhandled exception at 0x000000dd in iTunes.exe: 0xC0000005: Access violation reading location 0x000000dd."

[bozata]

Same problem here. Started with VB 3.1 / iT 9.1 and has been there in any combination, including the current 3.2.6 / 9.2.1 - XP guest, host is either W7 or Linux 2.6. If I enable VT-x works with no problems; with VT-x disabled it installs but I receive the error above when I try to launch iTunes. This is becoming a particular issue because iOS4 requires iTunes 9.2 or above and while I hate iTunes there is no viable alternative for what I am using it for, yet. And I hate to run a dedicated box just for it.

[Johannes Frank]

Well, the issue is still there with 3.2.8. What is the actual problem? It doesn't seem unreproducable, so why not just fix it, or find a workaround, other than using old itunes software. What is the value of being a major problem if not treated as major? I hope things speed up a litte bit.

[bozata]

Replying to jmfrank63:

Well, the issue is still there with 3.2.8. What is the actual problem? It doesn't seem unreproducable, so why not just fix it, or find a workaround, other than using old itunes software. What is the value of being a major problem if not treated as major? I hope things speed up a litte bit.

[bozata]

3.2.8 - confirmed in Linux 2.6 and Win 7, no changes in behavior. Anyone regressively tested iTunes > 9.2 with old VB versions in attempt to find one combination that works? Given that I have to run a special iTunes-only box I am seriously considering that. Developers: I will be happy to test a solution, if needed...

[Sam Jacobs]

Just adding my voice to this, really (and hoping this will subscribe me to the bug...).

I too can get recent versions of iTunes to start up in VMWare Player, but actually doing anything brings my system to a standstill (I probably shouldn't be virtualising on it anyway--it's an O2 Joggler, if anyone's interested: 1.3 GHz Atom Z520* with 512 MB(!) RAM--but it's the best I've got at the moment!) whereas it can just about cope with a VirtualBox VM with the same configuration. Besides, I'm not too fond of Player's UI, which fails to cope at all with 800x480.

I've not really done any extensive testing (apart from verifying that a recent version of iTunes wont run even on VirtualBox versions as old as at least 3.1.6), but it seems obvious that Apple are doing something different/new since about iTunes 9.0.3.

One might well wonder whether Apple are trying to specifically block virtualisation--after all, they obviously have contractual obligations to keep their FairPlay DRM secure--but given that recent versions of iTunes don't crash like this under VMWare, or indeed VirtualBox on a VT-x enabled host, the fault would appear to lie in VirtualBox.

What concerns me is that the developers don't seem to be at all interested in this. This bug as been open for two months, seemingly without any developer interest, although they have, ​according to a forum moderator, been aware of the bug for longer. I find statements like ​this, from another forum moderator, to be particularly worrying:

Just face it, iTunes sucks, there are plenty of better programs and I prefer to stay well away from Apple and their software. They always break something when you run don't it the way they want you to run it.

And I already gave you a solution, download the stupid program and complain at Apple.

With an attitude like that, is there any hope whatsoever?

Sam

• Which does actually have VT-x, but it's locked off and given the nature of the system I don't think anyone'll ever even try to figure out how to turn it on!

[BelowSky]

Lets just stop the conspiracy theory here.

I have said that earlier, with my old none-VTx proccessor, VMWare Player and iTunes did everything just fine for me.
I jailbroken my iPhone 3GS OSv3.1.3 with it.
Then updated iPhone to OSv4.0 and then to 4.0.1 with it
Not only that, I even synchronized lots of books and videos with it.

The problem seems to be that VirtualBox developers are not using iPhones (which I can understand) or they just LIKE to install the crapware called iTunes in their main host system.

There are no other explanation.

So, please, no conspiracy theories. The problem is only a VirtualBox problem.

[Sam Jacobs]

Yay I'm subscribed! There really needs to be another way to do that...

Anyway, yeah, sorry about the paranoia thing! I try my best, but it happens sometimes. Believe me, it gets to me more than it might annoy others--but there's not a whole lot I can do about it. Sorry.

It's just that it is, as you say, a bug in VirtualBox. This page here is a bug report on what you'd think is the project's official bug tracker. It's not as if said bug is exactly difficult to reproduce--step 1 of 1: launch iTunes--so why, in over two months, has this apparently received no developer attention whatsoever?

Ok, so it's certainly a possibility that none of the developers have fallen foul of this bug themselves, but surely that's half the reason public bug trackers exist!

It just feels like this is, for whatever reason, being deliberately ignored.

Oh, and some of us actually like iTunes.

Sam

[bozata]

Let's stop suggesting VMWare as a solution - at best, it is a workaround, and only in certain circumstances. I am running Puppy Linux (a minimalistic distribution that runs just fine on 1G internal CF card, including the XPe virtual disk) and I moved away from VMWare a few years ago because of they lacked decent USB support. I have been pretty happy with VirtualBox until iTunes 9.1 came out. I would be happy to stay on 9.0.2 forever but it does not support iOS 4. And I am yet to see a viable alternative for iTunes on Linux (everything I saw is missing one thing or another). Unfortunateloy, given the Apple's attitude I don't believe that will happen any time soon. On top of that VMWare does not work on Puppy (despite what their forums say) - VB, on the other hand, works like a charm. Given my minimalistic requirements, I cannot switch to a board that supports VT-x. In summary: VMWare does not help in all cases, there is no good alternative to iTunes on Linux and I hope this bug gets some attention. I cannot believe that only iTunes is affected...

[Luca]

It seems solved with iTunes 10 Guest XPSP3, Host Linux CentOS5 no VT-x processor

[bozata]

Yep, iTunes 10 + XPe guest works without VT-x on Win7/64 host. Haven't had a chance to test on Puppy Linux but I presume it will work.

[krsoulsby]

I agree iTunes 10 is working on a Windows 7 guest running on a Ubuntu 10.4 host

[krsoulsby]

Replying to krsoulsby:

I agree iTunes 10 is working on a Windows 7 guest running on a Ubuntu 10.4 host

and without VT-x running

[bozata]

I don't know how can we expect any movement on this bug since there is no one assigned to it...