Version 9 (modified by mitty, 14 years ago) (diff) |
---|
- VMware Communities: How to tell current config of VMNETs? ...
- Hurricane Labs Engineering Notes: Adding VMware Bridge Interfaces..... While Your Server is LIVE
- vmware-config.plを使わず(稼働中のVMをshutdownせず)に、vmnetを物理NICにbridgeする手法が書かれている。
- VMware Workstation for LinuxのGUI版Virtual Network Editorを移植すれば、Serverでも同様に使える模様。(もちろんconsole環境からは使えない)
- VMware Communities: why vmware delete "Virtual Network ...
- It is. Unfortunately we didn't have time to do all the packaging and testing work to get the editor in to Server 2.0. However, if you copy it over there manually, it'll work (or if you hack your installation so that you can install Server 2.0 and Workstation 6.5 side-by-side, which is wildly unsupported but can be done).
- VMware Communities: virtual network editor disapeared? ...
- The Virtual Network configuration tool is also missing from VMWare Player 3.1 for Linux. Unfortunately it doesn't seem to be included in the installation package; at least I can't find it. Anyway I've found a way to get vmnetcfg for Player on Linux (its not pretty).
- GUI版Virtual Network Editorを移植する具体的手順が書かれている。
- VMware Communities: why vmware delete "Virtual Network ...
add and customize Virtual Network on VMware Server
- VMware Workstationでは「仮想ネットワークの設定」や「チーム LAN セグメント」によって、ESXiではvSphere Clientから仮想ネットワークをGUIのみを使って簡単に増設・設定できるが、VMware Serverにおいては、web UIからはそもそも設定以前に、ネットワーク構成の詳細を知ることも出来ない。
- Linux ホストOS上でvmware-config.plを用いて増設・設定をする手順を以下にまとめる。
- Ubuntu Lucid上でvmware-config.plが動かない問題については => Server2onLucid?
initial state
- attachment:3nics_with_vic.png
- attachment:3nics_with_web.png
. vmnet0 is bridged to eth0 . vmnet1 is a host-only network on private subnet 172.16.211.0. . vmnet8 is a NAT network on private subnet 192.168.81.0.
add isolated networks
- sudo vmware-config.pl
Would you like to skip networking setup and keep your old settings as they are? (yes/no) [yes] no (snip) Would you prefer to modify your existing networking configuration using the wizard or the editor? (wizard/editor/help) [wizard] help The wizard will present a series of questions that will help you quickly add new virtual networks. However, you cannot remove networks or edit existing networks with the wizard. To remove or edit existing networks, you should use the editor.
- wizardでは、Bridge, NAT, host-onlyの設定しかできず、Workstationにおける「チーム LAN セグメント」を追加することが出来ないので、editorを選択する。
Would you prefer to modify your existing networking configuration using the wizard or the editor? (wizard/editor/help) [help] editor The following virtual networks have been defined: . vmnet0 is bridged to eth0 . vmnet1 is a host-only network on private subnet 172.16.211.0. . vmnet8 is a NAT network on private subnet 192.168.81.0. Do you wish to make any changes to the current virtual networks settings? (yes/no) [no] yes Which virtual network do you wish to configure? (0-254) 2 What type of virtual network do you wish to set vmnet2? (bridged,hostonly,nat,none) [none] b Configuring a bridged network for vmnet2. Please specify a name for this network. [Bridged] Bridged to none All your ethernet interfaces are already bridged. Are you sure you want to configure a bridged ethernet interface for vmnet2? (yes/no) [no] yes Your computer has the following ethernet devices: eth0. Which one do you want to bridge to vmnet2? [eth0] none The following virtual networks have been defined: . vmnet0 is bridged to eth0 . vmnet1 is a host-only network on private subnet 172.16.211.0. . vmnet2 is bridged to none . vmnet8 is a NAT network on private subnet 192.168.81.0. Do you wish to make additional changes to the current virtual networks settings? (yes/no) [yes] Which virtual network do you wish to configure? (0-254) 3 What type of virtual network do you wish to set vmnet3? (bridged,hostonly,nat,none) [none] The following virtual networks have been defined: . vmnet0 is bridged to eth0 . vmnet1 is a host-only network on private subnet 172.16.211.0. . vmnet2 is bridged to none . vmnet8 is a NAT network on private subnet 192.168.81.0. Do you wish to make additional changes to the current virtual networks settings? (yes/no) [yes] no (snip)
- 「none」という存在しないデバイスへブリッジされた仮想ネットワークvmnet2が作成される
- ls /dev/vmnet*
crw------- 1 root root 119, 0 2010-06-08 16:59 /dev/vmnet0 crw------- 1 root root 119, 1 2010-06-08 16:59 /dev/vmnet1 crw------- 1 root root 119, 2 2010-06-08 17:01 /dev/vmnet2 crw------- 1 root root 119, 3 2010-06-08 16:59 /dev/vmnet3 crw------- 1 root root 119, 4 2010-06-08 16:59 /dev/vmnet4 crw------- 1 root root 119, 5 2010-06-08 16:59 /dev/vmnet5 crw------- 1 root root 119, 6 2010-06-08 16:59 /dev/vmnet6 crw------- 1 root root 119, 7 2010-06-08 16:59 /dev/vmnet7 crw------- 1 root root 119, 8 2010-06-08 16:59 /dev/vmnet8 crw------- 1 root root 119, 9 2010-06-08 16:59 /dev/vmnet9
- これらは、vmware-config.pl内で「Do you want networking for your virtual machines? (yes/no/help) [yes]」と応えた際に自動的に作成される。
- VMware Infrastructure Clientによる設定画面
- web UIでは、「Bridged to none」デバイスのみが追加されたように見える
- 再起動すると、vmnet2以外は消えてしまう
- sudo reboot
- ll /dev/vmnet*
crw------- 1 root root 119, 0 2010-06-08 17:30 /dev/vmnet0 crw------- 1 root root 119, 1 2010-06-08 17:30 /dev/vmnet1 crw------- 1 root root 119, 2 2010-06-08 17:30 /dev/vmnet2 crw------- 1 root root 119, 8 2010-06-08 17:30 /dev/vmnet8
- attachment:only_vmnet2_is_remained.png
VI Clientからの設定
- vmware-config.plからは特に操作されていないvmnet9に対して、再起動前にVI Clientから操作を行った場合も、再起動後には消えてしまう
- attachment:vmnet9-1-property.png
- Port Groupが設定されていない
- attachment:vmnet9-2-add_port.png
- VMとの接続に使う仮想ネットワークとしての選択肢が提示される
- これがESXiであれば、ESXiのManager Networkとして使う選択肢も提示される
- attachment:vmnet9-3-network_label.png
- Network Labelの設定
- attachment:vmnet9-4-new_label.png
- Labelを適当に設定
- attachment:vmnet9-5-labeled.png
- 「interVM Network」というラベルが設定された
- attachment:vmnet9-6-finish_configuration.png
- 設定完了
- attachment:vmnet9-7-VM_networking.png
- VMの設定画面でも、接続する仮想ネットワーク候補として提示されるようになる
- attachment:vmnet9-webUI.png
- web UIの方にも出現する
- attachment:vmnet9-8-rebooted.png
- しかし、再起動すると消えてしまう
- attachment:vmnet9-webUI_rebooted.png
- web UIの方でも一覧から消えてしまう
- attachment:vmnet9-1-property.png
without vmware-config.pl
- Hurricane Labs Engineering Notes: Adding VMware Bridge Interfaces..... While Your Server is LIVE
- source:/trunk/TipAndDoc/vmware/hotaddbridge
- オリジナル(上記サイトのコメント)との違い
- キャラクタスペシャルファイルの存在確認が間違っているのを修正
- 再起動後もvmnetが消えてしまわないように、locationsへ追記
- 引数に「-d」があるときは、実在しないデバイス名を与えても無視して設定する
- どこにもブリッジされない(つまり隔離された)仮想ネットワークが作成される
- オリジナル(上記サイトのコメント)との違い
Attachments (15)
- 3nics_with_vic.png (22.3 KB) - added by mitty 15 years ago.
- 3nics_with_web.png (159.8 KB) - added by mitty 14 years ago.
- 10nics.png (38.7 KB) - added by mitty 14 years ago.
- only4nics_appear_in_web.png (153.3 KB) - added by mitty 14 years ago.
- only_vmnet2_is_remained.png (24.3 KB) - added by mitty 14 years ago.
- vmnet9-1-property.png (19.4 KB) - added by mitty 14 years ago.
- vmnet9-2-add_port.png (18.7 KB) - added by mitty 14 years ago.
- vmnet9-3-network_label.png (21.4 KB) - added by mitty 14 years ago.
- vmnet9-4-new_label.png (21.4 KB) - added by mitty 14 years ago.
- vmnet9-5-labeled.png (20.8 KB) - added by mitty 14 years ago.
- vmnet9-6-finish_configuration.png (22.9 KB) - added by mitty 14 years ago.
- vmnet9-7-VM_networking.png (31.4 KB) - added by mitty 14 years ago.
- vmnet9-8-rebooted.png (24.3 KB) - added by mitty 14 years ago.
- vmnet9-webUI.png (164.7 KB) - added by mitty 14 years ago.
- vmnet9-webUI_rebooted.png (155.3 KB) - added by mitty 14 years ago.
Download all attachments as: .zip