On Sat, 2012-04-28 at 02:12 -0500, Jonathan Nieder wrote:
> Bastian Blank wrote:
> > On Wed, Mar 24, 2010 at 12:15:40PM +, Ian Campbell wrote:
>
> >> The kernel should probably catch the ENOSYS from the new
> >> PHYSDEVOP_setup_gsi hypercall (which is what the hypervisor update is
> >> require
Bastian Blank wrote:
> On Wed, Mar 24, 2010 at 12:15:40PM +, Ian Campbell wrote:
>> 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
On Wed, Mar 24, 2010 at 12:15:40PM +, Ian Campbell wrote:
> 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
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 paravi
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:
>
On Wed, Mar 24, 2010 at 10:44:20AM +0100, Josip Rodin wrote:
> Ian Campbell 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.
> William, did you try the hypervisor upgrade, does it work then?
Al
Ian Campbell 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.
I'd just like to confirm this, I distinctly recall seeing the mention of
the exact Mercurial changeset on the xen-devel list for a new
On Tue, 2010-03-23 at 19:42 -0700, William Pitcock wrote:
> Package: linux-image-2.6.32-4-xen-amd64
> Version: 2.6.32-10
> Severity: grave
> Justification: renders package unusable
>
> Hello,
>
> The new 2.6.32 kernel packages fail to boot, resulting in a 100% CPU busy
> loop and blank
> screen
On Tue, 2010-03-23 at 19:42 -0700, William Pitcock wrote:
> Package: linux-image-2.6.32-4-xen-amd64
> Version: 2.6.32-10
> Severity: grave
> Justification: renders package unusable
>
> Hello,
>
> The new 2.6.32 kernel packages fail to boot, resulting in a 100% CPU busy
> loop and blank
> screen
Package: linux-image-2.6.32-4-xen-amd64
Version: 2.6.32-10
Severity: grave
Justification: renders package unusable
Hello,
The new 2.6.32 kernel packages fail to boot, resulting in a 100% CPU busy loop
and blank
screen at startup, when Xen relinquishes the VGA console.
Standard Xen troubleshooti
10 matches
Mail list logo
