virtualbox.org

So, today for some strange reason I seemed to have an issue with running the x64 guests I had installed yesterday (3 different instances of x64 ubuntu) refused to start (Stating that the detected proc is i686 & the kernel required x64 instead and to go install the correct kernel...) & a new instance of Solaris 10 I installed today went in as x86 instead of x64.

Long story short after tweeking all of the usual pseudo-processor'ish virtualization variables under the advanced tab to no avail, I took it upon myself to uninstall & reinstall purely for QA purposes...

Thankfully my virtual instances I had built the other day are still there (and they ACTUALLY DO run as expected now after reinstalling), however I seem to have somewhat of a issue (or at least I perceive).

In the process of building each of my instances, I wound up making a seperate virtual network adapter for each, In Vista's "Network Connections" none of these virtual interfaces now exist, not a big deal -Ill just recreate them... So I go to recreate them & the old names of all of the virtual instances are still there (Only the ones in use by each instance, not all lumped together like how they normally show, I can see the new virt-interfaces I just built lumped together -Just not the old ones), and I cant get rid of these previous existing interfaces and Im thinking that this will throw my naming convention for virtual interfaces.

Is there something Im missing here, or are there some reghacks I need to put in place to blow away the old instances?

And even more importantly, how can I keep from having to uninstall/reinstall the virtualbox hypervisor to run my x64 instances as expected?

Thanks,
D

2.0 is quite unstable. See the VirtualBox FAQ for what you need in order to run 64 bit clients (manual chapter 1.6 does the same).

Host Interfaces should be removed when you uninstall or upgrade VB. That's why they aren't listed in VB. Check your Device Manager to see if they are still listed there. You can remove them there if needed (and if possible).

Sasquatch,

I understand fine what is required to run x64 guests, to me it just seemed quite strange that one day x64 guest OS's would run as expected, and the next they wont... <Shrug>

In any event, last night after reinstalling I rebooted & they still worked fine. Im currently running some x64 guests in VB as we speak and they appear to be working as expected still, it just seemed as though something was gravely wrong when they wouldent work at all (after they were), and I made all the processor-level tweeks on the advanced tab possible & they still wernt working.

Anyway, after rebuilding all of my instances's network interfaces -It now appears as though there are no unuseable remnants of old virtual interfaces from the previous 2.0 install But Ill keep in mind to blow them all away prior to uninstalling or upgrading next time arround... =)

Thanks for the prompt responce !
-D

BTW- By any chance, do you happen to have an idea (time-wise, version-wise, or preferably both? ) when a more stable build will be available if this one is bleeding edge?

I know that they are working on it. The release is unknown, but if you look at the previous releases of 1.6.x, you can estimate when it can be online.

Exact same problem here. All Ubuntu 64-bit guest work one day but not the next. I think it has something to do with the host coming out of sleep. I did a complete powerdown of host and then Vbox was OK again.

I was just checking here to see if others were having same problem of found a solution yet. I has happened to me three times now. Very intermitant.

My thoughts are that Virtualbox is the cause of all of my Linux woes. Life would be allot easier if I just went out and bought a cheap box and throw linux on it.........

Arg!

My power-off reboot in 64-bit Vista Ultimate solved my problem and now Vbox 2.0.6 is presenting a 64-bit system to my 64-bit Ubuntu 8.04. I am no longer getting the error that Ubuntu needs a i686 64-bit CPU to run. I am not sure if a complete power-off boot is neccesary.

Like I said this is an intermittent problem. I think it has to do with the Vista guest sleeping and Vbox not coming out of it properly. Restarting vbox does not solve the problem. It takes a Vista reboot. Vbox was not running when Vista went to sleep.

What is odd is that I gott the various popup windows from Vbox regarding mouse/cursor and keyboard (Check not to see again) windows,when I reboot the Ubuntu guest after this problem occured. It may be because I reset all errors under the help pulldown. Not sure.

I am not a very good debugger anymore since I tried various things all at once. I an just happy it is working again after all the time I put into the Virtual Ubuntu.

I probably created more questions than I answered.

VT-x issues after suspending the host machine are known and fixed in the upcoming release.