Christian PERRIER <bubu...@debian.org> (2013-07-25): > Quoting Sander Marechal (san...@prezent.nl): > > Package: debian-installer > > Severity: normal > > Tags: d-i > > > > I installed a clean Debian Wheezy 7.1. The installer correctly > > determined that it was running in a Virtualbox VM and installed the > > virtualbox guest additions. The problem is that the additions were > > not correctly installed. The kernel module wasn't built so the guest > > additions did not work. > > > > I first had to install the build-essentials myself. Also, the > > installer installed the wrong kernel headers for my kernel. The > > debian installation came out running the -486 kernel but the > > installer installed the -686-pae kernel headers. > > > > IMHO if the debian installer installs the virtualbox guest > > additions, it should also build and load the kernel module.
Strange, ISTR that did work (and that was taking a fair amount of CPU time). Attaching your installer logs would be nice (I guess we only need syslog); /var/log/installer to the rescue. > To be confirmed but I suspect this is not the installer that > triggerred the installation of virtualbox extensions. > > I see nothing in tasksel's tasks that is related to virtualbox or > virtualization. Yeah, I needed a few minutes to find out, that's actually pulled through discover/discover-data: | discover-data (2.2010.10.14) unstable; urgency=low | | * Update HW mappings for PCI devices: | 8086:3582: install i810switch. | 80ee:beef: Install virtualbox-ose-guest-x11. | […] | | -- Petter Reinholdtsen <p...@debian.org> Thu, 14 Oct 2010 23:07:42 +0200 Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
