VMware Communities > VMTN > VMTN Solutions > User Solutions > Discussions
Up to Discussions in User Solutions
8 Replies Last post: Jun 23, 2006 2:42 AM by Borg Number One
Reply

Networking with VMplayer

Nov 22, 2005 7:35 AM

Click to view continuum's profile Guru continuum 12,253 posts since
Dec 18, 2003
If you want the same connectivity with VMplayer that you got with Workstation
use a detailed vmx-file:
Add
ethernet0.present = "TRUE"
ethernet0.connectionType = "custom"
ethernet1.present = "TRUE"
ethernet1.connectionType = "custom"
ethernet2.present = "TRUE"
ethernet2.connectionType = "custom"
(ethernet3.present = "TRUE"
ethernet3.connectionType = "custom")

first and then enter the vmnets like
ethernet0.vnet = "vmnet0"
ethernet1.vnet = "vmnet2"
ethernet2.vnet = "vmnet1"
(ethernet3.vnet = "vmnet8")

This will show up in the Player's GUI as connected - BUT none of the Bridged, NAT or Hostonly signs are checked.

You are NOT limited to ONE bridged, or NAT or hostonly-network.

Ulli
Reply Re: Networking with VMplayer Nov 22, 2005 8:04 AM
Click to view sbeaver's profile Guru sbeaver 7,718 posts since
Nov 1, 2004 Moderator
Nice post Ulli!!
Reply Re: Networking with VMplayer Nov 22, 2005 6:22 PM
Click to view JMills's profile Master JMills 2,621 posts since
Jun 18, 2004 VMware
And if you add:

[code]
ethernet0.startConnected = "TRUE"
ethernet1.startConnected = "TRUE"
ethernet2.startConnected = "TRUE"
ethernet3.startConnected = "TRUE"
[/code]
?
Reply Re: Networking with VMplayer Nov 23, 2005 1:29 PM
in response to: JMills
Click to view continuum's profile Guru continuum 12,253 posts since
Dec 18, 2003
This should only be needed to if you added
ethernet0.startConnected = "FALSE" before the last time you booted the VM and want to switch back to normal operation.

I think setting ethernet0.present = "TRUE" silently sets
ethernet0.startConnected = "TRUE" as well.

Don't know if you have a term for entries like that - I call them invisible defaults.
It doesn't hurt to add them but defacto they are only necessary when you change the default.

I think there are more of this invisible defaults for ethernet-settings: just giving some examples ...

vlance.noOprom = "TRUE" - can be used to turn-off the boot-rom for networkboot

ethernet0.allow64bitVlance = "FALSE"
ethernet0.allow64bitVmxnet = "FALSE"

ethernet0.allowGuestConnectionControl = "TRUE" - disable changing nics with the GUI

ethernet0.noPromisc = "FALSE" - disable promiscous mode
ethernet0.noForgedSrcAddr = "FALSE" - disable guest changing its MAC?
ethernet0.ignoreMACAddressConflict = "FALSE"

Reply Re: Networking with VMplayer Nov 23, 2005 1:29 PM
in response to: continuum
Click to view Ninho's profile Hot Shot Ninho 218 posts since
Feb 24, 2006
vlance.noOprom = "TRUE" - turn-off the boot-rom for networkboot

Very useful indeed. Does someone know how to turn-off the 16 k USB legacy bbot-rom which sits at 000DC000h ?

Also, can we have our own ROM files (including, maybe, modified main BIOS) and set them up at selected addresses ?
Reply null. disregard Nov 23, 2005 1:29 PM
in response to: continuum
Click to view Ninho's profile Hot Shot Ninho 218 posts since
Feb 24, 2006
sorry
Reply Null again, argh, sorry Nov 23, 2005 1:29 PM
in response to: continuum
Click to view Ninho's profile Hot Shot Ninho 218 posts since
Feb 24, 2006
(grrr)
Reply Re: Networking with VMplayer Feb 22, 2006 10:35 PM
Click to view san44s's profile Lurker san44s 1 posts since
Feb 22, 2006
It didnt work.

My host has 2 NICs

NIC1 connected to 10.0.0.2
NIC2 connected to 137.111.242.7

Guest XP OS
Ethernet IP 10.0.0.4

vmx
......
ethernet0.present = "TRUE"
ethernet0.connectionType = "custom"

ethernet1.vnet = "vmnet2"
..........

I want my guest to only talk to 10.0.0 network. It works fine. but when I chage the IP of guest NIC to 137.X.X.X. Try ping it wont work.
As soon as I unplug 10.0.0 network cable it starts working.

Can I get my VMPlayer to only talk to 10.0.0 NIC and network? Please help.
Reply Re: Networking with VMplayer Jun 23, 2006 2:42 AM
Click to view Borg Number One's profile Novice Borg Number One 33 posts since
Dec 24, 2004
Hi.

1.)
Referring to networking, and using own (Etherboot or any other network boot code, ...), I figured out many further interesting nonofficial switches, which were not known before.

The most interesting of the new switches are following:

e1000bios.filename = "path/filename to an external Intel E1000 network boot ROM"
nbios.filename = "path/filename to an external AMD LANCE network boot ROM"
nxbios.filename = "path/filename to an external VMXNET network boot ROM"

Examples:

ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.startConnected = "TRUE"
ethernet0.connectionType = "bridged"
e1000bios.filename = "C:\bios\eb-5.4.2-e1000-82545em-copper.zrom"

ethernet1.present = "TRUE"
ethernet1.virtualDev = "vlance"
ethernet1.startConnected = "TRUE"
ethernet1.connectionType = "bridged"
nbios.filename = "C:\Program files\VMware\VMware Workstation\vlance-org.bin"

ethernet2.present = "TRUE"
ethernet2.virtualDev = "vmxnet"
ethernet2.startConnected = "TRUE"
ethernet2.connectionType = "bridged"
nxbios.filename = "C:\Program files\VMware\VMware Workstation\vmware-vmxnet-org.bin"

For the Etherboot mailing list, I also prepared a small article and a nice animation:
http://bnobtc.pix-art.com/etherboot-oprom-in-vmware-and-bochs.txt
http://bnobtc.pix-art.com/images/borgbios/vmware/etherboot-in-vmware.gif

2.)
Referring to the USB stuff, I also took a memory dump ( suspend / pause VMware emulation to get a memory dump) and I could not find any USB related string / USB related code at 000DC000h .

I just could find the VGA BIOS at 000C0000h. :)

Could you list 16...64 Bytes (hex code) from 000DC000h of your memory dump here?

Are there typical (USB related) strings from 000DC000 - 000EFFFF in your memory dump?

Actions
Up to Discussions in User Solutions