VMware Fusion 3.0.0

VMware Fusion is not technically one of the supported platforms that we offer documentation/assistance for. There have been reports of users getting the LTM VE running on Fusion, though. I'd check this thread - Click here

 

 

Colin

So, I have this exact config running LTM VE, on my MBP 10.6.2 with VMWare Fusion 3.0. I don't have 10.6.3 yet, as it's not GA yet. Seems to run fine, although I have not spent a huge amount of time with it yet,

Same. MB 10.6.2, VMWare Fusion. Works like a charm.

 

 

The only issue I ever have is when I open my MB on the train, i can use the system fine until we go past a BTOpenzone AP... MB gets a new IP, but the VM doesn't re-DHCP, so you miss it. Changing the network to NAT'ed instead of bridged should sort you there.

 

 

H

Hamish: You should be able to run "service dhclient restart" to kick the dhclient into a new lease process. The dhclient is set to adhere to whatever lease is handed to it. Not having your mgmt port on a network that moves around a bunch is wise - the NAT'd solution covers that - that's a great suggestion.

Hey Tree, can't they just run 'config' and snag a new DHCP addy?

sure, config will do the same thing in the end - one must answer yes to the automatic IP address question, press enter and wait a few seconds for the lease negotiation before checking with "b mgmt". Using config for this is simple and straightforward with less typing. Nice!

I think my point should be taken with the view that if you run the interface NAT'ed, then it's transparent when you change our own IP. If you run the interface bridged to the ethernet connection, then you have to manually change your IP... if you're on a train (e.g. Westbound from London Paddington), you'll be updating your IP address every few minutes...

 

 

H

And if you use a NAT'ed interface for some reason you'll get a new IP everytime you wake your MB up... Ho hum... These things are sent to frustrate us...

 

One can work around changing IP addresses in two fashions:

 

1) Setup the LTM VE with a static management IP (the host network of your MB's Fusion environment won't change subnets magically, so this should be fine). Just because DHCP exists doesn't mean one must use it :-).

 

 

2) if one desires DHCP but also desires a static address, one may setup a host (MAC address) to IP mapping statement in the dhcpd configuration file that VMware uses - or on whatever DHCP daemon is handing out addresses.

 

vLTM seems remarkably resistant to letting you set a static IP. You can change between DHCP and static, but the static IP itself can't be set in the GUI... Or, rather, it can, but it'll be ignored (The static IP is set to the last DHCP address you got).

 

 

I've found you have to set the network up using the 'netconfig' utility... (Anything else and vLTM makes sure it gets setup again how it wants it, or just ignores it).