• 5 Posts
  • 376 Comments
Joined 1 year ago
cake
Cake day: July 4th, 2023

help-circle














  • You can boot the VM from a liveCD ISO and then mount the drives to extract files (share a USB storage device to easily get them off). You could also add a second virtual disk, put an NTFS partition on it (within the VM) and copy to that if you plan to rebuild the OS drive.

    If you need the offsets of the partitions you could also mount them from the disk image directly via a loopback device, but that’s a bit more complicated.

    When dealing with Windows either on bare metal or VMs, I’ve often found it useful to store my more important data on a second disk so that I can easily back it up and it will survive across a wipe+reinstall of the OS.




  • So essentially it’s running a single computer we if it were two seperate workstations?

    I could see an implementation that’s similar to those running a VM with a DGPU for gaming. User A could run a login against the primary GPU and OS. User B could run a VM with several cores allocated and the secondary GPU dedicated to the VM. If any shared did file resources in the primary OS are needed, KVM has ways to do that as well.


  • I find your mileage is somewhat dependent on the rest of the system config and how you access it. I kinda hate how WSL2 is based on hyper-V because the network stack for that is a pain in my ass, but tools like NMAP just don’t work on WSL1.

    I have found that using something like MobaXterm is pretty awesome. The built-in X-Server lets me run a few useful graphical tools within WSL (GIMP, Wireshark, etc) without needing to install their windows counterparts.