virtualbox.org

Clean Vista x64 install, then clean VB 3.0 install, then clean Ubuntu 8.10 x64 guest including all the updates and latest drivers for guest and host... And no Compiz with 3D enabled in Ubuntu... But I saw it, I swear, with VB 2.2.x...

Updating from 2.2.4 to 3.0.0 on opensuse 11.0:
Xp guest is rebooting and crashing, only boot after select know configuration. Guest does not permit copy files and files modified cannot be accessed again on virtual folders.

reverted to 2.2.4 and after some reboot all is normal again.

Marcelo Anelli

I'd like to share my expirience with new 3.0.0 release. My host OS'es are Fedora 11 and Ubuntu 9.04, guest OS'es are Fedora 11 and WinXP SP3.
I upgraded from 2.2.4 to 3.3.0 on both hosts.

1. On host with Genuine Intel(R) CPU 2160 (2 cores) under Ubuntu VB does not allow to use 2 CPU, IO APIC is on.
2. On host under Fedora 11 it is necessary to manually handle USB fs mounting, usb group creation and so on. May be it is Fedora fault but it can be done automatically by RPM installation script.

3. WinXP goes to infinite reboot after upgrading to new guest additions and rebooting. It is necessary to hit F8 and boot in "last working configuration" mode, remove old guest additions and install new. Something from old guest additions package does not get removed by Windows installation.

4. Fedora 11 guest waits a lot on "power on" if ACPI is on. Sometimes it does not boot at all with ACPI on.

There are other minor glitches too but above is most annoying. I understand that major 0.0 release is actually RC but SMP feature was one I've been "bought by", and this feature does not work for me. I'll may be stay with 3.0.0 release and wait instead of downgrading. Hope things go fast in open source world.

Anyway, thaks to authors for new major release.

Just follow-up about registration screen. It is silly, really silly. I have Sun's account for 10 years but use it from occasion to occasion and do not remember password. My Firefox browser does. Normal registration procedure will invoke browser and take you to registration/login page with password restore functionality. This new registration feature of VB 3.0.0 drives me just crazy. Open product registration must be optional, smart an easy. Nobody needs stupid one.

alukin wrote:Just follow-up about registration screen. It is silly, really silly. I have Sun's account for 10 years but use it from occasion to occasion and do not remember password. My Firefox browser does. Normal registration procedure will invoke browser and take you to registration/login page with password restore functionality. This new registration feature of VB 3.0.0 drives me just crazy. Open product registration must be optional, smart an easy. Nobody needs stupid one.

what's REALLY stupid is that you have to register at all.

is it just so sun can spam you?

if they want some usage statistics they have download logs.

Deleted by user

Again complaining about the registration? Is it really so hard to dismiss the dialog? It won't come back after three times.
I'd say pressing escape three times if you don't want to register is a small price to pay for a free piece of software.

Some people are really hard to please it seems. (most aren't, I know)

I don't mind to register. I registered already. I'm not complaining. I'm just criticizing really silly solution. You may have button "Never register" in this dialog as OO does. You may redirect user to actual SUN's password retrieval page if user enters invalid password. By the way, SUN's password retrieval for my old logins did not work...

Registration of free software is good thing (tm) because it gives real user base authors can relay on. Creating stupid registration service and GUI is bad thing (tm). It irritates users.

Wow, this release failed quickly and dramatically for me. Debian testing host (AMD64), Debian stable guest (x86). Running "apt-get update; apt-get upgrade" in the guest causes the VM to lock up solid; no mouse pointer response, no keyboard response, and VirtualBox consuming 100% of CPU. Tried twice and rolled back to 2.2.4, then the operation worked fine.

I upgraded from 2.2.4 and everything seemed to work fine. I am using a Windows XP sp3 host with 3 winxp sp2 guests.
I installed the 3.0 guest additions on one of my guests and rebooted and it started BSOD'ing at the Winxp Logon screen, I assumed it was from the guest additions so I started the guest in safe mode to uninstall the 3.0 guest additions. I did this and rebooted and it still BSOD'd.
I then tried the other 2 guests without installing the 3.0 guest additions and on reboot they both BSOD'd.

Now going back to 2.2.4! Thank god I took backups before trying 3.0!!!

I guess that problem root is lack of beta testers. There were no announces of beta releases on main virtualbox.org site and no noise in news. I discovered beta2 only on forums. Therefore real testing of release started only after 3.0.0 release.

OS X 10.5.7 Host. Upgrade was smooth. My Ubuntu 9 VM had no problem at all (upgraded the guest additions, feels a little faster). The Win XP guest went well. The Windows 7rc guest had a little hickup: after upgrading the guest additions and restarting, I was greeted by a message that the Windows 7rc install may not be genuine or some words to that effect - the WGA thing maybe ? Does installing the guest additions modify that Windows 7 rc install that much that it thinks it is a different install ? The only option I was offered was to cancel out of the message, and continue doing what I wanted.

I haven't tried the new toys on all those VM's yet. One thing I did note is that the VM manager feels a little more integrated into OS X. Nice.

Two wrote:VBox 3.0 on XP Sp3, Intel DualCore with 2 CPUs activated runs smooth, but after some time the VM screen freezes and the whole VM just hangs up. There is no load on the VM and I can control the host OS normally, but except for a reset, there is nothing I can do inside the VM, even the mouse pointer is no longer visible inside.

This is reproducable by letting the VM run idle with just the screensave active for some time (about 30-60 minutes). I experienced the same problem in the 3.0 beta.

The only setting I changed from the default settings is the ICH6 Controller and SATA. No DirectX/3D.

I believe that multicore support is broken. When I enable 2 core out of my Q9300. It seems to work alright but just lock up randomly. Cant even install windows XP with dual core enabled. When I enable all 4 cores the performance drops into useless and takes hell long to boot up fully. Im shocked that this could pass beta testing and nobody noticed it.

http://forums.virtualbox.org/viewtopic.php?f=2&t=19549
http://forums.virtualbox.org/viewtopic. ... 399#p84399

Considering the extremly short time from Beta2 to release and the amount of lockup/crashes, I get the feeling, that this release was rushed live too early.

Ugh

Upgraded to 3.0 on Ubuntu 64 bit Jaunty host.

I ended up wiping out my 32 bit XP guest. Stupid of me, I guess. I had made a snapshot of my VM, then after turning on two CPUs noticed XP saw but wasn't using both CPUs. After googling for how to upgrade XP to use the SMP kernel, I did the fix and rebooted the VM and black screen. I tried to revert the snapshot and it did a fuel gauge thing to 100%. Then I tried to boot off the reverted image and it told me the image was created with a different version of virtualbox and wouldn't boot it or let me edit the settings or anything. So I couldn't even boot off an XP CD to repair it.

So I set up a new vm with 2 processors and installed XP again. Horribly slow, and BSOD on a fresh install on the first login (to a domain). Rebooted the VM and it hung forever at the "loading your personal settings" dialog in XP, no start menu, no icons, no way to do squat with it.

So I wiped that out and set up a VM with 1 processor and XP installed like a champ and runs at least 30x faster (ridiculously noticeable) than with 2 processors in the VM. It just works.

EDIT: 1 CPU vs. 2 CPUs in the VM is incredibly faster. Things happen in the blink of an eye. The Windows install in a new VM with 2 CPUs took 3 hours. In a new VM with 1 CPU took 15 minutes. The 1 CPU VM boots windows in 5 seconds. Login to domain and load personal settings (it is a fresh XP install) in like 1 second.

I was hoping the 2 CPU VM would make firefox run faster. Well, appear to run faster, since it can hog a lot of one CPU and having another to do things like drag windows around or interact with other apps makes it feel faster.