From: "Doug Ritchie" <goprocom1@gmail.com>
To: "Proxmox VE user list" <pve-user@lists.proxmox.com>
Subject: [PVE-User] SPAM: Re: new to proxmox
Date: Thu, 10 Oct 2024 12:57:45 +0000 [thread overview]
Message-ID: <ema7b0cea8-70c8-476d-90ac-e62bfc0c9d2d@9324e94a.com> (raw)
In-Reply-To: <e886c85d-c7af-40c9-be50-83be6d795327@gmail.com>
Michel,
Just a note… an ‘old’ version of SCO Openserver isn’t going to run well
on Proxmox…. You need to have paravirtualized HBA and NIc drivers in the
OS to run well on Proxmox or any KVM-based hypervisor.
Xinuos (current owners of SCO Openserver product line) just released an
updated installer for Openserver 6 UNIX and ‘KVM Platform License’ that
includes support for ‘VirtIO SCSI single’ for the HBA and
paravirtualized NiC drivers to support Proxmox and other KVM-based
virtualization host platforms. Previous versions of Openserver 6 had
clock timing issues when ran on Proxmox.
In the past couple of weeks, I've been able to successfully install "SCO
Openserver 6 Definitive 2018" using their newest installer
(OpenServer6D2M2-DVD.iso - available from xinuos.com) using their
"Getting Started Guide" and SCO TA # 128147
<https://wdb1.sco.com/kb/showta?taid=128147>.
If you need assistance with XINUOS/SCO products… I’m part of a
not-for-profit users group that was originally formed as the SCO user’s
group… and is known as ‘iXorg, Inc’ (www.ixorg.org). In our upcoming
conference (“TestFest”) in November, as long as Orlando didn't get
washed away, we will be loading and configuring a Proxmox cluster for
running Openserver 6 Unix VM’s as a replacement for VMWare ESXi. We
have a couple members that work for Xinuos.
Doug Ritchie, treasurer - IXorg,Inc.
P.S. - If you are referring to "SCO Openserver 5.0.7 or older", these
versions of Unix have no plans to be updated for use on Proxmox/KVM.
--
Doug Ritchie
Technical Services Manager - ProCom Solutions, Inc.
(Systems Integrator/VAR/Reseller)
410-997-6777 ext.110
Direct Dial Voice & Fax: 443-393-3428 (Or Click Here
<https://service.ringcentral.com/ringme/ringme.asp?uc=44D6C07F00BE75B7BA5ECA2FDFA270D0875663454904,0,110,1,0&s=no&v=2&s_=1210>
to call me directly)
"Unix is user friendly... It's just picky about its friends..."
------ Original Message ------
From "Michel Donais" <midonais@gmail.com>
To pve-user@lists.proxmox.com
Date 10/9/2024 9:11:06 PM
Subject [PVE-User] new to proxmox
>I've installed Proxmox VE 8.1 to give a trial
>Ceated a VM from an old Sco Openserver system
>The VM can see the NIC but can't reach outside world
>Proxmox VE can see the nic and can communicate with the outside world
>
>Look a lot o sites to get a solution but none are working
>Can somebody can gide me to a solution?
>
>
>--
>Michel Donais
>
>-- This email has been checked for viruses by Avast antivirus software.
>www.avast.com
>_______________________________________________
>pve-user mailing list
>pve-user@lists.proxmox.com
>https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2024-10-10 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50806411-140d-42c0-97fb-fa8bc727c15f@telupton.com>
2024-10-10 1:11 ` [PVE-User] " Michel Donais
2024-10-10 2:03 ` Randy Bush
2024-10-10 4:46 ` ProCom Solutions
2024-10-10 12:57 ` Doug Ritchie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ema7b0cea8-70c8-476d-90ac-e62bfc0c9d2d@9324e94a.com \
--to=goprocom1@gmail.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox