From: Daire Byrne <Daire.Byrne@framestore.com>
To: kvm@vger.kernel.org
Subject: Direct kernel boot without harddrive image
Date: Fri, 7 Nov 2008 10:47:28 +0000 (GMT) [thread overview]
Message-ID: <1000286911.1948481226054848250.JavaMail.root@dahlback.prod.local> (raw)
In-Reply-To: <98571048.1948081226054745257.JavaMail.root@dahlback.prod.local>
Hi,
Admittedly this looks more like a Qemu issue but it effects KVM too which is all I'm interested in. I have a kernel and initrd which contains a mini busybox root environment which I want to boot directly using -kernel and -initrd. Now this works fine on first start but if I reboot within the system QEMU crashes out on the next run. I used "-hda /dev/zero" instead of a HD image. When qemu crashes after the reboot it dumps something like this:
[root@sys422 ~]# /usr/bin/qemu-kvm -m 1024 -smp 1 -name fedora3 -kernel vmlinuz-current -initrd initrd-diskless.img -append 'init=/init ramdisk_size=65536 root=/dev/ram0 rw' -hda /dev/zero
qemu: loading initrd (0x282bde bytes) at 0x000000001fd7d000
exception 13 (33)
rax 000000000000b141 rbx 0000000000000100 rcx 0000000000000000 rdx 0000000000000100
rsi 0000000000000000 rdi 0000000000000000 rsp 000000000000fff2 rbp 0000000000000000
r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000
rip 000000000000002c rflags 00033017
cs 1020 (00010200/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
ds 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
es 1000 (00010000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
ss 1000 (00010000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
fs 1000 (00010000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
gs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
tr 0080 (fffbd000/00002088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
ldt 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0)
gdt fb812/30
idt 0/3ff
cr0 10 cr2 0 cr3 0 cr4 0 cr8 0 efer 0
code: 00 d0 d7 1f de 2b 28 00 00 00 00 00 00 fe 00 00 00 00 02 00 --> ff ff ff 1f e8 cd 0c eb 0b 90 90 90 90 90 90 90 90 90 90 90 00 00 00 00 00 00 00 00 00 00
Is direct kernel booting just not really supported properly or is it just to do with Qemu forgetting about the direct boot kernel/initrd after a reboot?
Daire
next parent reply other threads:[~2008-11-07 10:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <98571048.1948081226054745257.JavaMail.root@dahlback.prod.local>
2008-11-07 10:47 ` Daire Byrne [this message]
2008-11-16 16:08 ` Direct kernel boot without harddrive image Avi Kivity
[not found] <1932790716.3894611227183794211.JavaMail.root@dahlback.prod.local>
2008-11-20 12:27 ` Daire Byrne
2008-11-24 17:39 ` Daire Byrne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1000286911.1948481226054848250.JavaMail.root@dahlback.prod.local \
--to=daire.byrne@framestore.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox