Bug 487835

Summary:	RFE: iface name: Generated <interface> targets should contain the VM ID, helps debugging
Product:	[Community] Virtualization Tools	Reporter:	Juan Urroa <observer1>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	berrange, clalance, crobinso, veillard, virt-maint, xen-maint
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-27 21:02:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	636033

Description Juan Urroa 2009-02-28 04:04:23 UTC

Description of problem:
This a whish to have not a bug. I think it would be very practical to show the vm id in the name of the vnets created by libvirt, just like in Xen

Version-Release number of selected component (if applicable):
all

How reproducible:
create a new vm and run ifconfig it shows vnet0, vnet1,...
It should be better if the look like vnet0.0, vnet11.0 like in Xen vifs
  
Actual results:
vnet0

Expected results:
vnet0.1

Comment 1 Mark McLoughlin 2009-03-25 18:15:38 UTC

Moving to upstream libvirt bugzilla - I guess it wouldn't be difficult to implement, but would it really help much?

Comment 2 Juan Urroa 2009-09-29 23:40:05 UTC

It helps when debugging the network with wireshark

Comment 3 Cole Robinson 2015-04-27 21:02:11 UTC

This never happened and I don't really expect it ever will, so just closing. If someone still cares I suggest sending a patch to libvir-list for discussion