I have been trying to run vagrant up but I keep getting an error, though I have run a command for the box vagrant init ubuntu/focal64 and the result said I am ready to vagrant up but I keep getting the error message as shown in the screenshot below.
Please how can I resolve this issue?
I am in need of quick help.
You need to enable virtualization within the BIOS of your machine. When you first boot the computer, there's usually a screen saying "Hit F2" or "Hit Del" to enter setup (the key varies per motherboard manufacturer). You need to go into the BIOS setup and enable Hardware Virtualization support (VT-x on Intel machines). Consult your computer/motherboard manufacturer manual.
Related
I follow this tutorial
https://docs.aws.amazon.com/deepracer/latest/developerguide/deepracer-ubuntu-update.html
on updating the deep racer software stack to Ubuntu 20.04 Software Stack. After installing the new ubuntu, I cannot enter my OS because it said "ubuntu has been blocked by the current security policy". In the BIOS menu, it doesn't have the option to disable security boot.
After that, I follow this tutorial https://github.com/awsdocs/aws-deepracer-developer-guide/blob/master/doc_source/deepracer-vehicle-factory-reset-preparation.md to try to install old Linux to revert back the process. It also gives me the same error as "ubuntu has been blocked by the current security policy".
I try to reinstall multiple times and still had no luck. I also see on AWS re:Post that some ppl are facing same issue too but n
I solved my problem, as deep racer bios do not have the option to disable secure boot. You have to make sure that the factory reset folder is unzipped, and drag all the files to the second partition of your USB as the document shows.
https://docs.aws.amazon.com/deepracer/latest/developerguide/deepracer-ubuntu-update.html
After that, you will select to boot from the USB drive after you enter the ubuntu, click install ubuntu 20. x.x.x. After installation, u need to once again to boot from USB and run the shell script in the factory reset folder in order to enter the Ubuntu. Otherwise, it will show the error it is blocked by the current security policy.
When I run the shell script, the first time I run I encountered an error saying cannot find the GPT partition table. The reason is that I skip some of the steps in the document and did not follow the step to do the partition. After I repeat the partition process. I was able to run a factory reset shell script. You should see it doing a writing block operation. After the script is finished
you should able to enter ubuntu 20. x.x.x without error.
I got a linux VM in Azure and from the screenshot via the Boot Diagnostics menu, I can see that it gives the following message :
"you are in emergency mode.....press Enter for maintenance or Press CTRL D to continue"
I tried to access the VM using the serial console and it connects to the console and I see a message as below :
"Connected to the serial port of the VM
If no loginprompt is displayed press ENTER"
But.....despite pressing Enter nothing happens! Ive tried rebooting, restarting etc but still stuck
For the error you are in emergency mode.....press Enter for maintenance or Press CTRL D to continue
The emergency mode sometimes means either your file system is corrupted or you created a new partition or edited existing partition.
Please perform a file system check using below command :
fsck.ext4 /dev/sda3
where sda3 can be your partition and if you are using ext3 file system, change the command as follows:
fsck.ext3 /dev/sda3
Cycle through the SDAs by changing the last number in the sda to see which file system has problems.
Ex: sda1, sda2, sda3, sda4, and so on
For the error Connected to the serial port of the VM If no loginprompt is displayed press ENTER
This issue occurs when the serial console connection is successfully made to the virtual machine, but the virtual machine is not configured for input/output on the serial port.
To ensure your Linux virtual machine works with Azure serial console, please follow the guidance: Create and upload an Ubuntu Linux VHD in Azure - https://learn.microsoft.com/en-us/azure/virtual-machines/linux/create-upload-ubuntu for the distribution you are using. Specifically you will need to perform these steps from the preceding link:
Modify the kernel boot line in GRUB or GRUB2 to include the following parameters. This will also ensure all console messages are sent to the first serial port, which can assist Azure support with debugging issues:
console=ttyS0,115200 earlyprintk=ttyS0,115200 rootdelay=300
In addition to the above, it is recommended to remove the following parameters if they exist:
rhgb quiet crashkernel=auto
Graphical and quiet boot are not useful in a cloud environment where we want all the logs to be sent to the serial port. The crashkernel option may be left configured if desired, but note that this parameter will reduce the amount of available memory in the VM by 128MB or more, which may be problematic on the smaller VM sizes.
Reference :
https://unix.stackexchange.com/questions/347808/ubuntu-gives-message-welcome-to-emergency-mode
https://github.com/Microsoft/azserialconsole/blob/master/Known_Issues/Hitting_enter_does_nothing.md
I have been trying to install macOS Catalina on virtual box foloowing this tutorial:
https://techsprobe.com/install-macos-catalina-virtualbox-windows/
When getting to the step of having to actually install catalina the virtual machine boots into an EFI shell
The same person who wrote the tutorial wrote a supposed fix:
https://techsprobe.com/how-to-fix-efi-internal-shell-on-macos-catalina-on-virtualbox/
The fix adds an ISO file which contains parts of an apple file system which is loaded via a startup.nsh file which you create in the shell.
The fix itself however does not work either. Now I have no idea about how EFI shells work or how "fs#" relates to loading files from the apfs ISO. Here is the startup.nsh file as well as the error associated with trying to run it:
Now like I said I dont have much of an idea of how EFI works or whats going on here in general, so feel free to educate me.
I was able to fix the UEFI problems as follows (credit to techrechard website):
At UEFI prompt: Type exit
You’ll be brought into an EFI text-mode GUI.
Select Boot Maintenance Manager and click.
Select Boot From File and click
You should see two entries in a list (they are cryptic looking PCI bus paths).
The first PCI path in the list is probably the boot partition that doesn’t contain bootable firmware. The second PCI path is probably to the recovery partition, the one you need to boot from. If the 2nd partition isn’t the recovery partition, look under the paths in the list to see if one of them is it. If the recovery partition isn’t present and valid, these instructions won’t work.
Click the 2nd entry, you should see (and then click):
macOS Install Data
Then click:
Locked Files
Then (if present), click
Boot Files
And finally click:
boot.efi
Installation will continue, or you will boot into the OS or get the Recovery Utilities menu (where macOS can be reinstalled from or Disk Utilities run). The ambiguity of that last statement is I did that awhile before writing this comment and I don’t recall what I booted into first, only that it worked and was not hard to figure out what to do at that point. If you have a recovery partition, to boot directly into the Recovery Mode turn on the Mac and immediately press and hold (⌘)-R
Apparently if you follow this link how to install catalina, you will get an error like the one you got (This is probably due tu the way virtualbox reads disks--> uefi or legacy). Mine was :‘FSL: \ system/library/coreservices \ boot EFI’ is not recognized as an internal or external command, operable program, or script file?. On another forum I found this command:
> Install.nsh
If you write it in the command line of your virtualbox MAC environment it should proceed. It worked fine when I typed it.
I am new to linux OS. According to the requirement of my project I have to install extensible Hypervisor Framework( XMHF) and then build the required hypapp over it. Grub is supposed to load the XMHF at boot time and then the ubuntu OS has to laod over it, But when i am trying to boot the system according to the steps mentioned to install XMHF the system stops at the Starting up.... state at the time of booting. I dont know where i have done mistake. I have checked it many times but nothing useful. Can anyone please help me with this?? "Installing XMHF" manual can be found at http://xmhf.sourceforge.net/doc/xmhf/doc/installing-xmhf.md.html
My grub entry for XMHF is
title XMHF
rootnoverify (hd0,0) // as i have no primary partition for the hard drive
kernel /boot/init-x86.bin
module /boot/hypervisor.bin.gz
modulenounzip (hd0)+1
I had the exact same problem.
I had to properly configure serial output, either physically or serial-over-lan, to see XMHF's output. In my case, I missed a Intel VT related switch in BIOS.
How to configure serial console can be found here: https://www.cyberciti.biz/faq/linux-serial-console-howto/
go through this http://xmhf.sourceforge.net/doc/xmhf/doc/installing-xmhf.md.html this will be helpful :D
I installed linux debian as a 2nd system and it works fine, however when I choose Windows in loader(lilo) to boot, it stops on a windows logo.
I tried to boot in safe mode, and it stops on classpnp.sys driver.
I'm not sure whether the problem is in classpnp or in some other driver which is failed to load after it.
I also tried to boot with bootlog (ntbtlog), however it is not created (I check C:\Windows).
It seems like smth is wrong with hard drive configuration with several partitions.
I've googled a lot of similiar issues with classpnp.sys, but none of the solutions helped:
-I tried to change bios SATA coniguration from IDE to AHCI,
-restore backup configuration files (SAM, DEFAULT, SECURITY etc).
If anyone knows what else can I do with this, please help.
This belongs on super user, but you need to press F8 and select safe mode. There you can fix your problems