[[PageOutline]] * [http://blog.as-is.net/2006/12/boot-from-san-1.html Ogawa::Buzz: 貧乏人のためのboot-from-SAN (1) 導入編] = VMware Server client = * [http://okyuu.com/ja/tips/3511 VMware Infrastructure ClientでVMware Server 2に接続 ノウハウ(Tips)] * ESXi 3.5付属のVICのログインウインドウで"IPアドレス/名前"にサーバのIPアドレスやFQDNでなく、下記のようにURLを指定すると、VMware Server 2にも接続できる。 {{{ https://127.0.0.1:8333 }}} * 最後に「/」は'''付けないこと'''。 * 4.0付属のvSphere Clientでは別途クライアントサポートファイルが必要な旨のプロンプトが出て接続できない。 * [http://www.natzworks.com/digital/entries/2010/000267.html VMware Server 2.0.2 を VMware Infrastructure Client で管理] == 注意点 == * 「Virtual Hardware Version」が「7」になっているVMのハードウェア構成は、VICからは編集できない(Power on/offは可能)ので、web UIから構成する必要がある。 * [http://d.hatena.ne.jp/k-na_s/20090415/1239798306 VMware Server 2.0.1？ その2 - k-na_sの日記] = install VMware Server 2.0.2 on Ubuntu Lucid (x64) = * インストール前にソースを編集する必要がある * => see [./Server2onLucid] = install VMware Server 2.0.1 on Ubuntu Hardy (x64) = * [http://ubuntuforums.org/showthread.php?t=943036 HOW TO: Install VMware Server 2 without X Server - Ubuntu Forums] * [http://www.howtoforge.com/how-to-install-vmware-server-2-on-an-ubuntu-8.04-desktop How To Install VMware Server 2 On An Ubuntu 8.04 Desktop | HowtoForge - Linux Howtos and Tutorials] * sudo aptitude install -R linux-headers-!`uname -r` build-essential * xinetdは必須ではない模様 * build-essentialの代わりにmake gccでも良い see [#installVMwareToolstoubuntuonVMware] * sudo mkdir /home/vmware * sudo chown USERNAME.GROUPNAME /home/vmware/ * tar xzf VMware-server-2.0.1-156745.x86_64.tar.gz * ~/vmware-server-distrib$ sudo ./vmware-install.pl {{{ Creating a new VMware Server installer database using the tar4 format. Installing VMware Server. (snip) Please specify a port for remote connections to use [902] Please specify a port for standard http connections to use [8222] Please specify a port for secure http (https) connections to use [8333] The current administrative user for VMware Server is ''. Would you like to specify a different administrator? [no] yes Please specify the user whom you wish to be the VMware Server administrator <> Using <> as the VMware Server administrator. In which directory do you want to keep your virtual machine files? [/var/lib/vmware/Virtual Machines] /home/vmware/ Please enter your 20-character serial number. (snip) Starting VMware services: Virtual machine monitor done Virtual machine communication interface done VM communication interface socket family: done Virtual ethernet done Bridged networking on /dev/vmnet0 done Host-only networking on /dev/vmnet1 (background) done DHCP server on /dev/vmnet1 done Host-only networking on /dev/vmnet8 (background) done DHCP server on /dev/vmnet8 done NAT service on /dev/vmnet8 done VMware Server Authentication Daemon (background) done Shared Memory Available done Starting VMware management services: VMware Server Host Agent (background) done VMware Virtual Infrastructure Web Access Starting VMware autostart virtual machines: Virtual machines done The configuration of VMware Server 2.0.1 build-156745 for Linux for this running kernel completed successfully. }}} * UI with IE8 => attachment:VMServer.png * ~~注: VMware on VMwareの場合、入れ子の中のVMは起動不可なので実用にはならない (ESXiはOKだったかもしれず)~~ * attachment:vmonvm.png * see [#VMonVM] = install VMware Server 2.0.1 on CentOS 5 (x86) = * SELinuxが有効だと、ポリシーに抵触してまともに動作しないので注意 * /etc/sysconfig/selinux で SELINUX=disabled とすればとりあえず動くが、根本的にはポリシーを設定するのが正しい * sudo yum install perl * sudo rpm -Uhv VMware-server-2.0.1-156745.i386.rpm {{{ Before running VMware Server for the first time, you need to configure it for your running kernel by invoking the following command: "/usr/bin/vmware-config.pl". }}} * sudo yum install kernel-headers make gcc * sudo vmware-config.pl {{{ The current administrative user for VMware Server is ''. Would you like to specify a different administrator? [no] yes Please specify the user whom you wish to be the VMware Server administrator root Using root as the VMware Server administrator. (snip) In which directory do you want to keep your virtual machine files? [/var/lib/vmware/Virtual Machines] /home/vmware/ The path "/home/vmware" does not exist currently. This program is going to create it, including needed parent directories. Is this what you want? [yes] }}} = Windows XP guest with SCSI HDD = * [http://communities.vmware.com/thread/141936 VMware Communities: Can i change the SSL Cert being used by VMWare Server?] * vmscsi-1.2.0.4.flpをFDDにマウントしてからCD bootしないと、SCSIドライバが無いためHDDにアクセスできないと言われるので注意 = Autostart with host boot = * attachment:autoboot.png * VMware Serverではゲストの自動起動が可能 * ホストの起動に合わせた自動起動は可能だが、自動shutdownのやり方は不明(ここでただ設定するだけでは不足？) = vmrun = * [http://plaza.rakuten.co.jp/u703331/diary/200907270000/ VMware Serverメモ - さすらいのプログラマ - 楽天ブログ（Blog）] * [http://genki01.cc.hokudai.ac.jp/reo/diary/?date=20081125 負け組日記 - VMware Server 2.0] * vmrun -> [./vmrun] = install VMware Tools to ubuntu on VMware = * sudo aptitude install -R linux-headers-!`uname -r` make gcc * sudo mount /dev/cdrom /media/cdrom0/ * tar -xzf /media/cdrom/VMwareTools-7.8.5-156735.tar.gz * ~/vmware-tools-distrib$ sudo ./vmware-install.pl --default * [http://ubuntuforums.org/showthread.php?t=294384 looking for /usr/src/linux/version.h - Ubuntu Forums] = install VMware Tools to CentOS on VMware = * sudo mount /dev/cdrom /media/ * sudo rpm -Uhv /media/VMwareTools-7.7.5-156745.i386.rpm {{{ Before running VMware Tools for the first time, you need to configure it for your running kernel by invoking the following command: "/usr/bin/vmware-config-tools.pl". }}} * sudo yum install perl * sudo vmware-config-tools.pl --default = cannot copy vmscsi.sys = * VMへのWindows XPインストールの際、FDDにvmscsi-1.2.0.4.flpをマウントしているのにも関わらず、「vmscsi.sysがコピーできない」旨のエラーメッセージが出ることがある。 * ServicePackなどを手動で統合したCDで、winnt.sifに特定の記述があるとこのエラーが出る。 * [http://communities.vmware.com/thread/119963 VMware Communities: setup cannot copy vmscsi.sys] * [http://communities.vmware.com/message/344803#344803 VMware Communities: Creating Windows XP VM on ESX server] * doesn't seem like a vmware problem. seems like your XP PRO has the OEMPREINSTALL set to YES. is this a custom XP install disk? check the WINNT.sif file in the i386 folder. Make sure the OEMPREINSTALL=no. I have built custom install before and if the OEMPREINSTALL is set to yes it will not copy new drivers into the INSTALL directory. * winnt.sifから「OemPreinstall=Yes」を取り除くことで解決する。 = add new Virtual Switch to VMware Server = * VMware Serverでは、Workstationの「仮想ネットワークの設定」や「チーム LAN セグメント」あるいはESXiのように、GUIのみを使って簡単に仮想ネットワークを追加することができない。 * => [./ServerNetworking] = misc = * attachment:snapshot.png * VMware ServerはWorkstationと違い、スナップショットは一つのみ可能 == VM on VM == * きちんと設定されていないと次のように表示される => attachment:vmsvonvmws.png * [http://communities.vmware.com/docs/DOC-8970 VMware Communities: Running Nested VMs] * VMware製品各種での設定がまとめられている * 実用的な実行速度で動かすためのハードウェア条件 * Intel VT-x * AMD-v with Barcelona or Phenom or later * AMD-V is supported on Rev F and later Family 0FH AMD64 processors, but current VMware products only support AMD-V on Family 10H or later AMD64 processors (Barcelona or Phenom). Thus, you can use AMD-V on Family 0FH Rev F and Rev G processors with Workstation 6.0. However, you need a Family 10H processor to use AMD-V with ESX 3.5 and Workstation 6.5 (or later). * 手持ちの「AMD Athlon 64 X2 5000+」では「MONITOR MODE: allowed modes : BT」となり、AMD-v使用不能。 * vmxファイルに以下の2行を追加すると可能になる(非Intel-VT, 非AMD-V環境では未テスト) {{{ monitor_control.vt32 = "TRUE" monitor_control.restrict_backdoor = "TRUE" }}} * IntelCPU+x64GuestだとVTが必須なので自動的に有効になる {{{ Software virtualization is incompatible with long mode on this platform. Virtual execution will begin in software mode, but will automatically switch to hardware mode if the guest enters long mode. }}} * それ以外の環境では、次の1行もあった方が良いかも知れない(入れ子内のVMguestの起動が非常に遅くなり得る) {{{ monitor.virtual_exec = "hardware" }}} == VMware Workstation == * Ubuntu 10.04 lucid on VMware Workstation 7.1.3 with Windows 7 x64 Host * Linux ubuntu32 2.6.32-26-generic #48-Ubuntu SMP Wed Nov 24 09:00:03 UTC 2010 i686 GNU/Linux * model name : Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz * 仮想マシン設定 > ハードウェア > プロセッサ > 優先モード * 自動 * vmware.log {{{ Dec 12 17:27:11.858: vmx| MONITOR MODE: allowed modes : BT32 HV Dec 12 17:27:11.858: vmx| MONITOR MODE: user requested modes : BT32 HV HWMMU Dec 12 17:27:11.858: vmx| MONITOR MODE: guestOS preferred modes: HWMMU BT32 HV Dec 12 17:27:11.858: vmx| MONITOR MODE: filtered list : BT32 HV Dec 12 17:27:11.858: vmx| HV Settings: virtual exec = 'dynamic'; virtual mmu = 'software' }}} * /proc/cpuinfo {{{ flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht nx lm constant_tsc arch_perfmon pebs bts tsc_reliable aperfmperf pni ssse3 cx16 hypervisor lahf_lm ida }}} * Intel VT-xまたはAMD-V * diff of Ubuntu32.vmx {{{ -monitor.virtual_mmu = "automatic" -monitor.virtual_exec = "automatic" +monitor.virtual_mmu = "software" +monitor.virtual_exec = "hardware" }}} * vmware.log {{{ Dec 12 17:53:28.574: vmx| MONITOR MODE: allowed modes : BT32 HV Dec 12 17:53:28.574: vmx| MONITOR MODE: user requested modes : HV Dec 12 17:53:28.574: vmx| MONITOR MODE: guestOS preferred modes: HWMMU BT32 HV Dec 12 17:53:28.574: vmx| MONITOR MODE: filtered list : HV Dec 12 17:53:28.574: vmx| HV Settings: virtual exec = 'hardware'; virtual mmu = 'software' }}} * /proc/cpuinfo {{{ flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht nx lm constant_tsc arch_perfmon pebs bts tsc_reliable aperfmperf pni ssse3 cx16 hypervisor lahf_lm ida }}} * 元々が「自動」だからなのか、CPU flagsに変化はなかった。