I did that, and since I got a dedicated SSD drive for it, I used it for the VM as a block device. Later after a GRUB update I discovered Windows in my GRUB boot menu. Turns out GRUB detected my VM, and now I can physically boot into my VM. Which I didn’t even know was possible.
So yeah, I accidentally dual boot Windows without meaning to, even though it’s a VM. Except when I boot into it, then it’s not, apparently.
r it, I used it for the VM as a block device. Later after a GRUB update I discovered Windows in my GRUB boot menu. Turns out GRUB detected my VM, and now I can physically boot into my VM. Which I didn’t even know was possible.
Grub did not detect your VM, it detected a bootable operating system on the drive because you passed it through to your VM.
So yeah its a nice way to be able to do both VM and Dual boot.
But i prefer using a raw disk file image on my btrfs FS because i have a sub volume for the windows 11 disk images that allows me to use btrfs filesystem snapshots with windows, so whenever i make a mistake on windows i can restore it to working state within 5 minutes.
I also prefer windows not running on bare metal, because i don’t trust it or what runs on it enough for that.
Grub did not detect your VM, it detected a bootable operating system on the drive because you passed it through to your VM
Yeah, the bootable drive that contained my VM install, that’s what I’m saying.
But i prefer using a raw disk file image
I started that way, but I had a disk with a single partition that contained a single file - the raw disk image file, and eventually decided this is silly, the filesystem on that disk is useless.
ted that way, but I had a disk with a single partition that contained a single file - the raw disk image file, and eventually decided this is silly, the filesystem
In that case its silly, i always try to dedicated hardware to things based on needs so
1TB NVME: RootFS
8TB 2x SSD4TB: Home partition
2TB NVME: Neural Network Models, Games requiring fast storage.
Based on that i setup my mounts in fstab so its not just vm images on there, i have 3 virtual disks for each class on there and i try to keep my VM images as small as possible so that i have more space for non VM things
I did that, and since I got a dedicated SSD drive for it, I used it for the VM as a block device. Later after a GRUB update I discovered Windows in my GRUB boot menu. Turns out GRUB detected my VM, and now I can physically boot into my VM. Which I didn’t even know was possible.
So yeah, I accidentally dual boot Windows without meaning to, even though it’s a VM. Except when I boot into it, then it’s not, apparently.
Grub did not detect your VM, it detected a bootable operating system on the drive because you passed it through to your VM. So yeah its a nice way to be able to do both VM and Dual boot.
But i prefer using a raw disk file image on my btrfs FS because i have a sub volume for the windows 11 disk images that allows me to use btrfs filesystem snapshots with windows, so whenever i make a mistake on windows i can restore it to working state within 5 minutes.
I also prefer windows not running on bare metal, because i don’t trust it or what runs on it enough for that.
Yeah, the bootable drive that contained my VM install, that’s what I’m saying.
I started that way, but I had a disk with a single partition that contained a single file - the raw disk image file, and eventually decided this is silly, the filesystem on that disk is useless.
1TB NVME: RootFS 8TB 2x SSD4TB: Home partition 2TB NVME: Neural Network Models, Games requiring fast storage.
Based on that i setup my mounts in fstab so its not just vm images on there, i have 3 virtual disks for each class on there and i try to keep my VM images as small as possible so that i have more space for non VM things