All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Charles Coffing" <ccoffing@novell.com>
To: xen-devel@lists.xensource.com
Subject: can't start domU
Date: Fri, 11 Nov 2005 15:12:38 -0700	[thread overview]
Message-ID: <4374B47B.D169.003C.0@novell.com> (raw)

I've been getting hangs while attempting to start domUs on recent
changesets.  I get an error such as:
Error: Device 0 (vif) could not be connected. Hotplug scripts not
working.

Yet if I run diagnose.py on the now- paused domU, I get this:
# python diagnose.py 2
Domain ID is 2.
Domain name is ExampleDomain.
Found 2 device classes in use.
Found 1 vbd devices.
Found device vbd, 769.
Backend is stuck waiting for frontend for device vbd, 769.
Device vbd, 769 hotplugging has completed successfully.
Found 0 vif devices.

Any idea why the front end would be stuck?

I'm running udev 068.

             reply	other threads:[~2005-11-11 22:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-11 22:12 Charles Coffing [this message]
2005-11-11 22:44 ` can't start domU Nivedita Singhvi
2005-11-11 23:13   ` Charles Coffing
2005-11-15 19:59     ` Steve Dobbelstein
2005-11-15 23:34       ` Ewan Mellor
2005-11-16 17:19         ` Steve Dobbelstein
2005-11-16 18:45           ` Ewan Mellor
2005-11-16 18:49             ` Ewan Mellor
2005-11-16 20:14               ` peter Bier
2005-11-16 23:21             ` Steve Dobbelstein
2005-11-18 17:32               ` Ewan Mellor
2005-11-18 19:07                 ` Steve Dobbelstein
  -- strict thread matches above, loose matches on Subject: below --
2005-11-16 20:23 Hien Nguyen
2005-11-16 23:39 ` Ewan Mellor
2005-11-17 16:39   ` Hien Nguyen
2005-11-17 16:55     ` Ewan Mellor
2005-11-17 21:15 Hien Nguyen

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=4374B47B.D169.003C.0@novell.com \
    --to=ccoffing@novell.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.