All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Fantoni <fantonifabio@tiscali.it>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: anthony.perard@citrix.com,
	xen-devel <xen-devel@lists.xensource.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: Update Seabios on xen-unstable
Date: Wed, 02 Jan 2013 15:41:15 +0100	[thread overview]
Message-ID: <50E4470B.9000302@tiscali.it> (raw)
In-Reply-To: <1357128605.5668.3.camel@zakaz.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 2283 bytes --]

Il 02/01/2013 13:10, Ian Campbell ha scritto:
> On Thu, 2012-12-20 at 12:34 +0000, Fabio Fantoni wrote:
>> I saw good news about qemu-xen on xen-unstable updates to latest stable
>> version (1.3), I already start test it and report bugs found.
>> I saw no seabios updates for now on xen-unstable, there is 1.7.1
>> upstream version since few months that include all vgabios.
>> Is possible to update seabios on xen-unstable please?
>> I have tried it time ago for probably resolution of qxl vga problem
>> without result.
>> It probably needs some particular settings or modification for correct
>> integration in xen about vgabios that I not know of.
>> Thanks for any reply.
> This is on my todo list, however it is made a bit tricky because SeaBIOS
> is quite picky about the compiler which is used (specifically the newest
> SeaBIOS won't build on a Debian Stable system, which affects both me and
> the Xen.org test system)
>
> The solution will probably be to ship a binary and only rebuild when
> explicitly asked to. I haven't quite got round to it yet though.
>
> Ian.
Thanks for your reply.
Seabios 1.7.1 is now on Debian sid repository, I tested it with Wheezy 
and xen-unstable and it is working.


Qemu still crashes if qxl is active and used but I don't think it is a 
seabios problem.

I've been looking for the problem in xen but I didn't find a solution at 
the moment. I can tell that seabios is called by hvmloader that sets a 
few things like acpi and e820 mapping before calling it. Could it be 
that hvmloader does something that interferes with seabios, like 
imposing restrictions?

In practice if I activate qxl but I use it only as stdvga I don't 
experience any problem except low video performance, but if I use it 
fully qemu crashes when spice start using qxl features, logging this error:
(/usr/sbin/xl:4658): Spice-CRITICAL **: red_memslots.c:123:get_virt: 
slot_id 194 too big, addr=c2c2c2c2c2c2c2c2

The only other possibility that comes to mind is that not enough 
videoram is successifully set. I thought this problem was already solved 
some months ago with xen and qemu upstream patches. Could there be other 
problems preventing the assignment and use 128 mb of videoram?

Thanks for any reply.


[-- Attachment #1.2: Firma crittografica S/MIME --]
[-- Type: application/pkcs7-signature, Size: 4510 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-01-02 14:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-20 12:34 Update Seabios on xen-unstable Fabio Fantoni
2012-12-28 15:38 ` Fabio Fantoni
2013-01-02 12:10 ` Ian Campbell
2013-01-02 14:41   ` Fabio Fantoni [this message]
2013-01-04 11:58     ` Fabio Fantoni
2013-01-04 12:10       ` Ian Campbell
2013-01-11  9:29         ` Fabio Fantoni
2013-01-11  9:54           ` Ian Campbell
2013-01-11 12:37             ` Ross Philipson
2013-01-11 13:12               ` Ian Campbell
2013-01-11 14:26                 ` Fabio Fantoni
2013-01-11 14:32                   ` Ian Campbell
2013-01-11 15:35                     ` Fabio Fantoni
2013-01-23 15:23                     ` Fabio Fantoni
2013-01-24 14:27                       ` Fabio Fantoni
2013-01-11 14:35                   ` Mats Petersson

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=50E4470B.9000302@tiscali.it \
    --to=fantonifabio@tiscali.it \
    --cc=Ian.Campbell@citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --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.