Michael Jinks wrote:
On Wed, Jul 15, 2009 at 6:24 PM, Chris Webb wrote:
You want
-net nic,vlan=0 -net tap,vlan=0,ifname=tap11 -net nic,vlan=1 -net
tap,vlan=1,ifname=tap12
Progress! This works, I can bring up the guest and watch it boot, but
both of its NICs came up bound to the first bridg
Michael Jinks writes:
> How do I make a guest use a specific tap? Quoting
> from my initial post, my -net options are:
>
> -net nic -net tap,name=tap11 -net nic -net tap,name=tap12
You want
-net nic,vlan=0 -net tap,vlan=0,ifname=tap11 -net nic,vlan=1 -net
tap,vlan=1,ifname=tap12
to get t
On Thu, Jul 16, 2009 at 01:12:19AM +0200, Andreas Plesner Jacobsen wrote:
> >>
> >> I tried "fd=" instead of "name=", but that looks for a file descriptor
> >> instead of a network interface name, and I didn't even know that Linux
> >> had file descriptors for network interfaces let alone how to ma
On Wed, Jul 15, 2009 at 6:35 PM, Andreas Plesner Jacobsen wrote:
> On Wed, Jul 15, 2009 at 06:22:56PM -0500, Michael Jinks wrote:
>> I suppose that's a good sign, but it still leaves me wondering how to
>> control which tap connects to which bridge, if I can't attach a guest
>> to an existing tap
On Wed, Jul 15, 2009 at 6:24 PM, Chris Webb wrote:
> You want
>
> -net nic,vlan=0 -net tap,vlan=0,ifname=tap11 -net nic,vlan=1 -net
> tap,vlan=1,ifname=tap12
Progress! This works, I can bring up the guest and watch it boot, but
both of its NICs came up bound to the first bridge on the system.
On Wed, Jul 15, 2009 at 06:22:56PM -0500, Michael Jinks wrote:
> >> # kvm -m 512M -net nic -net tap,name=tap11 -net nic -net
> >> tap,name=tap12 -hda /vmstore/wee -vnc :11 -cdrom
> >> /path/to/my/Windows.iso -boot d
> >
> > The parameter is "ifname", not "name".
>
> In that case, what does the "
device tap11 is already a member of a bridge; can't enslave it to bridge br0.
/etc/kvm/kvm-ifup: could not launch network script
Could not initialize device 'tap'
That's because your kvm-ifup scripts tries to connect the tap to the
bridge and it's already there. You should either remove it f
>> # kvm -m 512M -net nic -net tap,name=tap11 -net nic -net
>> tap,name=tap12 -hda /vmstore/wee -vnc :11 -cdrom
>> /path/to/my/Windows.iso -boot d
>
> The parameter is "ifname", not "name".
In that case, what does the "name" parameter mean? Quoting from the
manpage on my system:
-net ta
On Wed, Jul 15, 2009 at 07:05:48PM -0400, Stephane Bakhos wrote:
>>
>> I tried "fd=" instead of "name=", but that looks for a file descriptor
>> instead of a network interface name, and I didn't even know that Linux
>> had file descriptors for network interfaces let alone how to map them
>> to a ta
On Wed, Jul 15, 2009 at 6:12 PM, Andreas Plesner Jacobsen wrote:
> On Wed, Jul 15, 2009 at 07:05:48PM -0400, Stephane Bakhos wrote:
>>>
>> You need to add a vlan option to one of them, for example vlan=2
>> Otherwise kvm will bridge the interfaces together, and it's going to
>> create a packet stor
On Wed, Jul 15, 2009 at 05:54:14PM -0500, Michael Jinks wrote:
>
> Now I want to bring up a VM with two NICs, one attached to tap12
> (bridge 0), the other on tap11 (bridge 1), but I think I've
> misunderstood the versious "-net" options as described in the kvm man
> page. It *seems* to say that
bridge name bridge id STP enabled interfaces
br0 8000.00144fa1f17a no eth0
tap0
tap1
You need to add a vlan option to one of them, for example vlan=2
Otherwise kvm will bridge the interfaces together, and it's going to create
a packet storm.
I wondered about that -- but what's the relationship of a KVM vlan to
my existing bridge interfaces, and how can I control which one gets
m
On Wed, Jul 15, 2009 at 6:05 PM, Stephane
Bakhos wrote:
> You need to add a vlan option to one of them, for example vlan=2
> Otherwise kvm will bridge the interfaces together, and it's going to create
> a packet storm.
I wondered about that -- but what's the relationship of a KVM vlan to
my exist
14 matches
Mail list logo
