From: Fantu <fantonifabio@tiscali.it>
To: xen-devel@lists.xensource.com
Subject: Re: [qemu-upstream-unstable test] 12634: regressions - FAIL
Date: Wed, 11 Apr 2012 00:52:19 -0700 (PDT) [thread overview]
Message-ID: <1334130739587-5632069.post@n5.nabble.com> (raw)
In-Reply-To: <osstest-12634-mainreport@xen.org>
I had tested with latest xen-unstable (changeset 25161:d690c7e896a2) and qemu
upstream unstable windows xp and windows 7 work with xl, the issue found
that there is still no solution are:
- qxl vga and/or videoram over 4 mb
- reboot the domU not working (after shutdown seem destroy it)
- graphic performance issue: with vnc and cirrus very high latency of
refresh, with stdvga usable but performance is not good, with spice and
stdvga not enough but better, with qxl limited by only 4 mb videoram usable
Save/restore not tested for now, probably I will try it today.
--
View this message in context: http://xen.1045712.n5.nabble.com/qemu-upstream-unstable-test-12634-regressions-FAIL-tp5631581p5632069.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
prev parent reply other threads:[~2012-04-11 7:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 1:37 [qemu-upstream-unstable test] 12634: regressions - FAIL xen.org
2012-04-11 7:52 ` Fantu [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=1334130739587-5632069.post@n5.nabble.com \
--to=fantonifabio@tiscali.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).