ClientOS:Solaris10x86 not run at another PC

[SPACE2010]

I make the ClientOS (Solaris10 for x86) at My Computer .

ClientOS(Solaris10 for x86) run and I use this ClientOS at this Computer.

This Computer is follow;

HOST

OS: WindowsXPhome

VMwarePlayer2.02

CPU:Intel Core2DUO / MEM:1Gb (NOTEBOOK)

CLIENT

OS:Solaris10 forx86

DISPLAY 24inchWIDE 1920*1200

I copied this VMWARE files(vmx/vmdk/etc) to anther computers.

But ClientOS(Solaris10 for x86) not run at another computers.Why?

another machine is follow;

1. Windows machine

HOST OS:WindowsXPpro

VMWARE PLAYER2.0.2

CPU:Core2DUO 6600 2.4GHz / MEM:2GB

2.Macbook

HOST OS:MacOSX10.4.1

VMWARE FUSION 1.1.1

CPU MACBOOK2.16GHz Intel Core2Duo / MEM:1GB

I copied this VMWARE files(vmx/vmdk/etc) to more anther computer.

But ClientOS(Solaris10 for x86) run at more another computer.

more another machine is follow;

3. Windows machine

HOST OS:WindowsXPpro

VMWARE PLAYER2.0.2

CPU:Celeron 2.5GHz / MEM:2GB

-

---

vmx files is follow;

config.version = "8"

virtualHW.version = "6"

displayName = "Solaris10-Apach-PHP"

guestOS = "solaris10"

memsize = "512"

ethernet0.connectionType = "bridged"

ethernet0.present = "FALSE"

ethernet0.addressType = "generated"

usb.present = "FALSE"

floppy0.present = "FALSE"

sound.present = "FALSE"

sound.virtualdev = "es1371"

ide0:0.present = "TRUE"

ide0:0.deviceType = "disk"

ide0:0.filename = "6GB.vmdk"

ide0:0.startConnected = "TRUE"

ide0:0.mode = "persistent"

ide0:0.redo = ""

ide1:0.deviceType = "cdrom-image"

ide1:0.present = "FALSE"

ide1:0.fileName = "vmware-ws-solaris-tools.iso"

tools.syncTime = "FALSE"

virtualHW.productCompatibility = "hosted"

tools.upgrade.policy = "manual"

log is follow;

-

---

1.Windows Computer log

---

Feb 21 10:38:21.281: vmx| TimeTracker host to guest rate conversion 5192596419534 @ 2397660000Hz -> 5192596419534 @ 2397660000Hz

Feb 21 10:38:21.281: vmx| TimeTracker host to guest rate conversion ((x * 2147483648) >> 31) + 0

Feb 21 10:38:21.312: vmx| MKS REMOTE Loading VNC Configuration from VM config file

Feb 21 10:38:21.312: vmx| DISKUTIL: ide0:0 : capacity=25165824

Feb 21 10:38:21.312: vmx| VLANCE: send cluster threshold is 80, size = 2 recalcInterval is 2 ticks

Feb 21 10:38:21.312: vmx| VMXNET: send cluster threshold is 80, size = 2 recalcInterval is 2 ticks, dontClusterSize is 128

Feb 21 10:38:21.312: vmx| E1000: checksum cycles/kB: C=1009 asm=727

Feb 21 10:38:21.312: vmx| MStat: Creating Stat vm.heartbeat

Feb 21 10:38:21.312: vmx| DISKUTIL: ide0:0 : toolsVersion = 6404

Feb 21 10:38:21.312: vmx| TOOLS INSTALL initializing state to IDLE on power on.

Feb 21 10:38:21.312: vmx| PTSC to VMI Wallclock (nsec) 5192673746418 @ 2397660000Hz -> 1203557901000000000 @ 1000000000Hz

Feb 21 10:38:21.312: vmx| PTSC to VMI Wallclock (nsec) ((x * 3582632480) >> 33) + 1203555735274356491

Feb 21 10:38:21.312: vmx| VirtualProtect MapProtectMem(0x1bf0000,0x1000) returns 0x1e7

Feb 21 10:38:21.312: vmx| VirtualProtect MapProtectMem(0x1bf2000,0x0) returns 0x57

Feb 21 10:38:21.312: vmx| TOOLS received request in VMX to set option 'enableDnD' -> '1'

Feb 21 10:38:21.312: vmx| TOOLS received request in VMX to set option 'copypaste' -> '1'

Feb 21 10:38:21.328: vmx| VMX_PowerOn: ModuleTable_PowerOn = 1

Feb 21 10:38:21.328: vmx| VMX setting maximum IPC write buffers to 0 packets, 0 bytes

Feb 21 10:38:21.328: mks| Async MKS thread is alive

Feb 21 10:38:21.359: vmx| DnD rpc already set to 1

Feb 21 10:38:21.359: vmx| DnD CopyPasteRegisterRpc already set to 1

Feb 21 10:38:21.359: vcpu-0| APIC: version = 0x14, max LVT = 5

Feb 21 10:38:21.359: vcpu-0| APIC: LDR = 0x1000000, DFR = 0xffffffff

Feb 21 10:38:21.375: vcpu-0| guestCpuFeatures = 0x500001fa

Feb 21 10:38:21.375: vcpu-0| Init modules.

Feb 21 10:38:21.375: vcpu-0| CPU reset: hard

Feb 21 10:38:21.390: vcpu-0| sz=3047392

Feb 21 10:38:21.390: vcpu-0| vmm32 initialized: Releasebuild-59824. cflags: 0x20000002.08000002.a4000600.00000004

Feb 21 10:38:21.390: vcpu-0| MonitorInitNumaUnmapVMM32

Feb 21 10:38:21.578: vcpu-0| SVGA: Registering MemSpace at 0xf0000000(0x0) and 0xe8000000(0x0)

Feb 21 10:38:21.578: vcpu-0| SVGA: Unregistering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)

Feb 21 10:38:21.578: vcpu-0| SVGA: Registering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)

Feb 21 10:38:21.578: vcpu-0| SVGA: Unregistering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)

Feb 21 10:38:21.578: vcpu-0| SVGA: Registering IOSpace at 0x1060

Feb 21 10:38:21.578: vcpu-0| SVGA: Registering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)

Feb 21 10:38:21.796: mks| Connecting to window system.

Feb 21 10:38:21.812: mks| Ignoring update request in VGA_Expose (mode change pending).

Feb 21 10:38:21.812: mks| VMXAIOMGR: Disallowing USB connect. 1585604 us since last reopen

Feb 21 10:38:21.828: vcpu-0| VIDE: Curr CHS info cyls: 17475 heads: 15 sects: 63 lba_cap: 25165824

Feb 21 10:38:21.843: vcpu-0| BIOS-UUID is 56 4d 52 2a b7 b6 5a 8f-31 fa 95 fa b6 9c 5d 76

Feb 21 10:38:22.000: vcpu-0| DISKUTIL: ide0:0 : toolsVersion = 6404

Feb 21 10:38:22.000: vcpu-0| DISKUTIL: ide0:0 : toolsVersion = 6404

Feb 21 10:38:22.000: mks| Ignoring update request in VGA_Expose (mode change pending).

Feb 21 10:38:22.031: vcpu-0| VIDE: Curr CHS info cyls: 17475 heads: 15 sects: 63 lba_cap: 25165824

Feb 21 10:38:23.578: mks| VMXAIOMGR: Disallowing USB connect. 3354875 us since last reopen

Feb 21 10:38:26.671: mks| SVGA: Remote display status changed, enabling local optimizations

Feb 21 10:38:33.906: vcpu-0| SVGA: Unregistering IOSpace at 0x1060

Feb 21 10:38:33.906: vcpu-0| SVGA: Registering IOSpace at 0xfffffff0

Feb 21 10:38:33.906: vcpu-0| SVGA: Unregistering IOSpace at 0xfffffff0

Feb 21 10:38:33.906: vcpu-0| SVGA: Registering IOSpace at 0x1060

Feb 21 10:38:33.906: vcpu-0| Unknown int 10h func 0x1f00

Feb 21 10:38:33.906: vcpu-0| Unknown int 10h func 0x0000

Feb 21 10:38:34.171: vcpu-0| SVGA: Unregistering IOSpace at 0x1060

Feb 21 10:38:34.171: vcpu-0| SVGA: Registering IOSpace at 0xfffffff0

Feb 21 10:38:34.171: vcpu-0| SVGA: Unregistering IOSpace at 0xfffffff0

Feb 21 10:38:34.171: vcpu-0| SVGA: Registering IOSpace at 0x1060

Feb 21 10:38:34.187: vcpu-0| SVGA: Unregistering IOSpace at 0x1060

Feb 21 10:38:34.187: vcpu-0| SVGA: Registering IOSpace at 0xfffffff0

Feb 21 10:38:34.187: vcpu-0| SVGA: Unregistering IOSpace at 0xfffffff0

Feb 21 10:38:34.187: vcpu-0| SVGA: Registering IOSpace at 0x1060

Feb 21 10:38:39.593: vcpu-0| MonitorInitReserveMem64: vmm64OverheadPages=4761

Feb 21 10:38:39.609: vcpu-0| Monitor64_PowerOn()

Feb 21 10:38:39.609: vcpu-0| Msg_Hint: msg.monitorInit.vmm64.guestOS (sent)

Feb 21 10:38:39.609: vcpu-0| You are running a 64-bit guest operating system, but the virtual machine is configured to run a 32-bit operating system. To ensure that a 64-bit guest operating system will function correctly you must:

Feb 21 10:38:39.609: vcpu-0| 1. Power off this virtual machine.

Feb 21 10:38:39.609: vcpu-0| 2. Change the guest operating system type to a 64-bit operating system in virtual machine settings.

Feb 21 10:38:39.609: vcpu-0|

-

---

Feb 21 10:38:39.625: vcpu-0| vmm64-modules: vmm.vmm64 .data:0xfffffffffc04a000 .sdata:0xfffffffffc04c000 .statvars:0xfffffffffc04d000 .peer:0xfffffffffc04e000 .shared:0xfffffffffc074000 .bss:0xfffffffffc085000 .rodata:0xfffffffffc200000 .text:0xfffffffffc213000 .kstatvars:0x4000 .eh_frame:0xfffffffffc270000 ,mmu-pae.vmm64 .data:0xfffffffffc04b360 .peer:0xfffffffffc07293c .shared:0xfffffffffc083a4d .bss:0xfffffffffc08d4c0 .text:0xfffffffffc262a00 .statvars:0x1000 .kstatvars:0x1000 .scb:0x3480 .shared_meta:0x3480 .peer_meta:0xbd0 .eh_frame:0xfffffffffc280490 .comment:0xd02 ,sharedmmu-none.vmm64 .text:0xfffffffffc26c4b8 .eh_frame:0xfffffffffc281e40 .comment:0xdfe ,pv-none.vmm64 .shared:0xfffffffffc08435d .bss:0x1000 .text:0xfffffffffc26c4d0 .shared_meta:0x36f0 .eh_frame:0xfffffffffc281f90 .comment:0xe10 ,hv-vt.vmm64 .rodata:0xfffffffffc211e50 .data:0xfffffffffc04b384 .peer:0x2000 .shared:0x2000 .bss:0xfffffffffc08de00 .text:0xfffffffffc26c4e0 .statvars:0x2000 .kstatvars:0x2000 .eh_frame:0xfffffffffc282068 .comment:0xe58 ,<MonSrcFile> .rodata:0xfffffffffc2121af

Feb 21 10:38:39.640: vcpu-0| APIC: version = 0x14, max LVT = 5

Feb 21 10:38:39.640: vcpu-0| APIC: LDR = 0x2000000, DFR = 0xffffffff

Feb 21 10:38:39.656: vcpu-0| Init modules.

Feb 21 10:38:39.656: vcpu-0| vmm64: HV enabled

Feb 21 10:38:39.656: vcpu-0| VMM64 initialized

Feb 21 10:38:39.656: vcpu-0| MonitorInitNumaUnmapVMM64

Feb 21 10:38:41.343: vcpu-0| VIDE: (0x1f0) OUTB Cmd of 0x20 while drive 0 busy (status 0x90)

Feb 21 10:38:41.671: vcpu-0| VIDE: (0x1f0) OUTB Cmd of 0x20 while drive 0 busy (status 0x90)

Feb 21 10:38:42.046: vcpu-0| Triple fault.

Feb 21 10:38:42.046: vcpu-0| Msg_Hint: msg.monitorEvent.cpl0SS (sent)

Feb 21 10:38:42.046: vcpu-0| *** Virtual machine kernel stack fault (hardware reset) ***

Feb 21 10:38:42.046: vcpu-0| The virtual machine just suffered a stack fault in kernel mode. On a real computer, this would amount to a reset of the processor. It can be caused by an incorrect configuration of the virtual machine, a bug in the operating system, or a problem in the VMware Player software. Press OK to reboot virtual machine or Cancel to shut it down.

Feb 21 10:38:42.046: vcpu-0|

Feb 21 10:38:42.046: vcpu-0|-----

Feb 21 10:38:42.046: vcpu-0| CPU reset: hard

Feb 21 10:38:42.171: vcpu-0| SVGA: Unregistering IOSpace at 0x1060

Feb 21 10:38:42.171: vcpu-0| SVGA: Unregistering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)

Feb 21 10:38:42.234: vcpu-0| SVGA: Registering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)

Feb 21 10:38:42.234: vcpu-0| SVGA: Unregistering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)

Feb 21 10:38:42.234: vcpu-0| SVGA: Registering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)

Feb 21 10:38:42.234: vcpu-0| SVGA: Unregistering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)

Feb 21 10:38:42.234: vcpu-0| SVGA: Registering IOSpace at 0x1060

Feb 21 10:38:42.234: vcpu-0| SVGA: Registering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)

Feb 21 10:38:42.296: mks| Ignoring update request in VGA_Expose (mode change pending).

Feb 21 10:38:42.296: mks| Ignoring update request in VGA_Expose (mode change pending).

Feb 21 10:38:42.437: vcpu-0| VIDE: Curr CHS info cyls: 17475 heads: 15 sects: 63 lba_cap: 25165824

Feb 21 10:38:42.453: vcpu-0| BIOS-UUID is 56 4d 52 2a b7 b6 5a 8f-31 fa 95 fa b6 9c 5d 76

Feb 21 10:38:42.609: vcpu-0| DISKUTIL: ide0:0 : toolsVersion = 6404

Feb 21 10:38:42.609: vcpu-0| DISKUTIL: ide0:0 : toolsVersion = 6404

Feb 21 10:38:42.625: mks| Ignoring update request in VGA_Expose (mode change pending).

Feb 21 10:38:42.625: mks| Ignoring update request in VGA_Expose (mode change pending).

Feb 21 10:38:42.656: vcpu-0| VIDE: Curr CHS info cyls: 17475 heads: 15 sects: 63 lba_cap: 25165824

Feb 21 10:38:53.859: vcpu-0| SVGA: Unregistering IOSpace at 0x1060

Feb 21 10:38:53.859: vcpu-0| SVGA: Registering IOSpace at 0xfffffff0

Feb 21 10:38:53.859: vcpu-0| SVGA: Unregistering IOSpace at 0xfffffff0

Feb 21 10:38:53.859: vcpu-0| SVGA: Registering IOSpace at 0x1060

Feb 21 10:38:53.875: vcpu-0| Unknown int 10h func 0x1f00

Feb 21 10:38:53.875: vcpu-0| Unknown int 10h func 0x0000

Feb 21 10:38:54.125: vcpu-0| SVGA: Unregistering IOSpace at 0x1060

Feb 21 10:38:54.125: vcpu-0| SVGA: Registering IOSpace at 0xfffffff0

Feb 21 10:38:54.125: vcpu-0| SVGA: Unregistering IOSpace at 0xfffffff0

Feb 21 10:38:54.125: vcpu-0| SVGA: Registering IOSpace at 0x1060

Feb 21 10:38:54.140: vcpu-0| SVGA: Unregistering IOSpace at 0x1060

Feb 21 10:38:54.140: vcpu-0| SVGA: Registering IOSpace at 0xfffffff0

Feb 21 10:38:54.140: vcpu-0| SVGA: Unregistering IOSpace at 0xfffffff0

Feb 21 10:38:54.140: vcpu-0| SVGA: Registering IOSpace at 0x1060

Feb 21 10:39:00.968: vcpu-0| VIDE: (0x1f0) OUTB Cmd of 0x20 while drive 0 busy (status 0x90)

Feb 21 10:39:01.046: vcpu-0| VIDE: (0x1f0) OUTB Cmd of 0x20 while drive 0 busy (status 0x90)

Feb 21 10:39:01.187: vcpu-0| VIDE: (0x1f0) OUTB Cmd of 0x20 while drive 0 busy (status 0x90)

Feb 21 10:39:01.687: vcpu-0| Triple fault.

Feb 21 10:39:01.687: vcpu-0| Msg_Hint: msg.monitorEvent.cpl0SS (sent)

Feb 21 10:39:01.687: vcpu-0| *** Virtual machine kernel stack fault (hardware reset) ***

Feb 21 10:39:01.687: vcpu-0| The virtual machine just suffered a stack fault in kernel mode. On a real computer, this would amount to a reset of the processor. It can be caused by an incorrect configuration of the virtual machine, a bug in the operating system, or a problem in the VMware Player software. Press OK to reboot virtual machine or Cancel to shut it down.

-

---

2.MACBOOK Message

KARNEL DOWN RESTART

-

---

RESOLVED

1.AT anotherPC windows_xp

Solaris10x86 is run complete at anotherPC(windows_xp).

Current boot Parameters boot option

b kernel/unix

Solaris10x86 boot is OK. (32bit mode run)

I will try more another PC & Moacbook running.

refarrence :

I am sorry the refarrence & attached file is japanese language.

-

---

2.AT MACBOOK

Solaris10x86 is run complete at anotherPC(MAC OSX).

Same method at windows_xp , Solaris10x86 is OK. (32bit mde run)

Thank you.

[continuum]

Did you read the log you posted ?

Feb 21 10:38:39.609: vcpu-0| You are running a 64-bit guest operating system, but the virtual machine is configured to run a 32-bit operating system. To ensure that a 64-bit guest operating system will function correctly you must:

Feb 21 10:38:39.609: vcpu-0| 1. Power off this virtual machine.

Feb 21 10:38:39.609: vcpu-0| 2. Change the guest operating system type to a 64-bit operating system in virtual machine settings.

[PJN · Accepted solution]

Alternatively you could force Solaris to run in 32 bit mode - either

1. on the command line prompt run the command 'eeprom boot-file=kernel/unix'

... this stays in force until the next reconfiguration reboot (survives normal reboots)

OR

2. edit the gub command line to add 'kernel/unix' to the command that grub runs - you can also do this for the reconfiguration reboot grub command (where you put the 'kernel/drv' before the -r in the command)

... this only stays in force for that boot up of the VM.

Obviously you can use the grub method for the first boot and then run the eeprom command to make the change more permanent.