This hasn’t happened to me yet but I was just thinking about it. Let’s say you have a server with an iGPU, and you use GPU passthrough to let VMs use the iGPU. And then one day the host’s ssh server breaks, maybe you did something stupid or there was a bad update. Are you fucked? How could you possibly recover, with no display and no SSH? The only thing I can think of is setting up serial access for emergencies like this, but I rarely hear about serial access nowadays so I wonder if there’s some other solution here.

  • berylenara@sh.itjust.worksOP
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    16 days ago

    A rescue iso doesn’t work if you have encrypted disk. I thought everybody encrypted disk nowadays.

    If you don’t have a live boot option you can also pull the disk and fix it on another machine, or put a different boot disk in the system entirely.

    This is an interesting idea though, as long as the other machine has a different GPU then the system shouldn’t hijack it on startup.

    You can probably also disable hardware virtualization extensions in the bios to break the VM so it doesn’t steal the graphics card.

    AFAIK GPU passthrough is usually configured to detach the GPU from the host automatically on startup. So even if all VMs were broken, the GPU would still be detached. However as another commenter pointed out, it’s possible to detach it manually which might be safer against accidental lockouts.

    • mvirts@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      16 days ago

      😅 naa for me encryption a bigger risk than theft

      That said, you should be able to decrypt your disks with the right key even on a live boot. Even if the secrets are in the tpm you should be able to use whatever your normal system uses to decrypt the disks.

      If you don’t enter a password to boot, the keys are available. If you do, the password can decrypt the keys afaik.

      Again, I don’t do this but that’s what I’ve picked up here and there so take it with a grain of salt I may be wrong.

      • berylenara@sh.itjust.worksOP
        link
        fedilink
        English
        arrow-up
        2
        ·
        16 days ago

        Actually that might work. I thought that secure boot and disk encryption would prevent mounting the disk to a different system, but now I can’t think of any reason why it would. Good idea

    • Max-P@lemmy.max-p.me
      link
      fedilink
      arrow-up
      2
      ·
      16 days ago

      How’s the disk encrypted? I’ve never heard of anyone setting up an encrypted drive such that you can’t manually mount it with the password. It’s possible but you’d have to go out of your way to do that and only encrypt the drive with a TPM-managed key. It’s kind of a bad idea because if you lock yourself out your data’s gone.