VirtualBox 7.0.16 still has date/time issue with shared folders

I have installed 7.0.16 today on my Pure Oracle VirtualBox 15.5 system and every guest is at 7.0.16 guest additions.

All Fedora, Slowroll, and Tumbleweed have incorrect date and time on shared folders - I have notified Oracle VirtualBox about this issue and I suspect it is related to the 6.8.X kernel as does this with Oracle and OpenSUSE OBS generated code.

It is beyond my knowledge base to fix this - since it is also happening on Fedora - it is an Oracle issue and not OpenSUSE.

I will update this as I get more information.

1 Like

Hi @larryr I installed Virtualbox 7.0.16 this morning. I have a windows 11 Pro host with guest linux: Leap 15.5 XFCE, Leap 15.6 KDE and another 15.6 XFCE, slowroll KDE and slowroll XFCE, TW KDE and TW XFCE.
Besides opensuse I have MX Linux XFCE and Linux Mint XFCE. I manually installed the guest addictions ISO only on Linux Mint. The others have packages integrated into the distribution. All have date and time synchronized perfectly. Even in shared folders. I’m sorry about your problem. Hi

The date and time on shared folders is correct on all guests except Tumbleweed, Slowroll and Fedora (6.8.6 kernels).

@larryr hi. I have TW and kernel 6.8.6 and slowroll 6.8.4 RC1

I have it on good authority that the Oracle VirtualBox Host for 7.0.16 has a serious network bug that causes system crashes when the bridged networking is in use.

Oracle is in the process of confirming this.

I have had a crash on the 7.0.16 host so I am sure it is happening.

How is this related to the topic of this thread?

BTW:

For the “date/time issue with shared folders” there is a bug report and another thread on this forum.

I am updating everyone on the status of 7.0.16.

We cannot get 7.0.14 out of OBS for Leap. It has the USB fix but has been stuck for a few days.

Some folks do not use OpenSUSE version of VirtualBox but use Oracle’s - I report what might affect some OpenSUSE users.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.