From: "Doug Bissett" <virtualized_ecs_users@2rosenthals.com>
Message-ID: <100.d0480a0049e9fa67.020@ocii.com>
To: "Virtualized eCS Users Mailing List" <virtualized_ecs_users@2rosenthals.com>
Date: Sat, 12 Apr 2025 16:29:29 -0600 (MDT)
Reply-To: "Doug Bissett" <dougb007@ocii.com>
In-Reply-To: <list-12742942@2rosenthals.com>
References: <list-12742942@2rosenthals.com>
Priority: Normal
User-Agent: PMMail/3.26 (os/2; U; Warp 4.5; en-CA; i386; ver 3.26.00.2018)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Subject: Re: [Virtualized eCS] To upgrade to VBox 7.1.6 or not

On 2025-04-12, at 12:00:55, Allen Heath wrote:
>
>I've been happily running as a guest under VirtualBox 6.1.40 since 2022.
>However, it always reminds me that 7.1.6 is available, but I've been
>reluctant to rock a well working boat.  What's the advantage or
>disadvantage of either version under Windoze 11 host?
>
>The only "problems" I've had since 2022 are:
>* shared folders sometimes show shared host file timestamps in the Guest as
>GMT times for a while, then magically start displaying in the local
>timezone. And when that happens, if I create a file on the shared folder
>with the guest it appears at GMT time in the guest but the host displays it
>correctly in local time.  But restarting VirtualBox or just waiting a while
>the issue cures itself.
>* pretty good luck with the PCNet-Fast III adapter except that Net Used
>drives (or even a massive FTP) run out of resources after a lot of copying
>and then resume working again if I pause for about 10 minutes and then
>retry the operation.
>
>Will an upgrade fix any of this or just cause new problems?
>
>Thanks,
>Al

I have been using 7.1.6, with win 10, since it became available. It works MUCH better than older versions, especially when configuring the guest to use more than one disk (multiple VDIs, or one VDI with more than one drive). I don't know about your specific problems, I don't ever recall seeing them.

Unlike Lewis, I do recommend using AHCI, with the host cache, and setting the disk as a SSD (even when the real disk is a spinning disk). Performance improves.

Lewis recommends the Intel PRO/1000 MT NIC, which I fully agree with (be sure the driver is available in the VM, before switching).

I don't use shared folders with VBOX in windows. I have no reason to do so, but I think it works okay. Be sure that the VBOX is configured to use local time, not UTC.

Caveat: I don't really use this setup much, so I may be missing intermittent problems.

Note that it is very easy to back up the VM (just ZIP it up), then do the VBOX update. Test it (being careful to not do things like fetch mail, which can remove it from the server). If there is something wrong, try to fix it before restoring the working version. If it is working, you are done.

I don't know why people are so afraid of updating things. As long as you have a way to get back to what you started with, there is little risk. Over many years, I have found that "new" problems are easier to deal with, than "old" problems which get fixed, eventually.

-- 
**************************** 
From Doug Bissett's ArcaOS system 
dougb007 AT ocii.com 
**************************** 
... It's Always 9:30 in Zog.