Hi,

Actually udev renames the eth0 interface in guest to eth1 because macvtap0 has different mac address then eth0 on host..

Is there some way so that we can prevent changing this rename of eth0 to eth1 on guest. I don’t want to change udev files.

 

 

On 12/13/2011 12:59 PM, Amit Tewari wrote:

Hi all,

 

My test environment

Host os=rhel6.1

Guest os = rhel6.1

Libvirt=0.9.8

Kvm hypervisor

 

I have made this entry in guest xml file

 

<interface type='direct'>

      <source dev='eth0' mode='bridge'/>

      <model type='virtio'/>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>

    </interface>

 

Now when I start the guest

#virsh start guest

 

Following macvtap0 is created on host and is shown below

#ip link show macvtap0

51: macvtap0@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UNKNOWN qlen 500

    link/ether 52:54:00:55:AE:B5brd ff:ff:ff:ff:ff:ff

 

but when the guest is up and I try to perform

 

# ifup eth0

 

It gives following message

“Bringing up interface eth0:  Device eth0 does not seem to be present, delaying initialization.

[FAILED]”

The interface name may change to ethN(N may be 1 or 2 ...) due to the change of guest interface mac address.
You can log in guest and use command: "ip  link show" to get the value of N.
Then create ifcfg-ethN for it and use "ifup ethN" to start it in guest.

 

Guest eth interface does not create. What is the problem?

 

When I checked dmesg on host it gives following message—“macvatp0: ipv6 routers not present”

 

Please let me know how macvtap work on kvm.

 

DISCLAIMER: 

----------------------------------------------------------------------------------------------------------------------- 

The contents of this e-mail and any attachment(s) are confidential and

intended 

for the named recipient(s) only.  

It shall not attach any liability on the originator or NECHCL or its 

affiliates. Any views or opinions presented in  

this email are solely those of the author and may not necessarily reflect the 

opinions of NECHCL or its affiliates.  

Any form of reproduction, dissemination, copying, disclosure, modification, 

distribution and / or publication of  

this message without the prior written consent of the author of this e-mail is 

strictly prohibited. If you have  

received this email in error please delete it and notify the sender 

immediately. . 

-----------------------------------------------------------------------------------------------------------------------

--

libvir-list mailing list

libvir-list@redhat.com

https://www.redhat.com/mailman/listinfo/libvir-list

 

DISCLAIMER: 
----------------------------------------------------------------------------------------------------------------------- 
The contents of this e-mail and any attachment(s) are confidential and
intended 
for the named recipient(s) only.  
It shall not attach any liability on the originator or NECHCL or its 
affiliates. Any views or opinions presented in  
this email are solely those of the author and may not necessarily reflect the 
opinions of NECHCL or its affiliates.  
Any form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of  
this message without the prior written consent of the author of this e-mail is 
strictly prohibited. If you have  
received this email in error please delete it and notify the sender 
immediately. . 
-----------------------------------------------------------------------------------------------------------------------