Yeah that’s kind of what I meant. It’s just the kernel that runs a form of hyper v, but their marketing people at least said that they modified it heavily to run fast without a lot of overhead in terms of IO and memory. But hey I have no clue. If you run a wsl2 instance you at least can’t access it in the hyper v manager. I think they made hyper v run like Google’s project crostini. (I’m not sure if it was that one ,that lets you run Linux containers inside of a minimal vm.
There are significant number of people have a don’t trust their data to btrfs on Linux, which has had development by multiple companies and individuals for over a decade. On the other hand, Winbtrfs is a re-implementation from scratch, by pretty much one person.
The stability level of winbtrfs is somewhat lacking at the moment. I count a dozen open issues where people are getting blue screens on the issue tracker, and at least two issues where people have corrupted volumes.
So, I would not use it for real data(yet), at least not for anything where I care about losing the data on that drive. It is stable enough for testing and whatnot, but not for real usage.
sounds interesting considering ive been using it on my linux machine for 3.5 years and only had 1 transaction fail from my 2 hdds in raid 0 while they were already close to 10 years old and it was corrected by reading the check sums
that one hard drive had 17 errors in the smart log for the controller
i should also mention i dont use swap partitions