Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 11 months ago.
Improve this question
I'm using parallels an an m1 macbook pro and the virtualization of ubuntu 20.04 worked perfectly fine until today. I can't launch it and it tells me that "Image BSS overlaps adjacent EFI memory region".
Does someone know how to fix it ?
I also can't create a new virtual machine since it prints the same error when I try to launch the new one.
Booting into an older version of the Kernel allowed me to safely access the VM after this happened to me. Although I also was running out of disk and needed to increase the amount of disk space allocated to the virtual machine.
I believe the latest version of the Ubuntu 20.04 kernel may not work on Parallels for now. Specifically linux-image-5.13.0-35-generic gave me trouble and booting into linux-image-5.13.0-30-generic worked fine.
The steps I took were
Attempt to boot into VM. It should hang at Parallels error: "Image BSS overlaps adjacent EFI memory region"
Go to Actions > Stop
Attempt to boot into the VM once again, at this point it should allow you to select Advanced options for Ubuntu. Select this.
In this screen select an older kernel version to boot into. I didn't have to boot into Recovery Mode.
Uninstall the breaking kernel. I just did sudo apt-get purge linux-image-5.13.0-35-generic.
It should be noted that I had older kernel versions available. If you've also deleted older kernel version preemptively, then I'm not sure what can be done.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I have an Ubuntu 20.04 'VMWare Workstation 16' Virtual Machine on an Ubuntu 20.04 laptop. When I try boot my VM, I see this output:
SMBus Host Controller not enabled!
Assuming drive cache: write through
/dev/sda5: clean 519701/1933312 files, 7505521/7732480 blocks
Failed to start Load AppArmor profiles
Failed to start Load AppArmor profiles managed internally by snapd
The VM then crashes and does not boot, immediately after the last message above. The first message is also new.
I don't think that I can access the terminal in the VM before the VM crashes. So not sure how I can fix this?
I have information in the VM that I'd like to access.
Milan
When launching the VM, try pressing shift when the VMWare logo comes to enter the manual setup.
After pressing F2, select 'Advanced Options for Ubuntu' and boot in recovery mode. When offered a list of options about what to do, go onto the root terminal. Enter sudo apt purge snapd and add blacklist i2c-piix4 to the bottom of the file /etc/modprobe.d/blacklist.conf
Then resume the boot and both are resolved.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I have a problem on Oracle VirtualBox : it regularly tells me that I don't have enough space left on device, when updating or installing.
In the VB settings, I have set my Motherboard base memory at 3370MB.
My HD IDE Primary Master has an actual size of 2MB and virtual size of 20GB, and my Optical Drive IDE Secondary Master is 1,46GB.
The Linux distribution is 1.534G.
When I run df -h in the VB, it tells me that the full filesystems are :
/dev/sr0, 1.5G, mounted on /cdrom
/dev/loop0, 1.5G, mounted on /rofs
/cow, 1.7G and 72k available, mounted on /
I am running it from a Windows 7, and the distribution I use inside the box is the latest Linux Mint.
I don't know if this is the relevant information you need, please ask me if you need anything else.
Thank you in advance for your help
Ok, I found the solution. The problem is that if you don't install Mint inside of the virtual machine, the only space available is your memory, so it is used as drive space. The solution was to first boot it via the live CD version, then install it inside of the virtual machine, and then reboot it using the version of Mint you just installed on the virtual hard disk you have in the virtual machine.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
Being Belgian, all laptops come with windowsTM pre-installed. Ingnorantly, I bought on thinking I would be able to install (K)ubuntu. I found out the UEFI is just microsoft's way to prevent you doing this. It stops you booting from USB or CD, it does not allow installing Linux or anything.
I tried the F2/F10 options and settings, I disengaged the security options, disabled secure boot, changed boot order, I tried changing HD with compatible laptop and running OS, tried to bang it against my head, nothing lets me install Linux, it just says:"no bootable device found"
UEFI dual booting Linux and Windows is big tangled mess. I've pulled it off with Ubuntu and Fedora, but after a lot of effort. There are a lot of important variables here. I'm more likely to be able to offer a solution with the following info:
Which media are you using – USB or optical?
How did you create the media? (e.g. Pendrive, Rawwrite, etc.)
Which laptop manufacturer? (This is surprisingly relevant)
Also, it will help us all in the long run if we get more insight into the specific UEFIs and start documenting this issue more thoroughly. UEFIs are embedded software typically written by third-party companies like Insyde. You can find yours by installing a Windows system detailer like Speccy or HWInfo64. See the attached screenshot from Speccy. This info is unlikely to help here and now, but it will help us long-term: I'm looking to create a repository for these UEFI boot issues if someone hasn't done so already.
Try installing Fedora 22. There is a UEFI trampoline to get passed this hurdle. If I had a UEFI machine I'd have tested this answer; it is theoretical at best.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
Firstly I'd like to say that I'm new to LXC and I may have some problems getting the right idea of how the things should work. The thing is I'm trying to start a previously download vagrant-lxc box that holds an Ubuntu 12.04 x32. My development PC is running Ubuntu 13.10 x64 and lxc 1.0.0.alpha1 installed from the Ubuntu official repositories.
When I run vagrant up --provider=lxc I'm always getting
There was an error executing ["sudo", "lxc-create",
"--template", "vagrant-tmp-lxc-test_default-1393431786",
"--name", "lxc-test_default-1393431786",
"-f", "/home/ccvera/.vagrant.d/boxes/lxc-ubuntu-12.04/lxc/lxc.conf",
"--", "--tarball", "/home/ccvera/.vagrant.d/boxes/lxc-ubuntu-12.04/lxc/rootfs.tar.gz",
"--auth-key", "/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/keys/vagrant.pub"]
I might be making a dumb error here so my questions are:
Is there any problem running a box of x32 container inside a x64 host using LXC?
Is there any problem running a box with a different Ubuntu version (Kernel version) that the host machine does? In may case (Ubuntu 12.04 (kernel 2.6) vs Ubuntu 13.10 (kernel 3.11))
In the case that 1, 2 do not apply, then, how can I figure out what's the problem? prepending VAGRANT_LOG=DEBUG didn't make the trick, it just shows the above errors many times.
In the case that 1 or 2 do apply, then, how can I overcome the situation?, I need fast and well performance on test virtual machines, (so I think I need containers), but it is not feasible to me that the developers should have the same OS as the testing VMs
Updating to newer versions of lxc and vagrant-lxc did the trick.
And after some reading is seems that x32 box runs under x64 host kernel so it becomes on a x64 box, that's the idea of containers.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I am trying to install ubuntu 14.04.2 LTE. I have a lunovo ideapad with windows 8. I have followed all necessary steps flawlessly, and even factory reset my laptop to make this smoother. I get this error when trying to boot and install ubuntu. I also get it if i try to run ubuntu without installing. Also I tried re-downloading ubuntu, and remounting on my usb with the universal usb installer.
Is this error due to my computer, or the ubs/unbuntu? There was another option in the boot menu. It was check disk for error. I do not know if it was checking disk as in the iso disk or my hard drive, but a ubuntu lunch screen appeared and it was looking into some ubuntu files (on the usb), when it was done it said there was 2 errors. It did not say what kind or if it repaired it , or how to repair it. It only gave me the option to exit, then lunovo boot screen appeared and it stayed in a attempting to repair loop for quite a awhile so I gave up on that and shut down.
I would ask this in ask ubuntu, but I do not have enough "respect points" to upload an image.
Major respect to anyone who can help me out, I have been to get ubuntu for 2 days now, and I hit a dead end.
This error message can appears in those cases:
1. Your hardware it not compatible, usually ACPI issue. Try to boot with additional options: "noapic" and/or "acpi=off". You should be able to set parameters in "Other options" [F6 key].
2. Your RAM is broken. Check it in "Test memory" option.