Has anyone tried it yet in VirtualBox v6 and v7? Any issues as guests and hosts?
Thank you for reading and hopefully answering.
Windows 11 23H2 is out.
Re: Windows 11 23H2 is out.
Only some quick tests with 6.1.46. It is still nothing I would want to use. Taskbar is better and openshell menu still works but otherwise...
- Attachments
-
- Capture1.png (58.06 KiB) Viewed 7218 times
-
- Posts: 339
- Joined: 9. Jul 2007, 20:02
- Primary OS: MS Windows other
- VBox Version: OSE other
- Guest OSses: Windows and macOSes
- Location: An Ant Farm
- Contact:
Re: Windows 11 23H2 is out.
TY & SM FTW!
Re: Windows 11 23H2 is out.
I'm running Win11 as guest in VBox Version 7.0.12 r159484 (Qt5.15.11) on Fedora 38 host.
Everything functioned normally until 23H2... now my idle Win guest (3% cpu in task mgr) is cooking my fedora host.
I havn't been able to figure out what MS included in Services what could cause this, but with Windows still stripped to minimum (I'm just using it to run my company's Citrix Workspace which was unreliable on my linux host) problem persists from yesterdays 23H2 update.
With assigned 5 of 12 cores (Ryzen 3900) and 12 of 32GB of memory to guest, my top 3 VirtualBoxVM tasks are consuming up to 29% hosts cpu. No setting change besides the update.
UPDATE 8.11. morning: After disableing SearchIndexer in guest and updating host to fedora39 problem seems to be solved for now.
Everything functioned normally until 23H2... now my idle Win guest (3% cpu in task mgr) is cooking my fedora host.
I havn't been able to figure out what MS included in Services what could cause this, but with Windows still stripped to minimum (I'm just using it to run my company's Citrix Workspace which was unreliable on my linux host) problem persists from yesterdays 23H2 update.
With assigned 5 of 12 cores (Ryzen 3900) and 12 of 32GB of memory to guest, my top 3 VirtualBoxVM tasks are consuming up to 29% hosts cpu. No setting change besides the update.
UPDATE 8.11. morning: After disableing SearchIndexer in guest and updating host to fedora39 problem seems to be solved for now.