virtualized_ecs_users@2rosenthals.com メーリングリストのアーカイブ メッセージ #153

差出人: "Massimo S." <virtualized_ecs_users@2rosenthals.com> フル ヘッダー
未複合化メッセージ
件名: Re: [Virtualized eCS] Virtual box 6.0.14 r 133895, acpi shutdown with AOS 5.0.3 and virtual cpu - 2 cpu success
日付: Mon, 27 Jan 2020 19:04:21 +0100
宛先: Virtualized eCS Users Mailing List <virtualized_ecs_users@2rosenthals.com>



Il 27/01/2020 13:31, Massimo S. ha scritto:


Il 27/01/2020 12:35, Massimo S. ha scritto:


Il 18/01/2020 17:29, Doug Bissett ha scritto:
On 2020-01-18, at 10:59:28, Massimo S. wrote:


Il 17/01/2020 18:41, Doug Bissett ha scritto:
On 2020-01-17, at 11:27:51, Massimo S. wrote:


Il 17/01/2020 03:49, Doug Bissett ha scritto:
On 2020-01-16, at 21:54:31, Massimo S. wrote:
...snip the CONFIG.SYS details...
It appears that you have defined two NICs. The ancient
PCNTND.OS2 driver is for an old 100 Mbs NIC. I suggest
using
the
network driver for the Intel 1000 Mbs NIC (the first one in the
list
works well). BigIcons are also not necessary. If you don't want
those things, deselect them in the installer. Randomly REMing
lines
in CONFIG.SYS is not the best approach.
Doug, i'm in "trouble":)

i've put Intel pro 1000 but i'm not finding a single driver that
works
with
this configuration

altready tried, but they don't work

e1000.os2, ibmgc.os2, ibmge.os2, mmigb.os2....:(


massimo
In the VBox Network setup, select "Intel Pro/1000 MT Desktop
(8254OEM)". When you install ArcaOS, it will automatically
select
the Multimac MMLEM driver. That has always worked, for me. If
you
really do need a second NIC, select the same for Adapter 2.
hi,

i don't tried MMLEM since i heard somewhere that's not anymore
supported, am i right?

massimo
No. The ancient IBM drivers, and the early Multimac drivers
(E1000B, etc.) are no longer supported (they may still work,
depending on the hardware, but they have been replaced for a
reason). They were replaced by the later Multimac drivers
(MMLEM, etc. based on BSD drivers). Only the later Multimac
drivers (BSD) are supported (if you have a valid Arca Noae
software subscription). There are a few other differences.
Depending on the system capabilities, they*may*  use the MSI
interrupt method (requires a recent version of ACPI), which takes
some of the load off of the interrupt hardware (which is already
being done by software, in a VM). A few other device drivers*may* use the MSI interrupt method too.

It all fits together, and trying to eliminate parts of it can cause
unexpected problems. I suggest putting it together as the Arca
Noae installer builds it, and don't change that, unless you are very
familiar with the internal operation of modern OS/2.

Hi Doug,

i've moved to MMLEM.OS2 AN driver (1.1.3), but i'm still seeing poor datarates 4,7-6MegaBytes/sec  laptop -> AOS 503 VM
(the VM is hosted on a intel xeon 8 cores supermicro server)


massimo

more tests:

virtual-nic: AMD 1core 2,5MB/sec
virtual-nic: AMD 2core 3,5MB/sec
virtual-nic: MML 2core 4,5MB/sec

with MMLEM is syrely better
but very far for a VM that has his storage on SSD
and connected with Intel Gigabit NICs

any help?
thanks

i've tried an old eCS2.2b guest on VMware hypervisor ESX 6.5 running on the same hardware

i get about 20MegaBytes/sec ftp datarates...
same eCS 2.2b on vbox i get 4,5MegaBytes/sec ftp datarates...

(not talking that with Vbox i can't autostart VMs at boot)

if i find a free sw for live bkups of VMs under ESX
i will go with ESX has hypervisor

massimo

サブスクライブ: フィード, ダイジェスト, インデックス.
サブスクライブ解除
リスト マスターへメール