Public bug reported: I upgraded a machine from Xen 3.1 to Xen 3.2. The upgrade went relatively well until I attempted to remove xen-utils-3.1. There were 2 problems I encountered (not sure if they should be filed as separate bugs):
1. The first problem was that xen-utils-3.1 refused to be removed because the /etc/init.d/xend and /etc/init.d/xendomains were still present. I ended up having to move both of these files out of the way to complete the removal. I suspect this might be helped is xen- utils-3.1 conflicted with xen-utils-3.2 and vice-versa. 2. As documented elsewhere (https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/199533/comments/42), the removal of xen-utils-3.1 removes the symlink for /etc/udev/rules.d /z60_xen-backend.rules to ../xen-backend.rules. Without this link the following errors will be reported: * Error: Device 0 (vif) could not be connected. Hotplug scripts not working. * Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. Though the device numbers may be different. ** Affects: xen-3.1 (Ubuntu) Importance: Undecided Status: New ** Affects: xen-3.2 (Ubuntu) Importance: Undecided Status: New ** Also affects: xen-3.1 (Ubuntu) Importance: Undecided Status: New -- Removing xen-utils-3.1 after an upgrade to xen-utils-3.2 causes problems https://bugs.launchpad.net/bugs/236262 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
