virtualbox.org

belzecue wrote:What's the feeling on 2.2.4? Safe to upgrade from 2.1.4 now? All the horrible bugs from 2.2.0 gone?

i only had one bug with 2.2.2 and that's fixed in 2.2.4 (solaris guests).

2.1.4 had loads more bugs that any of the 2.2 series, and lots less functionality.

or are you using a windoze host?

sej7278 wrote:

belzecue wrote:What's the feeling on 2.2.4? Safe to upgrade from 2.1.4 now? All the horrible bugs from 2.2.0 gone?

i only had one bug with 2.2.2 and that's fixed in 2.2.4 (solaris guests).

2.1.4 had loads more bugs that any of the 2.2 series, and lots less functionality.

or are you using a windoze host?

Even with Windows host, 2.2 was better than 2.1.4...

I used 2.2.4 all day today, and I must say, it's quite speedy. It seems a bit more responsive... before with 2.2.2 I would get an occasional few-second hiccups.
I can also verify that COMPACT is indeed fixed. Overall I am very satisfied with this release.

One thing I have noticed though is that since 2.2.2 Windows XP 32bit takes more time to login than previous releases. Before the "Welcome" screen was just a flash, but now it seems to wait maybe 20 seconds. Maybe it has something to do with a change in the 2.2.2 Guest Tools? I might try uninstalling them and checking performance

Do you use Shared Folders and have them mounted permanently? If so, that's probably the reason. Windows tries to mount shared at logon. Just for fun, hit Alt+Tab when you see the Welcome message, you might be able to switch to a different task that is mounting the shares. Hitting Esc will cancel that, logging you in directly. The shares will still be available, but mounted when you access them.

Hmmm. Finally got around to testing some of the bugfixes, thought I'd start with Solaris x64 hanging. I clicked on "settings" for my Solaris VM, so I could re-enable VT, and I get a "Failed to access the USB subsystem. Could not load the Host USB Proxy Service (VERR_FILE_NOT_FOUND). The service might not be installed on the host computer." error. Happens when I edit settings for any VM, but all the VMs seem to work fine. Host is Vista x64.

Here's a reproducible way to make VirtualBox hang on startup:

1. Edit your machine xml file

2. define two port redirections with the same LUN/names... e.g.

<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/pmwiki/Protocol" value="TCP"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/pmwiki/GuestPort" value="443"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/pmwiki/HostPort" value="443"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/pmwiki/Protocol" value="TCP"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/pmwiki/GuestPort" value="80"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/pmwiki/HostPort" value="80"/>

3. Voila. That VM now hangs indefinitely on startup.

Yes, it's a silly mistake for a user to make, but there is no error checking to catch this situation.

SSCBrian wrote:Hmmm. Finally got around to testing some of the bugfixes, thought I'd start with Solaris x64 hanging. I clicked on "settings" for my Solaris VM, so I could re-enable VT, and I get a "Failed to access the USB subsystem. Could not load the Host USB Proxy Service (VERR_FILE_NOT_FOUND). The service might not be installed on the host computer." error. Happens when I edit settings for any VM, but all the VMs seem to work fine. Host is Vista x64.

That's when USB isn't working properly. You only get a warning, the rest will still function. It means that you can't use USB in the VM.

belzecue wrote:Here's a reproducible way to make VirtualBox hang on startup:

1. Edit your machine xml file

2. define two port redirections with the same LUN/names... e.g.

<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/pmwiki/Protocol" value="TCP"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/pmwiki/GuestPort" value="443"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/pmwiki/HostPort" value="443"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/pmwiki/Protocol" value="TCP"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/pmwiki/GuestPort" value="80"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/pmwiki/HostPort" value="80"/>

3. Voila. That VM now hangs indefinitely on startup.

Yes, it's a silly mistake for a user to make, but there is no error checking to catch this situation.

You should use the VBoxManage command line for that. It has some error checking, and should mention this when you use ports below 1024 as HostPort value when not running the VM with administrator/root privileges. On Linux, you can't run a VM as root like that, because the root user doesn't have the VM registered. In Windows, you have the same problem, but you usually run with administrator privileges anyway.

Sasquatch wrote:

SSCBrian wrote:Hmmm. Finally got around to testing some of the bugfixes, thought I'd start with Solaris x64 hanging. I clicked on "settings" for my Solaris VM, so I could re-enable VT, and I get a "Failed to access the USB subsystem. Could not load the Host USB Proxy Service (VERR_FILE_NOT_FOUND). The service might not be installed on the host computer." error. Happens when I edit settings for any VM, but all the VMs seem to work fine. Host is Vista x64.

That's when USB isn't working properly. You only get a warning, the rest will still function. It means that you can't use USB in the VM.

Is it normal for USB to not work in 2.2.4 then? I never got this message in previous versions. No big deal since I don't use USB in my VMs I guess.

SSCBrian wrote:

Sasquatch wrote:

SSCBrian wrote:Hmmm. Finally got around to testing some of the bugfixes, thought I'd start with Solaris x64 hanging. I clicked on "settings" for my Solaris VM, so I could re-enable VT, and I get a "Failed to access the USB subsystem. Could not load the Host USB Proxy Service (VERR_FILE_NOT_FOUND). The service might not be installed on the host computer." error. Happens when I edit settings for any VM, but all the VMs seem to work fine. Host is Vista x64.

That's when USB isn't working properly. You only get a warning, the rest will still function. It means that you can't use USB in the VM.

Is it normal for USB to not work in 2.2.4 then? I never got this message in previous versions. No big deal since I don't use USB in my VMs I guess.

No, it's not normal to get this message when it worked before. Did you have the same problems with 2.2.0 and 2.2.2, or did you upgrade from 2.1.4 directly to 2.2.4? Are you sure you enabled USB during installation? Maybe a repair will fix it.

Sasquatch wrote:No, it's not normal to get this message when it worked before. Did you have the same problems with 2.2.0 and 2.2.2, or did you upgrade from 2.1.4 directly to 2.2.4? Are you sure you enabled USB during installation? Maybe a repair will fix it.

Upgraded from 2.2.2 (which was upgraded from 2.2.0, and so on). Never had this message come up in any prior version. I'll try a repair (and uninstall/reinstall too if the repair doesn't do it) later on and see how it goes.

When I upgraded sometime ago from 2.1.4 to 2.2.2 I had issues on the networking area, so I went back to 2.1.4. With this new version I have tried it again and now it's working fine. The only thing which is not working in this release but also in the release of 2.1.4 is that the mouse integration within Windows XP guest system doesn't work. Within my Windows Vista guest system it does work. Maybe somebody knows the resolution for this problem. Now I need to activate and deactivate the USB mouse device to get it activated and deactivated within my Windows XP guest system.

alvarf wrote:When I upgraded sometime ago from 2.1.4 to 2.2.2 I had issues on the networking area, so I went back to 2.1.4. With this new version I have tried it again and now it's working fine. The only thing which is not working in this release but also in the release of 2.1.4 is that the mouse integration within Windows XP guest system doesn't work. Within my Windows Vista guest system it does work. Maybe somebody knows the resolution for this problem. Now I need to activate and deactivate the USB mouse device to get it activated and deactivated within my Windows XP guest system.

dunno about windows, but you shouldn't have to have a usb mouse connected via the usb filter system for it to work - on linux at least the host mouse is automagically connected to the guests (including xp) even on guests without usb enabled.

also, have you remembered to upgrade your guest additions to 2.2.4?

sej7278 wrote:

alvarf wrote:When I upgraded sometime ago from 2.1.4 to 2.2.2 I had issues on the networking area, so I went back to 2.1.4. With this new version I have tried it again and now it's working fine. The only thing which is not working in this release but also in the release of 2.1.4 is that the mouse integration within Windows XP guest system doesn't work. Within my Windows Vista guest system it does work. Maybe somebody knows the resolution for this problem. Now I need to activate and deactivate the USB mouse device to get it activated and deactivated within my Windows XP guest system.

dunno about windows, but you shouldn't have to have a usb mouse connected via the usb filter system for it to work - on linux at least the host mouse is automagically connected to the guests (including xp) even on guests without usb enabled.

also, have you remembered to upgrade your guest additions to 2.2.4?

I have upgraded my guest additions (2.2.4r47978). I believe you should enable the usb controller support within the settings of the Windows XP guest so when it boots it enables the usb poorts. If you do not enable this option usb support is not enable within Windows XP guest system.

My host is windows 7 64bit,virtualbox 2.2.4 everything seem work fine but sometime VB hang and I can't access my windows 7 taskbar (But other App still work), I must press Ctrl + Alt + Delete and end VB then every things come back to normal! I don't know why! Maybe it's a bug with windows 7 64bit?

alvarf wrote:I have upgraded my guest additions (2.2.4r47978). I believe you should enable the usb controller support within the settings of the Windows XP guest so when it boots it enables the usb poorts. If you do not enable this option usb support is not enable within Windows XP guest system.

forget usb, the type of mouse your host uses is irrelevant.