I just ran a quick test of the existing instance of Windows XP I had set up using Virtual Box to see if the software would run in Hardy Heron.
Initially Win XP wouldn’t load and I got an error indicating:
“VirtualBox kernal driver not installed. The vboxdrv kernal moducle was either not loaded or /dev/vboxdrv was not created for some reason. Re-setup the kernal module by executing ‘/etc/init.d/vboxdrv setup’ as root.”
However once I ran the command referenced by the error message I found I could boot up the virtual Windows XP OS just fine.
Looks like my fears that VirtualBox wouldn’t run on Hardy Heron yet have been proven unfounded. I’m happy to be wrong. (Apologies for the audio/video sync problems in the following clip.)
[youtube=http://youtube.com/watch?v=BzZIF0KOfBo]
Screenshots:
hi,
where did you follow the instruction when installing virtualBox on hardy heron ? I tried it earlier and after rebooting, the wireless and sound are gone.:(
Hi Jan,
Actually I didn’t install VirtualBox on Hardy Heron; the installation was already on my machine when I upgraded. I originally installed it on Gutsy Gibbon using the ‘deb http://www.virtualbox.org/debian gutsy non-free’ download from the Sun website. Then I followed the steps outlined on this YouTube clip here:
“How to run Windows XP on Linux Ubuntu with VirtualBox“
In my case when I upgraded to Hardy I had no idea whether VirtualBox would even work. I found the program started ok but the virtual machine wouldn’t load and instead displayed an error. All I did in Hardy was follow the instructions outlined in the error to reconfigure VirtualBox and found it worked. The fact you’re trying to perform a fresh install is a different matter entirely and I’m afraid I don’t have any experience in that respect. Though we can try and work this out together if you like.
That said though, are you aware of the fact you have to enable certain hardware elements in the VirtualBox settings area before they will become available to the virtual instance? For the record, they are available by highlighting the virtual machine in question, clicking settings, and then choosing an option from the left menu.
Note the virtual machine can’t be on, otherwise the settings option will be greyed out and unclickable.
In my case I believe the networking settings were enabled by default, but the sound wasn’t. I found once I ticked Enable Audio and chose the ALSA Audio Driver option I was able to hear sound in the virtual machine. There are options for both in the VirtualBox settings area and that’s where I’d look first if you haven’t already.
That said I hope you don’t mean your main Ubuntu wireless settings and sound are gone! Do you?
I’m happy to try and troubleshoot this issue with you if you care to provide a bit more detail on what’s happening and what you’ve done in the preliminary setup process.
Cheers,
Mike
This is exactly correct. after the upgrade just run
sudo /etc/init.d/vboxdrv setup
virtualbox is back
I had the same problem as Jan. To clarify, and Jan can correct me if having other symptoms, when I reboot I have no network or sound on the host OS. When I reboot my Ubuntu Hardy Heron install has no sound and no wireless connectivity at all. This was a fresh install attempting to get away from VMware.
I’m running the 2.6.24-16-generic kernel on a toshiba Satelite laptop.
I chose the VirtualBox 1.6 for Ubuntu 8.04 x86 from the dropdown on the VirtualBox site
Its also a fresh install of Hardy Heron – not an upgrade since I backed all my data up and did a clean install. (it had been a while…lol)
If you need me to run something and post the results just let me know.
Thanks in advance.
Hi Jack,
I’ll see what I can track down about this. In the short run I’ve run across a bug report on the VirtualBox website that sounds similar to the issue you mentioned regarding loss of sound.
“No sound available in host system after installation.”
Note this relates to previous versions of both VirtualBox and Ubuntu however, so it may prove unhelpful to you and Jan.
As far as the wireless connectivity is concerned I’ll keep digging.
Out of interest, have you tried running:
sudo /etc/init.d/vboxdrv setup
Cross your fingers, I’ll keep you posted on what I can track down.
Cheers,
Mike
Update: This may be potentially useful. I’ve just run across another bug report on the VirtualBox site from someone saying “Starting VirtualBox breaks host networking“.
The bug report is from mid-January and doesn’t appear to have had any responses, however the person who filed the report suggests a work around:
I have to say that I don’t know exactly what this command does though, so I’d recommend reading up on this elsewhere and/or contacting someone with more expertise in the commandline before implementing the command.
[NB: this may prove useful: "Disabling and Enabling network connections using CLI"]
Also, if you have luck with it you might want to add to the discussion on the bug report in the hopes of assisting others who are having similar difficulties. You’re more than welcome to post your results here too of course
Reference:
- “Ticket #277: No sound available in host system after installation.”
- “Ticket #845: Starting VirtualBox breaks host networking
I did a fresh install of Hardy Heron and then Add/Remove VirtualBox. I then tried creating a VM and get the following message (which is slightly different than yours.
“VirtualBox kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Please install the virtualbox-ose-modules package for your kernel, e.g. virtualbox-ose-modules-generic..
VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED).
Result Code:
0×80004005
Component:
Console
Interface:
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}”
I tried the “vboxdrv setup” approach, but per the comments:
Daniel Hahler: # – Removed “setup” action
Anyone with another idea?
I just found my answer (finally).
The VirtualBox I installed via the Add/Remove Programs list is the Open Source Edition which does not install all the parts and dependencies. I used the normal VirtualBox program
I removed it (via add/remove programs) and hten installed the sun released package which included the dependencies. I found the solution with instructions here:
http://ubuntuforums.org/showthread.php?t=770745
Hi Gary,
Good to hear that you got VirtualBox running, and thanks for posting your findings here. Hopefully your experiences will be of use to others who run across this post.
Cheers,
Mike
Pingback: Virtual Machines vs Parallel Installations « TechTicker