All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maloney <peter.maloney@brockmann-consult.de>
To: Mina Jafari <ai.minajafari@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Fwd: Dom0 can't boot properly
Date: Tue, 09 Apr 2013 13:11:52 +0200	[thread overview]
Message-ID: <5163F778.9050108@brockmann-consult.de> (raw)
In-Reply-To: <CAK-vE-XaiYG25xjRA3HzhYPmZL9VT+MG=TkU7SQ_OVonxVGZyQ@mail.gmail.com>


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

On 2013-04-09 12:54, Mina Jafari wrote:
> Hi all,
> I have compiled xen 4.1.2 on Fedora 13 and  kernel 3.2.7 as dom0,but
> whenever I try to start it,it got stuck because can't start xenstored.
> if I boot my regular Fedora13 without xen it comes up and if I
> "disable" xenstored and xencommons and xendomains and xend, dom0 will
> boot but I should first "modprobe xen-evtchn
> "  and then start those services mannually, even though xenstored cant
> be started even this way!
>
> these are the errors when at boot time:
>
> *Starting xenstored......FATAL:Failed to open evtchn device:No such
> file or directory*
> *xencommons should be started first*
>
I suspect your kernel is not compiled with the xen dom0 options.

Probably you will find some answers here:
http://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs

If not, here are some random ideas about how I would attempt to verify this:


post output of:

if booted in your xen:
grep -i xen /boot/config-$(uname -r)

if not, figure out which file it is and post that
ls /boot/config-*xen*
grep -i xen /boot/config-${whateveryoupickedfromabove}

Also you might find a /proc/config.gz if it's not in /boot.

If the output of the grep is very short, lthen it is probably not a xen
dom0 kernel. (see the url I pasted above, the "Configuring the Kernel
for domU Support" and "Configuring the Kernel for dom0 Support" sections)



boot up with the services disabled, then post the output from:
 ls -a /proc/xen

If the output is:
ls: cannot access /proc/xen: No such file or directory
Then it is likely you are not running a xen kernel. But sometimes it
bugged out for me in the past (4.1.2 I think...) and this directory
wouldn't be there until another reboot. With 4.1.4, this doesn't happen
any more.



Also try starting xencommons manually and post output.

And last, post output from:
xl dmesg
or
xm dmesg

(xm dmesg won't work since xencommons isn't running)



ps. you really should be using 4.1.4 rather than 4.1.2 unless it won't
run (in which case you should probably report that while you downgrade).

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

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

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

  reply	other threads:[~2013-04-09 11:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAK-vE-VaEg92DB3yUUOVXNBfv5Wgx=nbwiLiYEbTCikc4QXKLg@mail.gmail.com>
2013-04-09 10:54 ` Fwd: Dom0 can't boot properly Mina Jafari
2013-04-09 11:11   ` Peter Maloney [this message]
2013-04-09 19:43   ` Konrad Rzeszutek Wilk
2013-04-10  7:29     ` Peter Maloney

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=5163F778.9050108@brockmann-consult.de \
    --to=peter.maloney@brockmann-consult.de \
    --cc=ai.minajafari@gmail.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.