VMware Communities
gbullman
Expert
Expert

Solaris 10 Update 3 - Network Device Problems

This thread from a while back seems very similar if not the same problem that I'm experiencing;

http://communities.vmware.com/message/604081#604081

I downloaded the Solaris 10 Update 3 from Sun's site, and I'm trying to

run in on VMware Fusion 1.1.1 on a MacBook Pro with a core 2 duo

processor. I followed all of the steps concerning driver_aliases,

name_in_major, and /kernel/drv above, have rebooted after touching

/reconfigure that were contained in that thread. I still get the;

Failed to plumb IPv4 interface(s): vmxnet0

Failed to configure IPv4 DHCP interface(s): vmxnet0

when booting up the Solaris VM. And best I can tell networking is not

working at all within the VM. More about ifconfig behavior below.

The very first line of the Solaris boot messages indicate that it is

SunOS 5.10 and is 32-bit. I was getting errors about 32 / 64 bit

"mismatch", and currently have;

monitor_control.disable_longmode = "1"

set to make everything 32-bit.

I am setting the machine's hostname via the /etc/nodename file, and

that appears to be working correctly. My desired endstate is that this

VM configure the networking via DHCP, and I have modified

PARAM_REQUEST_LIST to remove 12 in /etc/default/dhcpagent so the DHCP

request does not ask for a hostname.

My .vmx file entries relative to ethernet are;

ethernet0.present = "TRUE"

ethernet0.addressType = "generated"

ethernet0.connectionType = "bridged"

ethernet0.generatedAddress = "00:0c:29:71:6d:23"

ethernet0.generatedAddressOffset = "0"

ethernet0.pciSlotNumber = "32"

Currently prtconf -D | grep 1022 returns;

  1. prtconf -D |grep 1022

pci1022,2000, instance #1 (driver name: vmxnet)

I believe I have set the eeprom file to boot 32-bit, eeprom returns;

  1. eeprom

kbd-type=US-English

ata-dma-enabled=1

atapi-cd-dma-enabled=0

ttyb-rts-dtr-off=false

ttyb-ignore-cd=true

ttya-rts-dtr-off=false

ttya-ignore-cd=true

ttyb-mode=9600,8,n,1,-

ttya-mode=9600,8,n,1,-

lba-access-ok=1

prealloc-chunk-size=0x2000

bootpath=/pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a

console=text

boot-file=kernel/unix

There is currently an empty file named /etc/dhcp.vmxnet0, and a file

/etc/hostname.vmxnet0 that has my desired hostname as its' only

conents. (I've seen some confusing guidance on the contents of this

file, some say it should be empty, others say it should have the

hostname).

Lastly, here are 2 what should be relevant ifconfig commands and their output;

  1. ifconfig -a

lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

  1. ifconfig vmxnet0 plumb

ifconfig: plumb: vmxnet0: Invalid argument

What else should I be checking, any ideas on why this is not working? I

would really like to get this working, and appreciate any guidance that

can be provided.

0 Kudos
1 Reply
gbullman
Expert
Expert

I decided to re-install vmware tools just to be sure they were installed correctly. I don't know if this was happening all along, but now I'm getting this response from vmware-config-tools.pl;

Starting VMware Tools services in the virtual machine:

...

Guest vmxnet fast networking device: failed

I haven't been able to find a log that gives me more information on what is going on. Not sure if this is progress or not.

0 Kudos