Page 3 of 3
Re: Discuss VirtualBox 2.2.4 Release
Posted: 8. Jun 2009, 15:42
by wyldfury
I was previously using 2.1.4 with "Host Interface" as my networking option. As far as I can see the only way to have a similar setup (access to LAN and other VMs) on 2.2.4 is by using bridging. After some frustration trying to get bridging working on Ubuntu 9.04 I gave up and switched back to 2.1.4.
Unless the removal of "Host Interface" networking is a problem on my system, I think I'll be sticking to 2.1.4 for now.
Cheers
Guy
Re: Discuss VirtualBox 2.2.4 Release
Posted: 9. Jun 2009, 13:47
by DEbox
I'm currently running 2.1.4 PUEL on Fedora 10.
The FAQ on updating notes possible de-installation issues with version 2.1.0...
Also, there's a thing about possible network problems after updating:
* Problems with network interfaces after installing or rebuilding the VirtualBox drivers: this is likely to be caused by a problem in the dkms tool. You can work around this by changing the line
/sbin/udevadm trigger
in the dkms script (/usr/sbin/dkms on Ubuntu) to
true
* dkms status fails after VirtualBox was removed (deb/rpm): The VirtualBox 1.6.0 and 1.6.2 packages did not properly de-register from dkms during uninstallation. To work around this problem do
rm -rf /var/lib/dkms/vboxdrv
after you uninstalled a VirtualBox deb/rpm package.
* The same problem happens after uninstalling / upgrading from VirtualBox 2.1.0. The solution is
rm -rf /var/lib/dkms/vboxnetflt
Will I be affected by these issues or are they 2.1.0 exclusively?
If not, how do I have to read the "by changing the line
/sbin/udevadm trigger
in the dkms script (/usr/sbin/dkms on Ubuntu) to
true"
instruction: Change "/sbin/udevadm trigger" to "True" or to "/sbin/udevadm trigger True" ?
I'd rather have to merely open the RPM-file and enjoy....
Thanks for any advice!
Achim
Re: Discuss VirtualBox 2.2.4 Release
Posted: 11. Jun 2009, 03:25
by puke76
I can get my WinXP SP3 guest to crash on 2.2.4 - it runs flawlessly on 2.2.2. See
http://forums.virtualbox.org/viewtopic.php?f=7&t=18611.
I can reproduce this issue. How can I get some diagnostic information to identify the problem? The guest just crashes (window closes and VirtualBox displays "aborted").
Re: Discuss VirtualBox 2.2.4 Release
Posted: 11. Jun 2009, 15:59
by aeichner
Open a defect in our bug tracker
http://www.virtualbox.org/wiki/Bugtracker and attach the VBox.log there along with a description of the problem and information of your host and guest. You can find the log in your home directory under ~/.VirtualBox/Machines/<VM name>/Logs/VBox.log
Re: Discuss VirtualBox 2.2.4 Release
Posted: 12. Jun 2009, 07:05
by david__schmidt
Running on Mac OS 10.5, OS/2 installs and boots like a champ. This is my first success with OS/2... the trick for me was to boost the initial RAM allocation way above whatever the default was (96M?) to 768M.