Thank you for doing this! When I first came across this poster, I was like "I NEED A PRINTED COPY OF THIS". I had a large custom canvas printed with it on it and it's hanging in my office. I didn't even realize / notice a few of the items that are pointed out on this site. I'm excited to see what other nuggets get added.
VM count is a poor metric. Spawning lots of VMs is a matter of looping over virt-install or "virsh create" or what have you. The real bottleneck is storage: how are you solving that such that you can migrate VMs around to service things. Once you get past a couple (~2) network storage arrays you're probably into "medium."
But I'll answer your question directly, nonetheless. At ~45 VMs, I consider the system "small."
Understand you're going to need intimate familiarity with the extant tools. Not that it's hard or anything. It's not point/click Proxmox style, though.
Good for you, glad you found some value in it. However, that's a no from me dawg. I'm waaaaay too accustomed to all of the niceties that modern syntax highlighting and LSP provide. I'm so certain that it's a huge step back for me that I won't even try it.
Quite a few people think that until they -do- try it and then find it has its advantages.
I know of a number of people who made the deal with themselves "I'll try it for a week/month and then see what I think" - I think over half went "well, that was interesting" and turned it back on, but a surprising (to me, a no-synhi preferring person who thought I was rarer than that) number switched to either "hilighting only for languages I'm unfamiliar with" or "no hilighting at all."
I don't recall anybody regretting trying the experiment.
(that's not to say you -should- try it, but I do think your certainty that you'd get nothing at all out of doing so may be misplaced)
If I already have a headless debian hypervisor using KVM / QEMU in place running multiple debian VMs, can I now use Virtual Box to manage / tweaks the config on those? And if so is there anyway to do it without having to install a window manager, etc. on the hypervisor?
We have a large legacy PHP code base originally using "xajax" in many places for asynchronous parts of the UI. We've pretty much got somewhat of our own "framework" and any sort of re-write is absolutely out of the question. We have been slowing replacing xajax with VueJS via a script tag and it's been working great for us as a modern / supported alternative to xajax . There are certain VueJS niceties we can't take advantage of because of the script tag approach, but that hasn't been a big deal.
Similar story here, we have a fairly large code base which has been continually evolved since year ~2000, with our own legacy "framework" for much of the server-side structure. Back then the forms used to reload the whole page, keeping user input and adding error messages (fun times!), then some kind of AJAX was added, where the server would send actual JS back to the client for execution. Some older pages still use jQuery.
A couple of years ago we needed to choose a way forward for new front-end dev, and we chose Vue just as Vue 3 was maturing. I didn't know much about reactive frameworks back then, so it was a bit of a hunch, but I'm very happy with how Vue3 has worked so far.
We did however do the effort of adding a build step. The site is basically multi-page, with small SPAs sitting at their own URLs for individual jobs. So we wrote a Rollup config to bundle each of the mini-SPAs into its own file, and modified the framework to add a way to configure "this page wants Vue3 and this is the path to its bundled JS". We load the main Vue script as a <script> tag of its own, instead of adding it to all the bundles, for better caching. But as far as I can tell, in this way we can use all the Vue3 niceties, including Single-File Components.
Anyone running virt-manager on mac connecting to a headless linux hypervisor on the same network? I tried installing it through "brew", but was getting many random errors.
I thought about running it over the network using XQuartz, but I'm not sure how maintained / well supported that is anymore.
