Like some previous Parallels users, I've had some problems with running Debian GNU/Linux as a guest OS. In all recent Parallels builds, booting into Debian (kernel 2.6.15+) results in the a kernel panic from the agpgart module (as seen in this post) . Previously, Debian would boot normally following the kernel panic, but more recently, it consistently hangs while loading cupsd. After a great deal of hassle, I found that cupsd was hanging while it tried to load a parallel port module. After renaming the agpgart.ko module file to prevent it from loading, cupsd started normally. I tried to prevent agpgart from loading during the boot process by adding it to a blacklist. In Debian, one can prevent modules from loading by creating a file in /etc/hotplug/blacklist.d/ and adding the module name to this file.
Adding a line with "agpgart" to /etc/hotplug/blacklist.d/agpgart didn't prevent the kernel panic. Checking the /lib/modules/2.6.15/modules.dep, I found the intel-agp module depends on agpgart and it was the attempt to load this module that caused agpgart to load despite being blacklisted. I removed agpgart from the blacklist file and added intel-agp instead. This removed the kernel panic, agpgart loaded normally, cupsd didn't hang, and Debian booted normally.
With regard to Ubuntu, I tried loading the live CD and experienced the same hang at "loading drivers" that other users have reported. After leaving the system loading for sometime, Ubuntu reports that /sbin/modprobe quits abnormally and then continues booting and hangs on loading cupsd. I suspect this behavior is due to the same issue I experience with Debian. I am less familiar with Ubuntu, but likely downloading the alternative installation CD and using that install process should allow one to blacklist intel-agp.
I would be interested in feedback from Parallels developers as to why intel-agp might be causing issues. As reported by the thread referenced above, I did experience some relief in previous builds of Parallels by changing the amount of available RAM, but that has no longer prevented the intel-agp kernel panic recently.
I hope this helps others who have had trouble running Debian.
Jeremy
Adding a line with "agpgart" to /etc/hotplug/blacklist.d/agpgart didn't prevent the kernel panic. Checking the /lib/modules/2.6.15/modules.dep, I found the intel-agp module depends on agpgart and it was the attempt to load this module that caused agpgart to load despite being blacklisted. I removed agpgart from the blacklist file and added intel-agp instead. This removed the kernel panic, agpgart loaded normally, cupsd didn't hang, and Debian booted normally.
With regard to Ubuntu, I tried loading the live CD and experienced the same hang at "loading drivers" that other users have reported. After leaving the system loading for sometime, Ubuntu reports that /sbin/modprobe quits abnormally and then continues booting and hangs on loading cupsd. I suspect this behavior is due to the same issue I experience with Debian. I am less familiar with Ubuntu, but likely downloading the alternative installation CD and using that install process should allow one to blacklist intel-agp.
I would be interested in feedback from Parallels developers as to why intel-agp might be causing issues. As reported by the thread referenced above, I did experience some relief in previous builds of Parallels by changing the amount of available RAM, but that has no longer prevented the intel-agp kernel panic recently.
I hope this helps others who have had trouble running Debian.
Jeremy
