virtualbox.org

This topic is for discussion of the 4.1.2 release
You may download it from here VirtualBox version 4.1.2

Still the same problem exists as described here in 4.1.

http://forums.virtualbox.org/viewtopic. ... 15#p194383

Thought I'd give it another run around in this new version since it says it has fixes for the WDDM. Everything clean installed, installed new experimental WDDM driver successfully. Still aero unstable afterwards. Changed settings in VM like in linked previous posts, same outcome. Unstable with GTX 480.
Windows 7x64 SP1 host. Same in guest.

Back to VMware player which works just fine.

Also the same to me, no change to WDDM
http://forums.virtualbox.org/viewtopic. ... 87#p195212

I also updated the NVIDIA drivers to the latest (280.13) on the host, no change.
Whetever I try

Code: Select all

winsat dwm

or

Code: Select all

winsat d3d

or do the test at Computer -> Properties the VM crashes or the whole host graphics freezes.

If I move the mouse cursor during the test only the VM crashes, if I don't move the whole host graphics freezes, except for the mouse cursor.

I am happy to report that this version of VirtualBox runs like a champ on my HP dm1z 3000 laptop, which is based on the AMD Fusion E-350 processor. In fact, it even performs better on my Linux host than KVM did!

And the goofy mouse behavior remains, too. Have to continue the same work-around as before: enable mouse trails and set to short.

Warnig: Extension Pack linked IS NOT for version 4.1.2 but for 4.0.12!

The exact link is: http://download.virtualbox.org/virtualb ... ox-extpack

It seems that the link on the download page must have been updated then. Link is valid.

trekfan1 wrote:Warnig: Extension Pack linked IS NOT for version 4.1.2 but for 4.0.12!

The exact link is: http://download.virtualbox.org/virtualb ... ox-extpack

Which link do you mean? The download page lists two extension packs. The first link ("All platforms" is the link to the 4.1.2 extpack, the other link to the 4.0.12 extpack. The reason for having both links there is that many people still run 4.0.12. Future versions of VirtualBox will contain an extended update checker which checks for extension pack updates as well.

My Win98SE VM still frozen stiff with 4.1.2, can't even get it to boot. I don't know that it actually locks up during the boot, but it just sits there on the Win98SE logo and after a few minutes of watching paint dry I get fed up and "power off" the VM. Status line shows no sign of disk or network activity. Host task Manager shows "VirtualBox.exe" has maxed out one core. VBoxSVC.exe is on 0% of CPU.

This VM was fine until I upgraded to 4.1.0. I have a different Win98SE VM on another PC (not a clone), and it does the same thing.

Is anyone able to run a Win98 VM satisfactorally with v4.1.x ? (satisfactorally, meaning as you would expect for an OS that isn't supported with GAs).

Aero still not working for me. Here's the output of 'Winsat formal'

> Run Time 00:00:00.00
> Run Time 00:00:00.00
> CPU LZW Compression 168.45 MB/s
> CPU AES256 Encryption 105.99 MB/s
> CPU Vista Compression 365.40 MB/s
> CPU SHA1 Hash 819.72 MB/s
> Uniproc CPU LZW Compression 67.98 MB/s
> Uniproc CPU AES256 Encryption 45.04 MB/s
> Uniproc CPU Vista Compression 132.33 MB/s
> Uniproc CPU SHA1 Hash 331.29 MB/s
> Memory Performance 18217.44 MB/s
> Dshow Video Encode Time 4.24613 s
> Media Foundation Decode Time 4.83644 s
> Disk Sequential 64.0 Read 173.20 MB/s 7.2
> Disk Random 16.0 Read 24.15 MB/s 6.1
> Responsiveness: Average IO Rate 1.34 ms/IO 7.7
> Responsiveness: Grouped IOs 8.53 units 7.4
> Responsiveness: Long IOs 5.81 units 7.7
> Responsiveness: Overall 49.54 units 7.0
> Responsiveness: PenaltyFactor 0.0
Error in saving results to the datastore winsat\main.cpp(4735)
> Total Run Time 00:00:20.41

After a little uninstalling and reinstalling of Guest additions, I now have Aero "working". I say working but it's incredibly buggy.

mpack wrote:My Win98SE VM still frozen stiff with 4.1.2, can't even get it to boot. I don't know that it actually locks up during the boot, but it just sits there on the Win98SE logo and after a few minutes of watching paint dry I get fed up and "power off" the VM. Status line shows no sign of disk or network activity. Host task Manager shows "VirtualBox.exe" has maxed out one core. VBoxSVC.exe is on 0% of CPU.

This VM was fine until I upgraded to 4.1.0. I have a different Win98SE VM on another PC (not a clone), and it does the same thing.

Is anyone able to run a Win98 VM satisfactorily with v4.1.x ? (satisfactorily, meaning as you would expect for an OS that isn't supported with GAs).

It has been so long since I tested my w-98 install that it was totally upset with all of the changes, but after reinstalling it seems to work just fine (well with known reservations).
I am using 4.1.2'ish and did not test it on anything else in the 4.* family.

Installation went without any issues. I noticed that the mouse cursor issue as described here for version 4.1 is still present in this updated release.

mpack wrote: Is anyone able to run a Win98 VM satisfactorally with v4.1.x ?

Yes, my Win98 SE VM still works with 4.1.0 and 4.1.2 like described here:
http://forums.virtualbox.org/viewtopic. ... 97#p196802

It takes 3 minutes to boot, but it works.

I am running VB 4.1.2 on two Ubuntu Lucid Linux 10.04.3 hosts with iSCSI shared storage and 26GB RAM per host.

When I try to teleport a VM on one host to the other host, something that worked correctly on 4.0.12, I get a guru meditation error. The screen shot only shows a login prompt. Here is the log

http://pastebin.com/Lj0zzvV6

The forum wouldn't let me paste the log file.

I depend on teleportation for maintenance purposes. I really need to know what is going on, please..

d.p.

virtualbox.org

Discuss the 4.1.2 release

Discuss the 4.1.2 release

Re: Discuss the 4.1.2 release

Re: Discuss the 4.1.2 release

Re: Discuss the 4.1.2 release

Re: Discuss the 4.1.2 release

Re: Discuss the 4.1.2 release

Re: Discuss the 4.1.2 release

Re: Discuss the 4.1.2 release

Re: Discuss the 4.1.2 release

Re: Discuss the 4.1.2 release

Re: Discuss the 4.1.2 release

Re: Discuss the 4.1.2 release

Re: Discuss the 4.1.2 release

Re: Discuss the 4.1.2 release

Re: Discuss the 4.1.2 release