Re: [Xen-users] xen-4.4.0 and (nic) assigned mac address errors

["squidmobile@xxxxxxxxxxx" <squidmobile@xxxxxxxxxxx>]

05 jul 2014

greetings,

> When that switch was made the scripts were modified to gate calls made
> via udev, see xen-hotplug-common.sh which should have near the top:
>   # Hack to prevent the execution of hotplug scripts from udev if the domain
>   # has been launched from libxl
>   if [ -n "${UDEV_CALL}" ] && \
>      xenstore-read "libxl/disable_udev" >/dev/null 2>&1; then
>       exit 0
>   fi

> Do your scripts have that? If you have an older version of the scripts
> installed then you might find that both udev and xl are running the
> script.

i checked my entire tree, and only two versions of
xen-hotplug-common.sh exist:  one for xen-4.3.1 and one for
xen-4.4.0.  they exist in separate trees and should NOT interfere
with each other.

the file contains the udev check.

a side-question for you:  why do you put the backslash at the end
of the if line.  my observations with ksh suggest the &&
automatically includes the next line.  is that a difference between
sh and ksh?  (i almost never use bash.)

> You should check that xen-backend.rules is up to date too. It should be
> setting UDEV_CALL = 1 when invoking the scripts.

many of the lines included this parameter:
  ENV{UDEV_CALL}="1"

for completeness, i unpacked the xen-4.4.0.tar.gz file and checked
these two files against those from the tar file.  they were
bytewise identical.

an interesting note for you:  the xen-4.3.1 and xen-4.4.0 versions
of xen-hotplug-common.sh and xen-backend.rules are identical.

i visually checked xen-backend.rules, and some things looked ...
interesting.
- KERNEL=="vif2-*", RUN+
  what is the difference between vif and vif2?  vif included the
  env parameter, but vif2 does NOT.  should vif2 include the env
  parameter?
- KERNEL=="vif*-emu",
  does the sequence of the parameters matter?  almost everywhere
  used the sequence ENV{UDEV_CALL}="1", ACTION, but vif*-emu
  used the sequence ACTION=="add", ENV


some ls data for your consideration:

lrwxrwxrwx 1 root root 53 2013-11-01 19:44
/etc/udev/rules.d/xen-backend.rules ->
/local/package/xen/etc/udev/rules.d/xen-backend.rules

lrwxrwxrwx 1 root root 28 2013-02-20 12:08 /etc/xen ->
../local/package/xen/etc/xen

lrwxrwxrwx 1 root root 9 2014-03-21 13:21 /local/package/xen ->
xen-4.4.0

-rw-r--r-- 1 root root 2901 2014-03-10 06:43
/local/package/xen-4.4.0/etc/xen/scripts/xen-hotplug-common.sh
-rw-r--r-- 1 root root 1303 2014-03-10 06:43
/local/package/xen-4.4.0/etc/udev/rules.d/xen-backend.rules

any ideas, suggestions, or comments?

thank you for your time and assistance.
frank smith

-- 
http://www.fastmail.fm - Same, same, but different...


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users