Recently bought an Asus PRIME B450-PLUS motherboard with 6 SATA connectors. I've got a couple of Akasa SATA hot-swap drives that I'm trying to get running on SATA 5 & 6. I've set the connections as HotSwap Enabled in the BIOS but hotswap is not working. Running journalctl -f while swapping drives shows no action.
SATA connectors 3 & 4 work fine with these same drives with journalctl -f showing all the communications with the kernel but I'd prefer to get them on 5 & 6, if only for neatness.
SATA connectors 5 & 6 are separated from 1-4 on the M/B, is there some jumper or BIOS setting I need to mess with?
Just got an email response from Asus support ...
The M.2 Socket shares bandwidth with the SATA_5/6 ports, and therefore
the SATA_5/6 ports cannot be used when an M.2 device is installed.
Which is bl*dy annoying as the reason I selected this M/B was in order to have 6 SATA ports and an M.2 device rather than fit a 2½" SSD drive. In fact it's even more annoying that the M.2 device takes out 2 SATA ports. Fortunately I only actually need 4 ports in this build with the M.2.
Related
I'm on Windows 11, using WSL2 (Windows Subsystem for Linux). I recently upgraded my RAM from 32 GB to 64 GB.
While I can make my computer use more than 32 GB of RAM, WSL2 seems to be refusing to use more than 32 GB. For example, if I do
>>> import torch
>>> a = torch.randn(100000, 100000) # 40 GB tensor
Then I see the memory usage go up until it hit's 30-ish GB, at which point, I see "Killed", and the python process gets killed. Checking dmesg, it says that it killed the process because "Out of memory".
Any idea what the problem might be, or what the solution is?
According to this blog post, WSL2 is automatically configured to use 50% of the physical RAM of the machine. You'll need to add a memory=48GB (or your preferred setting) to a .wslconfig file that is placed in your Windows home directory (\Users\{username}\).
[wsl2]
memory=48GB
After adding this file, shut down your distribution and wait at least 8 seconds before restarting.
Assume that Windows 11 will need quite a bit of overhead to operate, so setting it to use the full 64 GB would cause the Windows OS to run out of memory.
i have a machine with i3 10th gen, 4 gb RAM, windows 10 home, 1 TB HDD specification. When I downloaded Docker desktop my laptop started malfunctioning whenever i started it. Its screen flickered and no work could be done on it.
So we have a RHEL 7.6 workstation with 128 gigs of ram. The OS sees all the ram and 80 cors (40 HT)
We have 1 guest with 8 CPUs and 32gigs of ram running RHEL 7.6 workstation as well.
We are trying to create another guest with 64 CPUs and 80 gigs of ram.
We setup the system using virt-manager and PXE boot the system to install the OS.
All this goes without a hitch, but when we log in after the system is build with PXE and do a free -g it only shows 2 gigs instead of 80 gigs.
Any ideas?
Thanks!
Joe
The issue was related to using uefi bios and the OVMF.x86_64 package. Once we went back to a normal bios and no nvram, the issue went away.
Hope this helps someone :).
Joe
I have a 2013 Mac Pro running the latest Parallels Desktop Pro v
12.2.0 (41591)
On it, is a Windows 10 Pro virtual with Docker Version 17.03.1-ce-win10 (11972)
Docker can only run with 'windows containers' because when trying to fire up the 'MobyLinux' instance in Hyper-V, it never fires up always bombing at:
tsc: Fast TSC calibration failed
I understand this to be some time dependent sync that has to happen at boot time or such failure occurs. I bought a WD 1TB SSD on a Thunderbolt dock to speed up the run/boot time of the virtual. (it was on my platter RAID cage before) to no avail. No diff.
Parallels IS set to 'enable nested virtualization' and I have started a virtual in Hyper-V on the win 10 Pro VM just fine, no errors. I have checked and unchecked 'PMU Virtualization' which I understand will provide statistics to the host but slow the VM.
I tried:
reducing the number of assigned cores to the VM as suggested by
another post to no avail (2-6 cores tried)
Reducing the cores to '1' for Docker (and mixing with above attempt)
increasing the number of cores to docker
adding/reducing memory to VM/Docker
playing with the
C:\Program
Files\Docker\Docker\resources\MobyLinux.ps1
file that loads the VM whereas in another post I changed something to
verifying that "C:\Users\Public\Documents\Hyper-V\Virtual hard disks\MobyLinuxVM.vhdx" is teh correct location for the .vhdx
verifying that the .iso is at "C:\Program Files\Docker\Docker\Resources\mobylinux.iso"
uninstalling Hyper-v/reinstalling Hyper-v manually and letting Docker do it automatically
...
I am at wit's end. I specifically bought this machine so I could do my MS/Visual Studio development along with iOS development on the same box. I have done so, this way, for the past 5-6 years with a 2009 Mac Pro before and now my 2013 MP, but never with Docker before...
So, I need one of two solutions:
a way to make Visual Studio 2015/2017 'look' at my host Mac's Docker instance in order to debug/move on to development
a way to make this 'MobyLinux' Docker vm run.
I was having the same issues and I had initially set the memory to the highest levels allotted and Docker just flat would not run in the Windows box. After tinkering with it for a while I realized that in the Windows box I had not done any of the updates so I ran all those and logged back in, and was getting the same issues of docker not running. That is when I moved over to Parallels and made the changes shown below. Hopefully that helps!
result of docker version:
https://a.cl.ly/kpumLPz4
hyper v:
https://a.cl.ly/jkunldkm
settings in parallels:
https://a.cl.ly/QwuGKq1D
additional settings in parallels that I changed:
https://a.cl.ly/9ZuNElnb
command that I ran for hello_world:
docker run --rm busybox echo hello_world
windows docs on Linux containers 10
docker docs on windows install
I have successfully installed a 64 bit Fedora 11 guest os using VirtualBox on a host machine (AMD64) running 32 bit Windows XP .
At the moment the host machine has 2 Gb ram installed and I've allocated 1 Gb to the guest, which all works well.
The host machine can hold a maximum of 4 Gb ram, so I was wondering if it's worth buying an extra 2 Gb for it.
I know that 32 bit Windows XP can't use all of the 4 Gb, but can the guest os use any of the ram that the host os can't use?
No, you are limited what the host OS can see. If you open up task manager in the host OS, the guest OS's memory is mapped within there, so having memory that's mapped outside of the host OS is not possible.
That shouldn't discourage you from getting the extra ram, however. If you upgrade to 4 (or 3.5GB) then you'll still have about ~3.2GB of addressable memory to use, which is a substantial increase over 2GB especially if your memory usage is already near 2GB.