My grub configuration does not contain -esc.
How can I run my installed l4 over qemu?
Do you mean RS232 cable serial null modem cable? I am working L4 on laptop therefore I don't have a direct RS232 access. I can not maintain that logs now. Are there any other ways that can I collect that this log info?
Best regards
-- burak() (ps: bf) METU CENG '06
----- Original Message ---- From: Christian Helmuth ch12@os.inf.tu-dresden.de To: l4-hackers@os.inf.tu-dresden.de Sent: Thursday, March 29, 2007 2:04:23 PM Subject: Re: hda : lost interrupt
Hi,
On Thu, Mar 29, 2007 at 01:01:08AM -0700, Burak OGUZ wrote:
Also a warning complains about I should not use -esc in L4Input.
As libinput has no chance to check Fiasco's command line, it always logs this message. Just make sure your Fiasco grub module line does not contain "-esc".
Anyway, did you attach a serial null modem cable to your test box/virtual machine?
Greets
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Burak,
Burak OGUZ wrote on 29.03.2007 13:58 this:
My grub configuration does not contain -esc.
ok.
How can I run my installed l4 over qemu?
you could for instance create a bootable cd-rom image:
1. create a directory which will contain all the files of the iso-image. Lets call it iso 2. in the iso directory create a boot/grub directory 3. put the files you want to boot somewhere into the iso directory (preferably into boot/) 4. create the respective Grub entries in boot/grub/menu.lst (have a look at the demo-cd boot/grub/menu.lst for examples) 5. in the iso directory, call '$(L4DIR)/tool/bin/isocreator . image' 6. boot the image with 'qemu -serial stdio -cdrom image'
You might want to check which VBE modes qemu supports.
The option -serial stdio gives you the serial console in the terminal window where you started qemu.
Do you mean RS232 cable serial null modem cable? I am working L4 on laptop therefore I don't have a direct RS232 access. I can not maintain that logs now. Are there any other ways that can I collect that this log info?
As an alternative you can obtain the package dmon from our SVN repository (if you do not have it already). In the dmon directory is a README how to use it. Dmon basically opens a dope window and collects all debug logging information. This way you can see the log output even if you do not have a serial null modem cable and a second computer to debug.
On the downside you will have to copy the debug information by hand (write it down, type it into your email program...).
HTH, Ron. - -- Mit freundlichen Gruessen / with regards ra3 @ inf.tu-dresden.de http://os.inf.tu-dresden.de/~ra3/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Oh, I forgot:
Ronald Aigner wrote on 30.03.2007 10:34 this:
Hi Burak,
Burak OGUZ wrote on 29.03.2007 13:58 this:
My grub configuration does not contain -esc.
ok.
How can I run my installed l4 over qemu?
you could for instance create a bootable cd-rom image:
- create a directory which will contain all the files of the
iso-image. Lets call it iso 2. in the iso directory create a boot/grub directory
2b. put the file stage2_eltorito into that dir (I found it on my Debian distro here: /usr/lib/grub/i386-pc/; you can also get our modified grub from SVN and build the stage2 file yourself)
- put the files you want to boot somewhere into the iso directory
(preferably into boot/) 4. create the respective Grub entries in boot/grub/menu.lst (have a look at the demo-cd boot/grub/menu.lst for examples) 5. in the iso directory, call '$(L4DIR)/tool/bin/isocreator . image' 6. boot the image with 'qemu -serial stdio -cdrom image'
You might want to check which VBE modes qemu supports.
The option -serial stdio gives you the serial console in the terminal window where you started qemu.
Do you mean RS232 cable serial null modem cable? I am working L4 on laptop therefore I don't have a direct RS232 access. I can not maintain that logs now. Are there any other ways that can I collect that this log info?
As an alternative you can obtain the package dmon from our SVN repository (if you do not have it already). In the dmon directory is a README how to use it. Dmon basically opens a dope window and collects all debug logging information. This way you can see the log output even if you do not have a serial null modem cable and a second computer to debug.
On the downside you will have to copy the debug information by hand (write it down, type it into your email program...).
HTH, Ron.
Ron. - -- Mit freundlichen Gruessen / with regards ra3 @ inf.tu-dresden.de http://os.inf.tu-dresden.de/~ra3/
l4-hackers@os.inf.tu-dresden.de