search for: vnet6

...gt; <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> And afterwards: <interface type='bridge'> <mac address='52:54:00:34:a1:56'/> <target dev='vnet6'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> Someone has an idea whats causing this? Is there a s...

...vnet13 vnet2 vnet3 vnet4 vnet6 vnet8 br1 8000.00237dd22a50 no eth1 vnet1 vnet12...

...m to internet, and added them to another isolated > bridge what's not connected to internet. Problem is that I cannot reach > the other host in the isolated network. > > Something like this: > > virsh shutdown kvm66 > virsh shutdown kvm68 > > brctl delif br0 vnet10 vnet6 # the interfaces of kvm66 and kvm68 > brctl addbr br1 > brctl addif br1 vnet10 vnet6 The delif and addif commands won't do anything if the guests are not running (you've done "virsh shutdown", but that will either take some time, or never be honored (depending on how the...

...comfortable editing > XML). An additional command to run to verify your Ethernet bridge(s) operation is: brctl show brctl show <bridge> ~]# brctl show XX_br0 bridge name bridge id STP enabled interfaces XX_br0 8000.00151713fdbc no p1p1 vnet0 vnet1 vnet11 vnet12 vnet13 vnet19 vnet2 vnet4 vnet6 vnet7 -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20160318/0d883b73/attachment-0002.html>

...vnet13 vnet2 vnet3 vnet4 vnet6 vnet8 br1 8000.00237dd22a50 no eth1 vnet1 vnet12...

...vnet13 > > vnet2 > > vnet3 > > vnet4 > > vnet6 > > vnet8 > > br1 8000.00237dd22a50 no eth1 > > vnet1 > > vnet12 > >...

...omain='0x0000' bus='0x00' slot='0x03' > function='0x0'/> > </interface> > > > And afterwards: > > <interface type='bridge'> > <mac address='52:54:00:34:a1:56'/> > <target dev='vnet6'/> > <model type='virtio'/> > <alias name='net0'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x03' > function='0x0'/> > </interface> > > Someone has an ide...

...vnet13 vnet2 vnet3 vnet4 vnet6 vnet8 br1 8000.00237dd22a50 no eth1 vnet1 vnet12...

...pe='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <interface type='bridge'> <mac address='52:54:00:d3:c9:24'/> <source bridge='br57'/> <target dev='vnet6'/> <model type='rtl8139'/> <alias name='net1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </interface> <serial type='pty'> <sourc...

...let me know CentOS 6.2 x86_64 libvirt-0.9.4-23.el6_2.4 kernel-2.6.32-220.4.1.el6 # brctl show bridge name bridge id STP enabled interfaces br0 8000.001b21a1cf76 no eth3 vnet0 # Problematic host vnet1 vnet3 vnet4 vnet5 br1 8000.001b21a1ce4d no eth2 vnet6 virbr0 8000.525400a050ba yes virbr0-nic vnet2 # ARP entry when it's the correct MAC <omitted>.tamu.edu ether 52:54:00:e0:1e:6f C eth0 # ARP entry when it's wrong and ping or other connections time out <omitted>.tamu.edu ether 00:1e:...

...bridge(s) > operation is: > brctl show > brctl show <bridge> > > > ~]# brctl show XX_br0 > bridge name bridge id STP enabled interfaces > XX_br0 8000.00151713fdbc no p1p1 > vnet0 > vnet1 > vnet11 > vnet12 > vnet13 > vnet19 > vnet2 > vnet4 > vnet6 > vnet7 > > > > > -- > ---~~.~~--- > Mike > // SilverTip257 // > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > https://lists.centos.org/mailman/listinfo/centos-virt Hi, You need to look at the...

...pe='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <interface type='bridge'> <mac address='52:54:00:d3:c9:24'/> <source bridge='br57'/> <target dev='vnet6'/> <model type='rtl8139'/> <alias name='net1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </interface> <serial type='pty'> <sourc...

...STP enabled interfaces > > br0 8000.00237dd22a4c no eth0 > > vnet0 > > vnet10 > > vnet11 > > vnet13 > > vnet2 > > vnet3 > > vnet4 > > vnet6 > > vnet8 > > br1 8000.00237dd22a50 no eth1 > > vnet1 > > vnet12 > > vnet5 > > vnet7 > > vnet9 > > Needless to say the existing vnet?? Devices are in use...

...pe='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <interface type='bridge'> <mac address='52:54:00:d3:c9:24'/> <source bridge='br57'/> <target dev='vnet6'/> <model type='rtl8139'/> <alias name='net1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </interface> <serial type='pty'> <sourc...

<div style="FONT-FAMILY: Arial; COLOR: rgb(0, 0, 0); FONT-SIZE: 12px"><div>Thanks, I followed the 2nd article, and it got the existing virtual machines communicating with each other.<br /><br />However, any new virtual machines I created after making the changes can't communicate with anything, they can't even get out to the internet, even if I manually

...br0 8000.00237dd22a4c no eth0 > > vnet0 > > vnet10 > > vnet11 > > vnet13 > > vnet2 > > vnet3 > > vnet4 > > vnet6 > > vnet8 > > br1 8000.00237dd22a50 no eth1 > > vnet1 > > vnet12 > > vnet5 > > vnet7 > > vnet9 > > Needless to say the existing vnet??...

...x0000' bus='0x00' slot='0x03' > function='0x0'/> > </interface> > <interface type='bridge'> > <mac address='52:54:00:d3:c9:24'/> > <source bridge='br57'/> > <target dev='vnet6'/> > <model type='rtl8139'/> > <alias name='net1'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x07' > function='0x0'/> > </interface> > <serial type=...

...</span>vnet2</div><div class="gmail_extra"><span class="" style="white-space:pre"> </span>vnet4</div><div class="gmail_extra"><span class="" style="white-space:pre"> </span>vnet6</div><div class="gmail_extra"><span class="" style="white-space:pre"> </span>vnet7</div><div><br /></div></div><div class="gmail_extra"><br /></div>-- <br /><div class=&quo...

________________________________ From: centos-virt-bounces at centos.org <centos-virt-bounces at centos.org> on behalf of Laurentiu Soica <laurentiu at soica.ro> Sent: Sunday, August 14, 2016 10:17 AM To: Discussion about the virtualization on CentOS Subject: Re: [CentOS-virt] Nested KVM issue More details on the subject: I suppose it is a nested KVM issue because it raised after I

...' slot='0x03' >> function='0x0'/> >> </interface> >> <interface type='bridge'> >> <mac address='52:54:00:d3:c9:24'/> >> <source bridge='br57'/> >> <target dev='vnet6'/> >> <model type='rtl8139'/> >> <alias name='net1'/> >> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' >> function='0x0'/> >> </interface> >>...