** Description changed: To reproduce this issue, just use F4 option in the first screen of the - installer and select "Minimal virtual system". Once booted, run "uname - -a". You'll see the system is using the -generic-pae kernel image - instead of the expected -virtual. + installer and select "install minimal virtual machine". Once booted, run + "uname -a". You'll see the system is using the -generic-pae kernel image + instead of the expected -virtual. The -virtual kernel-image is supposed + to be an optimized kernel for the most common hypervisors. I can also + see that the -virtual image is installed but not used. Idon't get a grub + menu either, there is no menu.lst in /boot/grub. - Also, I get two error messages from plymout on boot this clean system in - both vmware xsphere 4.1 and Player. They read: - + Also, I get two error messages from plymout on boot this clean system in both vmware vSphere 4.1 and Player. + They read: init: plymouth-splash main process (567) terminated with status 1 init: plymouth-log main process (587) terminated with status 1 This is a clean install. To reproduce, just install as per the instructions given above. - - I think the F4 option to install a JEOS system is deprecated, so it - should be removed from the installer altogether.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689709 Title: When using F4 option to install a minimal virtual system, the kernel image used is -generic-pae instead of -virtual as documented. (10.04 LTS server i386) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
