I just installed karmic out of curiosity as a virtualbox guest. I just
updated all packages and after the required reboot, karmic stops early.
Step by Step:
1. starting virtualbox 3.08 r53138 with an image of
ubuntu-9.10-rc-dvd-i386.iso attached as a dvd drive. (I want to note
that a lot of other virtual machines work without problems).
The host machine is a Pentium4, 3GHz, 3GB RAM
Nvida video card with ~300MB of memory running ubuntu 8.04 up to date
(repositories are at the end of the message)
The karmic guest has 876MB of RAM
32MB of video memory activated 3D-acceleration
and a 8GB virtual harddisk (dynamic allocation of host disk space - the
disk isn't full as the image is only 3,6GB in size)
2. I booted up the live DVD and started the installer (In the installer
I always selected the default value.
Language and Keyboard layout: german
And I chose to encrypt my home directory.
3. After the installation I rebooted the virtual machine and installed
the dkms package (which installed something like "fakeroot" and "patch"
4. then I installed all updates by executing (no extra repositories
sudo apt-get update && sudo apt-get upgrade
5. During the installation process another application opened a window
and asked me if I wanted to create a passphrase for my encrypted home
directory. Some thing to write down for recovery if I forget my
password. I followed the procedure to create the passphrase, but I
didn't write it down. The virtual machine is just for some basic testing
. This passphrase dialogue wasn't related to the update process (at
least I think so)
6. After the update I was prompted for a reboot, I agreed to the reboot
7. Now the virtual machine doesn't boot any more. It stops at an early
stage with a blinking/flashing screen. Below is what is displayed on the
screen of the virtual machine (typed from a screenshot):
swap: waiting for /dev/mapper/cryptswap1
* Starting init crypto disk...
* Starting early crypto disk...
* cryptswap1 (starting)
* cryptswap1 (started)... [OK]
* Starting remaining crypto disks...
* Starting AppArmor profiles
* Running DKMS auto installation service for kernel 2.6.31-14-generic
* Starting Kernel Oops catching service kerneloops
* Speed-dispatcher configured for user sessions #note: the star to the
left is coloured red
* Starting Common Unix Printing System: cupsd
* PulseAudio configured for per-user sessions #note: the star to the
left is coloured red
* Enabling additional executable binary formats binfmt-support
* Checking battery state ...
Here the virtual system remains stuck.
8. I tried to reboot the system several times - same result. I didn't
manage to access the grub menu either (if this still exist in grub2)
I don't know if this halt is related to the encrypted filesytem or to
the dkms package. I installed the dkms package because the virtualbox
manual advised to install this package in linux guest, too.
Actually I don't need instant help on this issue, I have plenty of other
work to do. I just wanted to share this error (?) with you. If somebody
can reproduce the error we could file a bug on launchpad. (My research
on this topic did not show me similar reports).
This are the abbreviated software repositories of the host machine. (I
don't think they matter, but anyway)
hardy main restricted multiverse
hardy-updates main restricted multiverse
main universe multiverse
hardy-backports main restricted universe multiverse
hardy-security main restricted multiverse
main universe multiverse #Added by software-properties
ubuntu-users mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users