This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] XCP (bug?): another frontend device is already connected

To: George Shuklin <amarao@xxxxxxxxxxx>
Subject: Re: [Xen-devel] XCP (bug?): another frontend device is already connected to this domain
From: Daniel Stodden <daniel.stodden@xxxxxxxxxx>
Date: Thu, 2 Sep 2010 11:50:21 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 02 Sep 2010 11:51:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1283099946.2952.154.camel@xxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1283099946.2952.154.camel@xxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Sun, 2010-08-29 at 12:39 -0400, George Shuklin wrote: 
> Good day. 
> After few month of test usage suddenly got strange behavior:
> xe vm-install template=... new-name-label=...
> xe vif-create ...
> xe vm-param-set uuid=... other-config:install-repository=....
> xe vm-start uuid=...
> Got following error message:
> The server failed to handle your request, due to an internal error.  The
> given message may give details useful for debugging the problem.
> message: another frontend device is already connected to this domain
> (frontend (domid=0 | kind=vbd | devid=51712); backend (domid=0 |
> kind=tap | devid=51712))
> If I recreate VBD, it seems fine but say usual error about 'non
> bootable' (as if I run installation once and stops it).
> Main concern - first error message? What it is? And how can I debug i

It typically means dom0 failed to correctly deal with an (ephemeral) VBD
created to access a domU disk. The result is typically an xvd[a, in the
above case] node still hanging around, and thats why subsequent
operations choke.

Check /var/log/SMlog for errors around the time it happened.
If that doesn't help, run a xen-bugtool please.


> xensource.log is clear:
> [20100829T16:31:58.200Z| info|cvt-xh1|10262 unix-RPC|
> session.login_with_password D:6804a72a3b6a|http] stunnel pid: 23964
> (cached = true) connected to
> [20100829T16:31:58.225Z|debug|cvt-xh1|10263 unix-RPC||cli] xe vm-start
> uuid=105e35f9-71ba-799e-a8c0-4579f4c03087 username=root password=null

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-devel] XCP (bug?): another frontend device is already connected to this domain, Daniel Stodden <=