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-users] XCP can't delete vlan

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] XCP can't delete vlan
From: George Shuklin <sector-bl@xxxxxxxxx>
Date: Thu, 03 Jun 2010 16:51:02 +0400
Delivery-date: Mon, 14 Jun 2010 08:09:33 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1275569463; bh=tfqCs4nCB13CR/l+aUVzS9MK3qATHIEze1Zp+iKaRRk=; h=From:To:In-Reply-To:References:Subject:MIME-Version:Message-Id: Date:Content-Transfer-Encoding:Content-Type; b=l+8REE88x71cak8kYI4oiZjfPhhulrViFpiVKHEBewuNOMPei6d7Av/OZB9SMolm6 A6TuPL85+bTOKqwu+F9npi4CDoyyTMd2Mz+2OfJBxeTiwqKpe9ef6zFTaZymPAE7BF 0dGPHVv28Y/5fN/Qp9jqhWzJCElIteQUo3mogG54=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C06CF38.60501@xxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4C06CF38.60501@xxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I got same error when tried to bind xcp host managment interface to vlan 
instead 'native vlan' (or, in other terms, 'untagged traffic' in hybrid port).

As I understand after few experiments, Xen does not like managment interfaces 
on vlan. So, you can create separate network for vm's with tagged vlan, but 
managment interface shall be without tagging.

Let's assume it as bug-feature.

03.06.10, 01:38, "Anatoliy.Poloz" <Anatoliy.Poloz@xxxxxxxxxxxxxxxx>:

> Good day.encountered the following situation. I created a vlan for the VM and 
> then realized that it would not be able to migrate to another host, without 
> creating a vlan in the pool.when trying to create vlan in the pool ha console 
> reports that that"You tried to create a PIF, but it already exists.PIF: eth0 
> "that is logical.but when I try to delete this vlan I get the message"# Xe 
> vlan-destroy uuid = f9825480-9167-a380-569c-44a8e96af945The uuid you supplied 
> was invalid.type: PIFuuid: f9825480-9167-a380-569c-44a8e96a945 "me that 
> something is missed or a 
> mistake?_______________________________________________Xen-users mailing 
> listXen-users@xxxxxxxxxxxxxxxxxxxxxxx://lists.xensource.com/xen-users 


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>