[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-bugs] [Bug 248] Add associated bridge interface to xm list
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=248 ------- Additional Comments From ewan@xxxxxxxxxxxxx 2005-10-13 23:04 ------- xm network-list is almost providing this functionality: nic@wuwei:~$ sudo xm network-list 2 (1 ((backend-id 0) (mac aa:00:00:88:02:40) (handle 1) (backend /local/domain/0/backend/vif/2/1) (tx-ring-ref 521) (rx-ring-ref 522) (event-channel 10))) It's ugly, but you can almost figure out that vif2.1 corresponds to this domain. Rather than add this info to xm list, which is already just about full, it would be better to make xm network-list print out its info in a decent format. Maybe we preserve the current behaviour as xm network-list --long, for those who need to get their hands dirty. Maybe we can scrape ifconfig, brctl et al for other useful info TX & RX bytes, etc. -- Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. _______________________________________________ Xen-bugs mailing list Xen-bugs@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-bugs
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |