Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

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 at 20:51

5 Answers 5

This answer is from: http://finster.co.uk/2010/11/16/virtualbox-piix4_smbus-error/

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

This post is quite old so I am not sure if this answer will be useful. I met a similar problem with VirtualBox, and turned off the option "Enable Nested Paging" in the VM configuration under Setting->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 at 20:51

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 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

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.