All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralph Passgang <rp@trust-it.de>
To: xen-devel@lists.xensource.com
Subject: Re: (XEN) platform.c:994:d11 Unaligned ioport access:e15c2292, 4
Date: Mon, 12 Nov 2007 16:01:53 +0100	[thread overview]
Message-ID: <200711121601.53641.rp@trust-it.de> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01319FA2@trantor>

Am Montag, 12. November 2007 12:13:36 schrieb James Harper:
> Bah! My bad. I still had version a 3.0.4 of the hypervisor in /boot, and
> for some reason 'update-grub' thinks that 3.0.4 is a later version that
> 3.1.1 and put it first in menu.lst... Funny thing is, I think I actually
> submitted some updates to the Debian 'update-grub' xen-aware routines,
> so it probably really is my bad :)

Hi James,

I have the same problem with debian's "update-grub". Also on my system it 
orders my xen/kernel listing wrong. I don't think it's your mistake.

But as you said "2.6.18-5-xen...", this kernel is compiled against a xen 
3.0.3 patch, so it is maybe not what you want if you are using xen 3.1.x.

I patched my own kernel against a more recent xen 3.1.1 patch and this fixed 
some bugs for me. For example 32Bit-PV Guest on a 64Bit Kernel runs now 
like charm.

--Ralph

P.s.: I am very interessted in your PV Drivers, but I am not a windows 
developer at all. If your driver is available as binary for win xp or vista 
(32bit), I would really like to test it.

I tested the drivers from XenSource and Novell in the past (on a opensource 
xen hypervisor/kernel) and it never worked like expected. After installaing 
the novell driver my hvm-windows just stared directly into a bluescreen and 
with the xensource drivers there were actually some drivers installed, but 
the block-device didn't seem to work and my hvm guest always had 100% cpu 
utilisation after installing the driver (observerd with xm top), so these 
both drivers doesn't seem to work on an opensource xen installation.

> James
>
> > -----Original Message-----
> > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> > bounces@lists.xensource.com] On Behalf Of James Harper
> > Sent: Monday, 12 November 2007 22:03
> > To: xen-devel@lists.xensource.com
> > Subject: [Xen-devel] (XEN) platform.c:994:d11 Unaligned ioport
> > access:e15c2292, 4
> >
> > Suddenly my Windows PV drivers aren't working... I get this in 'xm
> > dmesg':
> >
> > "
> > (XEN) platform.c:994:d11 Unaligned ioport access: e15c2292, 4
> > (XEN) platform.c:994:d11 Unaligned ioport access: e15c1dbe, 4
> > (XEN) platform.c:994:d11 Unaligned ioport access: e15c1ffe, 4
> > (XEN) platform.c:1010:d11 Single io request in a movs crossing page
> > boundary.
> > (XEN) platform.c:994:d11 Unaligned ioport access: e15c2002, 4
> > (XEN) platform.c:994:d11 Unaligned ioport access: e15c18ea, 4
> > (XEN) platform.c:994:d11 Unaligned ioport access: e15c1416, 4
> > "
> >
> > I can't see anything that I've changed in the code I've written, but I
> > have upgraded to Debian kernel 2.6.18-5 on Dom0 from 2.6.18-4.
> >
> > Any suggestions? A few other strange things are happening too, like
>
> the
>
> > vnc port incrementing every time I start a new domain...
> >
> > I'll roll back the kernel and see what happens... but it just seems
> > strange!
> >
> > Thanks
> >
> > James
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

      reply	other threads:[~2007-11-12 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12 11:02 (XEN) platform.c:994:d11 Unaligned ioport access: e15c2292, 4 James Harper
2007-11-12 11:13 ` (XEN) platform.c:994:d11 Unaligned ioport access:e15c2292, 4 James Harper
2007-11-12 15:01   ` Ralph Passgang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200711121601.53641.rp@trust-it.de \
    --to=rp@trust-it.de \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.