VMware Communities
RJDickson
Contributor
Contributor
Jump to solution

Installing DB2 10.1 Windows 7 64bit 'hangs' at DAS

Hi all,

This is going to be a strange one, but please be assured this is no Holloween joke!

I have two MacBook Pro's.  They both have Mavericks 10.9, Fusion 6.0.1, and 16G of RAM. The first MacBook Pro is Early 2011, the second is Late 2013.  I also have a single VMware image that is Windows 7 64bit allocated with 2 cores and 3G of RAM.  Accelerated 3D graphics is 'Off'.

When I install DB2 ESE 10.1 on the Early 2011, all is good.

However, when I try the same install on the same VMware image (copied over, of course) on the Late 2013 MacBook Pro, the installer 'hangs' when installing DB2 Administration Server (DAS).  Just hangs.  Nothing in the logs.

I've 'upgraded' to Hardware version 10.

What in the world could prevent DB2 from installing in this VMware image on the Late 2013 MacBook Pro?

Thanks!

Robert

1 Solution

Accepted Solutions
admin
Immortal
Immortal
Jump to solution

The problem appears to be that the DB2 installer can't handle more than 4 responses to the CPUID query for deterministic cache parameters.  It just so happens that the mobile Haswell CPUs with integrated GPUs reply with 5 or 6 responses to the CPUID query for deterministic cache parameters.

The same thing would happen if the DB2 installer were run natively on these parts (e.g. in Boot Camp).  Note that this would not be an issue on desktop Haswell CPUs without integrated GPUs, since they only return 4 responses to the CPUID query for deterministic cache parameters.

Fortunately, with Fusion, you can configure your VM to lie about its deterministic cache parameters.  The following configuration options should do the trick:

monitor_control.enable_fullcpuid = TRUE
cpuid.4.4.eax = "0000:0000:0000:0000:0000:0000:0000:0000"


As always, the VM must be completely powered down (not suspended), and you should quit Fusion before making these changes.  It is always wise to make a back up first. See http://kb.vmware.com/kb/1014782 for details on editing your configuration file.

VMware cannot support this configuration, since we do not cover it in our testing, but this may be a reasonable workaround while you wait for a fix from IBM.

View solution in original post

34 Replies
SteveMM
Contributor
Contributor
Jump to solution

I am facing a similar issue.

VMWare Fusion 6.0.2

Mavericks OS X 10.9.1

MacBook Pro Late 2013

When I try to install DB2 ESE or DB2 Express the install hangs.

Have you been able to make any progress on this?

Thanks,

-Steve

0 Kudos
RJDickson
Contributor
Contributor
Jump to solution

Hi Steve,

Nothing yet.  VMware is pointing to DB2 as the issue.  I did not expect that, so I will check with IBM next and update all here when I know more.

-Robert

0 Kudos
adrianords
Contributor
Contributor
Jump to solution

I have the same issue with Windows XP and DB2 10.1. The error is "Memory 0xxxxxx could not be read". I have this issue in first time after upgrade Mavericks to 10.9.1 in a Early 2011 MacBook Pro.

VMWare Fusion 6.0.2

Mavericks OS X 10.9.1

MacBook Pro 15 Late 2013

Adriano.

0 Kudos
RJDickson
Contributor
Contributor
Jump to solution

Hi Adriano,

I am talking to DB2 support and will post any results here.  Nothing substantial yet...

Regards,

Robert

0 Kudos
ColoradoMarmot
Champion
Champion
Jump to solution

I've seen several reports of this - it appears that it's a lack of support for the new CPU in the new machines (in other words, apparently it won't install in boot camp either).

0 Kudos
RJDickson
Contributor
Contributor
Jump to solution

Hi,

The DB2 team just did an install on a PC with a Haswell chip.  No issues.  They (the DB2 team) are saying it must be a VMware issue.

I will let you know when I find out more.

0 Kudos
gosieg
Contributor
Contributor
Jump to solution

I'm having the same issue. For reference, there is a similar unanswered thread on the IBM forums: https://www.ibm.com/developerworks/community/forums/html/topic?id=224c1e39-a280-4a3e-8b31-d059542b33....

In my case, I've tried starting DB2 in a VM that's known to work in VMWare Workstation on a Windows machine, and I've tried installing DB2 on a blank VM. Both were unsuccessful. It's tough to say who is at fault, but this is a big issue that's holding up my productivity.

0 Kudos
ColoradoMarmot
Champion
Champion
Jump to solution

It does work on a Linux VM - so that's something you could do temporarily.

0 Kudos
DavidAsh
Contributor
Contributor
Jump to solution

I'm experiencing the same DB2 startup issues ("Memory 0xxxxxx could not be read") after copying a known working Windows 2008 R2 Enterprise Server guest to Fusion 6.0.2 on a late 2013 MacBook Pro with the i7 2.3GHz processor.

Any resolutions / work arounds?

Thanks!

0 Kudos
RJDickson
Contributor
Contributor
Jump to solution

IBM has told me that they have installed on bare metal Haswell chips, so the issue must be with VMware.  VMware keeps giving me a generic update of 'I will update the same to our engineering team and get back to you once I hear from them'.

I hate to point fingers, but it does appear the VMware is the problem, and I am frustrated with the generic responses.  There are a few stellar individuals at VMware that did try to help, but to no avail.

I suggest that you open a support ticket.  Maybe the volume of tickets related to this issue will convince VMware that this issue is real, and that we really, really, really need a fix!

Regards,

Robert

0 Kudos
DavidAsh
Contributor
Contributor
Jump to solution

I've opened a new Support ticket with VMWare, provided supporting material / logs. Awaiting response. Will provide outcome back to this thread.

0 Kudos
DavidAsh
Contributor
Contributor
Jump to solution

I've opened a new Support ticket with VMWare, provided supporting material / logs. Awaiting response. Will provide outcome back to this thread.

0 Kudos
gosieg
Contributor
Contributor
Jump to solution

Is it possible to "vote" on tickets? If so, could you send a link?

0 Kudos
RJDickson
Contributor
Contributor
Jump to solution

Hi,

Not sure, but my ticket number is 13400777211

0 Kudos
ColoradoMarmot
Champion
Champion
Jump to solution

I wonder if anyone's tried installing it on Boot Camp - maybe it's a mac hardware issue separate from Haswell....

0 Kudos
admin
Immortal
Immortal
Jump to solution

Please try the following:

1. Shut down Windows to power off the VM.

2. Edit the configuration file and add the following:

featMask.vm.cpuid.MODEL = "Val:44"

3. Power on the VM.

See if that makes any difference.

0 Kudos
gosieg
Contributor
Contributor
Jump to solution

Didn't make a difference for me.

0 Kudos
admin
Immortal
Immortal
Jump to solution

gosieg wrote:

Didn't make a difference for me.

Thanks.  Would you mind uploading the resulting vmware.log file?  (Click 'Use advanced editor' at the upper right of the forum composition box, and you will be able to attach a file to your reply.)

0 Kudos
gosieg
Contributor
Contributor
Jump to solution

Here you go.

0 Kudos