NetWare 6.0 Server
NetWare 6.0 Server
NetWare 6.0 Server
Support
This guest operating system is supported on the following VMware products:
| • |
|
VMware Workstation 4.0, 4.0.1, 4.0.2, 4.0.5, 4.5, 4.5.1, 4.5.2-Support Pack 3
VMware Workstation 5.0, 5.5, 5.5.1-Support Pack 4
VMware Workstation 5.5.2-Support Pack 5
Experimental support for 2-way Virtual SMP on Workstation 5.5, 5.5.1, 5.5.2 |
| • |
|
VMware ACE 1.0, 1.0.1, 1.0.2-Support Pack 3 |
| • |
|
VMware GSX Server 3.0, 3.1, 3.2, 3.2.1-Support Pack 3 |
| • |
|
VMware Server 1.0-Support Pack 5
Experimental support for 2-way Virtual SMP on VMware Server 1.0 |
| • |
|
VMware ESX Server 2.0.1, 2.1, 2.1.1, 2.1.2, 2.5, 2.5.1, 2.5.2, 2.5.3, 3.0
Support Pack 3 supported on ESX Server 2.1.1, 2.1.2, 2.5, 2.5.1, 2.5.2, 2.5.3
Support Pack 5 supported on ESX Server 2.5, 2.5.1, 2.5.2, 2.5.3, 3.0
No support for Virtual SMP |
Note: If you are installing a guest operating system through VMware VirtualCenter, be sure it is supported under the VMware product-ESX Server or GSX Server-on which you are running the virtual machine.
NetWare 6.0 Server
General Installation Notes
Be sure to read
General Guidelines for All VMware Products as well as this guide to installing your specific guest operating system.
You can install NetWare 6.0 in a virtual machine using the standard Novell NetWare 6.0 CD-ROM.
Keep the following issues in mind:
| • |
|
VMware recommends you install NetWare 6 on a computer with at least 256MB of memory. |
| • |
|
In the NetWare installation process, you must boot from the installation CD twice -once to format the virtual machine's disk drive, and then a second time to install files from the CD. |
On the reboot, you see a message that says "Operating System not found" and a dialog box with a message that says "No bootable CD, floppy or hard disk was detected."
In order to boot from the CD the second time, you must change the boot order.
As the virtual machine boots, click inside the virtual machine window. When the VMware logo appears, press Esc. Use the arrow keys to select the CD drive as the boot device, and then press Enter.
| • |
|
When you configure a virtual machine for a NetWare 6.0 guest, use the virtual LSI Logic SCSI adapter. NetWare 6.0 does not include a driver for the virtual BusLogic SCSI adapter. |
NetWare 6.0 Server
Installation Steps
To install NetWare 6 in a virtual machine, take the following steps.
1 Insert the Novell NetWare 6.0 CD in the CD-ROM drive.
2 Power on the virtual machine to start installing NetWare 6.0.
3 Read and accept the license agreement.
4 When prompted, choose IDE CD-ROM.
5 Create a new boot partition. The guest operating system reboots.
6 To configure IP networking, do one of the following:
n If you chose bridged networking for the virtual machine, enter its IP address.
When NetWare tries to load the LAN driver (using pcntnw.lan), it fails because it broadcasts for its own IP address. This causes IP networking to fail.
To work around this, open the System Console (press Ctrl-Esc) and type
set allow ip address duplicates=on
Press Alt-Esc to return to the installation.
n If you chose host-only networking for the virtual machine, look up the host machine's IP address.
At a command prompt on a Windows host, type
ipconfig /all
At a command prompt on a Linux host, type
ifconfig
Note the host's IP address for VMnet1 and change the last octet so it is greater than the last octet in the IP address of the host.
For example, if the host IP address is 192.168.160.1, the virtual machine's IP address is 192.168.160.###, where ### is any number greater than 1 and less than 128.
For the subnet mask, enter 255.255.255.0.
For the router gateway, enter the host's IP address (192.168.160.1 in this example).
n If you chose network address translation (NAT) for the virtual machine, look up the host machine's IP address.
At a command prompt on a Windows host, type
ipconfig /all
At a command prompt on a Linux host, type
ifconfig
Note the host's IP address for VMnet8 and change the last octet so it is greater than the last octet in the IP address of the host.
For example, if the host IP address is 192.168.160.1, the virtual machine's IP address is 192.168.160.###, where ### is any number greater than 2 and less than 128.
For the subnet mask, enter 255.255.255.0.
For the router gateway, enter the NAT service's IP address (192.168.160.2 in this example).
Note that with Network Address Translation, there are two IP addresses in use on the host:
The IP address assigned to the interface for VMnet8 appears in the ipconfig output with a 1 in the last octet.
The IP address used by the NAT device itself always uses 2 as the last octet.
7 Finish the installation.
After you finish the installation, install VMware Tools, which installs and loads the CPU idler program.
NetWare 6.0 Server
VMware Tools for NetWare 6.0 Guest Operating Systems
Be sure to install VMware Tools in your guest operating system. For details, see the manual for your VMware product or follow the appropriate link in the knowledge base article at
www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=340.
Installing VMware Tools also installs and loads the CPU idler program. NetWare servers do not idle the CPU when the operating system is idle. As a result, a virtual machine takes CPU time from the host regardless of whether the NetWare server software is idle or busy. To prevent unnecessary slowdowns, VMware recommends that, after you install VMware Tools, you keep the NetWare CPU idle program loaded.
NetWare 6.0 Server
Known Issues
NetWare 6.0 Server
Disconnecting VMware Tools ISO File
After the virtual machine reboots while installing VMware Tools, make sure the virtual machine releases the VMware Tools ISO image. Choose Edit > Removable Devices > CD-ROM, and if the CD-ROM's configuration shows the VMware Tools ISO image, change it back to Use physical drive.
NetWare 6.0 Server
Installation Failure on First Try
During the installation of the guest operating system, if you get an ABEND error in the JVM.NLM module, try installing the operating system again. This is a third-party problem that occurs rarely, but when it does, it occurs during installation only. Once you complete the installation, you should not see this error again.
NetWare 6.0 Server
Grabbing the Mouse Pointer
If the virtual machine is unable to grab or ungrab the mouse, it might be due to a Java class not being referenced in the virtual machine. In the NetWare 6.0 guest operating system, check the xinitrc file, which is located in sys:\java\nwgfx\. Take the following steps.
1 In the virtual machine, switch to the system console, and then type:
load edit
2 Press the Insert key to browse to the sys:\java\nwgfx\xinitrc file.
3 In the file, look for this line:
java -classpath $JAVA_HOME\classes\VMWtool.jar;$CLASSPATH VMWTool -iw
4 If the line does not exist, add it to the file. Press the Esc key. Save the file.
5 Restart the guest operating system. In the system console, type
restart server
The virtual machine should be able to grab and ungrab the mouse now.
NetWare 6.0 Server
Cannot Browse File System with Arrow Keys
If you are using text mode and want to browse the file system, you might notice that the arrow keypad and Insert key do not allow you to navigate directories. To work around this issue, use the numeric keypad, but first turn off the number lock by pressing the Num Lock key.
NetWare 6.0 Server
Netware 6.0 Server SP5 Crashes When Stack Dump Exceeds the Valid Memory Limit
ESX Server 3.0: Virtual machines running Netware 6.0 Server SP5 crash when a stack dump exceeds the valid memory limit. This problem might be accompanied by either of the error messages:
Problem executing SYMCJIT.NLM or
cdbe gremlin process crashed due to invalid opcode
This problem has been observed more frequently on guests with non-passthrough Raw Device Mapping (RDM). To work around this problem, reinstall Netware 6.0 Server SP5.
NetWare 6.0 Server
Netware Server Guest Inaccessible If Installed as RDM Virtual Machine Using the Same LUN as a Prior Windows NT RDM Guest Installation
If you install Novell Netware Server in a Raw Device Mapping (RDM) virtual machine, and you use the same logical unit number (LUN) previously used to install Windows NT in an RDM virtual machine on the same host, the installation will take place on an existing FAT16 partition that was created by the prior Window NT installation. The installation will proceed correctly until the final reboot, when it will load the Windows NT master boot record (MBR), but will crash to bluescreen due to an inaccessible device error. Even though Netware is installed, you will not be able to access the Netware operating system.
To work around this problem, format the LUN before you begin installing the Netware virtual machine. This ensures that the old FAT16 partition is formatted and that Netware will reboot correctly.
