is Windows Subsystem for Linux a complete replacement for Linux virtual machines? - virtual-machine

I'm investigating transitioning from Ubuntu 18 virtual machine to Ubuntu 18 WSL.
I know WSL has no gui, which is fine, but . . .
QUESTIONS
Besides lower memory usage, what is the advantage of using WSL instead of VM?.
Do I lose any capability by moving to WSL?

Related

GPU acceleration on Linux virtual machine

Is it possible to enable GPU acceleration on virtual machine, using Windows 10 Pro as host and Ubuntu 20.04 as virtual machine? I have tried Hyper-V and it didn't worked, propably because it is only for Windows Server 16. Unfortunately, I can't make a dualbot installation.
Does anyone have any proven way to use GPU and Linux, having only windows installed?

Mount VHDX within WSL Ubuntu 18.04 to edit Linux files

I'm looking to change a process (which currently is an elevated PowerShell script running in Windows 10, and I want to keep it close to that) I have that currently uses Paragon Linux Filesystem for Windows tool. While it does work, it doesn't work consistently. What I'd like to do instead is to use WSL on Windows 10, 1909 currently (will go to 2004 when available), to mount a VHDX which contains to partitions, /dev/sda1 for /boot, and /dev/sda2 another for an Linux LVM. The OS within this VHDX is CentOS 7.5, and the filesystem I want to modify is formatted in ext4. I need to edit some files within a logical volume within the group.
Currently, I'm running into an issue where qemu-nbd doesn't help, as there doesn't appear to be an NBD kernel mode driver provided by the Microsoft Linux kernel in Ubuntu 18.04 image from the Windows Store. I've tried guestfish (using guestmount), but it is unable to find an operating system and fails to mount any of the volumes.
Is this possible? Am I going down the wrong path, and is this not possible?
As I understand your question...
Seems to me that you want to offline access a .vhdx containing Linux
using powershell to manipulate some files...
(I think the issue here is ext4 and file rights)
1. Mount the .vhdx you want to '''work''' in a linux virtual machine as second disk
2. Install Powershell 7 in linux VM
3. Configure Powershell remote in the Linux VM (via SSH)
4. Access the Linux VM from Windows Powershell 7 and execute your scripts.
there are other ways using VMs+NBD or using WSL and mounted
drives... but this seems to be the most practical end efficient!
as you for sure know you can start/stop the VMs from Powershell

Server 2016 VM does not boot after hyper-v install

I am using VMWare Workstation 14, with Windows Server 2016 installed on it. A few weeks ago in my server class, we had an in class lab to setup a Nano Server. I successfully got that up and running and installed Hyper-V and loaded it into it. Started up, and signed in. Then two days later at class again, the VM just freezes at the windows logo with circling white dots.
I have installed multiple VMs trying to get it up and running. Always the same result. I have the virtualization enable in BIOS on my laptop.
I have a VM snapshot I just took before installing Hyper-V, installed the role, rebooted, and again, stops at the windows logo with circling dots.
I don't know where to check if there is an issue, or if something is configured incorrectly. I am just looking for some help and ideas on what I should check. I do also have the virtualization stuff within VMWare enabled under the properties for the VM.
System details:
Asus GL502VMZ
Version 10.0.17134 Build 17134
Processor Intel(R) Core(TM) i7-7700HQ CPU # 2.80GHz, 2808 Mhz, 4 Core(s), 8 Logical Processor(s)
Installed Physical Memory (RAM) 16.0 GB
NVIDIA GeForce GTX 1060 3GB
Have you tried uninstalling the anti-virus? I was running into the same issue in my server class (Using VMware to run server 2016 which we where using to nest hyper-v)until a class mate said he didn't have the AV (we where looking for differences on why his worked and mind didn't). I removed my AV (was AVG) now the server no longer stalls at the boot screen.
Just my 2 cents that may help someone in the future. I had the same issue on an HP Proliant ML310e that worked fine for the full install until enabling the Hyper-V role, then it would hang at the Windows icon screen with the swirling dots. I was able to get past that by disabling Intel VT-d in the bios. Not a particularly good solution, but it allowed the system to boot successfully and run normally.

OpsCenter : Installing on 32 bit linux machines

Is it possible to install opscenter on 32 bit linux machines (i am using beaglebone) running ubuntu 14.04 LTS? If not is it still possible to monitor a cassandra cluster which is running on 32 bit linux machines from a 64 bit machine? I see there is project done using raspberry pi here . I am not quite sure how they setup opscenter 5.0 to work with raspberry pi's.
Is it possible to install opscenter on 32 bit linux machines (i am using beaglebone) running ubuntu 14.04 LTS?
Yes, it is possible. Opscenterd supports both 32- and 64-bit distros, and agents run on JVM so they run pretty much anywhere.
If not is it still possible to monitor a cassandra cluster which is running on 32 bit linux machines from a 64 bit machine?
What makes you think it was not possible? Are there any articles/SO questions stating that? It should work just fine.

problems installing a virtual machine

I am tryin to install kali linux 1.0.9 on virtualbox for some testing purposes. (I am new with virtual machines). So i downloaded the 64-bit version of the os. i have got two problems:-
for some reason virtualbox does not show me a debian 64 bit version option in the settings(however it does show 32-bit option).
virtualbox doesnt allow me to change the no. of processors(default value is 1). i have got 8 cpus.
please help. my specs - intel i7 2670 memory- 6GB HDD-700 GB graphics - radeon 7670 HD
I have got windows 7 ultimate 64-Bit installed on the host
You need to enable 'Virtualization' option in your BIOS settings. The name of the settings may be different in different BIOS/motherboard brands. But you can easily identify it, in the BIOS.
I also had the same problem. I am in windows 8.1 and for my case, the problem was due to conflicts with Hyper-V who was activated in my system. I solved the problem by disabling Hyper-V.
Open windows features and Uncheck Hyper-V, click/tap on OK