On Wed, 2010-03-24 at 12:47 +0100, Josip Rodin wrote:
> On Wed, Mar 24, 2010 at 11:09:45AM +0100, Bastian Blank wrote:
> > > > IIRC these kernels require a newer hypervisor than is in stable at the
> > > > moment, at a minimum you need 3.4.3, RC's are available in testing.
> >
> > > The new paravirt_ops Xen dom0 kernel packages should probably simply have
> > > a:
> > > Conflicts: xen-hypervisor-3.4-$ARCH (<< 3.4.3~rc3),
> > > xen-hypervisor-3.2-$ARCH, xen-hypervisor-3.0-$ARCH
> >
> > No. Kernels are co-installable.
>
> Oh, crap, I forgot, yes. Maybe postinst messages then? Since the alternative
> is usually an instant reboot loop, which will inevitably result in people
> complaining.
The kernel should probably catch the ENOSYS from the new
PHYSDEVOP_setup_gsi hypercall (which is what the hypervisor update is
required for) and panic with a more useful/specific error message. I'm
not sure if that would prevent a reboot loop though so perhaps that
wouldn't help much.
Ian.
--
Ian Campbell
Current Noise: Coffins - Deadly Sinners
The nice thing about standards is that there are so many of them to choose from.
-- Andrew S. Tanenbaum
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
