Hotplug scripts are not installed anymore this fubars basically everything. Specially this: cat /etc/udev/rules.d/xen-backend.rules SUBSYSTEM=="xen-backend", KERNEL=="tap*", RUN+="/etc/xen/scripts/blktap $env{ACTION}" SUBSYSTEM=="xen-backend", KERNEL=="vbd*", RUN+="/etc/xen/scripts/block $env{ACTION}" SUBSYSTEM=="xen-backend", KERNEL=="vtpm*", RUN+="/etc/xen/scripts/vtpm $env{ACTION}" SUBSYSTEM=="xen-backend", KERNEL=="vif*", ACTION=="online", RUN+="$env{script} online" SUBSYSTEM=="xen-backend", KERNEL=="vif*", ACTION=="offline", RUN+="$env{script} offline" SUBSYSTEM=="xen-backend", KERNEL=="vscsi*", RUN+="/etc/xen/scripts/vscsi $env{ACTION}" SUBSYSTEM=="xen-backend", ACTION=="remove", RUN+="/etc/xen/scripts/xen-hotplug-cleanup" KERNEL=="evtchn", NAME="xen/%k" KERNEL=="blktap[0-9]*", NAME="xen/%k" Reproducible: Always Steps to Reproduce:
Please attach the build.log from emerging xen-tools-3.3
If you tell me how to produce a build.log I'm happy to make it. The bug still exists + is annoying with new installations.
ping
(In reply to comment #3) > ping pong
Which file exactly is missing for you? I cannot reproduce the error here, both udev rules and the scripts are installed for me. Can you attach the output of "qlist xen-tools | grep /etc" ? (In reply to comment #2) > If you tell me how to produce a build.log I'm happy to make it. The bug still > exists + is annoying with new installations. Set PORT_LOGDIR=/var/log/portage in make.conf and then find the log in the directory.
(In reply to comment #5) > Which file exactly is missing for you? I cannot reproduce the error here, both > udev rules and the scripts are installed for me. > Can you attach the output of "qlist xen-tools | grep /etc" ? /etc/hotplug/xen-backend.agent /etc/xen/README /etc/xen/xmexample.pv-grub /etc/xen/auto/.keep_app-emulation_xen-tools-0 /etc/xen/xm-config.xml /etc/xen/xmexample.vti /etc/xen/xmexample3 /etc/xen/scripts/xen-network-common.sh /etc/xen/scripts/xen-hotplug-cleanup /etc/xen/scripts/vtpm-hotplug-common.sh /etc/xen/scripts/vscsi /etc/xen/scripts/vtpm-delete /etc/xen/scripts/network-bridge /etc/xen/scripts/blktap /etc/xen/scripts/logging.sh /etc/xen/scripts/network-route /etc/xen/scripts/vif-route /etc/xen/scripts/locking.sh /etc/xen/scripts/network-nat /etc/xen/scripts/external-device-migrate /etc/xen/scripts/vtpm /etc/xen/scripts/xen-hotplug-common.sh /etc/xen/scripts/block /etc/xen/scripts/vtpm-migration.sh /etc/xen/scripts/block-enbd /etc/xen/scripts/block-common.sh /etc/xen/scripts/vif-common.sh /etc/xen/scripts/block-nbd /etc/xen/scripts/vtpm-impl /etc/xen/scripts/vtpm-common.sh /etc/xen/scripts/vif-bridge /etc/xen/scripts/vif-nat /etc/xen/scripts/xen-script-common.sh /etc/xen/qemu-ifup /etc/xen/xend-config.sxp /etc/xen/xend-pci-quirks.sxp /etc/xen/xmexample.hvm-dm /etc/xen/xmexample2 /etc/xen/xmexample1 /etc/xen/README.incompatibilities /etc/xen/xmexample.nbd /etc/xen/xmexample.hvm-stubdom /etc/xen/xend-pci-permissive.sxp /etc/xen/xmexample.hvm /etc/conf.d/xendomains /etc/init.d/xend /etc/init.d/xendomains Clearly /etc/udev/rules.d/xen-backend.rules is needed to not fubar Xen.
Please attach a build log and the USE flags you used, because I am not able to reproduce.
Created attachment 168182 [details] part 1 app-emulation/xen-tools-3.3.0 USE="api debug hvm -acm -custom-cflags -doc -flask -pygrub -screen"
Created attachment 168184 [details] part 2
I could confirm this bug within a clean fresh gentoo installation on x86_64 multilib arch.
I confirm this bug on x86_64 ~amd64 fresh Gentoo install. I have copied the xen-backend.rules from the xen package to /etc/udev/rules.d/92-xen-backend.rules and problem solved!
This problem emerges when you use ~amd64. ~amd64 keyword pulls out udev-135 which doesn't have /usr/bin/udevinfo symlink (says use udevadm instead when creating that symlink). xen-3.3.0/tools/examples/Makefile checks for udev version using udevinfo, which doesn't exist. So it installs only hotplug scripts ommiting udev rules. I've created a patch for xen-tools which replaces udevinfo with udevadm, tested with fresh install. If you don't want to mess with custom ebuilds - use amd64 keyword for udev (I didn't test it). It could be the same problem for ~x86.
Created attachment 177112 [details, diff] Fix for udevinfo
Created attachment 177114 [details] Ebuild using new patch
fixed in funtoo http://github.com/funtoo/portage/commit/09f19aa6e13f7d8fa4bac8ea4dc84a78ad7e1d1e
*sigh* ... @patrick: wanna look at this one? ;)
(In reply to comment #16) > *sigh* ... @patrick: wanna look at this one? ;) > Yeah, uhm, not really ;) But I do notice that both the patch and the patched ebuild have random junk characters in them. Will have to see (a) if it's still an issue with 3.4 and (b) how to patch it sanely :)
Ok, looks like everything got shifted around in 3.4 so it is now tools/hotplug/Linux/Makefile as far as I can tell. But the rules in that dir also look very different from what existed in 3.3, so I have no idea yet what to do with it.
The patch from https://bugs.gentoo.org/show_bug.cgi?id=271173#c7 does the job,so: 22 Jun 2009; Patrick Lauer <patrick@gentoo.org> +xen-tools-3.4.0-r1.ebuild, +files/xen-tools-3.4.0-udevinfo.patch: Udev rules fix, closes #236819. Thanks to Frank Ridderbusch for the shiny patch Hope that makes y'all very happy :)
