On Sun, Jul 29, 2007 at 10:24:02AM +0100, Xudong Guan wrote:
> Borislav Petkov wrote:
> > On Thu, Jul 26, 2007 at 09:31:54PM -0700, H. Peter Anvin wrote:
> > > If we can't reproduce the problem in simulation, that itself will tell
> > > us something very important. If we *can* reproduce it in simulation, it
> > > will be vastly easier to debug.
> >
> > [EMAIL PROTECTED]:10:34:25:qemu:9553)-> qemu -kernel
> > /boot/2.6.22-4fd06960f120e02e9abc802a09f9511c400042a5-12 -append
> > "root=/dev/hda" linux-0.2.img
>
> You are using qemu itself as the kernel loader instead of your
> possible problematic grub on your harddisk. To duplicate the problem,
> you need to manually copy your grub and the kernel to linux-0.2.img
> and boot it with "qemu linux-0.2.img", although I am not sure
> exactly how to manually do this. Another way is to know your
> installation media that contains the copy of grub you are using,
> and use it to do an installation in qemu.
Right, this was too easy to be true. I now did:
qemu -hda /dev/hda -snapshot
and booted from the hd using the installed grub and the same kernel and it
_didn't_ boot showing again "no setup signature found... "
--
Regards/Gruß,
Boris.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
