Discuss the 4.0.4 Release

[david2tm]

I have installed clean version (none was installed before).
Whenever I activate "VirtualBox Host-Only Network" LAN card on Host (Win7x64) the other LAN card can't connect to Internet.
Nothing is running on VB, just LAN enabled. If I disable the card - I can get Internet back.

[abcuser]

Nevermind...they are under /usr/share/virtualbox in the ISO image. Just mount the image:

Code: Select all

# mkdir /dvd
# mount -o loop VBoxGuestAdditions.iso /dvd
# 

Guest additions are in Linux available under /media/VBOX... directory. So by default there should be no mount needed.

[Etepetete]

The USB functionality functions very good. Very responsive and no lag accessing my USB stick via the VM.

While installing, I had similar issues as with past versions. I inserted my USB stick in the host started VBox GUI and then selected a filter for the USB stick. I closed VBox GUI, removed the USB stick, restarted the VBox GUI and booted the VM. I then inserted the USB stick where I then received the usual prompt from the host about installing the VBox USB driver and the unsigned driver, etc. After installation the VM didn't pickup the USB stick nor did my host see it. I shut down the VM, closed the VBox GUI and shut down my host before removing my USB stick. After restarting my host and VM, the USB stick was promptly recognized by the VM upon inserting it into my host.

[Etepetete]

I installed an update from MS Update and was prompted to restart. After ca. 4 minutes the VM screen turned black. After 25 minutes I ran Sysinternals Process Explorer and noticed the same KeyedEvent \KernelObjects\CritSecOutOfMemoryEvent. This was in the VBox.exe under explorer, the VBox.exe under VBoxSVC and in VBoxSVC.exe itself.

Copies of the handles view from Process Explorer are attached as well as the log file from the VM and the VMs xml file. I tried closing the VM window via the machine menu and nothing happened. When I tried closing the VM window via the red X I was prompted that it was not responding and selected to shut it down. Closing the VBox GUI thereafter was successful.

[Etepetete]

RE: Restart Issue

I wasn't able to exceed the limit of three attachments so here are the log file and the VM xml file.

[garym]

Hi,

First posted on the OpenSolais Guest forum, after no replies, I'm posting here...

Upgraded to 4.0.2 and installed guest 4.0.2, upgraded to 4.0.4 and guest 4.0.4 with the same result. Installing the Guest additions I get error: "Unknown version of the X Window System installed." The drivers were not installed.

On reboot it did not load virtual box drivers. Xwindows failed to complete loading. I guess the installer didn't lie.

Is there a work around to this issue ?

From the log file:
(II) Loading extension SolarisIA
(II) LoadModule: "xtsol"
(WW) Warning, couldn't open module xtsol
(II) UnloadModule: "xtsol"
(EE) Failed to load module "xtsol" (module does not exist, 0)
(II) LoadModule: "vboxvideo"
(WW) Warning, couldn't open module vboxvideo
(II) UnloadModule: "vboxvideo"
(EE) Failed to load module "vboxvideo" (module does not exist, 0)
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers/amd64/vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
compiled for 1.7.4, module version = 2.2.1
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "fbdev"
(WW) Warning, couldn't open module fbdev
(II) UnloadModule: "fbdev"
(EE) Failed to load module "fbdev" (module does not exist, 0)
(II) VESA: driver for VESA chipsets: vesa
(II) Primary Device is: PCI 00@00:02:0

Xwindows info:
X.Org X Server 1.7.4
Release Date: 2010-01-08
X Protocol Version 11, Revision 0
Build Operating System: SunOS 5.11 i86pc
Current Operating System: SunOS opensolariscloud 5.11 snv_134b i86pc
Build Date: 22 May 2010 10:19:23AM
Solaris ABI: 64-bit

[omascia]

I probably spoke too quickly, here:

Moved up from 4.0.2 to 4.0.4 on Mac OS X 10.6.6 host running a set of Windows 7 VMs (64 and 32 bits) and XP (32 bits), all usual features look good and those small ACPI issues I had reported (like others) and worked around in 4.0.2 seem properly fixed in 4.0.4. Seen from here with those mainstream host and guest, VB 4 now looks really nice. Performance is excellent too. ...

Well it turns out that USB support is completely broken: using a Mac OS X host, a Windows 7 64 bits guest, especially with more than one cpu. I have devices that only are recognized / working with a single cpu and fail with 2 or more, while another fail in all cases and is recognized with a strange change in the device name "Symbol PocketPC Device" becomes the strange "Symbö PocketPC Device" which in turns, despite the single cpu trick, fails the auto-connection on Windows side and the device is unusable.

There clearly is a *big* issue with USB, at least on some configurations. If only I had already some more experience with Vbox code and build procedure, I'd be hopefully more helpful than just reporting this here and in the bugtracker.

[omascia]

Well it turns out that USB support is completely broken: ...

Well, more than this, it looks like a (bad) joke, not even a buggy feature. I would slam my head on the wall not to have tested USB support earlier, taking it for granted (or not fearing anything about it) based on past experience with vmWare Fusion on one hand and Parallels Desktop on the other. I know both these other products also had USB difficulties, in their infancy, though here VirtualBox sports a nice V4.something tag.

I made more tests tonight on a Windows 7 guest (32 bits) on a distinct host hardware. The issues are NOT related to 32 or 64 bits, it's as weird in both cases. The number of cores configured for the VM is clearly part of the equation, but not the single variable. Once, but only once, I saw my Voyager GT USB disk connect correctly. If there is a sequence of actions to do for this, I didn't recognized it and could not reproduce this apparently erroneous ephemeral success.

Hopefully the Extension Pack (which brings closed-source USB support) is still available for free, else it would be good for a refund. For the same reason, I cannot offer to help fix it, other than dutifully testing whatever intermediate build of anything someone from Oracle would want to throw at me... Yes, I still like what I'm seeing here in VirtualBox and hope for a rather quick solution (< 4 weeks), but I'll have to switch back to another desktop VM solution in between. I do not depend daily on USB devices, but I cannot do without them for extended periods of time.

[abcuser]

Hopefully the Extension Pack (which brings closed-source USB support) is still available for free...

Extension Pack has the same license as in v.3x has whole product. You must install extension pack to USB work successfully. Download it: http://www.virtualbox.org/wiki/Downloads
See link: "VirtualBox 4.0.4 Oracle VM VirtualBox Extension Pack All platforms"

[omascia]

Hopefully the Extension Pack (which brings closed-source USB support) is still available for free...

Extension Pack has the same license as in v.3x has whole product. You must install extension pack to USB work successfully. Download it: http://www.virtualbox.org/wiki/Downloads
See link: "VirtualBox 4.0.4 Oracle VM VirtualBox Extension Pack All platforms"

You misunderstood my post or read it partially and out of context.
I know the license terms, and the extension pack IS installed, but it works as well or bad as described. My point was that if it had been available commercially through a paid license, it would be shaped for a refund (which of course it isn't).

It's fun and lovely to know that with some obscure (or limited diffusion) hosts and guests or decade old guests like Windows XP it works (according to some users here on the forums), but it was a huge disappointment to discover that for mainstream up to date OSes the picture looks very different.

[ingo2]

Fist of all THANKS für great 4.x version in general (mainly GPLv2-part and automatc mounting shared folders).

4.0.4 works fine here with all VM's moved from 3.2.12 without any problems (did create new VM's and attached the existing *.vdi after moving to the "new" location. Host ios Squeeze-amd64.

Also OS/2-Warp4.5 beheaves fine - with anciend GuestAdditions v1.6.51 from 2008! (mouse, clipboard, all ok)

At this occasion one question: is there any major change to OS/2-GuestAdditions since that time which is really worth to update them?
Otherwise I would follow the habit of "never touch a running system".

Best regards,
Ingo

[Bullitt]

Has performance been increased in the new release?

I am having som big issues with SQL Server 2008 R2 - a test scripts takes much longer in the VM compared to the physical machine

[sej7278]

Has performance been increased in the new release?

I am having som big issues with SQL Server 2008 R2 - a test scripts takes much longer in the VM compared to the physical machine

i'd file a bug report with microsoft, sql server is rubbish even in virtual pc/server (or hardware )

[mpack]

or decade old guests like Windows XP it works (according to some users here on the forums), but it was a huge disappointment to discover that for mainstream up to date OSes the picture looks very different.

If your criteria for operating system selection is fashionability rather than functionality then I'm not surprised that you suffer performance problems (so to speak).

[Bullitt]

Has performance been increased in the new release?

I am having som big issues with SQL Server 2008 R2 - a test scripts takes much longer in the VM compared to the physical machine

i'd file a bug report with microsoft, sql server is rubbish even in virtual pc/server (or hardware )

I am new to VMs, so I assume that I need to optimiza VB for better SQL I/O performance.

I asked a question here:
http://forum.virtualbox.org/viewtopic.p ... 319b7e80d1