| 3 Jan 2024 |
 K900 | (not necessarily the same implementation as IBM, as no one but IBM had it, but same interface) | 10:16:09 |
| K900 | And eventually UEFI came along and now most firmware actually implements UEFI, not BIOS | 10:17:06 |
| K900 | Though most consumer desktop boards also have a compatibility mode that provides BIOS-compatible interfaces on top of the UEFI firmware | 10:17:42 |
| K900 | In reply to@crushing-smite:matrix.org
EFI = firmware, UEFI = bootloader? There isn't really a distinction | 10:17:50 |
| K900 | EFI is what the spec used to be called when it was only an Intel thing | 10:17:56 |
| K900 | Eventually it got spun off into the UEFI Forum | 10:18:24 |
| K900 | And they added a "U" to differentiate | 10:18:32 |
| K900 | (EFI stands for Extensible Firmware Interface, U stands for Universal) | 10:18:48 |
 crushing-smite | Is it possible to feed an existing "real" parititon to the VM? | 10:24:50 |
 @atemu12:matrix.org | Sure | 10:24:57 |
| @atemu12:matrix.org | You can even pass an entire drive | 10:25:04 |
| K900 | Yes, but Windows generally tends to get VERY CONFUSED when you replace hardware under it | 10:25:09 |
| crushing-smite | Since I've dual-booted windows and nixos, could I pass the existing windows as virtualized on nixos? | 10:25:16 |
| K900 | So if you're thinking of virtualizing your existing Windows install, probably don't | 10:25:22 |
| @atemu12:matrix.org | IME it can handle it just fine | 10:25:27 |
| @atemu12:matrix.org | :( :) | 10:25:45 |
| crushing-smite | should I just go for it? | 10:25:48 |
| K900 | IME it can handle it just fine, but it can also break something ten layers in and you only find out two months later when you give up, reinstall and suddenly everything stops crashing | 10:25:54 |
| crushing-smite | confused - will it break everything and make windows unbootable, or will it just at worst not work when virtualized with nixos host? | 10:26:10 |
| @atemu12:matrix.org | That could also just be usual Windows shenanigans | 10:26:19 |
| K900 | If you want to use the same Windows install inside the VM and outside the VM at the same time, definitely don't do that | 10:26:36 |
| K900 | Because Windows will attempt to reconfigure itself when it sees new hardware | 10:26:51 |
| K900 | And that is persistent | 10:26:55 |
| crushing-smite | ok | 10:26:58 |
| crushing-smite | but what would be the difference in hardware? | 10:27:07 |
| K900 | So every time you switch from inside VM to outside VM, it'll have to reinstall all the drivers for everything | 10:27:07 |
| K900 | And it would very likely EVENTUALLY cause it to break in some funny way | 10:27:18 |
| crushing-smite | am I not supplying the very same hardware (especially with GPU passthrough)? | 10:27:23 |
| K900 | In reply to@crushing-smite:matrix.org
but what would be the difference in hardware? Literally everything except the GPU | 10:27:25 |
| K900 | The GPU you're passing through as-is | 10:27:33 |
