smxi svmi sgfxi :: feature requests

[Crust]

There is a new VirtualBox release. Could you update the download link? Thanks.

Debian 5.0 ("Lenny") i386
[link]
Debian 5.0 ("Lenny") AMD64
[link]

Debian 4.0 ("Etch") i386
[link]
Debian 4.0 ("Etch") AMD64
[link]

VirtualBox 2.2.4 (released 2009-05-29)

This is a maintenance release. The following items were fixed and/or added:

* Windows Installer: fixed a potential hang during installation
* Windows Installer: fixed several problems (bug #3892)
* Solaris hosts: make it work with Solaris build 114 or later (bug #3981)
* Solaris hosts: fixed a bug serial port character handling found during loopback (bug #3120)
* Linux hosts: adapted vboxdrv.sh to the latest changes in VBoxManage list runningvms (bug #4034)
* Windows hosts: fixed a crash caused by host-only/bridged networking
* Mac OS X hosts: fixed access to host DVD with passthrough disabled (bug #4077)
* Guest Additions: fixed problems with KDE 4 not recognizing mouse clicks
* Windows Additions: fixed incorrect 8-bit guest color depth in Windows 7 guests
* GUI: warn if VT-x/AMD-V could not be enabled for guests that require this setting (bug #4055)
* VMM: fixed occassional crash due to insuffient memory
* VMM: fixed hanging 64 bits Solaris guests
* VMM: restore from a saved state occassionally failed (bugs #3984 and #2742)
* Clipboard: fixed a deadlock while shutting down the shared clipboard on X11 hosts (bug #4020)
* OVF: fixed potential hang during import
* OVF: fixed potential crashes during import/export on Win64 hosts
* VBoxManage modifyhd --compact: fixed bug which could lead to crashes and image corruption (bug #3864)
* VBoxManage metrics collect: now flushes the output stream.
* VHD: made VBoxManage internalcommands sethduuid work for .vhd files (bug #3443)
* VHD: some .vhd files could not be cloned (bug #4080)
* VMDK: fixed creating snapshots
* NAT: improvement of TCP connection establisment (bug #2987)
* NAT: fixed order of DNS servers in DHCP lease (bug #4091)
* NAT: fixed DHCP lease for multiple name servers (bug #3692)
* NAT: fixed a potential segfault if the host lost its connectivity (bug #3964)
* Shared Folders: deny access to parent directories on Windows hosts (bug #4090)
* Shared Folders: make rm/rmdir work with Solaris guests on Windows hosts
* Networking: fixed the problem with blocked receiving thread when a broadcast packet arrives too early to be handled by uninitialized e1000 adapter.
* Networking: fixed the problem that caused host freezes/crashes when using bridged mode with host’s interface having RX checksum offloading on (bug #3926 and related). Fixes problems with TX offloading as well (bug #3870)
* PXE boot: Added support for PRO/1000 MT Server adapter.
* Python bindings: fixed keyword conflict
* SCSI: fixed occasional crashes on Win64
* Serial: allow to redirect the serial port to a raw file (bug #1023)
* VRDP: fixed a rare incorrect screen update

[Crust]

After installing a kernel, you are required to recompile the kernel module for the non-free version of virtualbox.

Could you make this a choice available in the virtual machine menu?

The command is:

:: Code ::

/etc/init.d/vboxdrv setup

It would be even better if the script detected if virtualbox non-free is installed and performed this automatically after a kernel upgrade, but I know I'm probably asking for too much.

As always, all your work is greatly appreciated.

[anticapitalista]

dpkg-reconfigure virtualbox

does the same.

Which is the 'best' way to do this?

[Crust]

anticapitalista,

The command above is the recommended way.

dpkg-reconfigure virtualbox does not do the same thing (it does more, it reconfigures the virtualbox package).

The command "/etc/init.d/vboxdrv setup" does not require any user input.

[techAdmin]

crust give it a try now, should be updated and with new module builder command. I don't use non ose so if you can test this it would be good.

[Crust]

It works great, thanks.

[Crust]

h2,

This is Crust.

The Amarok package group test should no longer include amarok-engine-xine. amarok-engine-xine is only needed for Amarok 1.4 The new version in sid does not need it. Dist-upgrade works fine with Amarok, but smxi is still holding Amarok because of the check for amarok-engine-xine.

Thanks.

[Crust]

h2,

I see that there is now a new conflict between amarok (2.1.1-3) and amarok-common (2.1.1-4), but smxi should still not use amarok-engines (1.4.10-3), amarok-engine-xine (1.4.10-3+b1), amarok-engine-yauap (1.4.10-3+b1) as part of the version conflict detection logic as they are no longer needed in the new amarok version. They should be purged if you are using amarok in sid.

[techAdmin]

ok, those are removed from the list now, thanks.

[Crust]

Thanks.

BTW, can you remind me why joystick is on hold?