From: Ted Kaczmarek <tedkaz@optonline.net>
To: Xen Devs <xen-devel@lists.xensource.com>,
Nicholas Lee <emptysands@gmail.com>
Subject: Re: cannot boot domU
Date: Mon, 17 Oct 2005 08:17:45 -0400 [thread overview]
Message-ID: <1129551465.3496.75.camel@pluto.linsolutions.com> (raw)
In-Reply-To: <2b6116b30510170330l6c9bb023m14bd1f254f6a03c0@mail.gmail.com>
On Mon, 2005-10-17 at 23:30 +1300, Nicholas Lee wrote:
> On 10/17/05, Stephan Böni <boeni@bpm.ch> wrote:
> > # xm console inhouse
> > Linux version 2.6.12.6-xenU (root@xen1) (gcc version 4.0.2 20050901
> > (prerelease)
> > (SUSE Linux)) #1 SMP Sun Oct 16 15:40:12 CEST 2005
>
>
> I've not heard if Xen works with gcc 4.0. That might be worth checking.
Unstable works as well for me with gcc 4.0.1 as 3.4.3.
>
> Otherwise I suggest sending though logs from xm dmesg, vgdisplay and
> anything else that might be useful.
>
> Not sure what else I can suggest, pretty much told you everything I've
> figured out so far. :)
xen_changeset : Sun Oct 16 12:25:15 2005 +0100 7396:9b51e763767
This changeset appears to have less issues with respect to creating the
disk device for the domU, but I am having lots of problems with vifs
being mapped to the bridges, manually mapping them doesn't help. This
may be specific to the present setup I am using, eth0 is used for the
domU's and eth1 is the egress interface.
Regards,
Ted
>
> --
> Nicholas Lee
> http://stateless.geek.nz
> gpg 8072 4F86 EDCD 4FC1 18EF 5BDD 07B0 9597 6D58 D70C
next prev parent reply other threads:[~2005-10-17 12:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-16 14:38 cannot boot domU Stephan Böni
2005-10-16 14:52 ` stoeni
2005-10-17 10:30 ` Nicholas Lee
2005-10-17 12:17 ` Ted Kaczmarek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-16 15:01 Stephan Böni
2005-10-16 20:50 ` Nicholas Lee
2005-10-17 8:43 Stephan Böni
2005-10-17 9:58 ` Nicholas Lee
2005-10-17 9:59 Stephan Böni
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=1129551465.3496.75.camel@pluto.linsolutions.com \
--to=tedkaz@optonline.net \
--cc=emptysands@gmail.com \
--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.