I am running Ubuntu as a guest OS using VMware player on my Windows 7 machine. The problem I have is syncing the clock in the Ubuntu machine. This happens only when I close the VMware player and open the suspended session. For example if I close my VMware player running Ubuntu at 4:15 PM and then restore it at 5:45 PM, it still shows 4:15 PM. (This does not happen when I shutdown the Ubuntu OS.)
I searched the StackOverflow forum and found that by setting
tools.syncTime = true
tools.syncTime.period = 60
should help resolve the problem. But this change did not work for me. Any pointers to resolve this issue would be helpful.
I had the same clock sync issue. Installing VMware tools solves the problem.
But if it doesn't help, you can do it manually by calling sudo ntpdate ntp.ubuntu.com every time you open the suspended session.
Related
I have updated Windows 10 PRO to 1903. Reinstalling VMware Workstation and setting existing virtual machine when i run it give me this error:
"VMware Workstation and Device/Credential Guard are not compatible. VMware Workstation can be run after disabling Device/Credential Guard."
I have done it. And i have looked too here:
http://www.vmware.com/go/turnoff_CG_DG
But nothing to do. Not solved.
So i ask your how i can solve it.
Thanks
This solved my problem (run from command prompt, as admin..)
bcdedit /set hypervisorlaunchtype off
and reboot windows..
I had the same problem. I had VMware Workstation 15.5.4 and Windwos 10 Pro version 1909 and installed Docker Desktop.
Here how I solved it:
1- Install new VMware Workstation 16.1.0
2- Update my Windwos 10 from 1909 to 20H2
As VMware Guide said in this link: https://kb.vmware.com/s/article/2146361
If your Host has Windows 10 20H1 build 19041.264 or newer,
upgrade/update to Workstation 15.5.6 or above. If your Host has
Windows 10 1909 or earlier, disable Hyper-V on the host to resolve
this issue.
Now VMware and Hyper-V can be at the same time and have both Docker and WMware at my Windows
Similar question is answered here:
VMware Workstation and Device/Credential Guard are not compatible
I've Windows 10 Pro system, and use Hyper-V on that system. Due to the needs of device redirection doesn't works well with Hyper-V, I've installed VMWare Workstation 14.
I have to disable Hyper-V to make VMWare Workstation work, at beginning. It worked until last weekend , seems because of the QFE update. I just verified, it was not QFE but Feature update to Windows 10, version 1803 that triggered the problem with VMWare Workstation again.
After Windows update completed (after reboot), I tried to start a VM in VMWare. I get the error dialog complaining about Device/Credential Guard.
Following the instruction in this link: https://kb.vmware.com/s/article/2146361, and after the reboot, I get another complaint about incompatibility with Hyper-V.
After reset the Hyper-V selection in Windows Feature or confirm that HyperV is not already removed, and reboot, the first error came back.
It gets in a loop of error complaining about Device Guard and complaining about Hyper-V for VMWare.
Ok, thanks to the answer from communities of VMWare: https://communities.vmware.com/thread/588526
The issue is now gone, by applying the following change:
Disable credential guard by using readiness tool from Microsoft: https://www.microsoft.com/en-us/download/details.aspx?id=53337, with this command: DG_Readiness_Tool_v3.2.ps1 -disable
Disable Hyper-V by using PowerShell command: Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V
Reboot and accept to boot without CG/DG.
Although I don't like that VMWare cannot work together with device guard from system, I get my VM working for the moment.
1- run cmd as admin
2- run : bcdedit /set hypervisorlaunchtype off
3- reboot
let me knew if it works please
good luck
here are the few steps for you to solve this issue:
Disable the HvHost service (and any other services with prefix Hyper-V if needed) from windows TaskManager(Ctrl+Alt+Del)
use the tool from the official website
Uncompress the downloaded zip file to your own directory, take C:\DG_Readiness_Tool_v3.5 here for instance.
Run Windows PowerShell as admin, type the following two commands:
cd C:\DG_Readiness_Tool_v3.5
.\DG_Readiness_Tool_v3.5.ps1 -Disable
Reboot
Adrian at https://answers.microsoft.com/en-us/windows/forum/windows_10-security/cannot-disable-memory-integrity-core-isolation-in/29ac5ce4-30d2-47d1-ab17-734980fd287b
says "I think it's a bug that this cannot be disabled via UI but fortunately it's possible through the registry by setting the following key to 0:"
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity\Enabled
This worked for me as well [Windows 10 Pro Version 1803(OS Build 17134.112, VMWare Workstation 14 Pro Version 14.1.2]
When I run vagrant up from the command line, it is a crap shoot at best as to whether vagrant will boot up or not. It stops at this line:
SSH auth method: private key
And then may or may not include this line:
Warning: Remote connection disconnect. Retrying...
As I said, sometimes it works and sometimes it does not. Why is this problem happening? For the record it would happen (less often) on my production MacBook at work.
Can I maybe change the auth method if there is no good answer for this? Trust me I have been looking and not found any answer on this yet.
whats happening is the following :
vagrant up will spin a new VM, basically it contacts virtualbox (or the specific provider) and run command to start a VM
the VM will start on the virtualbox side
note: if you run form a command line terminal in macos, you can see the title switching from 'Ruby' to 'VBoxManage'
the VM takes some time to start
because the VM does not send a specific signal when its done, vagrant will check at regular interval if the VM is fully booted and available to ssh-in
once the VM is available, vagrant can run the ssh command and complete the config (network, shared folder, etc...)
so in your case, the VM takes a bit longer to boot (this can be due to high activity on your mac, specific setup of the VM that runs on boot ...)
Basically this is harmless and is not necessarily a bad sign.
Please look at my accepted answer on this. It turns out that this was a memory allocation issue, and I only discovered it when watching the terminal for the VM provider (VirtualBox). Once I closed some programs I was (generally) able to boot up just fine.
There seems to be an incompatibility problem with Vagrant/VirtualBox & the Windows Hypervisor Platform feature in Windows 10
I had this problem and this is how I got get Vagrant & WSL2 working side by side
I have the following environment:
Hardware Virtualization enabled in BIOS
Windows 10 (Insider Program with Release Preview Channel)
-- Windows 10 with WSL 2 Version 10.0.19041 Build 19041
VirtualBox 6.1.12
-- Extension Pack Installed
Vagrant 2.2.9
These are the settings that worked for me:
Windows Hypervisor Platform: Off
Virtual Machine Platform: On
Windows Subsystem for Linux: On
I have successfully installed and run the OSX 10.11 on virtualbox a few while ago and I was able to successfully work with it and install xcode 7 on it and work with it without problems.
Now after a few days I have come to it and I have run the virtual machine and got the following error!!
It says: "Checking catalog file, incorrect number of thread records". It keeps working a while and finishes with closing the VM.
I didn't make any changes to it. I even created a new machine again using the existing ".VMDK" file and still no change.
I really need the data on it. Can you please help me with fixing the virtual machine? I have a .VMDK file with the size of 43 GB.
Thanks in advance.
Thanks GOD, I could finally find a solution for this problem. I launched another Mac virtual machine and followed this link on Youtube and installed Diskwarrior on the vm and from this vm, I could repair the other .VMDK file using Diskwarrior. I hope it helps :)
I had the same problem, found a simplier solution. I booted the virtual machine with Ubuntu live cd.
In terminal:
sudo apt install hfsprogs
# HFS file system consistency check, use fdisk -l to find your disk indetifier
sudo fsck.hfsplus /dev/sda2
I am trying to install Mac(OSX-Mavericks) using virtualbox On Windows 8.1.
Everything works fine But, when MAC Installation setup starts in virtual machine, it keep on loading and do not start the installation wizard stays on the first screen.
I have waited for a log time like 3-4 hrs but unable to figure out the problem as there is no error.
I am using a dell(Inspiron 3537).
I have installed Mac on my previous Samsung laptop successfully in the same way.
I will provide other information on demand as I'm not sure where the problem is as setup loads but not starts the installation process.
Thanks in advance
enable virtualisation on your BIOS, it may helps.
Open an administrator CMD shell and try this:
cd "C:\Program Files\Oracle\Virtualbox"
VBoxManage modifyvm <name_of_your_vm> --cpuidset 00000001 000306a9 00020800 80000201 178bfbff
Then close/VirtualBox and open again (to save your new settings). Boot OSX with "-v" flag.