[Pkg-xen-devel] Bug#519149: Bug#519149: Logs

[William Pitcock]

Hi,

On Wed, 2009-03-11 at 07:57 +0000, Ian Campbell wrote:
> (adding William to CC which I missed before)
> On Tue, 2009-03-10 at 22:14 +0000, Ian Campbell wrote:
> > Hi William,
> > 
> > Please could you provide some more details of the failure since this
> > functionality works for me both with the Debian packages and upstream
> > and I don't recall any additional patches upstream.
> > 
> > Are there any messages in the logs? Particularly /var/log/xen/xend*
> > and /var/log/xen/domain-builder-ng.log.
> > 
> > Which kernel are you trying to load? The standard Lenny -686-bigmem
> > kernel packages work for me, so do various self built bzImages.
> 
> Oh, hang, on, you aren't trying to load a bzImage dom0 kernel are you?

Yes, I am. But, we need to make sure that squeeze ships with support for
this. So I think we should keep this open, but maybe with downgraded
severity. Considering paravirt-ops dom0 support is basically a release
goal, though...

> The bzImage support mentioned in that changelog entry is for domU
> kernels only (yes, it could be clearer).

I figured as such, but figured I would give it a try anyway. The
paravirt-ops work is getting to a point where real-world testing is
desirable.

> 
> Support for dom0 bzImage is present in xen-unstable.hg and will
> therefore be in 3.4 which is in plenty of time for squeeze.

Yes, I'm running xen-unstable.hg at present. An updated package for this
would be nice, but right now I am tracking tip, so it would be worthless
for me at present.

I might look into preparing an updated package for xen-unstable.hg.

I suppose I could feed the hypervisor the raw vmlinux binary on a
production-like machine in the meantime. That should work. At least,
that's what we do for non-pvops kernels.

William