Hi, On Fri, Mar 6, 2009 at 5:24 PM, Dustin Kirkland <dustin.kirkl...@gmail.com> wrote: > KVM is then going to try and execute arbitrary code in that disk's boot > sector, and poof, it's not going to boot ;-)
Hmm. But real hardware and some other virtualization solutions say something like "not bootloader found" or something like that. Why shouldn't kvm be able to say that? > This is an issue with Intel processors, that don't handle real mode > properly. > > The "fix" is to recreate your vm image and start your install over. Yes, I know it's not too hard to fix. I already wrote a workaround in the bugreport. Anyway, if you think it cannot be fixed, do what you think fits. Henning -- KVM crashes with "exception 13 (33)" after an interrupted installation https://bugs.launchpad.net/bugs/254174 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
