Easily done - all attached. thanks!
On Fri, Jul 5, 2013 at 6:59 AM, Andrew Cooper <andrew.coop...@citrix.com>wrote: > All of that information from your current mac mini should be fine, even > with your hack in place. > > specifically, given the last two attachments, I can give you a less > fragile hack. > > ~Andrew > > > On 05/07/13 11:56, Andrew Eross wrote: > > Hi Andrew, > > Sure will - > > I've hacked/fixed up that one system already so it won't be as helpful > for logs/config - but on Monday I'm going to install a clean XS 6.2 on our > other identical Mac Mini + USB NIC and I'll be glad to collect the > requested data to send along. > > USB definitely wouldn't be the norm =) but we have this mirrored pair of > mac minis acting as our local office servers with the built-in gigabit used > for a dedicated DRBD cross-over, so hence the USB network for the > management interface - good fun. > > Cheers, > Andrew > > > On Fri, Jul 5, 2013 at 6:48 AM, Andrew Cooper > <andrew.coop...@citrix.com>wrote: > >> Hello, >> >> You are correct - I never considered USB ethernet devices when writing >> interface-rename. I shall raise a ticket to deal with this. This logic >> was substantially "improved" from 6.0.2 -> 6.1, including much more careful >> control of what was considered valid. >> >> In an effort to help (as we don't appear to have any in our testing >> environment), could you collect the outputs of "biosdevname -d", "lspci >> -tv", "lsusb", "lsusb -tv" and also attach /var/log/interface-rename.log ? >> >> As for a temporary hack for this system, can you attach your current >> /etc/udev/rules.d/60-net.rules and the output of "udevinfo -a -p >> /sys/class/net/<bad eth>" ? >> >> ~Andrew >> >> >> On 05/07/13 11:03, Rob Hoes wrote: >> >> Hi Andrew, >> >> The interface-rename script is intended to deal with situation where >> network cards are being replaced, removed or added, and tries to make sure >> that you still have the eth* names you would expect. For example, if you >> have a host with 2 NICs and replace eth1 with a new NIC in the same slot, >> the new NIC will again be called eth1 (and not eth2). >> >> However, this wasn't designed with USB interfaces in mind, because USB >> is not very common on the servers for which XenServer is normally used. So >> it is probably not going to work very well, as you have noticed. >> >> CC'ing Andrew Cooper, who worked on this. Andrew: do you think this is >> easy to address? A quick solution may be to give USB NICs a prefix other >> than "eth" to separate them from the regular PCI NICs, and to leave them >> alone after that? >> >> Cheers, >> Rob >> >> On 5 Jul 2013, at 00:52, Andrew Eross <er...@locatrix.com> wrote: >> >> Update to that - >> >> I've found there is kind of a work-around, although this isn't a great >> idea. >> >> Since I know my simple system only has eth0/eth1 and one of them is USB >> and is detected later in the boot process, there's probably little chance >> of any race conditions with the adapters, so basically if you disable >> net-rename-sideways.sh, >> it can work for the moment. >> >> I temporarily disabled /etc/udev/scripts/net-rename-sideways.sh by just >> a hack: >> if [[ "$1" =~ "^TEMPDISABLEDeth[0-9]+$" ]] >> >> And now it all works again after doing the usual to introduce a >> physical interface, etc: http://support.citrix.com/article/CTX121615 >> >> Of course, I hope there's a real/better solution for the future and I >> wouldn't be doing the above on important production systems (well, I >> probably also wouldn't be using a USB network adapter on a really important >> system, but I digress). >> >> Cheers, >> Andrew >> >> On Fri, Jul 5, 2013 at 9:33 AM, Andrew Eross <er...@locatrix.com> wrote: >> >>> Hi guys, >>> >>> I had a Mac Mini running XS 6.0.2 that used a USB network adapter for >>> it's management interface. >>> >>> Never any issues. >>> >>> I've installed a clean XS 6.2 over it this morning, with no changes >>> made to the hardware setup, just installed the new software. >>> >>> Now the USB network adapter is no longer working properly, and is >>> named "side-48348-eth1" instead of "eth1". >>> >>> I've dug further into this and I think it's something to do with >>> interface-rename.py/udev/net-rename-sideways.sh >>> >>> net-rename-sideway.sh is correctly renaming the adapter to >>> 'side-<random number-eth1' at start-up, which is normal >>> >>> The problem seems to be that it doesn't get renamed back to eth1 later >>> on like it's supposed to be. >>> >>> I see "Later, an RC3 script will take these renamed devices and rename >>> them correctly." inside net-rename-sideways.sh, but this doesn't seem to be >>> happening. >>> >>> I might've found a hint when I tried running interface-rename.py >>> manually just to see what happens: >>> >>> ./interface-rename.py --rename >>> ERROR [2013-07-05 09:30:46] Can't generate current state for >>> interface '{'Driver': 'asix', 'Bus Info': 'usb-0000:00:1d.7-1.3', 'BIOS >>> device': {'all_ethN': 'eth1', 'physical': ''}, 'Assigned MAC': >>> '80:49:71:11:84:FC', 'Firmware version': 'ASIX AX88772 USB 2.0 Ethernet', >>> 'Driver version': '14-Jun-2006', 'Kernel name': 'eth1'}' - Unrecognised PCI >>> address 'usb-0000:00:1d.7-1.3' >>> >>> Maybe some sub-system doesn't like the PCI address being a usb device? >>> There must've been a change somewhere between XS 6.0.2 to 6.2 related to >>> this? >>> >>> Any ideas on a work-around / hopefully we can fix this in a future >>> release? >>> >>> Thanks! >>> Andrew >>> >>> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >> >> >> >> > >
[root@vh03 ~]# biosdevname -d
BIOS device: eth0
Kernel name: eth0
Permanent MAC: 3C:07:54:6A:3F:ED
Assigned MAC : 3C:07:54:6A:3F:ED
Driver: tg3
Driver version: 3.124c
Firmware version: 57765-v1.42
Bus Info: 0000:02:00.0
PCI name : 0000:02:00.0
PCI Slot : Unknown
Index in slot: 1
BIOS device: eth1
Kernel name: eth1
Assigned MAC : 80:49:71:11:84:FC
Driver: asix
Driver version: 14-Jun-2006
Firmware version: ASIX AX88772 USB 2.0 Ethernet
Bus Info: usb-0000:00:1d.7-1.3
[root@vh03 ~]# lspci -tv
-[0000:00]-+-00.0 Intel Corporation 2nd Generation Core Processor Family DRAM
Controller
+-01.0-[01]--
+-01.1-[06-9c]--
+-02.0 Intel Corporation 2nd Generation Core Processor Family
Integrated Graphics Controller
+-16.0 Intel Corporation 6 Series/C200 Series Chipset Family MEI
Controller #1
+-1a.0 Intel Corporation 6 Series/C200 Series Chipset Family USB
Universal Host Controller #5
+-1a.7 Intel Corporation 6 Series/C200 Series Chipset Family USB
Enhanced Host Controller #2
+-1b.0 Intel Corporation 6 Series/C200 Series Chipset Family High
Definition Audio Controller
+-1c.0-[02]--+-00.0 Broadcom Corporation NetXtreme BCM57765 Gigabit
Ethernet PCIe
| \-00.1 Broadcom Corporation NetXtreme BCM57765 Memory
Card Reader
+-1c.1-[03]----00.0 Broadcom Corporation BCM4331 802.11a/b/g/n
+-1c.2-[04-05]----00.0-[05]----00.0 Texas Instruments
XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express]
+-1d.0 Intel Corporation 6 Series/C200 Series Chipset Family USB
Universal Host Controller #1
+-1d.7 Intel Corporation 6 Series/C200 Series Chipset Family USB
Enhanced Host Controller #1
+-1f.0 Intel Corporation HM65 Express Chipset Family LPC Controller
+-1f.2 Intel Corporation 6 Series/C200 Series Chipset Family 4 port
SATA IDE Controller
\-1f.3 Intel Corporation 6 Series/C200 Series Chipset Family SMBus
Controller
[root@vh03 ~]# lsusb
Bus 001 Device 090: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
Bus 001 Device 007: ID 05ac:820b Apple, Inc.
Bus 001 Device 008: ID 05ac:8281 Apple, Inc.
Bus 001 Device 002: ID 0424:2513 Standard Microsystems Corp.
Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of
BCM2046 Bluetooth)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 001 Device 006: ID 05ac:820a Apple, Inc.
Bus 002 Device 005: ID 05ac:1402 Apple, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0424:2513 Standard Microsystems Corp.
Bus 002 Device 004: ID 13fd:2040 Initio Corporation
Bus 002 Device 003: ID 05ac:8242 Apple, Inc. IR Receiver [built-in]
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[root@vh03 ~]# lsusb -tv
Bus# 4
`-Dev# 1 Vendor 0x1d6b Product 0x0001
Bus# 3
`-Dev# 1 Vendor 0x1d6b Product 0x0001
Bus# 2
`-Dev# 1 Vendor 0x1d6b Product 0x0002
`-Dev# 2 Vendor 0x0424 Product 0x2513
|-Dev# 3 Vendor 0x05ac Product 0x8242
|-Dev# 4 Vendor 0x13fd Product 0x2040
`-Dev# 5 Vendor 0x05ac Product 0x1402
Bus# 1
`-Dev# 1 Vendor 0x1d6b Product 0x0002
`-Dev# 2 Vendor 0x0424 Product 0x2513
|-Dev# 3 Vendor 0x0a5c Product 0x4500
| |-Dev# 6 Vendor 0x05ac Product 0x820a
| |-Dev# 7 Vendor 0x05ac Product 0x820b
| `-Dev# 8 Vendor 0x05ac Product 0x8281
|-Dev# 90 Vendor 0x045e Product 0x00cb
`-Dev# 5 Vendor 0x413c Product 0x2003
[root@vh03 ~]# cat /etc/udev/rules.d/60-net.rules
# Automatically generated file from
/etc/sysconfig/network-scripts/interface-rename.py
ACTION!="add" GOTO="network-done"
# Rules generated from static configuration and last boot data
SUBSYSTEM=="net" KERNEL=="eth*" SYSFS{address}=="3c:07:54:6a:3f:ed"
ID=="0000:02:00.0" NAME="eth0"
# Rename unrecognised devices sideways to deal with them later
SUBSYSTEM=="net" KERNEL=="eth*"
PROGRAM="/etc/udev/scripts/net-rename-sideways.sh %k" NAME="%c"
LABEL="network-done"
[root@vh03 ~]# udevinfo -a -p /sys/class/net/eth1
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/class/net/eth1':
KERNEL=="eth1"
SUBSYSTEM=="net"
SYSFS{addr_len}=="6"
SYSFS{dev_id}=="0x0"
SYSFS{ifalias}==""
SYSFS{iflink}=="3"
SYSFS{ifindex}=="3"
SYSFS{features}=="0x0"
SYSFS{type}=="1"
SYSFS{link_mode}=="0"
SYSFS{address}=="80:49:71:11:84:fc"
SYSFS{broadcast}=="ff:ff:ff:ff:ff:ff"
SYSFS{carrier}=="1"
SYSFS{dormant}=="0"
SYSFS{operstate}=="up"
SYSFS{mtu}=="1500"
SYSFS{flags}=="0x1103"
SYSFS{tx_queue_len}=="1000"
looking at parent device
'/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.3/2-1.3:1.0':
ID=="2-1.3:1.0"
BUS=="usb"
DRIVER=="asix"
SYSFS{bInterfaceNumber}=="00"
SYSFS{bAlternateSetting}==" 0"
SYSFS{bNumEndpoints}=="03"
SYSFS{bInterfaceClass}=="ff"
SYSFS{bInterfaceSubClass}=="ff"
SYSFS{bInterfaceProtocol}=="00"
SYSFS{modalias}=="usb:v05ACp1402d0001dcFFdscFFdp00icFFiscFFip00"
SYSFS{supports_autosuspend}=="1"
SYSFS{interface}=="0"
looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.3':
ID=="2-1.3"
BUS=="usb"
DRIVER=="usb"
SYSFS{dev}=="189:132"
SYSFS{configuration}=="0"
SYSFS{bNumInterfaces}==" 1"
SYSFS{bConfigurationValue}=="1"
SYSFS{bmAttributes}=="a0"
SYSFS{bMaxPower}=="250mA"
SYSFS{urbnum}=="43633450"
SYSFS{idVendor}=="05ac"
SYSFS{idProduct}=="1402"
SYSFS{bcdDevice}=="0001"
SYSFS{bDeviceClass}=="ff"
SYSFS{bDeviceSubClass}=="ff"
SYSFS{bDeviceProtocol}=="00"
SYSFS{bNumConfigurations}=="1"
SYSFS{bMaxPacketSize0}=="64"
SYSFS{speed}=="480"
SYSFS{busnum}=="2"
SYSFS{devnum}=="5"
SYSFS{version}==" 2.00"
SYSFS{maxchild}=="0"
SYSFS{quirks}=="0x0"
SYSFS{authorized}=="1"
SYSFS{manufacturer}=="Apple Inc. "
SYSFS{product}=="Apple USB Ethernet Adapter"
SYSFS{serial}=="20BAA4"
looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb2/2-1':
ID=="2-1"
BUS=="usb"
DRIVER=="usb"
SYSFS{dev}=="189:129"
SYSFS{configuration}==""
SYSFS{bNumInterfaces}==" 1"
SYSFS{bConfigurationValue}=="1"
SYSFS{bmAttributes}=="e0"
SYSFS{bMaxPower}==" 2mA"
SYSFS{urbnum}=="45"
SYSFS{idVendor}=="0424"
SYSFS{idProduct}=="2513"
SYSFS{bcdDevice}=="0bb3"
SYSFS{bDeviceClass}=="09"
SYSFS{bDeviceSubClass}=="00"
SYSFS{bDeviceProtocol}=="02"
SYSFS{bNumConfigurations}=="1"
SYSFS{bMaxPacketSize0}=="64"
SYSFS{speed}=="480"
SYSFS{busnum}=="2"
SYSFS{devnum}=="2"
SYSFS{version}==" 2.00"
SYSFS{maxchild}=="3"
SYSFS{quirks}=="0x0"
SYSFS{authorized}=="1"
looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb2':
ID=="usb2"
BUS=="usb"
DRIVER=="usb"
SYSFS{dev}=="189:128"
SYSFS{configuration}==""
SYSFS{bNumInterfaces}==" 1"
SYSFS{bConfigurationValue}=="1"
SYSFS{bmAttributes}=="e0"
SYSFS{bMaxPower}==" 0mA"
SYSFS{urbnum}=="36"
SYSFS{idVendor}=="1d6b"
SYSFS{idProduct}=="0002"
SYSFS{bcdDevice}=="0206"
SYSFS{bDeviceClass}=="09"
SYSFS{bDeviceSubClass}=="00"
SYSFS{bDeviceProtocol}=="00"
SYSFS{bNumConfigurations}=="1"
SYSFS{bMaxPacketSize0}=="64"
SYSFS{speed}=="480"
SYSFS{busnum}=="2"
SYSFS{devnum}=="1"
SYSFS{version}==" 2.00"
SYSFS{maxchild}=="8"
SYSFS{quirks}=="0x0"
SYSFS{authorized}=="1"
SYSFS{manufacturer}=="Linux 2.6.32.43-0.4.1.xs1.8.0.835.170778xen ehci_hcd"
SYSFS{product}=="EHCI Host Controller"
SYSFS{serial}=="0000:00:1d.7"
SYSFS{authorized_default}=="1"
looking at parent device '/devices/pci0000:00/0000:00:1d.7':
ID=="0000:00:1d.7"
BUS=="pci"
DRIVER=="ehci_hcd"
SYSFS{vendor}=="0x8086"
SYSFS{device}=="0x1c26"
SYSFS{subsystem_vendor}=="0x8086"
SYSFS{subsystem_device}=="0x7270"
SYSFS{class}=="0x0c0320"
SYSFS{irq}=="22"
SYSFS{local_cpus}=="ffffffff"
SYSFS{local_cpulist}=="0-31"
SYSFS{modalias}=="pci:v00008086d00001C26sv00008086sd00007270bc0Csc03i20"
SYSFS{enable}=="1"
SYSFS{broken_parity_status}=="0"
SYSFS{msi_bus}==""
SYSFS{companion}==""
looking at parent device '/devices/pci0000:00':
ID=="pci0000:00"
BUS==""
DRIVER==""
SYSFS{uevent}==""
interface-rename.log
Description: Binary data
_______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
