From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>,
M A Young <m.a.young@durham.ac.uk>
Cc: xen-devel@lists.xensource.com, Don Dutile <ddutile@redhat.com>,
Wilk <konrad.wilk@oracle.com>,
Konrad
Subject: RE: Help booting Xen under RHEL6 beta2
Date: Sat, 10 Jul 2010 19:24:29 -0700 (PDT) [thread overview]
Message-ID: <530185ed-c8b1-4ace-ab3f-f237e62b33d3@default> (raw)
In-Reply-To: <e637f372-3f1f-45b3-91af-117debd4dbde@default>
Slightly more progress. I discovered xenstored is not running...
so I did:
# modprobe xen-evtchn
# xenstored
# xenconsoled
# /etc/init.d/xend start
but xend fails to start with the same messages (ending
in "Connection refused").
> -----Original Message-----
> From: Dan Magenheimer
> Sent: Saturday, July 10, 2010 3:42 PM
> To: M A Young
> Cc: xen-devel@lists.xensource.com; Don Dutile; Konrad Wilk
> Subject: RE: [Xen-devel] Help booting Xen under RHEL6 beta2
>
> Hi Michael --
>
> Thanks for the help!
>
> > Also I suggest you check whether the hypervisor and xen software are
> > the same version. If they aren't then xend may not be able to the
> > hypervisor.
>
> They are definitely the same version as I cloned only xen-4.0-testing
> and built/installed both on the test machine itself.
>
> > Are you limiting the memory for dom0? If so I suggest you allow it
> > more, or don't limit it at all and see if it boots any more
> > successfully.
>
> Yes, I think you are right. I have always booted dom0 with 256M
> on this box, but I guess more recent gnome tools are much more
> bloated so that accounts for the swapping and slowness.
>
> > It is
> > also probably worth booting direct to run level 3 (add 3 to the boot
> > line) to so you can eliminate whether or not graphics is an issue.
>
> Yes, I did that. This skips the graphics looping but xend
> still fails to start (and I can no longer VNC to the box...
> fortunately it is a laptop at least).
>
> Thanks,
> Dan
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-07-11 2:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 22:16 Help booting Xen under RHEL6 beta2 Dan Magenheimer
2010-07-09 5:30 ` Pasi Kärkkäinen
2010-07-09 14:09 ` Don Dutile
2010-07-09 17:44 ` Konrad Rzeszutek Wilk
2010-07-09 18:09 ` M A Young
2010-07-09 20:01 ` Konrad Rzeszutek Wilk
2010-07-09 22:48 ` Dan Magenheimer
2010-07-09 23:27 ` M A Young
2010-07-10 21:42 ` Dan Magenheimer
2010-07-11 2:24 ` Dan Magenheimer [this message]
2010-07-12 10:37 ` Stefano Stabellini
2010-07-12 13:59 ` Dan M @ Oracle
2010-07-12 14:06 ` Stefano Stabellini
2010-07-12 14:30 ` Keir Fraser
2010-07-12 14:37 ` Ian Campbell
2010-07-12 20:19 ` Dan Magenheimer
2010-07-12 20:38 ` Keir Fraser
2010-07-12 20:44 ` Dan Magenheimer
2010-07-12 21:10 ` Keir Fraser
2010-07-12 21:36 ` Dan Magenheimer
2010-07-13 6:19 ` Keir Fraser
2010-07-13 0:39 ` Dan Magenheimer
2010-07-13 1:30 ` Konrad Rzeszutek Wilk
2010-07-13 23:55 ` Dan Magenheimer
2010-07-14 15:31 ` Dan Magenheimer
[not found] <4a7f9b7c-0f2d-4f6c-898d-9716d55e1ace@defaultC8613BEA.3186%keir.fraser@eu.citrix.com>
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=530185ed-c8b1-4ace-ab3f-f237e62b33d3@default \
--to=dan.magenheimer@oracle.com \
--cc=ddutile@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=m.a.young@durham.ac.uk \
--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 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).