unwillingsomnambulist

The one black PSU fan is throwing off the vibe. I can’t stop looking at it.

If you want to hear this pronounced, listen to “Big Church” by Sunn O))). Vocalist, Attila Csihar, tends to use Hungarian lyrics.

If you haven’t listened to Sunn O))) before…it’s the weird side of metal. Powerful speakers recommended, especially heavy on the bass. You want to feel it in your chest. The album it’s on, “Monoliths & Dimensions,” is about 53 and a half minutes long but consists of 4 tracks, with “Big Church” being the shortest at 9:43.

Not entirely sure why this reply is being panned (was at -6 when I first saw it).

OP is in the process of upgrading their PC to a Ryzen 9. If we make the assumption that this Ryzen 9 is on the AM5 platform, the CPU comes equipped with an IGPU, meaning the RTX 3060s are no longer needed by the bare metal. So, installing a stable, minimal point release OS as a base would minimize resource utilization on the hardware side. This could be something like Debian Bookworm or Proxmox VE with the no-subscription repo enabled. There's no need for the NVIDIA GPUs to be supported by the bare metal OS.

Once the base OS is installed, the VMs can be created, and the GPUs and peripherals can be passed through. This step effectively removes the devices from the host OS -- they don't show up in lsusb or lspci anymore -- and "gives" them to the VMs when they start. You get pretty close to native performance with setups of this nature, to the point that users have set up Windows 10/11 VMs in this way to play Cyberpunk 2077 on RTX 4090s with all the eye candy, including ray reconstruction.

Downsides:

• Three operating systems to maintain: bare metal, yours, and your partner's.
• Two sets of applications/games to maintain: yours and your partner's.
• May need to edit VM configs somewhat regularly to stay ahead of anti-cheat measures targeted at users of VMs.
• Performance is not identical to bare metal, but is pretty close.
• VM storage is isolated, so file sharing requires additional setup.

Upsides:

• If you don't know a lot about Linux, you'll know a bunch more when you're done with this.
• Once you get the setup ironed out, it won't need to change much going forward.
• Each VM's memory space is isolated, so applications won't "step on each other" -- that is, you can both run the same application or game simultaneously.
• Each user can run their own distro, or even their own OS if they wish. You can run Fedora and your partner can run Mint, or even Windows if they really, really want to. This includes Windows 11 as you can pass an emulated TPM through to meet the hardware requirements.
• Host OS can be managed via web interface (cockpit + cockpit-machines) or GUI application (virt-manager).

It's not exactly what OP is looking for, but it's definitely a valid approach to solving the problem.

I’ve been waiting for a beta of the Debian-based version. The Ubuntu-based version seemed to run reasonably well on my old Thinkpad T460, but I didn’t try too much serious stuff on it that I don’t already do on regular Debian with Distrobox.

I currently pay $45/mo for 75/20 DSL over 1960s copper. 3 streets over, they’re paying $45/mo for 300/300 fiber from the same ISP. You tellin’ me the FCC can punish them for that?

I didn’t see myself making it this far to begin with, so I haven’t the slightest idea. Assuming I stay the course, though, hopefully completing the huge project I’m doing at work, because it’ll take that long.

Or in a Ziploc bag, in a Folgers can, on a shelf. Ya know, dead as fuck.

Debian’s great for this.

I’m also running NextCloud (the official AIO Docker image) on Debian. Great for that too.

I’d say “the office dress code,” but what I really mean is my gut.

I don’t necessarily think this is brand new. Cold War era thinking was nutty, basically “hey let’s shove a reactor into everything.” We had the SLAM program and Project Pluto in the US during the 50s and 60s, I’m sure the USSR had something similar then too; probably a case of dusting off 60-70 year old plans and seeing if they still carry weight.

How recently did calling become supported? About a month ago I was still unable to even log in using Firefox unless I used a user agent switcher, and even then only text-based messaging worked.

I graduated a few years before you, also in Illinois, and can confirm that.

I can also confirm that I have not resisted the devil’s lettuce.

Depends on what level of responsiveness you need from the support team. I run it in my home lab and haven’t needed to raise any tickets as all the info I need to solve problems is readily available on their forums or in assorted blog posts. A company relying on it for their critical infrastructure would probably be best-served with Standard (4-hr response within a business day) or Premium (2-hr response within a business day).

If those still aren’t quick enough it may be worth looking into a partner of theirs, or into another commercial option altogether. I’ve interacted with the Red Hat support team on some high-severity issues and they are top-tier; that was unrelated to virtualization, though, and they tend to push the Red Hat Enterprise Virtualization solution quite hard. I’m talking a response time of minutes.

If I’m using kvm on any standalone (non-clustered) hosts on the data center it’s typically on Ubuntu LTS, knowing that the company I work for has a Canonical support agreement in their back pocket, but we haven’t needed it.