Dave Walker writes ("[Bug 803488] Re: [Oneiric] Load xen_blkback and xen_netback on startup"):
> I think I was confused on what the proposed Oneiric resolution was. I
> thought it was being suggested that adding the two modprobes to the init
> script would be a suitable resolution.
>
> Looking at the current archive package for modprobes it contains:
> ./debian/xen-utils-common.xend.init: modprobe xenfs 2>/dev/null
> ./debian/xen-utils-common.xend.init: modprobe xen-evtchn 2>/dev/null
>
> Therefore the requirement is to add xen_blkback & xen_netback (and drop
> it for P-Series).
Yes, that was my understanding. I'm confident that this will be a
safe fix. It will only affect people who have xen-utils-common
installed, of course, and those people are presumably intending to run
Xen and do need those modules loaded.
Dave Walker writes ("[Bug 803488] Re: [Oneiric] Load xen_blkback and xen_netback on startup"): xen-utils- common. xend.init: modprobe xenfs 2>/dev/null xen-utils- common. xend.init: modprobe xen-evtchn 2>/dev/null
> I think I was confused on what the proposed Oneiric resolution was. I
> thought it was being suggested that adding the two modprobes to the init
> script would be a suitable resolution.
>
> Looking at the current archive package for modprobes it contains:
> ./debian/
> ./debian/
>
> Therefore the requirement is to add xen_blkback & xen_netback (and drop
> it for P-Series).
Yes, that was my understanding. I'm confident that this will be a
safe fix. It will only affect people who have xen-utils-common
installed, of course, and those people are presumably intending to run
Xen and do need those modules loaded.
Ian.