So you added the interface, when the domain was shut down?
Exactly
Do you have a chance to test libvirt 0.6.1 from unstable/testing?
I backported libvirt 0.6.1-1 from squeeze to lenny. If I now add
an additional network adapter via virt-manager, it gets correctly
displayed in hardware-column of virt-manager.
Also libvirt's XML
<interface type='bridge'>
<mac address='00:16:36:36:0d:11'/>
<source bridge='br0'/>
<script path='vif-bridge'/>
<target dev='vif-1.0'/>
</interface>
<interface type='bridge'>
<mac address='00:16:36:76:fb:11'/>
<source bridge='virbr1'/>
<script path='vif-bridge'/>
<target dev='vif-1.1'/>
</interface>
and xend's domain file refer the same
(device
(vif
(bridge br0)
(mac 00:16:36:36:0d:11)
(uuid fb9eda8a-24ae-1c70-afc4-3d1149178957)
(script vif-bridge)
)
)
(device
(vif
(bridge virbr1)
(mac 00:16:36:76:fb:11)
(uuid 44a01541-b8f0-9da5-9f1b-3c8d7dd08382)
(script vif-bridge)
)
)
Doing further modifications, deleting a NIC, adding a NIC, removing
one in the middle no longer mix up the setup. So 0.6.1 indeed
resolves this bug.
Cheers,
Andreas
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
