virtualbox.org

ingo2 wrote:

srv1973 wrote:Hi,

3D acceleration is broken in this version. See https://www.virtualbox.org/ticket/10071. Looks like 4.1.8 uses a library call that's only available in 64bit versions of XP (RegGetValueA).

Are you sure you did not exchange host and guest system? Your bug report says host= WinXP-ia32, guest=Win7-amd64 - really strange setup if true.

All is fine here with 3D acceleration:
Host: Squeeze-amd64, NVIDIA gForce 210, drivwer version 185.136.31, OpenGL 1.4
Guest: Wheezy-amd64, 2 CPU's, 128MB graphics RAM

Ingo

I didn't actually file that bug report, so the host/guest OS description there does not match my setup. My setup is:

Host: XP SP3 32bit
Guest: Linux 3.x kernel (I've got 3, Mint, Ubuntu and Xubuntu).

I downgraded to 4.1.6 and everything works again. Maybe I should try to upgrade again and see what happens.

Maarten

It's consistent. I upgraded again to 4.18 and it doesn't work (as per the VBoxTestOGL run). Downgrading to 4.16 makes it work again.

Take note that this only seems to be a problem on 32 bit installations of Windows hosts!

srv1973 wrote:It's consistent. I upgraded again to 4.18 and it doesn't work (as per the VBoxTestOGL run). Downgrading to 4.16 makes it work again.

Take note that this only seems to be a problem on 32 bit installations of Windows hosts!

I'm on Lucid 64 bit and NVidia gt250 and the problem is there on all VM. Downgrade to 4.1.6 and the checkbox are still disabled

oc010000 wrote:Yes, though I can cut-n-paste, or even worse, manually edit in vi the source but a RealPatchfile(TM) would be nice for versions 4.1.6 and 4.1.8 so I can just do patch < file.diff .

.

the requested patch you can find at http://wiki.centos.org/HowTos/Virtualiz ... entOSguest

4.1.x just adds more and more serious issues

the VM video freeze when exiting scale mode
the VM hang/bsod/autoclose of the VM when clicking scan for hardware changes in device manager(XP) (ICH9 and PII3x) which is most likely a bug in the ICH8 sata emulation

Installed Windows 8 Consumer Preview fresh install on my laptop and installing VirtualBox 4.1.8 kills my internet connection!

Wireless card: Realtek RTL8188CE Wireless LAN 802.11n COMBO PCI-E NIC

Luckily I can revert to using Hyper V included with Windows 8!

kevinjp wrote:Installed Windows 8 Consumer Preview fresh install on my laptop and installing VirtualBox 4.1.8 kills my internet connection!

Well tough! Use a supported host OS, then maybe we can talk.

Well I uninstalled my previous, working version (sorry can't remember version but it was fairly recent) and installed 4.1.8 on my Ubuntu 10.10 AMD64 laptop.

If I run it, the main UI flashes up (with my one VM shown) and then immediatey disappears.

VBoxSVC.Log says:
dmesg shows one additional log made while doing this:
Uninstalling and re-installing didn't help. I can't see any obvious errors in the install log file in /var/logs.

Any ideas?

00:00:06.941 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={c28be65f-1a8f-43b4-81f1-eb60cb516e66} aComponent={VirtualBox} aText={The object is not ready}, preserve=false

seems to be a problem with access rights

The latter two messages seem to be somewhat generic - not demonstrably specific to 4.1.8. I would have thought the question was better asked in "Linux Guests", since it seems to be a Linux folder permissions issue.

Hans Eberhardt wrote:

00:00:06.941 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={c28be65f-1a8f-43b4-81f1-eb60cb516e66} aComponent={VirtualBox} aText={The object is not ready}, preserve=false

seems to be a problem with access rights

To what though?

mpack wrote:The latter two messages seem to be somewhat generic - not demonstrably specific to 4.1.8. I would have thought the question was better asked in "Linux Guests", since it seems to be a Linux folder permissions issue.

Well I've never had a problem with previous releases, and it doesn't seem to have anything to do with guests. I only added a test guest (via vboxmanage) to see if it made any difference. I can delete the guest from the virtualbox.xml file and it doesn't make any difference.

You say in your own earlier message that you don't know what version you upgraded from, which means you also can't say with any confidence that this is a new problem in v4.1.8 (or indeed that it's a problem in VirtualBox at all). This thread is for discussing new issues in v4.1.8 - and frankly it's even a little late for that, given that a new release is likely soon. As I said before, "Linux Guests" seems to me like the right place to discuss your problem with a Linux Guest.

mpack wrote:You say in your own earlier message that you don't know what version you upgraded from, which means you also can't say with any confidence that this is a new problem in v4.1.8 (or indeed that it's a problem in VirtualBox at all). This thread is for discussing new issues in v4.1.8 - and frankly it's even a little late for that, given that a new release is likely soon. As I said before, "Linux Guests" seems to me like the right place to discuss your problem with a Linux Guest.

With all due respect, please read what I actually write. This is nothing to do with guests. My linux *host* won't run vbox any more (never mind run a guest), and all I did was upgrade to 4.1.8. Prior to that, it did. The previous version wasn't old. I also just upgraded to 4.1.10 and the problem remains. While I can't (as no-one can) guarantee that it isn't a system problem, I don't have problems running anything else, and didn't have a problem running Virtualbox before.

NeBlackCat wrote:This is nothing to do with guests. My linux *host* won't run vbox any more

Ah yes: my mistake, sorry. In my defence your first message refers to running "it", however a more careful reading would indeed have deciphered what "it" you referred to.

Still, just replace the phase "Linux Guests" with "Linux Hosts" and the thrust of my comments still apply - more so now that 4.1.10 has now been released.