Originally posted by Xaero_Vincent
View Post
Announcement
Collapse
No announcement yet.
Microsoft Begins Rolling Out Windows Subsystem For Linux 2
Collapse
X
-
Originally posted by Azrael5 View PostMicrosoft is going to adopt Linux as operating system.
And this is pointless anyhow.. don't pass your GPU via Hyper-V, do it with KVM (or Bhyve)
Microsoft Linux ME ('Millennial' Edition) *spits on the ground*Last edited by k1e0x; 13 June 2019, 04:10 PM.
Comment
-
Originally posted by andy22 View PostSo there is some "magic" (hopefully not the buggy 9p or samba mount) going on to have this special VHD root-filesystem shared for WSL2 and Win10. I just wonder how exactly this VHD is actually shared for the linux VM and Win10 point of view?
This should mean sqlite+wal should work on this VHD, since its a normal ext4 FS from the VM/Docker daemon viewpoint..
Three months ago, we announced that the Windows Subsystem for Linux will be able to access Linux files from Windows in the blog post: What’s new for WSL in Windows 10 version 1903, and in today’s post we will be showing you how we made these changes possible.
So 9p to access Linux ext4 VHD from Windows and 9p for Linux to access windows partitions.
So yes Linux kernel running 9p server for windows to access files contained inside the VHD. Windows will also have its own 9p server for sharing windows drivers. Really in a lot of ways this makes sense only 1 OS can control locks on a local file system at a time.
Windows with functional 9p support will make it a lot better OS for me to place in a virtual machine.
Only magic will be if Microsoft makes a functional file system.
Most likely going to have to wait for WSL3 for the virtio-fs magic. Basically this WSL2 will be virtio-9p with may of the 9p bugs fixed on the windows side. virtio-9p other than lacking performance with Linux to Linux hypervisor setups have been highly stable and dependable.
Comment
-
Originally posted by oiaohm View PostBasically this WSL2 will be virtio-9p with may of the 9p bugs fixed on the windows side.
So i have very little confidence that WSL2+9p will work any better, this means i need to keep the problematic mounts inside the VHD/root, while using the 9p mounts as simple network drive for just basic file i/o. At least i have this option now with WSL2, since docker-lcow always uses 9p.
I still think it will work better than my VM+Docker, since its managed by WSL2 and i can drop all the ssh stuff for doing basic config changes or backups. I mainly need to test how WSL2-9p performs against my reverse samba4 server, that has a physical disk (ext4) mounted inside my VM.Last edited by andy22; 13 June 2019, 07:07 PM.
Comment
-
Dont let it all fool you. It doesnt change the fact that Microsoft Windows is still an evil closed source OS. The source code is at best shared with a select few that Microsoft likes, plus you have to sign nasty NDAs that you cant talk about what you see. Overall, its just proprietary hell.
Comment
-
Originally posted by andy22 View PostSo i have very little confidence that WSL2+9p will work any better, this means i need to keep the problematic mounts inside the VHD/root, while using the 9p mounts as simple network drive for just basic file i/o. At least i have this option now with WSL2, since docker-lcow always uses 9p..
My main interest is improve 9p. I run windows in a virtual machine under Linux. So my Linux VM can use virtio-fs that gives me DAX and other features that cannot be done over 9p or samba.
WSL2 is still a generation or two behind what us using native Linux do. Windows has equally the same problems in VM instances where you are forced to samba instead of virtio-9p or virtio-fs.
Comment
-
Originally posted by oiaohm View PostWindows Improved 9p support will improve docker-lcow as well.
There the major issues are:
These operations are not currently working for bind-mounted volumes:- XAttrCreate
- Lock
- Getlock
- INotify
There are also a few that are not fully implemented:- Open – Only ReadWrite, WriteOnly, and ReadOnly flags are implemented
Code:Docker version master-dockerproject-2019-06-05, build c02f389c Kernel Version: 10.0 18362 (18362.1.amd64fre.19h1_release.190318-1202) Operating System: Windows 10 Pro Version 1903 (OS Build 18362.145) 4.19.27-linuxkit
Last edited by andy22; 14 June 2019, 04:27 AM.
Comment
-
Originally posted by andy22 View Post
I could not find any new change-logs regarding 9p and WSL2, so the "latest" information i have is this: https://docs.microsoft.com/en-us/vir...rs#bind-mounts
There the major issues are:- MkNod
- XAttrWalk
- XAttrCreate
- Lock
- Getlock
- Auth
- Flush
- INotify
So if Microsoft does fix up their 9p support things should improve a lot for the
Originally posted by andy22 View PostSo unless WSL2 adds support for those i/o operations, the 9P mounts are useless for most of my containers.
Basically Linux to Linux 9p mounts are not as bad as you have been having under windows. Ok they are not as good as they could be under Linux missing INotify is a serous pain in the tail.
Comment
-
Originally posted by oiaohm View PostSo if Microsoft does fix up their 9p support things should improve a lot for the
Comment
Comment