Installation Problem with Windows 2003 on IVM 4.0

[squirrel_2]

Hi folks,

I ran into a problem with the installation of an Integrity VM (4.0) with Windows Server 2003.

The installation runs fine until SAC appears. After I entered Administrator password and product key, the installation hangs.

The setuplog.txt shows the following:

Time,File,Line,Tag,Message
10/13/2008 10:02:14,d:\srvrtm\base\ntsetup\syssetup\sacchan.c,99,,Successfully opened GuiModeDebug channel

10/13/2008 10:02:15,d:\srvrtm\base\ntsetup\syssetup\sacchan.c,135,,Successfully opened ActionLog channel

10/13/2008 10:02:15,d:\srvrtm\base\ntsetup\syssetup\sacchan.c,171,,Successfully opened ErrorLog channel

10/13/2008 10:02:15,d:\srvrtm\base\ntsetup\syssetup\syssetup.c,6763,BEGIN_SECTION,Installing Windows NT
10/13/2008 10:02:17,d:\srvrtm\base\ntsetup\syssetup\wizard.c,1543,,SETUP: Calculating registery size
10/13/2008 10:02:17,d:\srvrtm\base\ntsetup\syssetup\wizard.c,1575,,SETUP: Calculated time for Win9x migration = 120 seconds
10/13/2008 10:02:17,d:\srvrtm\base\ntsetup\syssetup\syssetup.c,6794,BEGIN_SECTION,Initialization
10/13/2008 10:02:17,d:\srvrtm\base\ntsetup\syssetup\syssetup.c,6913,BEGIN_SECTION,Common Initialiazation
10/13/2008 10:02:17,d:\srvrtm\base\ntsetup\syssetup\syssetup.c,1694,BEGIN_SECTION,Initializing action log
10/13/2008 10:02:17,d:\srvrtm\base\ntsetup\syssetup\log.c,316,,GUI mode Setup has started.

10/13/2008 10:02:17,d:\srvrtm\base\ntsetup\syssetup\syssetup.c,1699,END_SECTION,Initializing action log
10/13/2008 10:02:17,d:\srvrtm\base\ntsetup\syssetup\syssetup.c,1803,BEGIN_SECTION,Creating setup background window
10/13/2008 10:02:17,d:\srvrtm\base\ntsetup\syssetup\syssetup.c,1821,END_SECTION,Creating setup background window
10/13/2008 10:02:17,d:\srvrtm\base\ntsetup\syssetup\syssetup.c,1894,BEGIN_SECTION,Initializing SMS support
10/13/2008 10:02:17,d:\srvrtm\base\ntsetup\syssetup\syssetup.c,1903,,Setup: (non-critical error): Failed load of ismif32.dll.
10/13/2008 10:02:17,d:\srvrtm\base\ntsetup\syssetup\syssetup.c,1905,END_SECTION,Initializing SMS support
10/13/2008 10:02:17,d:\srvrtm\base\ntsetup\syssetup\syssetup.c,1936,BEGIN_SECTION,Shutting down power management
10/13/2008 10:02:17,d:\srvrtm\base\ntsetup\syssetup\syssetup.c,1939,END_SECTION,Shutting down power management
10/13/2008 10:02:17,d:\srvrtm\base\ntsetup\syssetup\syssetup.c,2028,BEGIN_SECTION,Processing parameters from sif


I recreated the VM and even tried different EBSUs, but with no success.

Any ideas?

Thanks in advance!

[melvyn burnard]

well first question is whether this is Win2k3 Enterprise or Datacenter Edition, 64 bit for Itanium.
If not, you will get all sorts of strange issues.

[squirrel_2]

Hehe, yes I know. :)
I found that many times on this forum.

My Microsoft Select media says:
"Windows Server 2003 Enterprise Edition for Itanium-based Systems with Service Pack 1"

I guess this must be the correct media, otherwise I would not have managed to get up to the SAC.

[Tim Nelson · Accepted solution]

1) Did you install all the recommeded vHost patches for IVM 4.0 ??
â ¢ PHSS_38566 â HPVM-CORE patch
â ¢ PHSS_38567 â VM Scheduler (vmagent) patch
â ¢ PHSS_38610 â 11.23 HPVMUPGRADE patch
â ¢ PHSS_38611 â 11.31 HPVMUPGRADE patch
â ¢ PHSS_38631 â HPVM Serviceguard Tool kit patch

2) Need to have Windows 2003 Server (Enterprise or Datacenter edition) SP2
(according to the same release notes.)

http://www.docs.hp.com/en/T2767-90179/index.html

[squirrel_2]

Thanks, I found it yesterday that SP2 is needed. Unfortunately my colleague with the TechNet login is on vacation. :-/

Regarding the patches:

I have 11.31 September 2008 release, which is just a few weeks old.
Do I really already need patches for it to work properly?

[melvyn burnard]

Yes, there are MUST LOAD patches or as HP refer to them "Day One " patcehs that must be installed for HP IVM 4.0 on the Host OS

[squirrel_2]

Okay, I download all the patches from the Release Notes including their prerequisites, but all of them are marked as "already installed" on 11.31 September 2008 release.

Hopefully the SP2 media arrives by tomorrow.

[Tim Nelson]

You should be good on patches then.

Beware that just because you have Sept '08 distribution that does not mean that it contains the latest patches. My last experience was that it was close but missing some criticals.

I would also apply the latest patch bundle for 11.31 also labled sept '08. ( if the analyze says they are all already installed then at least you checked )

[squirrel_2]

Gnaaa...

Today my SP2 installation media arrived, so I created a fresh virtual machine, booted EBSU, then switched to the Windows setup CD and BANG - "bluescreen" on console:

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this Stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use Safe Mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical information:

*** STOP: 0x0000000A (0x00000000000003E8,0x000000000000000C,0x0000000000000000,0xE00000008400E180)


Beginning dump of physical memory

Physical memory dump complete.
Contact your system administrator or technical support group for further
assistance.

[squirrel_2]

I restarted the installation from the Windows-CD and came beyond the bluescreen.

But now the installation hangs exactly at the same stage:

10/15/2008 10:51:11,d:\nt\base\ntsetup\syssetup\syssetup.c,2028,BEGIN_SECTION,Processing parameters from sif

Seems to make no difference if using SP1 or SP2 media...

[squirrel_2]

Finally Windows is running.

If somebody is interested:

The error "STOP: 0x0000000A (0x00000000000003E8..." is in the release notes as "in investigation".

After replacing my AVIO LAN with normal LAN and and configuring the DVD from "null" to "file", Windows is running several attempts later.

Splendid!

[squirrel_2]

One more thing:

SLES10 SP2 runs fine in a virtual machine, but Windows shows a nearly 100% host CPU load in Virtual Machine Manager in SMH and top.

Did anybody already come across this?