From: Matt Ayres <matta@tektonic.net>
To: Tony Hernandez <ttony.hernandez@gmail.com>
Cc: Colin Brown <brownc@franklin.edu>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
xen-users@lists.xensource.com
Subject: Re: [Xen-users] vdb and vif connection errors
Date: Fri, 07 Apr 2006 10:45:20 -0400 [thread overview]
Message-ID: <44367B00.5010603@tektonic.net> (raw)
In-Reply-To: <91f07eb00604070735m65c23a3fg74b9badf303ce51d@mail.gmail.com>
Tony Hernandez wrote:
> Colin,
>
> I've had this problem too. I've noticed that if I destroy the domU and
> then mount the vdb through a loop back, access a file (not sure if this
> step is necessary, but I do it), then unmount it, I'm able then to start
> the domU.
>
> As for your other questions, I have no idea.
>
>
>
> On 4/7/06, *Colin Brown* <brownc@franklin.edu
> <mailto:brownc@franklin.edu>> wrote:
>
> I hate intermittent problems ...
>
> Most of the time, my domUs launch just fine. But, occasionally I get a
> failure to connect a vdb or vif and the domU fails to completely launch
> ("xm list" shows it is present but no console activity either through
> "xm create -c" or through "xm console"). The log shows a stack trace
> in DevController.py in the area of waiting for hotplug response --
> sometimes a timeout, sometimes an error. There is usually no indication
> in the main log or the hotplug log as to the ultimate cause. Usually
> the device is the first vdb in my disk array; but often it's either
> another of the vdb's or a vif.
>
> I sometimes find it's something I did wrong like mistyping a vdb file
> name, in which case I have no cause for complaint.
>
This seems to be an old problem re-introduced in Xen 3.0.2. I am
experiencing it on my test server. In my specific scenario sometimes a
guest won't start properly due to a vbd not "connecting" properly. It
occurs only when there is heavy access to xend. Simply waiting until
there are no other xm commands running lets the domains start-up. At
boot though even with the 5 second delay in starting domains some will
exhibit this error. On my side hotplug "cleans" itself and I'm not
stuck with a paused domain, a simple xm create starts it right up.
Just a "me too". I'm cross-posting this to xen-devel as I know the
developers don't actively monitor the xen-users list as closely.
Thanks,
Matt Ayres
parent reply other threads:[~2006-04-07 14:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <91f07eb00604070735m65c23a3fg74b9badf303ce51d@mail.gmail.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=44367B00.5010603@tektonic.net \
--to=matta@tektonic.net \
--cc=brownc@franklin.edu \
--cc=ttony.hernandez@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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.