From: Boris Derzhavets <bderzhavets@yahoo.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com
Subject: Attempt to load the most recent 2.6.30-rc-tip under Xen-3.3.1 on F11-preview
Date: Wed, 29 Apr 2009 08:13:32 -0700 (PDT) [thread overview]
Message-ID: <178595.15145.qm@web56103.mail.re3.yahoo.com> (raw)
In-Reply-To: <49F648B5.4030003@goop.org>
[-- Attachment #1.1: Type: text/plain, Size: 393 bytes --]
Booting hangs at xend startup :-
mount : block device xen is write-protected mounting read-only
mount : cannot mount block device xen read only
grep: /proc/xen/capabilities
No such file or directory
I believe the last message is from /etc/init.d/xend attempting to start
and exiting.
if ! grep -q "control_d" /proc/xen/capabilities ; then
exit 0
fi
Boris.
[-- Attachment #1.2: Type: text/html, Size: 571 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2009-04-29 15:13 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 19:22 Xen with dom0 pvops on ultra-recent "git tip" kernel on x86_64 Christophe Saout
2009-01-10 20:11 ` Marc - A. Dahlhaus
2009-01-10 20:28 ` Christophe Saout
2009-01-10 20:37 ` Pasi Kärkkäinen
2009-01-10 20:49 ` Marc - A. Dahlhaus
2009-01-10 20:54 ` Christophe Saout
2009-01-10 21:13 ` Christophe Saout
2009-01-11 14:17 ` Christophe Saout
2009-01-11 14:52 ` Christophe Saout
2009-01-11 16:35 ` Christophe Saout
2009-01-11 16:59 ` Christophe Saout
2009-01-11 20:13 ` Christophe Saout
2009-01-12 14:17 ` Christophe Saout
2009-01-12 16:41 ` Christophe Saout
2009-01-13 9:28 ` Christophe Saout
2009-01-13 15:33 ` Pasi Kärkkäinen
2009-01-13 16:41 ` Christophe Saout
2009-01-13 16:57 ` Christophe Saout
2009-01-16 17:23 ` Jeremy Fitzhardinge
2009-01-16 17:40 ` Christophe Saout
2009-01-16 17:52 ` Jeremy Fitzhardinge
2009-01-17 16:29 ` Christophe Saout
2009-01-18 20:10 ` Christophe Saout
2009-01-18 21:28 ` Christophe Saout
2009-01-18 22:39 ` Xen with dom0 pvops on ultra-recent "git tip"kernel " Keir Fraser
2009-01-19 9:52 ` Christophe Saout
2009-01-19 12:33 ` Christophe Saout
2009-02-22 23:28 ` Jeremy Fitzhardinge
2009-02-24 9:32 ` Christophe Saout
2009-02-24 10:41 ` Christophe Saout
2009-02-24 16:20 ` Boris Derzhavets
2009-02-24 21:22 ` Jeremy Fitzhardinge
2009-02-24 21:51 ` Andrew Lyon
2009-02-25 7:16 ` Boris Derzhavets
2009-04-23 21:49 ` Nvidia drivers on " Nigel Gamble
2009-04-24 7:43 ` Andrew Lyon
[not found] ` <1240816930.4387.18.camel@petrie>
2009-04-28 0:07 ` Jeremy Fitzhardinge
2009-04-28 5:33 ` William Pitcock
2009-04-29 15:13 ` Boris Derzhavets [this message]
2009-04-29 15:58 ` Attempt to load the most recent 2.6.30-rc-tip under Xen-3.3.1 on F11-preview Boris Derzhavets
2009-04-29 16:35 ` Jeremy Fitzhardinge
2009-04-29 18:42 ` Boris Derzhavets
2009-02-25 6:39 ` Xen with dom0 pvops on ultra-recent "git tip"kernel on x86_64 Boris Derzhavets
2009-01-20 20:08 ` Xen with dom0 pvops on ultra-recent "git tip" kernel " Jeremy Fitzhardinge
2009-01-20 21:27 ` Pasi Kärkkäinen
2009-01-21 18:32 ` Andrew Lyon
2009-01-26 19:56 ` Adam Wendt
2009-01-13 18:16 ` Pasi Kärkkäinen
2009-01-16 17:26 ` Jeremy Fitzhardinge
2009-01-16 18:22 ` Pasi Kärkkäinen
2009-01-10 20:40 ` Marc - A. Dahlhaus
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=178595.15145.qm@web56103.mail.re3.yahoo.com \
--to=bderzhavets@yahoo.com \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.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 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.