From: Fabio Fantoni <fantonifabio@tiscali.it>
To: fantonifabio@tiscali.it
Cc: Anthony Perard <anthony.perard@citrix.com>,
xen-devel <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Ross Philipson <Ross.Philipson@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: Update Seabios on xen-unstable
Date: Thu, 24 Jan 2013 15:27:21 +0100 [thread overview]
Message-ID: <510144C9.3080802@tiscali.it> (raw)
In-Reply-To: <51000066.50404@tiscali.it>
[-- Attachment #1.1: Type: text/plain, Size: 2626 bytes --]
Il 23/01/2013 16:23, Fabio Fantoni ha scritto:
> Il 11/01/2013 15:32, Ian Campbell ha scritto:
>> On Fri, 2013-01-11 at 14:26 +0000, Fabio Fantoni wrote:
>>> I know that isn't optimal use firmware passtrought for vgabioses but
>>> I'm
>>> not sure that seabios actually loads (automatically) the vgabioses.
>> SeaBIOS *does* load the VGA BIOS. You can see it if you use SDL (or are
>> quick enough with the VNC).
>>
>> Ian.
>>
>>
>>
>> -----
>> Nessun virus nel messaggio.
>> Controllato da AVG -www.avg.com
>> Versione: 2013.0.2890 / Database dei virus: 2637/6024 - Data di
>> rilascio: 10/01/2013
>>
>>
> I done other test with all spice seabios and qemu updated.
> Based on qxl patch v7 (
> http://lists.xen.org/archives/html/xen-devel/2013-01/msg01405.html )
> by default xen should assign 128 mb total of videoram and also set
> with -global to qemu the 2 qxl ram region correctly to 64 mb each.
>
> I actived also qxl debug and on log show this:
> /var/log/xen/qemu-dm-W7.log
> qxl-0: ram/pri: 32 MB [region 0]
> qxl-0: vram/32: 0 MB [region 1]
> qxl-0: vram/64: 0 MB [unmapped]
> ...
>
>
> Seem can use only 32 mb and only on one region instead of 64 mb on
> region 0 and 64 mb on region 1
> Added as attachment also with log of xl -vvv create
>
> Does anyone know what can cause this problem?
> Can be somethink in hvmloader that fixed videoram to one region 32 mb
> always?
>
> Thanks for any reply and sorry for my bad english.
>
Tried Wheezy hvm domU with xen, qemu crash and give this out of memory
error on qemu log:
id 0, group 0, virt start 0, virt end ffffffffffffffff, generation 0,
delta 0
id 1, group 1, virt start 7f3034a29000, virt end 7f3035a27000,
generation 0, delta 7f3034a29000
id 2, group 1, virt start 7f30337ff000, virt end 7f3033803000,
generation 0, delta 7f30337ff000
(/usr/sbin/xl:19287): Spice-CRITICAL **:
red_memslots.c:94:validate_virt: virtual address out of range
virt=0x7f3035a29398+0xbf slot_id=1 group_id=1
slot=0x7f3034a29000-0x7f3035a27000 delta=0x7f3034a29000
Same domU launching qemu only:
/usr/lib/xen/bin/qemu-system-i386 -name WHEEZY -k it -spice
port=6002,tls-port=0,addr=0.0.0.0,disable-ticketing,agent-mouse=on
-device qxl-vga -global qxl-vga.vram_size=16384 -global
qxl-vga.ram_size=16384 -boot order=dc -smp 2,maxcpus=2 --global
qxl-vga.debug=1 -global qxl-vga.guestdebug=20 -m 2016 -drive
file=/mnt/vm/disks/WHEEZY.disk1.xm,if=ide,index=0,media=disk,format=raw,cache=writeback
No qemu crash and no memory error, this is probably the confirm some xen
memory bug with hvm.
[-- 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
next prev parent reply other threads:[~2013-01-24 14:27 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
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 [this message]
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=510144C9.3080802@tiscali.it \
--to=fantonifabio@tiscali.it \
--cc=Ian.Campbell@citrix.com \
--cc=Ross.Philipson@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.