Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to boot Ubuntu 13.04 in VirtualBox, but every time I boot, I get an error that says:

SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr

This happens right after I start the virtual machine, and the operating system does not even start properly. I see the error, then the screen just goes black and gives me a blinking cursor. The solutions I have found online tell me to open up a terminal only after the OS boots correctly. Sadly, I cannot even get to that stage, so I can't use that solution.


By the way, I am VERY new to Virtual Box and creating virtual machines, so excuse me if I'm not familiar with some of the terminology. Another thing, if it helps, is that I'm running Windows 7 as my host OS.

share|improve this question
Have you considered accepting Guest_vh's solution as an answer? – Mike Jan 29 '15 at 20:51

16 Answers 16

Turn off the option "Enable Nested Paging" in the VirtualBox configuration under Settings->System->Acceleration.

This allowed me to get Ubuntu running with the desktop.

share|improve this answer
This worked for me when trying to install Xubuntu 14.10 on VirtualBox 4.3.18_Ubuntu. It seems like the simplest solution by far. Hopefully the author will accept it as the answer. – Mike Jan 29 '15 at 20:51
Confirming this works with Ubuntu 15.04 as well. – arhuaco Jun 9 '15 at 19:14
Yes, this worked for me to. This should be the accepted answer. – Andritchi Alexei Aug 7 '15 at 12:35
BEWARE: Applying this fix could cause your VM to do this: (guest OS is Xubuntu 15) – Mike Mügge Feb 25 at 17:20
Didn't work for me, virtual machine still won't boot (guest OS Ubuntu Gnome 15.10, host W10). – Mr D Mar 9 at 5:11

This answer is from:

SMBus base address uninitialized - upgrade bios or use force_addr=0xaddr

This error is caused by VM having no smbus but Ubuntu always trying to load the module. It doesn't affect anything but is a bit annoying.

  1. Check module is being loaded

    lsmod | grep i2c_piix4
  2. If so, blacklist it in the file /etc/modprobe.d/blacklist.conf, by adding the following to the end of the file:

    blacklist i2c_piix4
  3. Update the initramfs

    sudo update-initramfs -u -k all

You might want to optionally remove unneeded kernal images before updating the initramfs to cut down on how long that part takes.

share|improve this answer
MountainX sorry to say you are wrong it does affect something it will stop you from loading Ubuntu into a virtual state so in that term it does affect something you will end with a black screen for hours no matter speed or such I got the same results trying it with the information. – user256572 Mar 9 '14 at 23:51
Your comment doesn't make sense to me... However, if you think this information is wrong, please take that up with the person who wrote it at the link I gave. I only copied that information here. – MountainX Mar 10 '14 at 1:38

We can safely ignore the warning

SMBus base address uninitialized 

This indicates that we run without a System Management Bus, which is to expected on a virtual machine.

Your boot failure does have a different reason. Anything from incompatible settings of your virtual machine to incompatibilites with your Windows kernel or drivers.

Try to boot the virtual machine while pressing and holding the left Shift key to boot a root shell for further investigation, to upgrade your guest OS, or to install the guest additions.

share|improve this answer
installing guest additions did the trick for me. – th1rdey3 Nov 19 '14 at 4:32

The error message is not related to the problem of Ubuntu not booting. I have had the same problem. After displaying the error message the colors became crazy and the system seems to halt, however moving the mouse resulted in some pixel garbage.

Disabling "Nested Paging" in Setting->System->Acceleration allows to start the system.

Tested using VirtualBox 4.3.20 (64bit on Windows 7) with Kubuntu 14.10. After changing the setting, I was able to boot and install Kubuntu, however the error message appears on every boot.

share|improve this answer

I am running Virtual Box 5.0.0 r101573 on Windows 7 Enterprise SP1. Ubuntu 15.04 has the problem listed, which went away after I unchecked Enable Nested Paging.

share|improve this answer

This message appears in my VirtualBox while I was installing/starting Ubuntu 15.10. (The same problem will occurs for previous version as well)

The solution was I restarted my computer and went to BIOS. I enabled Intel® Virtualization Technology (Intel® VT).

Save my BIOS configuration.

Start VirtualBox, (Ctrl+s) right click on your image Settings->System->Acceleration.
And check Enable Nested Paging in Acceleration Fan enter image description here

and fire-up Ubuntu and walla it works with out any problem.

share|improve this answer

Encountered a similar issue and the same fix worked for me. On my pc i get a blank screen and in VirtualMachine i get the force_addr=0xaddr error after upgrading from a workstation.

Found the fix at: My computer boots to a black screen, what options do I have to fix it?

Just hold Shift when starting to get into GRUB, press E to edit the entry, search for "quiet splash" (without commas) erase that and type in "nomodeset" (no commas) and then press Ctrl+X to boot.

I actually typed just "nomode" once and it still booted for me.

share|improve this answer

Solved in my case.

When I loaded a virtual Mint 17.1 on a Virtualbox 5.0.0, I stranded in this situation. I tried the procedures shown by MountainX.

Next, an another error (No support for locale: en_US.utf8) occured and was solved by this command:

locale-gen --purge --no-archive

After that, I encoutered a login loop and attempted to solved it with a following article (Japanese):

rm -f /home/<user>/.ICEauthority
rm -f /home/<user>/.Xauthority

Finally a virtual mint 17.1 works well on a VirtualBox 5.0.0.

I wish this will help you.

share|improve this answer

Encountered the same issue after ubuntu software update(kernel image was updated with this batch of updates).

Workaround: enter grub menu recovery mode for your kernel -result the os loads completely

A persistent workaround: edit /boot/grub/grub.cfg and add the word nomodeset right along [quiet splash] -result os will load completely even after restarts


Once inside the OS(after a successful boot), Reinstall the VBoxLinuxGuestAdditions

NOTE: the message "SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr" still shows up even when the workaround/solution is applied.

HOST: OSX Yosemite 10.10.3, GUEST: Ubuntu 15.10 (lubuntu), KERNEL: 4.2.0-25 generic(updated from 4.2.0-16), VBox: 5.0.14

share|improve this answer

I think it is a common problem caused by not changing the boot order from 'optical disk' to 'hard disk' and can be remedied by 'Power off' the VM then selecting the "System" setup option in the VM and UNcheck the "Optical Disk" selection in the boot order. Then try again ...

I sometimes forget to do it too and have been using VM's since dinosaurs ruled ... :). I also move the "Optical Disk" down in the selection order but doubt that matters - it is not a real 'BIOS' option for the VM even tho' it does act like it.

It could of course be something more sinister/complicated but this method has always worked for me.

HTH ...

share|improve this answer

Turn off other virtual machines. This includes "saved-state" machines.

Whew, I thought I was in trouble for a second there.

Running Ubuntu 16.04 i386 on a 64 bit system; decided to install a 64 bit version of Ubuntu on a virtual machine. I looked up everything and it says I can do it.

When I ran the ISO on the VM using Oracle Virtualbox, I kept seeing an orange error on boot similar to this one:

SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr

Then the display was all colors and blocks and you know was like "This is a test of the emergency broadcast system..."

It didn't say that; it just looked like that to me.

Anyway, I have another VM on Virtualbox that I'd left in a "saved state." I force quit her. I was able to boot to the ISO on the PIA machine after that.

share|improve this answer

Same symptoms as The Emperor of the Republic when installing Ubuntu 16.04 LTS desktop to vm on Virtual Box 5.0.20. Changing to 2 processors and 48MB Video memory and disabling Nested Paging under System / Acceleration permitted installation, but had similar screen on reboot. Booted into grub recovery mode took care of it.

share|improve this answer

If you have ICH9 available, switch to that instead of the PIIX3 chipset (Settings->System->Motherboard). Support for it is 'Experimental' by VirtualBox, but it's stable on my Mac Book Pro host.

share|improve this answer

I am loading a virtual Ubuntu 14.04 onto a virtual Mint 17.1.

The error was the same however I just continued to boot until it booted up. We're talking about a host to guest in which becomes the host to another guest. Don't get concerned about errors, just simply get back up and start "walking" again.

share|improve this answer

I started receiving the exact same error when starting a VM of Ubuntu 14.04 inside VirtualBox. In my case the acceleration options mentioned by maytham were grayed out. I was able to correct the issue by increasing the processor execution cap from 1% to 41% (Settings->System->Processor). image of VB system>processor options

share|improve this answer

Only Enable EFI checked allowed me to be able to install, just saying.

It's on one the tabs in system, where I was looking about the nested option.

(I must provide a more complete answer, with the exact details. Latter.)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.