Version 31 (modified by mitty, 12 years ago) (diff) |
---|
- VMware Communities: Purpose of GuestAppsCache files?
- VM-sickbay » Blog Archive » How to disable Unity for all VMs in WS 7.1
isolation.tools.unity.disable = “true”
- VMware Communities: Workstation 7.1 caches directory?
You would have to create the config.ini file, and it would go in your %APPDATA%\VMware directory (alongside the preferences.ini file).
- C:\Users\mitty\AppData\Roaming\VMware\config.ini など
isolation.tools.unity.disable = "true"
- C:\Users\mitty\AppData\Roaming\VMware\config.ini など
- VM-sickbay » Blog Archive » How to disable Unity for all VMs in WS 7.1
- VMware Workstation6のゲストOSでUSBブートを試してみるテスト - Y型ヒキコモリ日誌
調べるまで知らなかったけど、USBブートってHDDそのままの構造なんですね。という事は、VMwareでもHDDとしてマウントしてあげれば、USBメモリをブートディスクとして使えるはず?
- VMware Communities: Enable Routing between NAT Guest and Physical Host Subnets
Okay...after a lot of digging, I found out that this is not possible within OOTB VMWare Workstation.
- VMware Communities: VMware Workstation Guest OS with NAT Can Only Communicate with Host
Yeah, preferrably I need to figure out how to access the guest OS's from the physical network...
- VMware Communities: VMware Workstation Guest OS with NAT Can Only Communicate with Host
VMware Workstation for Linux without X
- X11Forwardingを用いることで、Xが入っていないホストでも動作可能
- VmWare8起動時 に ~/.vmware/dndlogs/dndlog.conf がないよ、と怒られる問題 - おもてなしの空間
% mkdir -p ~/.vmware/dndlogs/ && touch ~/.vmware/dndlogs/dndlog.conf
インストーラをX11forward経由で起動する場合、root権限が必要となる関係からroot login via sshが必要となる- PuTTY X11 proxy: MIT-MAGIC-COOKIE-1 data did not match
- => wiki:TipAndDoc/network/ssh#X11Forwardingwithanotheruser
- CygwinのX Serverでも十分実用に耐える
- 以下のようなエラーが出て、ゲストを起動できないことがある
Could not open /dev/vmmon: No such file or directory.
- lsmod | grep vm で何も出ない場合は、sudo service vmware start
Ubuntu 10.04
- X11forwardingでVMware WSを使用する際に必要となるパッケージ
- Ubuntu 10.04.2 x86_64 (Linux hostname 2.6.32-31-generic #61-Ubuntu SMP Fri Apr 8 18:25:51 UTC 2011 x86_64 GNU/Linux)
- build-essential
- kernel moduleをbuildするために必要
- gconf2
bash: gconftool-2: command not found
- x11-utils
LOG NOT INITIALIZED | Unable to spawn xprop to determine whether accessibility is enabled or not.
- libxrandr2
/usr/lib/vmware/bin/vmware-vmx: error while loading shared libraries: libXrandr.so.2: cannot open shared object file: No such file or directory
not required
- 必須ではない(と思われる)パッケージ
- 無くてもVMの起動そのものには支障がない模様
- libglu-dev (Provided by: libglu1-mesa-dev)
- libasound2
Failed to load Alsa sound library: libasound.so: cannot open shared object file: No such file or directory. Alsa sound will not be used.
Debian 6.0
- 必要なパッケージ
- build-essential gconf2 x11-utils ia32-libs libxrandr2 libgtkmm-2.4-1c2a libglu-dev libasound2 ttf-vlgothic linux-headers-$(uname -r)
- VMware Workstation 8 on Debian 6.0 x86_64では、insservまわりでエラーが出る
- aptitude install ... で次のようなエラー
- $ sudo aptitude install -R mdadm
(snip) insserv: warning: script 'S50vmware-USBArbitrator' missing LSB tags and overrides insserv: warning: script 'vmware' missing LSB tags and overrides insserv: warning: script 'vmware-workstation-server' missing LSB tags and overrides insserv: warning: script 'vmware-USBArbitrator' missing LSB tags and overrides insserv: There is a loop at service munin-node if started insserv: There is a loop between service vmware-USBArbitrator and checkroot if started (snip)
- vmwareのinitスクリプト修正for Squeeze - labunix の ラボゆにっくす
- amd64版で module-init-tools を update したら、設定が失敗する問題 - おもてなしの空間 => 採用
- Fixing VMware Workstation 8 and insserv | schlü.tech
- Debian User Forums • View topic - |Solved| Vmware errors when I use apt-get, aptitude, etc.
- 下の内容の /etc/insserv/overrides/vmware というファイルを作って、実行パーミッションを立てる
### BEGIN INIT INFO # Provides: vmware # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # X-Start-Before: # X-Stop-After: # Default-Start: 2 3 5 # Default-Stop: 0 6 # Short-Description: This service starts and stops VmWare sercices # Description: c.f. http://forums.debian.net/viewtopic.php?f=5&t=73507 ### END INIT INFO
- /etc/insserv/overrides/vmware-USBArbitrator というファイルも同様に作って実行パミッションを立てる
### BEGIN INIT INFO # Provides: vmware-USBArbitrator # Required-Start: $local_fs # Required-Stop: $local_fs # X-Start-Before: # X-Stop-After: # Default-Start: 2 3 5 # Default-Stop: 2 3 5 # Short-Description: This services starts and stops the USB Arbitrator daemon when vmware starts ### END INIT INFO
- /etc/insserv/overrides/vmware-vmware-workstation-server
### BEGIN INIT INFO # Provides: vmware-workstation-server # Required-Start: $network vmware vmware-USBArbitrator hal # Required-Stop: $network vmware vmware-USBArbitrator hal # X-Start-Before: # X-Stop-After: # Default-Start: 2 3 5 # Default-Stop: 0 6 # Short-Description: This service starts and stops the Workstation as a Server ### END INIT INFO
- 以下を実行
% cd /etc/insserv/overrides % sudo insserv -r vmware-workstation-server % sudo insserv -r vmware-USBArbitrator % sudo insserv -r vmware % sudo insserv vmware % sudo insserv vmware-USBArbitrator % sudo insserv vmware-workstation-server
- munin-nodeと干渉した
- /etc/insserv/overrides$ sudo insserv -r vmware-workstation-server
insserv: warning: script 'vmware-workstation-server' missing LSB tags and overrides insserv: There is a loop between service munin-node and vmware-workstation-server if stopped insserv: loop involving service vmware-workstation-server at depth 2 insserv: loop involving service munin-node at depth 1 insserv: Stopping vmware-workstation-server depends on munin-node and therefore on system facility `$all' which can not be true! insserv: exiting now without changing boot order!
- いったんmunin-nodeをremoveしてからinsservするか(スマートには回避出来ず…)
- munin-nodeをインストールする前にVMware WSをインストールしておくことが必要
- /etc/insserv/overrides$ sudo insserv -r vmware-workstation-server
- |VMware||Debian| VMwarePlayerの影響がinsservが引っかかる - わんこ日記(2011-11-22)
3.2.0-0.bpo.2-amd64
- SlackBlogs: VMWare Workstation 8.0.2 and Linux Kernel 3.2 Patch
- vmware workstation 8.0.2 7.1.5 / player 4.0.2 3.1.5 fixes for linux 3.2 and linux 3.3 | Weltall's blog
- $ wget http://weltall.heliohost.org/wordpress/wp-content/uploads/2012/01/vmware802fixlinux320.tar.gz
- $ cd /usr/lib/vmware/modules/source/
- /usr/lib/vmware/modules/source$ sudo tar xf vmnet.tar
- /usr/lib/vmware/modules/source$ sudo tar xzf /home/mitty/vmware802fixlinux320.tar.gz
- /usr/lib/vmware/modules/source$ sudo patch -p1 < vmware3.2.0.patch
patching file vmnet-only/filter.c patching file vmnet-only/netif.c patching file vmnet-only/userif.c
- /usr/lib/vmware/modules/source$ sudo tar cf vmnet.tar vmnet-only/
- vmware を再起動 -> 自動でモジュールがビルドされる
input underscore to Guest OS
- 参考になるが、以下では解決しなかった
.vmware/config
- 以下で解決
- 仮想サーバの構築(VMware Server)
■ゲストOSで'_'(アンダーバー)が入力できない
- 仮想サーバの構築(VMware Server)
- mitty@hades:~$ cat > .vmware/config
xkeymap.language = jp106 xkeymap.keycode.211 = 0x073
- mitty@hades:~$ sudo service vmware restart
kernel update
- ホストのカーネルがバージョンアップしバージョンナンバーが変わるとカーネルモジュールのリビルドが必要
- vmwareコマンドでGUIを起動しようとすると、自動でリビルドが走る
- rootで実行しないといけない場合がある模様
kernel.sched_compat_yield
- マルチコア(マルチCPU)構成のゲストを起動しようとすると、以下の質問をされる
The host's Linux kernel yield() functionality is disabled. Multiprocessor virtual machines exhibit degraded performance without yield(). Choose 'OK' to enable the sysctl 'kernel.sched_compat_yield' or 'Cancel' to continue without yield().
- ここでOKとすると、一時的に /proc/sys/kernel/sched_compat_yield = 1 となるが、再起動するとこの設定は揮発する
- /etc/sysctl.d/30-vmware-player
kernel.sched_compat_yield=1
- ファイル名に.confが付かないと読み込まれないので、ファイル名を変更する
- $ sudo mv /etc/sysctl.d/30-vmware-player /etc/sysctl.d/30-vmware-player.conf
- see also vmware:1027987
Promiscuous Mode
- デフォルトではPromiscuous Modeは仮想NICに対して使用出来ない
- vmware:287 Using Virtual Ethernet Adapters in Promiscuous Mode on a Linux Host
VMware software does not allow the virtual Ethernet adapter to go into promiscuous mode unless the user running the VMware software has permission to make that setting. This follows the standard Linux practice that only root can put a network interface into promiscuous mode.
One way to do this is to create a new group, add the appropriate users to the group, and give that group read/write access to the appropriate device. These changes need to be made on the host operating system as root (su). For example:
chgrp newgroup /dev/vmnet0 chmod g+rw /dev/vmnet0
If you want all users to be able to set the virtual network adapter (/dev/vmnet0 in our example) to promiscuous mode, you can simply run the following command on the host operating system as root:
chmod a+rw /dev/vmnet0
- Hostを再起動すると元に戻るので注意(udevの設定をする必要があると書かれているが未検証)
- VMware Communities: Promiscuous Mode and LAN Segments
Well, Linux host? In that case it seems that code is using /dev/vmnet0 when it meets with PVN.
Attachments (14)
- dndlog.conf.png (9.1 KB) - added by mitty 14 years ago.
- vmware-ws-installer.png (56.9 KB) - added by mitty 14 years ago.
- unable_change_power_state.png (31.0 KB) - added by mitty 13 years ago.
- Failed_to_ load_GLU.png (4.9 KB) - added by mitty 13 years ago.
- 3D_disabled.png (5.5 KB) - added by mitty 13 years ago.
- libasound.png (21.3 KB) - added by mitty 13 years ago.
- underscore_xp.png (64.5 KB) - added by mitty 13 years ago.
- underscore_bsd.png (47.6 KB) - added by mitty 13 years ago.
- kb880943.png (99.2 KB) - added by mitty 13 years ago.
- xkeymap.png (29.0 KB) - added by mitty 13 years ago.
- sched_compat_yield.png (25.8 KB) - added by mitty 13 years ago.
- kernel-update.png (21.9 KB) - added by mitty 13 years ago.
- PromiscuousMode.png (29.6 KB) - added by mitty 13 years ago.
- no_3d_support.png (12.0 KB) - added by mitty 12 years ago.
Download all attachments as: .zip