On Fri, 2012-02-17 at 10:06 +0000, Owen Dunn wrote: > On Wed, 15 Feb 2012, Owen Dunn wrote: > > > On Tue, 14 Feb 2012, Ian Campbell wrote: > > >>>> Also would it be possible to try the 4.1 hypervisor from Wheezy on this > >>>> machine? > >>> > >>> Probably... What packages do I need to install to do that? > >> > >> Just xen-hypervisor-4.1-amd64 since we don't really care about tools etc > >> at this stage. > >> > >> You could even just extract the xen.gz from that package and drop it > >> in /boot for the purposes of this test, if you want to avoid polluting > >> your Squeeze system with partial upgrades. > > > > I've done this and it seems to fix the problem (both with and without > > serial > > debugging enabled). I'll try a few times over the next day or two just in > > case the problem has only gone away temporarily... > > I've rebooted the system several times with the 4.1 hypervisor and it > seems to be working reliably. Is there anything you'd like me to do to > help pin down why this should be the case?
Unless you are interested in bisecting xen-unstable between 4.0 and 4.1 to find the cause (which I appreciate is a lot of work) so we can see if it is backportable then I'm not sure there is much else that can be done. > (Ideally I'd prefer not to have to have the wheezy xen packages on this > machine, but if they don't have too many dependency tentacles it's > workable with.) It'd be worth ago to see what it wants to pull in. Alternatives would be to rebuild the Wheezy packages on Squeeze or perhaps consider a backports.org upload. Ian. -- Ian Campbell In 1880 the French captured Detroit but gave it back ... they couldn't get parts. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org