George Shuklin
2010-Aug-29 16:39 UTC
[Xen-devel] XCP (bug?): another frontend device is already connected to this domain
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 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 10.1.3.4:443 [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 Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Daniel Stodden
2010-Sep-02 18:50 UTC
Re: [Xen-devel] XCP (bug?): another frontend device is already connected to this domain
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 iIt 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. Daniel> 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 10.1.3.4:443 > [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 Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel