My System (Windows 8 running in VirtualBox) shutdowned unexpectedly. When I restarted the system Veracypt wouldn't start saying. "The device is not ready. Source: Mounted:4743"
Restarting the system seem to have solved the problem
Related
I'm using Windows, I've started to use VMware recently and when I installed Ubuntu on it, it stopped responding. I ended the VMware workstation with Windows Task Manager, and when I restarted it, the VM appeared to be powered off in the VMware station, but the VMware Tray Process still displayed the Virtual Machines are running. They captured a lot of CPU usages and memory, especially the VMware Workstation VMX.
The processes seem to be unkillable though I'd tried to kill them in many ways: task manager, taskkill, process explorer, even deleting the virtual machine from the disk (but the only file had been deleted is the vmd file, others still stay and cannot be removed because another process is using it).
I've tried reinstalling the OS 3 times and the same problem still occurs, except for the last time when I booted CD-ROM first with default hardware settings. However, when I changed the memory and the disk space, it stopped responding when I started it, and that problem occured.
Now I've had 3 virtual machine running and always occupies more than 95% CPU usage and I've got no idea how to shut them down and delete them completely. Please show me how, thank you.
Problem solved:
I restarted my computer
When the services hadn't started yet, I deleted the folders which had the running virtual machines, and it works because no process is using them.
Finally, no virtual machine is running in the background and the CPU usage is back to normal.
Time Machine and AFP have stopped working. I think it may have happened at the firmware update before last but cannot confirm that.
I have an HS-251+ w/ firmware version 4.3.6.0959
I have macOS 10.14.5 and QNAP.
When I try connect to the NAS using Finder (Go > Connect to Server > "afp://NAS1" > Connect) I receive an error: "There was a problem connecting to the server NAS1. The server may not exist or is not available. ...etc"
I can no longer see the server in Finder side panel, but if I click Network I can see it only if I turn on Windows Networking.
On a linux workstation I can see all the NFS mounts fine.
Time Machine can no longer find NAS1 to back up either.
I am completely stumped as to how to fix this.
Thanks
Bryon
QNAP Support confirmed this is a bug.
I was able to confirm that it only happens if you create additional shares - then time Machine stops working. You delete the shares and time machine can see the Nas again.
I am trying to install a virtual machine to have linux (Ubuntu) run on my system which is a Windows 10 with following specs:
Intel Core i5-4200 CPU RAM 8GB 64 bit OS.
I downloaded the necessary ISO file from Ubuntu itself but it still wont run and I can not delete the file either for some reason! The virtual machine runs fine and I open the program i.e. VM software not the VM itself to run Linux. However when I try and start the virtual machine I get a load of errors which includes this:
Failed to open a session for the virtual machine LearnEnough VM v.1.4.
VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED). Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
I successfully used Ubuntu on an old laptop a few years ago which was running Vista so I don't see why this machine is having trouble.
Is anyone able to assist please thank you in Advance T
Go to BIOS Setup.
Enable Virtualization technology
Reboot.
That should get it done. 👍
I have dumped a SSD to a raw image file with dd. It is mountable and seems to be working fine. The OS installed is a Windows 7 32bits.
I tried to start a vm on qemu with this image disk as "hda" :
qemu-system-i386 -enable-kvm -hda my_image.001 -m 1024 -vga std &
I tried it with qemu-system-x86_64 too.
When the vm starts, the windows logo appears and a BSOD occurs. I do not have time to read the error message.
When it restarts it says that due to a recent hardware change windows has failed and starts on a windows repair tool.
The windows repair tool fails to fix the problem
Since Windows seems to start booting before crashing, I am guessing this is due to some driver being missing from the disk for windows to load. Is there a way to get the actual error or missing driver?
Thanks for your help.
EDIT :
According to the following link, I need to retrieve the drivers for the qemu emulated hardware and put it on the disk I want to use. I will try copying the drivers from a working VM to the one I want to fix.
http://www.dowdandassociates.com/blog/content/howto-repair-windows-7-install-after-replacing-motherboard/
It was due to drivers being loaded automatically at startup. Disabling the corresponding registry keys of the OS forces Windows to reload new drivers on next boot.
It worked properly.
in "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services"
Set the "Start" value to 0 for Amdide iaStorV and pciide.
I've just installed the VMware Workstation 10.0.1, but when I try to boot a virtual machine (I've created a new guest and I also have a virtual disk image of another VM), it doesn't start to run and I get this error: "Cannot find a valid peer process to connect to". I've googled around but didn't find a solution to the problem. I am using Windows 7 64 bit.
I also have VirtualBox installed (maybe VMware goes in conflict with VirtualBox?).
What should I do? I need those virtual machines to run.
If the above solution didn't work, just restart your machine (Physical machine) and try booting again.
I needed to "allow" the VMware system extension (macOS warned me about this being blocked on install, but I ignored it).
In brief: System Preferences > Security and Privacy > General > Click "Allow" on the "VMware blocked" message
See accepted answer here for further details: https://superuser.com/questions/1256489/how-to-fix-vmware-fusion-pro-10-cannot-find-a-valid-peer-process-to-connect-to
Am not sure if this is really a solution but in my case it worked.
I had to go to the "Virtual Machine Library" and Double-click the VM that's throwing the error and that fixed it.