From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daire Byrne Subject: Direct kernel boot without harddrive image Date: Fri, 7 Nov 2008 10:47:28 +0000 (GMT) Message-ID: <1000286911.1948481226054848250.JavaMail.root@dahlback.prod.local> References: <98571048.1948081226054745257.JavaMail.root@dahlback.prod.local> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from mx1.framestore.com ([193.203.83.30]:36121 "EHLO mx1.framestore.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751007AbYKGKxv (ORCPT ); Fri, 7 Nov 2008 05:53:51 -0500 Received: from dahlback.prod.local (dahlback.prod.local [172.16.17.9]) by mx1.framestore.com (Postfix) with ESMTP id 67A654805B6E for ; Fri, 7 Nov 2008 10:47:28 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by dahlback.prod.local (Postfix) with ESMTP id 647EAD8004AA2 for ; Fri, 7 Nov 2008 10:47:28 +0000 (GMT) Received: from dahlback.prod.local ([127.0.0.1]) by localhost (dahlback.prod.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ue+J6Q31hPYZ for ; Fri, 7 Nov 2008 10:47:28 +0000 (GMT) Received: from dahlback.prod.local (dahlback.prod.local [172.16.17.9]) by dahlback.prod.local (Postfix) with ESMTP id 4E8C9D8004AA0 for ; Fri, 7 Nov 2008 10:47:28 +0000 (GMT) In-Reply-To: <98571048.1948081226054745257.JavaMail.root@dahlback.prod.local> Sender: kvm-owner@vger.kernel.org List-ID: 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