I am trying to install redhat (rhel8) in virtualBox 6.1 on a windows 10 64 bit Home edition machine.
I verified the checksum of the iso file after download and its correct (I compared the checksum against another friend iso file who is able to install properly), still I am getting exception like
dnf.exceptions.error some packages from local repository have incorrect checksum
I even tried to run troubleshooting, but it raise exceptin like
failed to start media check on /dev/sr0 virtualbox
I have downloaded the iso files from multiple places and every time it gives me the same exception.
Any help is highly aprreciated.
Finally I found the reason for the above error.
Virtual Box uses virtualization to run multiple Operating Systems and in one system (let's say a windows machine) only one of the application will be allowed to use system virtualization capability.
So we have to disable any manual virtualization if performed in the system.
So we can disable virtualization by following ways:
Search for “Turn Windows features on or off” in the Start menu, hit
the Enter key to open the Windows Features window. Here, scroll down
to Hyper-V and disable it by clearing checkbox next to it. Then click
OK
Disable Hyper-V by using command.
Press Windows logo key + X, then hit A to run Command Prompt as administrator. In Command Prompt window, type
bcdedit /set hypervisorlaunchtype off
and hit Enter key to execute this command.
Finally restart system.
Related
I have a Windows10 Azure Virtual Machine running, and via the Windows Update Config screen (in Windows) I see several updates ready to install. However, the Update and Restart option in the start menu doesn't seem to do anything, and the same for the Restart functionality in the Virtual Machine pane of Azure.
I created an Update Management schedule (via Guest & Host Update menu), but this also doesn't seem to do anything. It succeeds after one minute, and when I look on the VM it still lists the updates as needed to install.
How can I install these updates on a Windows10 Azure Virtual Machine?
Try following the steps in this article to clear the Windows Update Cache. Then attempt installing one at a time
https://blogs.technet.microsoft.com/mckittrick/windows-update-issues-clear-windows-update-cache/
If that fails, please try the following :
Click on Start, and then click Run.
Type cmd in the Open box to get a DOS prompt.
Type "net stop wuauserv" without the quotes at the command prompt, and press
Enter.
Delete (or put in recycle bin) the contents of
C:\WINDOWS\SoftwareDistribution (but not the SoftwareDistribution folder)
Type net start wuauserv at the command prompt, and press Enter.
Now try Windows Update again.
If the issue still persists, kindly share the screenshot of the windowsupdate
Also is this the only VM where the issue is happening?
Everything used to work fine, but I haven't been using Virtual Box for several weeks. Now all of the sudden, I get the following exception when trying to start my Windows 10(32-Bit) VM. Note - Things were working fine several weeks ago. As far as I can tell, I haven't changed anything on my system that would cause this. The exception details are as follow:
VirtualBox - Error In supR3HardenedWinReSpawn (rc=-5640)
Please try reinstalling VirtualBox. where supR3HardenedWinReSpawn
what: 1 VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification
Failure: The process has more than one thread
I have been researching this for some time, to avail. Any help would be greatly appreciated.
There is a workaround:
Open VMbox manager
Run your VM with option "Detachable start"
Wait a while and then use "Show" to show the screen
Detachable start option
Show the screen
My setup:
Oracle VM Box 6.0 running on Win10,
VM is Ubuntu 18.04
If you are using vagrant to boot up your Virtual machine, then in most cases the error is due to improper shutdown of the VM. A fix that worked for me is to execute vagrant halt or similar commands multiple times until you have a clean boot.
In case anyone is in the same predicament, I will share what finally fixed my issue. I found a post during my hours and hours of searching that said you have to enable virtualization in BIOS settings. I checked my machine and virtualization was enabled, so I went on searching. At a loss for what to try next, I finally tried turning virtualization off, just to see. No change, but when I went to turn it back on, just as a flook I turned Turbo off, and what do you know - All of the suddent I can start my VM. So the solution, in case it saves someone time:
Uninstall Virtual Box (Latest Version)
Reboot your machine and enter BIOS
Make sure anything with the term 'Virtualization' is turned on
Make sure anything with the term 'Turbo' is turned off
Reboot your machine
Install Virtual Box
Hopefully this saves some poor soul what I had to go through to get this thing working.
METHOD A
If you are using WindHawk, exit it and re-try.
Method B
download previous version from https://www.virtualbox.org/wiki/Download_Old_Builds
install & extensions
Try to re-run your guest OS.
Try to do these steps:
1. Uninstall the VirtualBox program.
2. In your C:\users\\ might have two folders called ".VirtualBox" and "VirtualBox VMs": Delete them
3. Restart your PC
4. Install VirtualBox again
5. Add again your VM
6. It must working fine!
These steps worked for me!
Workaround 1:
Just increase the RAM size from virtual box settings
Right Click on OS image .
Settings->System->MotherBoard
Increase the base memory
Workaround 2:
Change the Paravirtualization Interface from default to none
Right Click on OS image .
Settings->System->Acceleration
Change acceleration from default to none.
The above one's was basically a workaround , which can work in some but not in all.
The best thing would be to reinstall virtual box with latest version which virtual box has tried to rectify the bug and use the same vdi files which was made by Virtual Box .
One of the most common causes that will cause this type of behaviour is a missing driver (VBoxDrv.inf). It’s possible that due to some permission issues, the installation of this crucial driver doesn’t complete during the initial installation. In this case, you can fix the problem by installing the VBoxDrv.inf manually.
1.Fix the directory problem Press Windows key + R to open up a Run dialog box. Inside the text box, type ‘regedit’ and press Enter to open up Registry Editor. When you’re prompted by the User Account Control (UAC), click Yes to grant admin access.
Once you’re inside the Registry Editor, use the left-hand section to navigate to the
following location: HKEY_LOCAL_MACHINE\system\currentcontrolset\services\vboxdrv
After you arrive at the correct location, move over to the right-hand section and
double-click on ImagePath the path associated should be \C:\Program
Files\Oracle\VirtualBox\drivers\vboxdrv\VBoxDrv.sys
if not replace with the above path and click ok.
Install the VBoxDRV.inf OPen location C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv right-click on VBoxDrv.inf and choose Install from the context menu.
Then in cmd run command "sc start vboxdrv"
Restart system. This should work.
I am developing xamarin apps under windows.
I want to regularly run the app under:
Windows Phone Emulator
iPhone Emulator
For the first, Hyper-V needs to enabled under windows.
For the second, one needs an OSX to connect to. I am trying to run OSX under VirtualBox. For this to work, Hardware Virtualization needs to be enabled.
Now, when I enable Hyper-V VirtualBox does not detect the hardware virtualization. And according to this, that will not change.
Is there an solution how I can test iOS and WindowsPhone without having to enable/disable Hyper-V (which requires a restart)?
I understand your pain-point, but this is just not possible to attain w/o a system restart because of the simple fact that the virtualization technologies you mentioned here are of different types.
In your case, Hyper-V that you use for #1 is a "Type 1" hyper-visor which run on host machine hardware. Other examples in this category include Citrix XenServer and VmWare ESXi.
The Virtual Box that you use for #2 is a "Type 2" hosted hyper-visor which runs within an OS.
If you need to toggle b/w these, a restart is eminent AFAIK.
A quick way to see the mode is by running "bcdedit" from Command Prompt to see the current config.
1. To disable Hyper-V run:
bcdedit /set hypervisorlaunchtype off
2. To turn Hyper-V back on run:
bcdedit /set hypervisorlaunchtype auto
However, you would need to reboot in both the cases. I just mentioned a easy config way to make you understand what was happening in the boot loader when toggling between the Type 1 and Type 2 hyper-visor modes.
Virtualbox 6 can use Hyper-V as backend virtualization engine. So that you can use them at same time.
You can enable this feature by this command:
cmd
cd "C:\Program Files\Oracle\VirtualBox"
VBoxManage setextradata global "VBoxInternal/NEM/UseRing0Runloop" 0
According to this:
https://docs.oracle.com/en/virtualization/virtualbox/6.0/admin/hyperv-support.html
This is an experimental feature.
So this feature could be unstable and doesn't even work.
At least it work on my laptop.
Screenshot that Vbox and HyperV at same time
You can do it via opening powershell in administrator mode and run the following code :
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
OK, so I would like to install openSUSE 13.2 64bit with my USB (want to install it, not to use LiveCD - so i downloaded installation 4.7GB iso). I have used Universal USB Installer 1.9.5.7 to create installation media. Everything worked without problem. When I boot from it, first a openSUSE screen shows up with options Install, Upgrade, Something-I-Don't-Remember and Check installation media. If I choose Install, terminal shows and at the end it says that it is launching "openSUSE installation program". After that, a graphically stunning screen with header "linuxrc" (seems to be responsible for launching installer) shows up and asks me to insert installation media and then press Yes to continue. If I click yes, it shows again, if I click no, it shows me another screen with options Install, Check disk integrity, Reboot and so on... I choose install and it asks for source medium. Options are CD/Network/HDD. However, I want to install it from an USB.
So, my question is: What am I doing wrong? Because I got that feeling that after choosing Install in the first screen (that one with openSUSE background), something else should happen instead of showing up linuxrc. Like launching or whatever. Or should I use another app to "burn" my ISO on USB?
Ok i just managed to make it work.
I am using ISO downloaded today morning (5.November 2014 at 13:11) and ImageWriter ( http://www.mediafire.com/download/9haeauu9sq8xtkx/ImageWriter.exe ). And it seems to work. If you get error about writeToDisk, close the program and launch it as Administrator (i mean it, right click and select run as administrator, it asks you for admin password even if you launch it with doubleclick but it won't work). Then find your file (it shows only *.*raw files in open dialog so you will have to just start writing iso file name in Open bar), choose right device and it will do the hard work. If it finishes with "Sucess" message box, restart PC and boot from USB. Then select Installation.
I am attempting to launch the windows phone 8 SDK emulator on my Mac so that i can do simple web testing of mobile websites i build.
I have followed several guides and they all say the same thing.
Such as:
6. Once the content (list of files and folders) is displayed, find the VMware virtual machine configuration file – the file with the .vmx extension.
hypervisor.cpuid.v0 = “FALSE”
And this guide proved to be quite useful to get it setup:
http://developer.nokia.com/Community/Wiki/Windows_Phone_8_SDK_on_a_Virtual_Machine_with_Working_Emulator
I was able to get Hyper-V support enabled and I have even managed to open the Windows Phone 8 Emulator directly from the Hyper-V Manager. But in this state it is missing the chroming, the buttons, and when the mouse goes across the screen it disappears. The solution to this is said to be launching the emulator directly from Visual Studio.
My problem is when ever i try to launch the emulator from Visual Studio it creates a new image and then goes into a boot look where it keeps crashing and restarting over and over again.
When viewing the Hyper-V event logs i see this error:
'WP8SDK720P' has encountered a fatal error. The guest operating system reported that it failed with the following error codes: ErrorCode0: 0xC000021A, ErrorCode1: 0x88EB9150, ErrorCode2: 0x0, ErrorCode3: 0xC0000022, ErrorCode4: 0xD203BC. If the problem persists, contact Product Support for the guest operating system. (Virtual machine ID 50607D9A-6E23-4369-9D89-2730614219BA)
How can i get past this error?
In the end I found a solution, I managed to launch the original Windows Phone VM image directly from the commandline with this command:
"C:\Program Files (x86)\Microsoft XDE\8.0\XDE.exe" /vhd "C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.0\Emulation\Images\Flash.vhd" /name WP8SDK720P
I created a new text file with notepad and put this command in it and saved the file on my desktop as a .bat file. This way i can just double click the shortcut and launch the sim.
Hopefully this helps someone else out there. In this way, you don't even need to start visual studio to run the emulator, it makes it much simpler if all you are using the emulator for is testing web-apps.
N.B. if you press FN+DOWN-ARROW you can enable the keyboard to work in the sim.
Follow these steps and see if it might help you to fix the problem.
Step 1: Shut down the Guest operating system (Windows 8 in this case).
Step 2: Open the settings for the VM and select Processors. Look at the left pane and see if you have CHECKED the option "Virtualize Intel VT-x/EPT or AMD-V/RVI" under the Virtualization engine section.
Step 3: Open the configuration file (Windows 8 x64.vmx) for the VM and check if you had added the following line of command (hypervisor.cpuid.v0 = "FALSE") to it as shown in the screen shot. You will generally find the file at the location where the virtual hard disk is placed.
If every thing is right, check to see if you had installed Visual Studio 2012 Update 3 (if you are using Visual Studio 2012 as your IDE).
Hope this helps to fix the issue. If you need more information on how to create a VM for developing windows phone 8 apps, there is a great article on nokia developer forum. You can find it here
Happy Coding!!