Hallo,
im GSX30vm_manual.pdf
Download from here:
http://www.vmware.com/pdf/gsx30vm_manual.pdf
ist auf Seite 232 beschrieben, was bei der händischen Änderung von MAC-Adressen zu beachten ist.
Ob die Änderung von MAC-Adressen zu Bluescreens führt, kann ich nicht beurteilen, ich nutze diese Möglichkeit nicht.
Abhängigkeiten bei Softwareinstallationen zu MAC-Adressen sind mir noch nie begegnet.
Was in diesem Zusammenhang aber zu prüfen ist, ist die Produktaktivierung von Windows XP. Möglicherweise wird hier bei der Aktivierung auch die MAC-Adresse herangezogen. Allerdings weiss ich das nicht genau.
Hartmut
Hier der Auszug zum Thema MAC-Adress-Änderungen:
Maintaining and Changing the MAC Address of a Virtual Machine
When a virtual machine is powered on,GSX Server automatically assigns each of its virtual network adapters an Ethernet MAC address.MAC stands for media access control. A MAC address is the unique address assigned to each Ethernet device. The software guarantees that virtual machines are assigned unique MAC addresses within a given host system.In most cases,the virtual machine is assigned the same MAC address every time it is powered on,so long as the virtual machine is not moved (the path and filename for the virtual machine ’s configuration file must remain the
same)and no changes are made to certain settings in that file.
In addition,GSX Server does its best, but cannot guarantee,to automatically assign unique MAC addresses for virtual machines running on multiple host systems.
Avoiding MAC Address Changes
To avoid changes in the AC address automatically assigned to a virtual machine,you must not move the virtual machine ’s configuration file.oving it to a different host computer or even moving it to a different location on the same host computer changes the MAC address. You also need to be sure not to change certain settings in the virtual machine ’s configuration files.If you never edit the configuration file by hand and do not remove
the virtual Ethernet adapter,these settings remain untouched.If you do edit the configuration file by hand,be sure not to remove or change the following options:
ethernet[n].generatedAddress ethernet[n].addressType ethernet[n].generatedAddressOffset uuid.location uuid.bios ethernet[n].present
In these options,[n] is the number of the virtual Ethernet adapter,for example
ethernet0 .
Note:To preserve a virtual Ethernet adapter ’s MAC address,you also must be careful not to remove it.If you remove the adapter,then recreate it,it may receive a different MAC address.
Manually Assigning a MAC Address
If you want to guarantee that the same AC address is assigned to a given virtual machine every time,even if the virtual machine is moved,or if you want to guarantee a unique MAC address for each virtual machine within a networked environment,you can assign the address manually instead of letting GSX Server assign it automatically.
To assign the same,unique AC address to any virtual machine manually,use a text editor to remove three lines from the configuration file and add one line.The configuration file has a .vmx extension at the end of the filename.On a Linux host,a virtual machine created with an earlier VMware product may have a configuration file with a .cfg extension.
Remove the three lines that begin with the following from the configuration file:
ethernet[n].generatedAddress ethernet[n].addressType ethernet[n].generatedAddressOffset
In these options,[n] is the number of the virtual Ethernet adapter — for example
ethernet0 .
Add the following line to the configuration file :
ethernet0.address = 00:50:56:XX:YY:ZZ
In this line,XX must be a valid hexadecimal number between 00h and 3Fh ,and YY and ZZ must be valid hexadecimal numbers between 00h and FFh .Because GSX Server virtual machines do not support arbitrary MAC addresses,you must use the above format.
So long as you choose a value for XX:YY:ZZ that is unique among your hard-coded addresses (where XX is a valid hexadecimal number between 00h and 3Fh ,and YY and ZZ are valid hexadecimal numbers between 00h and FFh ),conflicts between the automatically assigned MAC addresses and the manually assigned ones should never occur.
Controlling Routing Information for a Host-Only Network on a Linux Host
A host-only network is a full-fledged network.It has a network interface associated with it (V net1)that is marked “up ” at the time the host operating system is booted..
Consequently,routing server processes that operate on the host operating system, such as routed and gated ,automatically discover it and propagate information on how to reach it unless you explicitly configure them not to do so. If either of these programs is being run only to receive routing information,the easiest solution is to run it with a -q option so that it does not supply routing information, only receives it. If,however,they are running because they are to supply routing information,then you
need to configure them so they do not advertise routes to the host-only network.
Unfortunately,the version of routed that comes with many distributions of Linux has no support for specifying that an interface should not be advertised.Consult the routed(8) manual page for your system in case you have a more contemporary version of the software.
For gated ,configuration is involved.You need to explicitly exclude the V net1 interface from any protocol activity.If you need to run virtual Machines on a host-only network on a multihomed system where gated is used and have problems doing so, please contact VMware technical support by submitting a support request at
www.vmware.com/requestsupport .
wert eintragen
