Fwd: Dom0 can't boot properly

Fwd: Dom0 can't boot properly

[Mina Jafari]

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

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*

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

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

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

Re: Fwd: Dom0 can't boot properly

[Peter Maloney]

[-- 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

Re: Fwd: Dom0 can't boot properly

[Konrad Rzeszutek Wilk]

On Tue, Apr 09, 2013 at 03:24:40PM +0430, 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

Why are you using such an old version of Fedora? If ou update to
F17 or F18 you have Xen out of the box.

> 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*

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

Re: Fwd: Dom0 can't boot properly

[Peter Maloney]

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

On 2013-04-10 08:45, Mina Jafari wrote:    (he seemed to send this to me and not the list)

> I couldn't find config file in /boot or the other place but it's the
> config file I used to compile kernel with,and I've tried changing xen
> related features in config and compiled kernel over and over but
> nothing happened!
>
> grep -i xen /home/MJina/linux-3.2.7/.config
> CONFIG_XEN=y
> ...
> CONFIG_XEN_DEV_EVTCHN=m
> ...
> I previously said that it won't work even when I mannually start the
> services, but if I modprobe xen-evtchn first and try to start services
> even thought it says xenstored cannot be started but xend restarts
> successfully and xen works.
> #modprobe xen-evtchn
> # /etc/init.d/xend restart
> # /etc/init.d/xencommons start
> Starting xenstored.................................
> Could not start xenstored
> # /etc/init.d/xendomains start
>> ...
>> 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

Okay so then as suspected, your kernel is not exactly according to spec
for a dom0 kernel. The page I linked says you need:
CONFIG_XEN_DEV_EVTCHN=y
but you have
CONFIG_XEN_DEV_EVTCHN=m

 Do some other comparisons and see what else is wrong. Since "modprobe"
lets you start xend, probably that is equivalent to =y, but something
else is likely wrong. And if those wrong lines are =m instead of "# ...
is not set" then you can probably modprobe them too (for testing at
least... and then recompile with =y later)

(also I think you're missing CONFIG_X86_IO_APIC=y ... make sure to do a full compare)

eg. What i would try first is copy and paste all the dom0 and domu options from the
page into a file, then sort the file with
sort xenwikidom0config > xenwikidom0configsorted
then do the same with your config, and then do a diff

or I'd write a bash script that takes the key name (before the =) from
the xen wiki page config, and greps your config for the option to see
what the setting is.


And after you resolve this, you should report to whoever created your
kernel config that it should be fixed. (or is that you?)




On 2013-04-09 21:43, Konrad Rzeszutek Wilk wrote:
> On Tue, Apr 09, 2013 at 03:24:40PM +0430, 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
> Why are you using such an old version of Fedora? If ou update to
> F17 or F18 you have Xen out of the box.
>

Yes, I agree with that also... and upgrading a Linux distro release is easy.





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

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

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