So, i have that assignment about docker stuff. nifty piece of software i must say.

anyways im installing docker software on windows bc im thinking if i have something that gives me at least the correct structure and some skeletal syntax i will have a faster grasp of the thing. expecting some sort of high level ide but end up instead with what looks like a blank window, with the only obvious choice being sign into some bullshit i dont need. but thats another story

my point is:
when installing the thing it prompted me to install WSL2. which i supposedly am not supposed to have because my cpu doesnt support intel virtualisation. but being impatient (thats why i came to look for an assisted solution), i pursued the installation.

lo and behold: i end up with a shell prompt at the root of a linux filesystem!
i ran 2 or 3 muscle-memory commands and closed the prompt, i was in docker stuff up to the neck.
later on, when i go back to my project, in a virtual machine its sluggish af and screams at me that amd-v is not supported because of something something nested pages (will look up later how that one works).

dont have time to explore it some more yet, and especially experiment or even barely look at this glorious mess because i have something barely working and no time to have it fail.
but this story definitely left me perplexed.

and also : you can run WSL2 on an fx8350

  • 3
    Unless you want Windows containers (don't know who wants that) you always will have virtualization going on. WSL2 and Hyper-V both run mobylinux in a hypervisor. So VT-x, AMD-V and friends are highly recommended.
  • 0
    @hjk101 yeah, but it still doesnt shed light on the fact that somehow i got wsl2 that seems to be working, while it shouldnt, and lost amd-v in the process.
    looks like some clusterfuck of windows trying to run intel-v on a cpu that doesnt support it, default to an older process and somehow keep working?
    or maybe its some finnicky implementation of a translation layer?

    in any case im not looking into that right now
  • 1
    @bad-frog chances are likely that you don't have WSL2 installed, your shell is the docker substrate that's installed with hypervisor.

    Docker doesn't run natively on anything other than Linux. Because of this both Windows and Mac require a VM to be installed.

    It is curious though that you are able to install and run a VM but not WSL2.

    It could also be a Windows edition thing too. I think you need at least a pro license for WSL to install.

    If you still need a shell interface, I recommend an older solution, Babun. The command structure is similar to that of Debian based systems and still has a great feature set even though it lost support several years ago.
  • 0
    @sariel from what i understand WSL is like at a lower level than a traditional hypervisor, something akin to how docker works itself. i think.

    as for docker its an assignment, so i dont have the choice in the matter. not that i complain about that. the idea of dockerfile and its interface is something i got easily used to:)
  • 1
    @bad-frog no docker does not implement a hypervisor. That is always provided by Windows. Even without VT-x you can run it.
    There is no magic WSL2 is just a better integrated VM
  • 1
    If you can, give WSL a try

    I was skeptical as well, but it served me well for couple of years
  • 1
    Just to clarify some things here...

    The term "nested paging" should refer to SLAT, second level address translation.

    Other marketing terms are Rapid Virtualization Indexing / Extended Page Tables.

    Simply put, it adds another layer to page table lookups for virtual memory If I remember correctly to "ease" up the necessary seperation of virtual memory virtual machine vs hypervisor vs host.

    To run a virtual machine there is - strictly speaking - no hardware instruction set necessary, any hypervisor can run on X86.

    What's tricky is emulation of virtual machines that do not match the host system, e.g. an X86 host running an ARM 64 virtual machine.

    Many hypervisors support things running in software only - but yes. This will be slowtastic.

    WSL is a kind of mixed bag.

    It's full name is Windows Subsystem for Linux. Which explains a lot of why it is _not_ just a virtual machine running on an hypervisor.

    They e.g. finally came to their senses and started moving away from translating e.g. file system calls to using Plan 9 file system.

    WSL 1 translated manually file system calls to NTFS... ;)
  • 0
    @IntrusionCM @hjk101 thanks for the enlightenment:)
Add Comment