2012-11-19T09:57:04ZFluxBBhttps://bbs.archlinux.org/viewtopic.php?id=153197Chroot from live media seems to be your only option if the machine doesn't boot. Chroot into it and remove virtualbox and all related packages. See if it boots then.]]>https://bbs.archlinux.org/profile.php?id=210602012-11-19T09:57:04Zhttps://bbs.archlinux.org/viewtopic.php?pid=1195512#p1195512Thank all for your replies. No, I haven't tried loading vboxdrv and running virtualbox. I should do that.

How should I fix it? Should I boot it with the Arch iso and then change to root and fix it there?

]]>https://bbs.archlinux.org/profile.php?id=507022012-11-19T03:11:31Zhttps://bbs.archlinux.org/viewtopic.php?pid=1195386#p1195386Your flaw is using dkms. When you build the virtualbox-ck-modules packages, you are circumventing the need for dkms completely by providing the modules yourself.

1) Use DKMS and do not use virtualbox-ck-modules.2) Use virtualbox-ck-modules and not DKMS.

Note - the whole reason I wrote the package in the AUR (...and the virtualbox-xxx modules for the repo) is to keep users from having to use DKMS which is horribly unreliable in my experience.

]]>https://bbs.archlinux.org/profile.php?id=210602012-11-18T13:29:14Zhttps://bbs.archlinux.org/viewtopic.php?pid=1194989#p1194989To build modules you only need virtualbox-host-source. Since you have installedvirtualbox-ck-modules which contains prebuilt ck modules, you don't need to build them at all.

Either remove virtualbox-host-source and use prebuilt modules or remove virtualbox-ck-modulesand build them yourself.

Errors are probably caused by existing ck modules. Have you even tried loading modules and running VBox?