donderdag, december 13, 2007

VMware: Installing Suse Linux Enterprise 10 on ESX

After installing the VMware Tools on our Suse Linux Enterprise 10 guest, we kept losing the network configuration. Apparently, after loading the vmxnet driver there were 2 network cards present.

So here is the workaround:

  • Start yast (or use the gnome desktop to configure yast via the GUI)
  • Click the Network devices link and click on Network Card
  • Leave the default “traditional method with ifup” and click Next
  • Select the current configured card and click the Edit button
  • Write down (copy) the current configuration name (eth-id-xxxxxxx)
  • Click the back button and remove the current configured network card by pressing the delete button. NOTE: only 1 network card should remain
  • Back in yast overview, navigate to Network devices => Network Card
  • Select the card that is not configured and click the Edit button
  • On the configuration name, replace pci-xxx by eth-id-xxxx (written down earlier)
  • Fill out all necessary IP configuration (IP Address, subnet mask).
  • Leave yast and commit your changes
  • Done!

3 opmerkingen:

Js Opdebeeck zei

Hello

One Good stuff is also to Create a new 'Incarnation' of the machine, if you use it as a 'Template'.

Novell - SLES Cloning ... please check this procedure

In this example I've just cloned an ESX Image.

The problem is that Clone has bad settings (duplicated), and can't be used as this.
Server Keys

Go to /etc/ssh and do :

cd /etc/ssh
rm *key*

Go to /etc/zmd and do :

cd /etc/zmd
rm deviceid
rm secret

Regenerate a new machine ID

/usr/bin/uuidgen

Hostname and Network

With Yast :

* change the hostname
* remove the old/bad nework interface(s)
* assign IP address
* assign gateway.

vijayscsa zei

Hi Vincent

Need some inputs on the following contexts. I'm having HP DL360G5 server with 500 GB of internal harddisk storage space,with VMWare ESX 3.0.1 and have configured 5 VMs. Recently i removed one VM,as it was not required. The situation now is the disk space of the removed VM is not reflecting the free space of data store.

Need some inputs and your views to solve this issue.

Thanks

regards
vj

Duncan Epping (VMware) zei

I had the same issue a while back, indeed Yast is the way to solve it