Page 1 of 1

Guest additions hang on start - Fedora 13

Posted: 5. Aug 2010, 15:35
by jdmcalee
Update: I found that if I removed the shared folder I previously had, the additions install and start just fine. In fact, I added the shared folder back, and they still start successfully. I am not going to try a reinstall because I have work to do, but maybe this can help somebody else down the road.

With the latest several kernels, the guest additions just hang as they try to start (on boot, or reinstall). With the latest kernel update, my last working kernel was removed, so I'm now left with a crippled guest. The only info I've found related to the hang is the trace sent to syslog. Any ideas?

Aug 4 10:44:27 rubicon kernel: INFO: task modprobe:4607 blocked for more than 120 seconds.
Aug 4 10:44:27 rubicon kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 4 10:44:27 rubicon kernel: modprobe D 0000008d 0 4607 1728 0x00000080
Aug 4 10:44:27 rubicon kernel: e443dd50 00000086 43eb2cbe 0000008d c0429242 c0a266e4 c0a2b200 c0a2b200
Aug 4 10:44:27 rubicon kernel: c0a2b200 f467689c 001a3434 0004b211 00000000 00000000 00000000 0000008d
Aug 4 10:44:27 rubicon kernel: f4676600 fa053c1e f46efe80 c09581d8 fa053c1e 7fffffff 7fffffff f4676600
Aug 4 10:44:27 rubicon kernel: Call Trace:
Aug 4 10:44:27 rubicon kernel: [<c0429242>] ? update_curr+0x132/0x1fa
Aug 4 10:44:27 rubicon kernel: [<fa053c1e>] ? rtR0MemAlloc+0x2c/0x4a [vboxguest]
Aug 4 10:44:27 rubicon kernel: [<fa053c1e>] ? rtR0MemAlloc+0x2c/0x4a [vboxguest]
Aug 4 10:44:27 rubicon kernel: [<c076fc4d>] schedule_timeout+0x22/0xad
Aug 4 10:44:27 rubicon kernel: [<c044bfea>] ? prepare_to_wait+0x4e/0x55
Aug 4 10:44:27 rubicon kernel: [<fa0552ac>] rtSemEventMultiWait+0x92/0xc2 [vboxguest]
Aug 4 10:44:27 rubicon kernel: [<c044be05>] ? autoremove_wake_function+0x0/0x2f
Aug 4 10:44:27 rubicon kernel: [<fa055355>] RTSemEventMultiWait+0x36/0x40 [vboxguest]
Aug 4 10:44:27 rubicon kernel: [<fa04ea6e>] VBoxGuestHGCMAsyncWaitCallbackWorker+0x122/0x200 [vboxguest]
Aug 4 10:44:27 rubicon kernel: [<fa04eb5f>] VBoxGuestHGCMAsyncWaitCallback+0x13/0x15 [vboxguest]
Aug 4 10:44:27 rubicon kernel: [<fa051eac>] VbglR0HGCMInternalConnect+0x8b/0xbb [vboxguest]
Aug 4 10:44:27 rubicon kernel: [<fa0506a8>] VBoxGuestCommonIOCtl+0xabe/0x14da [vboxguest]
Aug 4 10:44:27 rubicon kernel: [<fa04eb4c>] ? VBoxGuestHGCMAsyncWaitCallback+0x0/0x15 [vboxguest]
Aug 4 10:44:27 rubicon kernel: [<fa053c1e>] ? rtR0MemAlloc+0x2c/0x4a [vboxguest]
Aug 4 10:44:27 rubicon kernel: [<fa052668>] ? RTMemAllocZ+0x11/0x28 [vboxguest]
Aug 4 10:44:27 rubicon kernel: [<fa04e328>] VBoxGuestIDCCall+0x3a/0x3f [vboxguest]
Aug 4 10:44:27 rubicon kernel: [<f7c53cd2>] vbglDriverIOCtl+0x11/0x13 [vboxsf]
Aug 4 10:44:27 rubicon kernel: [<f7c545b6>] VbglHGCMConnect+0x51/0x80 [vboxsf]
Aug 4 10:44:27 rubicon kernel: [<fa053c1e>] ? rtR0MemAlloc+0x2c/0x4a [vboxguest]
Aug 4 10:44:27 rubicon kernel: [<f7c54fb0>] vboxConnect+0x5e/0x8c [vboxsf]
Aug 4 10:44:27 rubicon kernel: [<f7c45000>] ? init+0x0/0x1e8 [vboxsf]
Aug 4 10:44:27 rubicon kernel: [<f7c450aa>] init+0xaa/0x1e8 [vboxsf]
Aug 4 10:44:27 rubicon kernel: [<c0401139>] do_one_initcall+0x4c/0x13a
Aug 4 10:44:27 rubicon kernel: [<c045f9cb>] sys_init_module+0xa7/0x1dc
Aug 4 10:44:27 rubicon kernel: [<c0771044>] syscall_call+0x7/0xb