That's a shame. I hope someone continues a fork and calls it Shinyaku Toaru.
I was talking about the 1000 vs 1024 issue, do the dd test yourself and it's easy to verify that he was right.
As for the specific descrepancy that you're seeing, lots of things can throw off a file size calculation - symlinks, sparse files, reflinks, compression etc. Since you're the only one with access to your files, you'll need to investigate and come to a conclusion yourself (and file a bug report if necessary).
No, @[email protected] is correct.
I just did a test using dd - I created 100 files of exactly 1 MiB each (1048576 bytes). du reported the size as "100M" as expected, whereas eza reported it as "105M" - which is what you'd get if you divided 104857600 by 1000000 (= 104.8576 or 105M if you round it off).
If you're going for a container/VM-first approach, you might be interested in Bluefin DX - it's an immutable distro based on Fedora Atomic, and follows a workflow revolving around containers and VMs. Basically tuned exactly for homelab users and developers, who're looking for a stable yet up-to-date base (unlike Debian, which tends to use outdated packages, unless you're on Sid). The biggest advantages of using an immutable distro is that you never have to worry about a broken update again - so you can just focus on your work.
Along the same lines: Inception. There's tons of little details that you don't pick up in your first watch.
Ignore the GPU-passthru suggestions (at least for now), as they would be overkill for running MS Office.
The best way to get a decent-performing, dual-screen, productivity oriented Windows to display is via RDP and FreeRDP. You can use the following command to run your VM in fullscreen across both your monitors:
xfreerdp /monitors:1,2 /multimon /v:<host>
But run xfreerdp /monitor-list to check your monitor numbers first.
I use FreeRDP and Windows regularly for work (and my host OS is Linux), so I've explored multiple options and none of the usual Spice-clients were any good; FreeRDP was by far the best option I found. It also supports DPI scaling, shared folders, clipboard sharing etc - all work pretty much out of the box (you may need to pass the respective parameters to the command though - run xfreerdp --help to check the options)
One thing though, make sure you get FreeRDP version 3.xx. Some distros are still on 2.xx for whatever reason, but I'd highly recommend upgrading to 3.xx because there have been a ton of performance and QoL improvements since then, that'll make a big difference for your usage.
As for the VM performance itself, make sure you give it sufficient CPUs (at least 4 cores, and passthru the CPU topology) and RAM (at least 8GB). It might also be worth debloating your Windows VM, using a script such as Win11Debloat (it works with Win10 as well btw).
suspend the VM if I switch away from that workspace back to Linux
You can use the virsh suspend command for that. But to have it automatically suspend when you switch workspaces, you'll need to manually set up some automation, which depends on your DE/WM. KDE for instance has KWin rules which you can use to trigger a script or a command, other DE/WMs might have something similar. So you'll need to explore your DE/WM's window/workspace management and scripting options.
But get familiar with the virsh command, as that's what you'll be relying on to manage your VM via scripts. The documentation has more details on the shutdown/suspend/hibernate features that's worth taking a look at.
can't think of on3 scenario that windows is the best option for a server.
There are plenty of enterprise scenarios: eg an AD server for Windows clients, a DFS server, or servers to run certain Windows-only applications such as SCCM etc.
It's just a check on the version number. As per my previous link, Void's FreeRDP is still stuck on 2.x, whereas 3.x stable came out last December, with the latest stable being v3.4.0, released 3 weeks ago.
Nix also fails this test btw, since they too are still stuck on 2.x - and this is an example I've been using often as an argument against Nix fanbois who tend to claim that Nixpkgs is equivalent or even superior to the AUR, when in reality that's not the case.
The reason why I'm so interested in 3.x is because it's a major upgrade with a ton of QoL improvements. Any serious RDP user will want to switch to FreeRDP 3.x, especially if they're a Wayland user / game over RDP /use RemoteApps (eg WinApps) etc. So I check the FreeRDP version of a distro as an indicator whether that distro is worth my time or not, hence why I call it the "freerdp test". 3.x is also consider stable release btw, so there's really no excuse for a distro not to package it and at least make it available - perhaps with a new name so as to not force an upgrade, if they're concerned about compatibility issues.
This is quite interesting, especially that tool to check changes made to /etc. Might have to give Void a try now. But does anyone know what the update cadence is like? Is it bleeding-edge like Arch, where you get new kernels and Mesa etc not long after upstream updates?
Edit: Nevermind, looks like Void fails my freerdp test. Guess that seals the deal.
Is it the XPS 13 (9370)? If so, apparently everything works fine in Arch, except the fingerprint sensor. So might be worth a shot giving it a try.
I wouldn't be surprised if some of your issues are partly related to Ububtu. Personally, I wouldn't recommend using it even if a device has official support for it.
I use Rectangle on macOS as well, and use Wayfire on Linux. Wayfire has a tiling plug-in that does exactly what Rectangle does.
Mint and Cinnamon are quite outdated btw, I wouldn't really recommend them unless you've got an old PC and you're just a basic user.
iwd is great. In fact I'd say take it a step further and get rid of the beast that is NetworkManager as well.
https://austindw.com/networkmanager-is-bloat/