virtualbox.org

Intrepid i386 Host. XP Guest
Was hoping to fix my abysmal shared folder speed. Install log all looked well and VirtualBox won't open on my user account. When I try to start the VM with the startvm command I get a black window like it's going to boot and then it freezes. In my normal administrator account VirtualBox opens fine but I don't have any vm's installed and haven't tried to install any.

I attempted to run vboxsrv setup and I get: "Cannot unload module vboxnetflt"

I have rm -rf the vboxnetflt folder and uninstalled and reinstalled vbox and I still get the same error when I try to rebuild the vboxdrv.
Then I did a dpkg -P virtualbox-2.2

Now the virtualbox window shows up fine for normal user and If I disable USB the guest starts properly.

If I re-enable usb guest freezes immediately and I am part of the vboxusers group.

log: http://www.tinysave.net/files/download.php?file=596868

Downgraded to 2.1.4 and all is back and working. Well except for shared folders they're still extremely slow. If 2.2 doesn't improve speed I'm going back to 2.1.0

If you have a line like that:
in your /etc/fstab remove it. I had the same problem (black screen on guest) and removing this line solved the problem.

Regarding the "Share Folders" I have no problem with their speed since version 2.1.0. My host is Opensuse 11.1 x86_64

I have a similar problem with USB on 2.2. I have a Windows box with USB 1.1 working fine in 2.1.4 and before, USB 2.0 causes Windows to intermittently fail to boot. But that's a different problem... I've tried with EHCI enabled, disabled, UHCI enabled and disabled and only when USB is completely disabled does the Windows VM boot. I've been tempted to open a bug, so now that I know someone else is experiencing this problem, I may just do that.

-Paul

You might indeed file a bug report in the Bugtracker. It's really strange, as I have a working USB just like in previous versions. Even the NAT bug that's mentioned in http://www.virtualbox.org/ticket/3655 is something I don't see in my VMs. That makes me wonder, do I have some kind of special power that makes everything work? . It's really strange to see so many issues from others, that you don't see on your own system. I think the better answer is that I know what I'm doing (most of the time anyway ) and maintain my system, unlike some of the users here. Well, anyway, I always have a strange situation where everything mostly works.

Sasquatch wrote:I think the better answer is that I know what I'm doing (most of the time anyway ) and maintain my system, unlike some of the users here. Well, anyway, I always have a strange situation where everything mostly works.

I also maintain my system since I use if for work and usb is also not working for me in the new release. I must have something to do with the Linux distro you have or the type of hardware.

Very Puzzling

MCP

I disclose the hardware, as I have no issues on both my PC and laptop. PC is AMD with nVidia, laptop is Intel with ATi. Distro is Ubuntu 8.10, Xfce edition.
Now you have different levels of maintaining a system. You can keep it clean by running several anti-spy-/malware apps, a firewall and an anti-virus, but nothing else, except for the ocassional update. I tweak it a bit every once in a while. Each their own. This is what makes bugtracking so hard. A user can reproduce it every time, while you, with a test system similar to the user, cannot.

Sasquatch wrote:I disclose the hardware, as I have no issues on both my PC and laptop. PC is AMD with nVidia, laptop is Intel with ATi. Distro is Ubuntu 8.10, Xfce edition.
Now you have different levels of maintaining a system. You can keep it clean by running several anti-spy-/malware apps, a firewall and an anti-virus, but nothing else, except for the ocassional update. I tweak it a bit every once in a while. Each their own. This is what makes bugtracking so hard. A user can reproduce it every time, while you, with a test system similar to the user, cannot.

You got me there. I haven't installed any updates for fear I might hose my system. That could be the problem. Or it might be the window manager. I'm using Klikit (based on Kubuntu) and KDE 3.xxx. So you are right, hard to find what's at fault. Hopefully all will get sorted out so that I can take advantage of any improvements.

MCP

I have two machines, the USB bug affects only one.

The affected machine is running 64-bit Fedora 10 as host. Immediately after updating to VB 2.2.0, I noticed that my USB filters were gone so I had to recreate them from scratch. Then, when attempting to boot into a 64-bit Fedora Rawhide guest with USB enabled, it froze. The only thing I could do was to kill it, and ps still showed "VirtualBox <defunct>" (zombie process?) and I couldn't start VirtualBox again until I rebooted. After rebooting, if I disabled USB, then it would run fine and there appears to be no corruption of the guest. But it always freezes if USB is enabled.

The unaffected machine is running 32-bit Fedora 10 as host. On this box, updating to 2.2.0 did NOT delete my USB filters. When I run the Windows XP guest, it works fine with USB enabled.

Edit: The affected box has 7 guests, and it appears that the USB filters were only deleted on the first 4 in the list. When I tried to boot one of the last ones (Vista), it immediately locked up my entire box and I had to do a hard shutdown. After disabling USB in this guest, it comes up fine.

I discovered from another post that you can enable a usb device by right clicking on the usb icon at the bottom of the vm window. I tried enabling usb in properties but not on the filters, my vm started just fine. Then after it booted up I rightclicked on the icon and enabled one of my usb filters and it worked as it should. So all that keeps is from booting up is having the filters enabled at bootup.

Someone else suggested a line be inserted in the fstab file but so far it hasn't helped.

Any suggestions?
MCP

mcp: I can confirm that if USB is enabled with all filters disabled at guest startup, it starts up normally, and right-clicking on the USB icon then gives access to the devices. I also found that new guests created after my update to VB 2.2.0 work completely normally. It's only the guests that existed before the update that require the USB workaround. I tried deleting and then recreating all the USB filters for the old guests but that doesn't help.

Although nothing is mentioned in the Changelog, after updating to VB 2.2.2 it seems that everything works normally again.

Edit: There actually is a mention in the Changelog of http://www.virtualbox.org/ticket/3787 being fixed.