xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "michele.paolino" <michele.paolino@studio.unibo.it>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	Xen-devel@lists.xensource.com
Subject: Re: simple scheduler
Date: Sat, 20 Feb 2010 10:06:20 +0100	[thread overview]
Message-ID: <14f366f91002200106j1d10f944i9be6b701654e031b@mail.gmail.com> (raw)
In-Reply-To: <20100219141744.GA14359@phenom.dumpdata.com>


[-- Attachment #1.1: Type: text/plain, Size: 1132 bytes --]

ops...Thanks! ;)


On Fri, Feb 19, 2010 at 3:17 PM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:

> On Thu, Feb 18, 2010 at 06:34:41PM +0100, michele.paolino wrote:
> > Here's my grub.conf. With George's suggestion my dom0 start normally. I
> think
> > that my serial console configuration is correct, but is important for
> > me know that my
> > serial console is well configured for my future debugging.
> >
> > ## enable console output to serial port
> > serial --unit=0 --speed=11520 --word=8 --parity=no --stop=1
>
> That is wrong. 11520 ?
> > terminal --timeout=15 serial console
> >
> > ## Xen Linux kernel options to use with the default Xen boot option
> > xenkopt=console=ttyS0
>
> Where is that used. Doesn't look right.
> >
> >
> > title        Xen 3.4 serial simple
> > root        (hd0,0)
> > kernel        /boot/xen-3.4.2.gz dom0_mem=262144 sched=simple loglvl=all
> > guest_loglvl=all com1=115200,8n1 console=com1
> > module        /boot/vmlinuz-2.6.18.8-xen root=/dev/hda1 ro console=hvc0
> > earlyprintk=xen nomodeser
>
> What does 'nomodser' do?
> > module        /boot/xen-3.4.2-initrd.img
> > quiet
>

[-- Attachment #1.2: Type: text/html, Size: 1648 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

      parent reply	other threads:[~2010-02-20  9:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15 13:19 simple scheduler michele.paolino
2010-02-15 13:59 ` George Dunlap
2010-02-15 18:54   ` Pasi Kärkkäinen
2010-02-16 18:18     ` michele.paolino
2010-02-16 18:29       ` Pasi Kärkkäinen
2010-02-17 11:43         ` George Dunlap
2010-02-18 16:51           ` michele.paolino
2010-02-18 16:55             ` George Dunlap
2010-02-18 17:34         ` michele.paolino
2010-02-19 14:17           ` Konrad Rzeszutek Wilk
2010-02-19 14:40             ` Pasi Kärkkäinen
2010-02-20  9:06             ` michele.paolino [this message]

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=14f366f91002200106j1d10f944i9be6b701654e031b@mail.gmail.com \
    --to=michele.paolino@studio.unibo.it \
    --cc=Xen-devel@lists.xensource.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=konrad.wilk@oracle.com \
    /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;
as well as URLs for NNTP newsgroup(s).