I'm trying to run an old SCO 5.0.4 server into VMWare workstation (and later, ESX). I've used Ghost to dump the entire image into the virtual disk, and of course it won't start since the SCSI drivers need to be replaced.
Now I've tried to boot the virtual system with a generic boot/rootdisk, and used the link=blc command to make the kernel aware BusLogic (vmware emulates those). This seems to go well, as I can see the %Sdsk device in the boot screen (see attachment). I can also see a few hd devices in /dev including hd0root, and for example, a 'head /dev/hd02' returns some binary garbage telling me that I'm looking at the raw disk contents.
Now, what I intend to do is to mount the system, try to chroot to it, and adjust the kernel and boot parameters to make the system bootable again. However, I can't seem to mount the hd devices ("cannot stat /dev/hd*). This could be due to my lack of knowledge concerning SCO installation and boot options (all SCO systems I managed were already installed and ran fine).
My questions: How do I proceed in mounting the disks? Should I have created a kernel with BusLogic drivers -prior- to making the Ghost image? Is it even possible with SCO 5.0.4 as I notice that 5.0.7 actually recognises the disk as VMware? Should I use a system specific bootdisk (created on the old physical machine)?
I know there are some good documents on installing SCO in VM on the web, but I've not yet seen a good procedure on virtualizing existing servers..
Hi folks,
First of all, sorry about my english, isn't the best and thks for advance.
Here es my problem...
I have virtualize an SCO unix with VMware ESX 3 and everything was going on beatifull until that i try to connect from anorther host, i can't do it so i check the connection with... (5 Replies)
I am haveing a problem with my VMware ESXi 4.1 server and a virtual SCO UnixWare 7.1.4 server that I need for a legacy application for my company. The problem seems simple but I can't find a solution. The UnixWare (UW) server is a clean install and patched as SCO recommends. I am able to telnet to... (1 Reply)
Sir I am trying to install UnixWare7.1.4 on vmware workstation9, virtualbox and I am getting the following error
FATAL BOOT ERROR: decompression failed
For installing SCO Unixware7.1.4 I have created virtual harddisk of size 18GB, 1024 RAM, 64bit video memory, chosen unixware7.1.4... (1 Reply)
I've moved a physical server over to VMWare ESXi 5.1 using SCO 6.0 with MP4. For whatever reason, people are occasionally getting kicked out or are closing out their telnet session and it is leaving their processes running. When this happens, the sar %idle drops from 98-95% down to 25-20%. ... (1 Reply)
Some years ago our company chose to run a critical proprietary app under SCO Unix.
My predecessor tried to move A SCO Unix virtual machine from our dedicated VMWare environment to a shared Cloud VMWare environment. My predecessor received licensing messages from these critical servers so... (2 Replies)
hi
i installed sco unix open server 5.0.7 on virtual machine vmware and runing it,
its work perfect and good.
now how i can configuare network at scoadmin that i able to access nework ?
---------- Post updated at 08:56 AM ---------- Previous update was at 01:47 AM ----------
nobody can... (2 Replies)
Discussion started by: farzad226
2 Replies
LEARN ABOUT FREEBSD
vmx
VMX(4) BSD Kernel Interfaces Manual VMX(4)NAME
vmx -- VMware VMXNET3 Virtual Interface Controller device
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device vmx
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_vmx_load="YES"
DESCRIPTION
The vmx driver provides support for the VMXNET3 virtual NIC available in virtual machines by VMware. It appears as a simple Ethernet device
but is actually a virtual network interface to the underlying host operating system.
This driver supports the VMXNET3 driver protocol, as an alternative to the emulated pcn(4), em(4) interfaces also available in the VMware
environment. The vmx driver is optimized for the virtual machine, it can provide advanced capabilities depending on the underlying host
operating system and the physical network interface controller of the host. The vmx driver supports features like multiqueue support, IPv6
checksum offloading, MSI/MSI-X support and hardware VLAN tagging in VMware's VLAN Guest Tagging (VGT) mode.
The vmx driver supports VMXNET3 VMware virtual NICs provided by the virtual machine hardware version 7 or newer, as provided by the following
products:
o VMware ESX/ESXi 4.0 and newer
o VMware Server 2.0 and newer
o VMware Workstation 6.5 and newer
o VMware Fusion 2.0 and newer
For more information on configuring this device, see ifconfig(8).
MULTIPLE QUEUES
The vmx driver supports multiple transmit and receive queues. Multiple queues are only supported by certain VMware products, such as ESXi.
The number of queues allocated depends on the presence of MSI-X, the number of configured CPUs, and the tunables listed below. FreeBSD does
not enable MSI-X support on VMware by default. The hw.pci.honor_msi_blacklist tunable must be disabled to enable MSI-X support.
LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5).
hw.vmx.txnqueue
hw.vmx.X.txnqueue
Maximum number of transmit queues allocated by default by the driver. The default value is 8. The maximum supported by the VMXNET3
virtual NIC is 8.
hw.vmx.rxnqueue
hw.vmx.X.rxnqueue
Maximum number of receive queues allocated by default by the driver. The default value is 8. The maximum supported by the VMXNET3
virtual NIC is 16.
hw.vmx.txndesc
hw.vmx.X.txndesc
Number of transmit descriptors allocated by the driver. The default value is 512. The value must be a multiple of 32, and the maxi-
mum is 4096.
hw.vmx.rxndesc
hw.vmx.X.rxndesc
Number of receive descriptors per ring allocated by the driver. The default value is 256. The value must be a multiple of 32, and
the maximum is 2048. There are two rings so the actual usage is doubled.
EXAMPLES
The following entry must be added to the VMware configuration file to provide the vmx device:
ethernet0.virtualDev = "vmxnet3"
SEE ALSO altq(4), arp(4), em(4), netintro(4), ng_ether(4), pcn(4), vlan(4), ifconfig(8)AUTHORS
The vmx driver was ported from OpenBSD and significantly rewritten by Bryan Venteicher <bryanv@freebsd.org>. The OpenBSD driver was written
by Tsubai Masanari.
BSD March 17, 2014 BSD