[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xen-users
Subject:    Re: [Xen-users] [Xen-devel]  xl and vifname
From:       chris <tknchris () gmail ! com>
Date:       2011-12-28 13:59:57
Message-ID: CAKnNFz8sHNvKEyF=oRci6rwO6a82XS3x9AJMACPdu3_qTSx8Dg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


+1 to using vifname pretty heavily, sure you can get the job done without
but why suffer needlessly? :)

On Wed, Dec 28, 2011 at 6:19 AM, Pasi K=E4rkk=E4inen <pasik@iki.fi> wrote:

> On Mon, Dec 19, 2011 at 12:57:43PM +0100, Florian Heigl wrote:
> > Hi,
> >
>
> Hello,
>
> > 2011/12/17  <mark@internecto.net>:
> > > While using xen 4.1-testing.hg (r23202) I noticed that the 'vifname'
> > > config value is not handled by xl, but is handled by xm. Is there a
> > > workaround or patch for this? My firewall and scripts depend on stati=
c
> > > vifnames.
> >
> > xl does not support vifname as of now.
> > Except for one type of HVM domU, where it does support vifname.
> >
> > You might want to communicate to xen-devel that you rely on it and all
> that.
> >
>
> Added xen-devel to CC list ..
>
> > I also think I need vifname support - it's unbearable to work without
> > vifnames if you run a setup with potentially many 100 vifs + vlans +
> > brides + bonds.
> > (I guess thats how the whole UUID disaster in XenServer happened)
> >
> > I said "think I need" because I DO rely on them, but maybe something
> > happens that makes me suddenly understand that it's better to script
> > against some API to get the information reliably without any problem
> > by changing domIDs and always being up-to-date.
> > Oh wait, that would be like setting vifname and just looking at the
> > ifconfig output :)
> >
> >
> > Florian
> >
> > --
> > the purpose of libvirt is to provide an abstraction layer hiding all
> > xen features added since 2006 until they were finally understood and
> > copied by the kvm devs.
> >
>
> -- Pasi
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

[Attachment #5 (text/html)]

+1 to using vifname pretty heavily, sure you can get the job done without but why \
suffer needlessly? :)<br><br><div class="gmail_quote">On Wed, Dec 28, 2011 at 6:19 \
AM, Pasi Kärkkäinen <span dir="ltr">&lt;<a \
href="mailto:pasik@iki.fi">pasik@iki.fi</a>&gt;</span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">On Mon, Dec 19, 2011 at 12:57:43PM +0100, Florian Heigl \
wrote:<br> &gt; Hi,<br>
&gt;<br>
<br>
Hello,<br>
<div class="im"><br>
&gt; 2011/12/17  &lt;<a \
href="mailto:mark@internecto.net">mark@internecto.net</a>&gt;:<br> &gt; &gt; While \
using xen 4.1-testing.hg (r23202) I noticed that the &#39;vifname&#39;<br> &gt; &gt; \
config value is not handled by xl, but is handled by xm. Is there a<br> &gt; &gt; \
workaround or patch for this? My firewall and scripts depend on static<br> &gt; &gt; \
vifnames.<br> &gt;<br>
&gt; xl does not support vifname as of now.<br>
&gt; Except for one type of HVM domU, where it does support vifname.<br>
&gt;<br>
&gt; You might want to communicate to xen-devel that you rely on it and all that.<br>
&gt;<br>
<br>
</div>Added xen-devel to CC list ..<br>
<div class="im"><br>
&gt; I also think I need vifname support - it&#39;s unbearable to work without<br>
&gt; vifnames if you run a setup with potentially many 100 vifs + vlans +<br>
&gt; brides + bonds.<br>
&gt; (I guess thats how the whole UUID disaster in XenServer happened)<br>
&gt;<br>
&gt; I said &quot;think I need&quot; because I DO rely on them, but maybe \
something<br> &gt; happens that makes me suddenly understand that it&#39;s better to \
script<br> &gt; against some API to get the information reliably without any \
problem<br> &gt; by changing domIDs and always being up-to-date.<br>
&gt; Oh wait, that would be like setting vifname and just looking at the<br>
&gt; ifconfig output :)<br>
&gt;<br>
&gt;<br>
&gt; Florian<br>
&gt;<br>
&gt; --<br>
&gt; the purpose of libvirt is to provide an abstraction layer hiding all<br>
&gt; xen features added since 2006 until they were finally understood and<br>
&gt; copied by the kvm devs.<br>
&gt;<br>
<br>
</div>-- Pasi<br>
<br>
<br>
_______________________________________________<br>
Xen-devel mailing list<br>
<a href="mailto:Xen-devel@lists.xensource.com">Xen-devel@lists.xensource.com</a><br>
<a href="http://lists.xensource.com/xen-devel" \
target="_blank">http://lists.xensource.com/xen-devel</a><br> </blockquote></div><br>



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

[prev in list] [next in list] [prev in thread] [next in thread]