Can't start virtualbox windows 7 32 bit image anymore please h[SOLVED]

Question

Hello guys,
Just recently, I upgraded my system by executing "sudo pacman -Syu". It upgraded my kernel and kernel header files and mesa devu etc... including virtualbox-ose 3.2.10-3.
Someoutputs that could be useful:
(Please note I picked up only installed ones from the output)
pacman -Ss virtualbox
community/virtualbox-additions 3.2.10-1 [installed]
    Guest additions for VirtualBox
community/virtualbox-ose 3.2.10-3 [installed]
    Powerful x86 virtualization for enterprise as well as home use (Open Source Edition)
pacman -Ss kernel26
core/kernel26 2.6.36.1-3 (base) [installed]
    The Linux Kernel and modules
core/kernel26-headers 2.6.36.1-3 [installed]
    Header files and scripts for building modules for kernel26
core/linux-firmware 20101108-1 [installed]
    Firmware files for Linux
extra/nvidia 260.19.21-2 [installed]
    NVIDIA drivers for kernel26.
I also recompiled the new virtualbox modules by doing:
sudo /etc/rc.d/vboxdrv setup
Password:
:: Unloading VirtualBox kernel modules                                                                                                                                    [DONE]
:: Removing old VirtualBox netadp kernel module                                                                                                                           [DONE]
:: Removing old VirtualBox netflt kernel module                                                                                                                           [DONE]
:: Removing old VirtualBox kernel module                                                                                                                                  [DONE]
:: Recompiling VirtualBox kernel modules                                                                                                                                  [DONE]
:: Reloading VirtualBox kernel modules                                                                                                                                    [DONE]
On my archlinux (64-bit) system, I installed windows 7 (32-bit) using virtualbox-ose. It was working fine before I did the upgrade. Now, whenever I try to start the windows 7 (32-bit), it starts the windows 7 until the windows logo comes (just before the login mask of windows 7 comes), my computer restarts itself without giving any error or something. My pc just restarts itself. I think this is only related to virtualbox. When I do not try to start virtualbox, arch linux itself is working fine so far. Only when I try to start the windows 7, my pc gets restarted. Have you guys had any problem of this kind? First, I will wait for your responses. The options that I could think of right at the moment are:
1. Downgrade the kernel back (I do not know how to and do not see it as a good choice)
2. Downgrade the virtualbox-ose only (I also do not know how to do that.)
3. Uninstall the virtualbox-ose and reinstall it again without removing my windows 7 OS (32-bit) (I hope I can continue using it)
4. Delete the existing windows 7 OS and try to install freshly new Windows 7 OS again
Guys, please help me. I really need to use windows 7 sometimes. I would be really grateful if some of you guys can help me.
And again thanks for reading my long post.
Thanks in advance.
Last edited by Archie_Enthusiasm (2010-12-08 19:25:30)

Answer 1

Hi guys, thanks for your responses.
What is this vboxnetflt for? Which modules are the essential modules for virtualbox? What I mean is: do those nice features like mouse point integration, full screen supportment etc... rely on vboxnetflt and vboxnetadp?
What I have in my configuration file is:
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(vboxdrv vboxnetflt vboxnetadp)
I think vboxnetadp is used for networkiing. and vboxnetflt sounds like network filtering stuff. Can someone please confirm me? I think the problem was the sequence of upgrading. Firstly it updated the kernel and then installed the new version of virtualbox. I think if it could install the new version of virtualbox first and then the kernel, it would go without any problem, just my opinion as I said.
Let's keep tracked on this. Maybe someone will find a solution before virtualbox developers :-)