12-09-2010
A legacy application which started life on Openserver 5.0.2, was ported to 5.0.6 when the hardware died and which now needs new hardware again.
Perhaps I should add that they seem to be committed to this application long term, so I was thinking that the next time the hardware died it should be quite simple to find some new hardware that would run VMware instead of worrying about finding something to run SCO.
Last edited by KevinGB; 12-09-2010 at 10:39 AM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I've just installed Unix SCO OpenServer System v in an Intel PC and Everithing ok, except just one thing, in the begining of the installation the wizard asked me about the mouse , i have a generic 3 buttons mouse and i took a logitech and did not work
i need to change the mouse configuration, ... (2 Replies)
Discussion started by: jimmyvaldes
2 Replies
2. UNIX for Dummies Questions & Answers
hello!
when i try to make my system dual boot with both win98 & sco open server 5.5 it doesn't work at all.neither win98 take start nor sco open server boots.what should i do ?
kindly help me
thanks (1 Reply)
Discussion started by: buntty
1 Replies
3. UNIX for Advanced & Expert Users
I am doing some work for a customer that is running SCO 5.0.2 openserver and they have lost their cd. Is there anyplace I can download it? I have a replacement being shipped but it will not be here for two days and they are down. Any ideals? (3 Replies)
Discussion started by: SCOoT
3 Replies
4. UNIX for Dummies Questions & Answers
I'm running SCO Unix openserver 5.0.4 at the moment. The problem is my dissatifaction with the web browser netscape 3.01. I wanted a better browser, and tried to install netscape 4.7, and the required rs504c patch. I'm still not able to see web pages in a satisfying matter, it is mostly black. I... (0 Replies)
Discussion started by: cantona007
0 Replies
5. UNIX for Dummies Questions & Answers
Hi there guys.
I just got this new SCO version and i'm having some problem printing from shell,
This is what i'm typing at the # sign : lp -dHP /etc/hosts and it prints no problem but when i use any other user at the $ sign it gives me this error.
/dev/fd/7: /usr/lib/lp/sysv/7: not found.
... (1 Reply)
Discussion started by: josramon
1 Replies
6. SCO
Dear members
when i installed dual processor patch in openserver 5.0.7 in hp ML370 G4 server it hangs in sco at G_hd_config.
i tried MP4, EFS 5.64,5.70A but not solved the problem.. (0 Replies)
Discussion started by: M_farooqui
0 Replies
7. SCO
Here is an odd one. Every time that our server is restarted, the time is changed by 1 hour. I'm located in Puerto Rico which is GMT -4:00. I've tried EST and AST but the problem continues. Anyone has any ideas as to the cause?
Juan Navarrete (0 Replies)
Discussion started by: jn5519
0 Replies
8. SCO
I spent last weekend building a new system for a client.
The old (current production) system is an Acer Altos G700 with 512mb memory, dual P4 2.4ghz processors, dual channel LSI RAID controller with 4 72gb Seagate disks. This system runs SCO 5.0.7 with MPX and all the patches applied.
The test... (4 Replies)
Discussion started by: jgt
4 Replies
9. SCO
I am looking for openserver 5.0.6 media. I need build a new production server and we only have the 5.0.5 media.
If anybody can help that be awesome. (9 Replies)
Discussion started by: stlwindadmin
9 Replies
10. UNIX for Advanced & Expert Users
Hi:
I'm installing SCO Open Server 6.0v on VMWare ESXi,
The instalation procedure giving by UnXis is using OVF deploy template and
it create a primary partition of 10gb only.
Any one know, if the OVF template could be edited to create a larger partition??
Thanks (0 Replies)
Discussion started by: Ccarballo
0 Replies
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