Hi, all. I want to study kernel, so I tried booting my custom compiled kernel on qemu with '-kernel' and '-initrd' option. First, I installed ubuntu 10.10 with cdrom, no LVM. $ qemu disk.img -cdrom ubuntu-10.10-server-i386.iso -vnc :1 After installation, I tried booting my custom compiled kernel(but not modified, just compiled). $ sudo qemu -m 512 -enable-kvm disk.img -nographic -append "console=ttyS0 root=/dev/sda1 ro" -kernel bzImage -initrd initrd.img-2.6.37 And I got result like this. [ 2.687558] EXT4-fs (sda1): INFO: recovery required on readonly filesystem [ 2.688085] EXT4-fs (sda1): write access will be enabled during recovery [ 2.691679] EXT4-fs (sda1): recovery complete [ 2.944387] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. [ 2.988413] e1000 0000:00:03.0: eth0: (PCI:33MHz:32-bit) 52:54:00:12:34:56 [ 2.988871] e1000 0000:00:03.0: eth0: Intel(R) PRO/1000 Network Connection After that, the machine just stopped and I don't know the cause. What is the cause, or how to find the cause? The whole log is in this url. https://gist.github.com/916961 Thank you for reading.
Hi... :) On Wed, Apr 13, 2011 at 11:27, Minwoo Lee <ermaker@gmail.com> wrote:
Hi, all.
I want to study kernel, so I tried booting my custom compiled kernel on qemu with '-kernel' and '-initrd' option.
First, I installed ubuntu 10.10 with cdrom, no LVM. $ qemu disk.img -cdrom ubuntu-10.10-server-i386.iso -vnc :1
After installation, I tried booting my custom compiled kernel(but not modified, just compiled). $ sudo qemu -m 512 -enable-kvm disk.img -nographic -append "console=ttyS0 root=/dev/sda1 ro" -kernel bzImage -initrd initrd.img-2.6.37
Just to make sure few things: 1. are you really going to setup serial console only guest? because I saw that nographic and console=ttyS0 2. and the initrd, is that the correct initrd that is built against your kernel?
And I got result like this.
[ 2.687558] EXT4-fs (sda1): INFO: recovery required on readonly filesystem [ 2.688085] EXT4-fs (sda1): write access will be enabled during recovery [ 2.691679] EXT4-fs (sda1): recovery complete [ 2.944387] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. [ 2.988413] e1000 0000:00:03.0: eth0: (PCI:33MHz:32-bit) 52:54:00:12:34:56 [ 2.988871] e1000 0000:00:03.0: eth0: Intel(R) PRO/1000 Network Connection
just a guess: maybe it didn't freeze...it just display things but toward serial console.... for a test, I suggest (untested) to dump out -nographic and instead use buit in qemu serial console. Switch to it by pressing Ctrl-Alt-3 and see if there are message showing there... -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
Hi, So the chain to boot would be something like : $ sudo qemu -m 512 -enable-kvm disk.img -append "console=ttyS0 root=/dev/sda1 ro" -kernel bzImage -initrd initrd.img-2.6.37 On 14/04/2011 03:51, Mulyadi Santosa wrote: > Hi... :) > > On Wed, Apr 13, 2011 at 11:27, Minwoo Lee<ermaker@gmail.com> wrote: >> Hi, all. >> >> I want to study kernel, so I tried booting my custom compiled kernel >> on qemu with '-kernel' and '-initrd' option. >> >> First, I installed ubuntu 10.10 with cdrom, no LVM. >> $ qemu disk.img -cdrom ubuntu-10.10-server-i386.iso -vnc :1 >> >> After installation, I tried booting my custom compiled kernel(but not >> modified, just compiled). >> $ sudo qemu -m 512 -enable-kvm disk.img -nographic -append >> "console=ttyS0 root=/dev/sda1 ro" -kernel bzImage -initrd >> initrd.img-2.6.37 > Just to make sure few things: > 1. are you really going to setup serial console only guest? because I > saw that nographic and console=ttyS0 > > 2. and the initrd, is that the correct initrd that is built against your kernel? > >> And I got result like this. >> >> [ 2.687558] EXT4-fs (sda1): INFO: recovery required on readonly filesystem >> [ 2.688085] EXT4-fs (sda1): write access will be enabled during recovery >> [ 2.691679] EXT4-fs (sda1): recovery complete >> [ 2.944387] EXT4-fs (sda1): mounted filesystem with ordered data >> mode. Opts: (null) >> Begin: Running /scripts/local-bottom ... done. >> done. >> Begin: Running /scripts/init-bottom ... done. >> [ 2.988413] e1000 0000:00:03.0: eth0: (PCI:33MHz:32-bit) 52:54:00:12:34:56 >> [ 2.988871] e1000 0000:00:03.0: eth0: Intel(R) PRO/1000 Network Connection > just a guess: maybe it didn't freeze...it just display things but > toward serial console.... for a test, I suggest (untested) to dump out > -nographic and instead use buit in qemu serial console. Switch to it > by pressing Ctrl-Alt-3 and see if there are message showing there... >
Hi... On Thu, Apr 14, 2011 at 09:49, Luis Cebamanos <luiceur@gmail.com> wrote:
Hi,
So the chain to boot would be something like :
$ sudo qemu -m 512 -enable-kvm disk.img -append "console=ttyS0 root=/dev/sda1 ro" -kernel bzImage -initrd initrd.img-2.6.37
I think so...let's see if that works for the original poster's problem... -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
Hi, Mulyadi and Luis. Your suggestion is correct. Thank you. It just display things but not toward serial. Could I ask you about one more question? I want to use serial for login and doing some command in shell. I found that it is about /etc/init and getty, but I just found the solution with /etc/inittab (I knew it is for old version). 2011/4/14 Mulyadi Santosa <mulyadi.santosa@gmail.com>
Hi...
On Thu, Apr 14, 2011 at 09:49, Luis Cebamanos <luiceur@gmail.com> wrote:
Hi,
So the chain to boot would be something like :
$ sudo qemu -m 512 -enable-kvm disk.img -append "console=ttyS0 root=/dev/sda1 ro" -kernel bzImage -initrd initrd.img-2.6.37
I think so...let's see if that works for the original poster's problem...
-- regards,
Mulyadi Santosa Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Oh, I found it. Thank you for replying my stupid questions. This is the information about my question. https://help.ubuntu.com/community/SerialConsoleHowto <https://help.ubuntu.com/community/SerialConsoleHowto> 2011/4/15 Minwoo Lee <ermaker@gmail.com>
Hi, Mulyadi and Luis. Your suggestion is correct. Thank you. It just display things but not toward serial.
Could I ask you about one more question? I want to use serial for login and doing some command in shell. I found that it is about /etc/init and getty, but I just found the solution with /etc/inittab (I knew it is for old version).
2011/4/14 Mulyadi Santosa <mulyadi.santosa@gmail.com>
Hi...
On Thu, Apr 14, 2011 at 09:49, Luis Cebamanos <luiceur@gmail.com> wrote:
Hi,
So the chain to boot would be something like :
$ sudo qemu -m 512 -enable-kvm disk.img -append "console=ttyS0 root=/dev/sda1 ro" -kernel bzImage -initrd initrd.img-2.6.37
I think so...let's see if that works for the original poster's problem...
-- regards,
Mulyadi Santosa Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
On Thu, Apr 14, 2011 at 16:29, Minwoo Lee <ermaker@gmail.com> wrote:
Oh, I found it. Thank you for replying my stupid questions. This is the information about my question. https://help.ubuntu.com/community/SerialConsoleHowto
Minwoo, I think qemu-devel is more appropriate forum to discuss this qemu specific questions. We welcome you there :) -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
participants (3)
-
Luis Cebamanos -
Minwoo Lee -
Mulyadi Santosa