On 08/26/13 06:46, Michael Chang wrote: > On Fri, Aug 23, 2013 at 08:33:31PM +0200, Laszlo Ersek wrote:
>> Closing note... Even with Jordan's patch in place (or with Michael's, >> makes no difference in this regard), the OS installer can *still* store >> a wrong device path in the boot option (step 5) before the warm reboot >> (step 6). So, even if >> - this issue is fixed, and >> - the reboot is warm too, and >> - the installer media has been removed (or the qemu boot order lists it >> as second), >> the user may still not see an automatic reboot into the OS just >> installed, if the device path is borked. >> >> ... This is exactly what happens with the RHEL-6 / Fedora(-19?) >> installer, on virtio (-blk or -scsi) target disk :) >> >> https://bugzilla.redhat.com/show_bug.cgi?id=998611 > > Weird, I use virtio-blk and boot from lvm volume, not seeing any > problem so far. Presumably, if you can boot off a logical volume, then you've already loaded grub. In my case grub itself isn't found. The difference is that you (most probably) use the OpenSUSE installer (I don't know its name, apologies), while I use the RHEL-6 installer (called "Anaconda"). Anaconda has a component called "booty" I believe, and that one seems to have a (virtio-dependent) bug when determining the device path leading to grub, to be stored in the boot option. IOW this problem is unique to Anaconda / RHEL-6. I guess it has been fixed for later Anaconda versions (anaconda-16.5-1+) in Anaconda commit de146901. Thanks Laszlo ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
