[데스크탑] VMware 설치 및 사용법

### VMware 설치 사용법 ###

설치사양: P-III 700

메모리: 256M

기본OS: ALZZA LINUX 6.2 (kernel 2.2.16)

가상OS: Win2000

설치에 앞서서 자신의 홈디렉토리에 .vmware 라는 디렉토리를 만들고 license

파일을 그 디렉토리 안에다가 놓아둡니다. 그런후

root 권한으로 VMware-2.x.x.rpm 을 설치합니다.

[root@zzang911 root]# rpm -Uvh VMware-2.0-476.i386.rpm

그런후 Shell 에서 다음과 같이 입력합니다.

[root@zzang911 root]# vmware-config.pl

————————————————————————–

Making sure VMware’s services are stopped.

Stopping VMware services:

   Virtual machine monitor          [  OK  ]

You must read and accept the End User License Agreement to continue.

Press enter to display it.      –<그냥 엔터>

VMware, Inc. End User License Agreement

Notice to User: This End User License Agreement (EULA) is a CONTRACT

between you (either an individual or a single entity) and VMware,

Inc. (VMware), which covers your use of either “VMware for Linux” or

“VMware for Windows NT and Windows 2000” and related software components,

which may include associated media, printed materials, and “online” or

electronic documentation.  All such software and materials are referred to

here as the “Software Product.” If you do not agree to the terms of this

EULA, then do not install or use the Software Product.  By explicitly

accepting this EULA, however, or by installing, copying, downloading,

accessing or otherwise using the Software Product and/or license key,

you are acknowledging and agreeing to be bound by the following terms:

1. WARNING — (for Evaluation Licenses only).

This Software Product can be used in conjunction with a free evaluation

license and associated license key  If you are using such an evaluation

license, you may use the Software Product only to evaluate its suitability

for purchase. Evaluation licenses have an expiration date; you may renew

your evaluation license at the VMware web site. VMWARE BEARS NO LIABILITY

FOR ANY DAMAGES RESULTING FROM USE (OR ATTEMPTED USE AFTER THE

EXPIRATION DATE) OF THE SOFTWARE PRODUCT, AND HAS NO DUTY TO

PROVIDE ANY SUPPORT.

–

–

–

어쩌구 저쩌구 …쌀라쌀라…

–

14. Governing Law; Entire Agreement.

This EULA is governed by the laws of the State of California, U.S.A.,

excluding the application of its conflict of law rules.  The United

Nations Convention for the International Sale of Goods shall not apply.

This EULA is the entire agreement between us and supersedes any other

communications or advertising with respect to the Software Product;

this EULA may be modified only by written agreement signed by authorized

representatives of you and VMware.

15. Contact Information

If you have any questions about this EULA, or if you want to contact

VMware for any reason, please contact VMware: VMware, Inc., 3145 Porter

Drive, Building F, Palo Alto, CA 94304, United States of America or

email info at vmware.com.

질문시에는 그냥 enter 하세요.

Do you accept? (yes/no)yes

Thank you.

Trying to find a suitable vmmon module for your running kernel.

None of VMware’s pre-built vmmon modules is suitable for your running kernel. Do

you want this script to try to build the vmmon module for your system (you need

to have a C compiler installed on your system)? [yes] yes

What is the location of the directory of C header files that match your running

kernel? [/usr/src/linux/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

make: Entering directory `/tmp/vmware-config0/vmmon-only’

make[1]: Entering directory `/tmp/vmware-config0/vmmon-only’

make[2]: Entering directory `/tmp/vmware-config0/vmmon-only/driver-2.2.16-3.azsmp’

make[2]: Leaving directory `/tmp/vmware-config0/vmmon-only/driver-2.2.16-3.azsmp’

make[2]: Entering directory `/tmp/vmware-config0/vmmon-only/driver-2.2.16-3.azsmp’

make[2]: Leaving directory `/tmp/vmware-config0/vmmon-only/driver-2.2.16-3.azsmp’

make[1]: Leaving directory `/tmp/vmware-config0/vmmon-only’

make: Leaving directory `/tmp/vmware-config0/vmmon-only’

The module loads perfectly in the running kernel.

Making sure that both the parport and parport_pc kernel services are available.

Trying to find a suitable vmppuser module for your running kernel.

None of VMware’s pre-built vmppuser modules is suitable for your running kernel.

Do you want this script to try to build the vmppuser module for your system (you

need to have a C compiler installed on your system)? [yes] yes  –< 당근 yes 겠죠 >

Extracting the sources of the vmppuser module.

Building the vmppuser module.

make: Entering directory `/tmp/vmware-config0/vmppuser-only’

make: Leaving directory `/tmp/vmware-config0/vmppuser-only’

The module loads perfectly in the running kernel.

The module loads perfectly in the running kernel.

Do you want this script to automatically configure your system to allow your

Virtual Machines to access the host filesystem? (yes/no/help) yes

The version of Samba used in this version of VMware is licensed as described in

the “/usr/doc/vmware/SAMBA-LICENSE” file.

Hit enter to continue.

Enabling networking (this is required to share the host filesystem).

Extracting the sources of the vmppuser module.

Building the vmppuser module.

make: Entering directory `/tmp/vmware-config0/vmppuser-only’

make: Leaving directory `/tmp/vmware-config0/vmppuser-only’

The module loads perfectly in the running kernel.

Do you want this script to automatically configure your system to allow your

Virtual Machines to access the host filesystem? (yes/no/help) yes

The version of Samba used in this version of VMware is licensed as described in

the “/usr/doc/vmware/SAMBA-LICENSE” file.

Hit enter to continue.

Enabling networking (this is required to share the host filesystem).

Trying to find a suitable vmnet module for your running kernel.

None of VMware’s pre-built vmnet modules is suitable for your running kernel. Do

you want this script to try to build the vmnet module for your system (you need

to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmnet module.

Building the vmnet module.

make: Entering directory `/tmp/vmware-config0/vmnet-only’

make: Leaving directory `/tmp/vmware-config0/vmnet-only’

The module loads perfectly in the running kernel.

Enabling host-only networking (this is required to share the host filesystem).

Do you want this script to probe for an unused private subnet? (yes/no/help)

[yes]

ng for an unused private subnet (this can take some time).

The subnet 172.16.22.0/255.255.255.0 appears to be unused.

Press enter to display the DHCP server copyright information.

The VMware host-only networking support uses a customized version

of the DHCP server application distributed by the Internet Software

Consortium (ISC).  This software is used in compliance with their

copyright notice which appears in its entirety below.

Please note that it is NOT advised that you use our customized

server for normal DHCP service; you can retrieve this software

directly from the ISC (http://www.isc.org).

#

# Copyright (c) 1996, 1997, 1998 The Internet Software Consortium.

# All rights reserved.

#

# Redistribution and use in source and binary forms, with or without

# modification, are permitted provided that the following conditions

# are met:

#

–

–

–

–

어쩌구 저쩌구….

–

–

–

This system appears to have a CIFS/SMB server (Samba) configured for normal use.

If this server is intended to run, you need to make sure that it will not

conflict with the Samba server setup on the private network (the one that we use

to share the host filesystem). Please check your /etc/smb.conf file so that:

. The “interfaces” line does not contain “172.16.22.1/255.255.255.0”

. There is a “socket address” line that contains only your real host IP address

Hit enter to continue.         < 그냥 엔터 >

Starting VMware services:

   Virtual machine monitor          [  OK  ]

   Virtual bidirectional parallel port                     [  OK  ]

   Virtual ethernet                 [  OK  ]

   Bridged networking               [  OK  ]

   Host-only and samba networking (background)             [  OK  ]

You have successfully configured VMware to allow your Virtual Machines to access

the host filesystem. Would you like to add a username and password for accessing

your host filesystem at this time? (yes/no/help) [yes]

Please specify a username that is known to your host: alang  <호스트네임>

New SMB password: <삼바패스워드>

Retype new SMB password:

Added user alang.

Password changed for user alang.

You have successfully configured VMware to allow your Virtual Machines to access

the host filesystem.  Your system appears to already be set up with usernames

and passwords for accessing the host filesystem.  Would you like to add another

username and password at this time? (yes/no/help) [no] 기본값이 No 이니깐…no

You can add more usernames at any time by invoking the following command as

root: “/usr/bin/vmware-smbpasswd vmnet1 -a <username>”

The configuration of VMware 2.0 build-476 for Linux for this running kernel

completed successfully.

You can now run VMware by invoking the following command: “/usr/bin/vmware”.

Enjoy,

–the VMware team

이제 설치는 끝이 난거 같네요..

###### VMware 프로그램 설정 ####

이제 프로그램을 실행해 볼까요..

[root@zzang911 /root]# vmware

그러면 초기 실행 상태가 됩니다.

file -> Wizard 을 실행하면 configure wizard 창 이 뜹니다.

여기선 그냥 next ..

그럼 Guest operating system 선택이 나옵니다. 여기서는 win2000을 선택합니다.

(물런 다른 OS 를 사용하시면 다른걸 선택하시면 되고요..)

다음으로  Virtual Machine Directory 설정이 나옵니다. 앞에 설치환경에 맞추어

설정되어져 있습니다. 그럼 다음으로

Disk type setting 부분입니다.

여기서 win2000을 새로 설치할것인지 아님 기존에 설치된것을 사용할것인지 선택.

raw disk permision setting 입니다. 읽기 쓰기 권한을 다 줍니다.

그런 다음 cdrom, floppy, network 설정부분이 나오는데 그냥 기본으로 하시면

됩니다.

그런뒤 설정된 conf파일을 이용하여 상위 메뉴의 power on 을 누르면 ok..

그럼 시스템 초기화 화면이 나타나는데 ….아마 이런 에러가 뜰것입니다.

” vmware internal moniter error (bug 455) ”

이때는 http://www.vmware.com/support/reference/win/acpihal_w2k.html 로 가시면

해결방법이 나와져 있는데 간단히 소개하면…

win2000 으로 부팅을 하시고 도스창을 열어놓고 …Windows 2000 installation CD

를 삽입합니다.

그런뒤 도스창에다가 다음과 같이 입력합니다.

expand D:\\I386\\HAL.DL_ C:\\WINNT\\SYSTEM32\\VMHAL.DLL

expand D:\\I386\\NTOSKRNL.EX_ C:\\WINNT\\SYSTEM32\\VMOSKRNL.EXE

여기는 D:\\ 는 CD-ROM drive 입니다.

그런뒤 boot.ini 파일을 수정해야 하는데 속성을 먼저 바꾸도록 하죠.

attrib c:\\boot.ini -s -h -r

#### Sample boot.ini Files #####

boot.ini 수정 전 파일

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\\WINNT

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\\WINNT=”Microsoft Windows 2000 Advanced Server”

/fastdetect

boot.ini 수정 후 파일

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\\WINNT

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\\WINNT=”Microsoft Windows 2000 Advanced Server”

/fastdetect

multi(0)disk(0)rdisk(0)partition(1)\\WINNT=”Microsoft Windows 2000 Advanced Server Virtual

Machine” /fastdetect /KERNEL=VMOSKRNL.EXE /HAL=VMHAL.DLL

이렇게 수정하시고 다시 리눅스로 부팅하시어 vmware를 실행하시면해결이 됩니다.

### 그래픽 카드 설정 ###

이제 VGA Card 를 잡도록 해보죠..

지금까지 설치 단계로 아마 일반 모드로 vmware 를 통한 win2000 부팅이 가능할것입니다.

vga 를 잡기전에 먼저 vmware-tools 란 프로그램 을 win2000 상태에서 설치하셔야 합니다.

그런뒤 vmware 상의 win2000을 재시작 하시면 자동으로 VGA Card를 인식하여 설치할것입니다.

설치 과정에 vmx_svga.sys 라는 설치 드라이브 파일을 찾습니다. 이파일은 다음 경로에

있습니다.

C:\\Program files\\vmware\\driver 에 얌전히 숨어 있죠..^^;

찾아서 선택해주시면 알아서 설치가 됩니다.

#### 사운드 카드 설정 #####

먼저 vmware 프로그램 상에서 setting -> sound 에 가시면 초기에 remove 로 설정이 되어져

있습니다. 이것을 ㅹnstall 로 설정해 주시고 vmware 부팅..

제어판 ->새하드웨어 추가/삭제 를 선택하시면 자동으로 하드웨어 list 를 보여 줍니다.

여기서 “새하드웨어 추가”  –> “새하드웨어 검색” 과 ” 목록에서 선택 ” 두개의

선택사항이

나오죠 여기사 ” 목록에서 선택” 을 누르시고 ” 비디오 사운드,게임컨트롤러” 를 선택하신후

creative technologd 사의 Sound Blaster 16 or AWE32 ”’ 를 선택하세요.

기종에 관계없이 Sound Blaster 16을 선택하셔야 합니다. 그럼 사운드 설치가 완료 되죠..

사운드 기종에 따라 찌져지는 혹은 깨어지는 소리가 나는 경우도 있습니다. 뭐…해결책은

…..

### 네트워크 설정 ####

네트워크설정은 ip address가 많으신 분들은 그냥 다른 ip address 를 네트워크 설정에서

설정해 주시면 되시고요..없으신 분들은 Ipchain 을 이용하여 ip를 마스크레이딩 하여

가상 ip 를 셋팅해 주시는 방식으로 하시면 됩니다.

여기에서 ipchains 와 ip-mas 에 대해 설명하기엔 조금….대신 리눅스 팁 게시판에

여기에 대한 문서를 올려 놓았습니다.

이상으로 VMware 의 대략적인 설정 방법과 사용방법에 대해 설명하였습니다.

도움이 되시길 바랍니다. 흑….옆에 무서운 사람의 협박에 못이겨서…이글을 올립니다.