Es geht darum, nicht wie man denkt (Um Windows Updates) um VirtualBox.
Wir haben den VM-Host nicht immer auf der aktuellsten Version die verfügbar ist.
Wir haben nähmlich ein paar Dienste am laufen die nicht stoppen dürfen. Die basieren auf Virtual Box.
Also wir sind oft auf einem alten Patch.
Bis vor kurzen waren wir noch auf 6.0 jetzt konnten wir vor 2 Monaten auf 6.1 Wechseln. Momentan sind wir auf der Patch Linie:
"6.1.30" und wir kriegen immer die Messagebox das ein neuer Patch (Stand 13.Juli 2022: Patch v6.1.34a) verfügbar ist.
Wird uns das in einer großen art auf dem Forum beinschränken, und wenn ja dann auch Software-Teschnisch?
Sind später auch Versions Sprünge wie bei etwa bsp. Windows Server 2003 R2 auf Windows Server 2008 R2 möglich?
Also Ungefähr hier wie von Version 6.1 auf 6.3 in der Zukunft? Es müsstemöglich sein. Weil von dem Internen Offline-Zeitraum könnten wir das schaffen
solche Upgrades dann endlich ausführbar zu machen. Vielen Dank!
-wowinyou Software - M.Schäfer - Leitung der Gruppenarbeiten
Forum Beinschränkungen?
-
wowinyou Software
- Posts: 1
- Joined: 13. Jul 2022, 21:53
- Primary OS: MS Windows 8.1
- VBox Version: OSE other
- Guest OSses: Windows 7 Professional
- Location: Germany
- Contact:
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Forum Beinschränkungen?
It sounds like you're wondering if updating Virtualbox will still let your VMs still run.
There is a saying that I go by:
You can look at the changelogs in the new version to see if there are any changes that will impact your system. New versions typically work well, as long as the host OS doesn't change much. (That doesn't mean bugs don't happen: when Windows 11 came out while 6.1.26 was out, the developers started working to make Virtualbox compatible with 11's Hyper-V. Some bugs crept into Virtualbox's handling of Windows 10's Hyper-V. These bugs are reported to be fixed in the 6.1.35 test build, which should be released as 6.1.36 soon.)
For essential systems, it's best to test any changes in any software on a test computer, and not change the important computer until the tests succeed.
The OS's inside the VMs should remain compatible regardless of host Virtualbox version.
The 'new version' update box only shows that the new version is available, not that you must update. I'm still running 6.0.14 on my important Windows 10 host.
There is a saying that I go by:
I don't know how well it translates into German, but it means, don't change a working system until it needs to be changed.If it ain't broke, don't fix it
You can look at the changelogs in the new version to see if there are any changes that will impact your system. New versions typically work well, as long as the host OS doesn't change much. (That doesn't mean bugs don't happen: when Windows 11 came out while 6.1.26 was out, the developers started working to make Virtualbox compatible with 11's Hyper-V. Some bugs crept into Virtualbox's handling of Windows 10's Hyper-V. These bugs are reported to be fixed in the 6.1.35 test build, which should be released as 6.1.36 soon.)
For essential systems, it's best to test any changes in any software on a test computer, and not change the important computer until the tests succeed.
The OS's inside the VMs should remain compatible regardless of host Virtualbox version.
The 'new version' update box only shows that the new version is available, not that you must update. I'm still running 6.0.14 on my important Windows 10 host.