From: "kevin.zhang@octlink.com" <kevin.zhang@octlink.com>
To: Fabio Fantoni <fabio.fantoni@m2r.biz>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: QXL problem: Xen 4.4.1 rc1 and xen 4.5 unstable
Date: Mon, 14 Jul 2014 13:29:52 +0800 [thread overview]
Message-ID: <2014071413295244395449@octlink.com> (raw)
In-Reply-To: 2014071410264327208736@octlink.com
[-- Attachment #1.1: Type: text/plain, Size: 5900 bytes --]
Hi Fabio Fantoni,
Today, I've done another test on xenbits xen 4.5 unstable.
This time, I directly compiled xen on my test server, and use default libspice-server-dev and libspice-protocol-dev header files for spice option.
root@debian:~# apt-cache policy libspice-server-dev libspice-protocol-dev
libspice-server-dev:
Installed: 0.11.0-1+deb7u1
Candidate: 0.11.0-1+deb7u1
Version table:
*** 0.11.0-1+deb7u1 0
500 http://cdn.debian.net/debian/ wheezy/main amd64 Packages
100 /var/lib/dpkg/status
libspice-protocol-dev:
Installed: 0.10.1-1
Candidate: 0.10.1-1
Version table:
*** 0.10.1-1 0
500 http://cdn.debian.net/debian/ wheezy/main amd64 Packages
100 /var/lib/dpkg/status
I also download qemu-2.0 source code from qemu.org, and compiled it by the way mentioned in http://wiki.xen.org/wiki/QEMU_Upstream.
Then I create win7 hvm with qemu-xen and /usr/local/bin/qemu-system-i386 respectively.
The result shows that:
1 . qemu-upstream used in xen 4.5 unstable still exited when changing screen resolution,
2. my self-compiled qemu2.0 behave normally.
I think maybe there's still some differences between the two qemu repository.
I'm actively waiting for your advice and willing to do the following debug.
vm config file is as follow:
name='Win7'
builder="hvm"
memory=2048
vcpus=2
vif=['bridge=br0']
disk=['/srv/vm_templates/1.qcow2,qcow2,hda,rw',',raw,hdb,ro,cdrom']
boot='dc'
device_model_version="qemu-xen"
#device_model_override="/usr/lib/xen/bin/qemu-gdb"
#device_model_override="/usr/local/bin/qemu-system-i386"
viridian=1
vnc=1
vnclisten="0.0.0.0"
on_crash="destroy"
vga="qxl"
spice=1
spicehost='0.0.0.0'
spiceport=6000
spicedisable_ticketing=1
spicevdagent=1
spice_clipboard_sharing=1
spiceusbredirection=4
soundhw="hda"
localtime=1
videoram=128
Best Regards
From: kevin.zhang@octlink.com
Date: 2014-07-14 10:26
To: Fabio Fantoni; xen-devel
Subject: Re: [Xen-devel] QXL problem: Xen 4.4.1 rc1 and xen 4.5 unstable
Hi Fabio Fantoni,
Thank you for your help.
If I use your method to run qemu-gdb when using xl create, xl will complain startup timeout.
Perhaps I did not describe my problem clearly enough, I can successfully create windows HVM, my problem happened when I change windows screen resolution.
The qemu process suddenly exited while xl list can still list the domU information.
I am using debian wheezy 7.5 amd 64, I am using fantu's xen 4.5 unstable and the qemu-xen-remote in his code repository,
root@debian:~# /usr/lib/xen/bin/qemu-system-i386 -version
QEMU emulator version 2.0.0, Copyright (c) 2003-2008 Fabrice Bellard
And I compiled Xen from fantu's xen repository in compilation server, then use install.sh in dist dir to install xen packages in my test server.
My compilation server has spice 0.12.4 compiled and installed.
My test server has debian wheezy backport qemu installed with spice-server:
dpkg -l |grep spice
ii libspice-server1:amd64 0.12.4-0nocelt2~bpo70+1
Then how can I obtain useful debug information after qemu exit with vm running?
Best Regards
From: Fabio Fantoni
Date: 2014-07-11 18:06
To: kevin.zhang@octlink.com; xen-devel
Subject: Re: [Xen-devel] QXL problem: Xen 4.4.1 rc1 and xen 4.5 unstable
Il 11/07/2014 04:38, kevin.zhang@octlink.com ha scritto:
Hi all,
Firstly please forgive me if I put this problem in the wrong mail list.
However, it seems that xen-users mail list cannot resolve this QXL problems. Therefore, I have to post QXL problem in devel mail list.
My problem is as follow:
I'm testing QXL for windows HVM, spice works well with stdvga.
However, when I switch to QXL, qemu exit abnormally:
I specify vga="qxl" and videoram=128, using qemu-xen. The windows 7 boots and automatially switch resolution for me in virt-viewer.
While display and sound transfering very well, if I change display resolution, the virt-viewer will be suddenly closed and
I check the physical server, the qemu process disappear simultaneously.
Then I switch to wheezy backport qemu 2.0 as device model, the qemu process will exit as soon as the welcome page appears and at the beginning of resolution change.
I tested and found the same bug on both xenbits xen 4.4.1 rc1 and Fantu's Xen 4.5 unstable, this problem exists in both branches.
Is it a known issue or is there any solution for this bug?
Thank you very much!
Thanks for testing spice and qxl and report issue.
I have spice + qxl working as kvm on xen unstable except this problem:
http://lists.xen.org/archives/html/xen-devel/2014-07/msg01021.html
Please post details on your dom0 installation and domU (for example xl cfg,
spice guest tools version ecc...)
About qemu crash try to take a full backtrace with gdb and post it here.
Small help with gdb of qemu launched by xl:
Add the line below in domU's xl cfg:
device_model_override="/usr/lib/xen/bin/qemu-gdb"
vi /usr/lib/xen/bin/qemu-gdb # create the file, change the qemu path if
needed
#!/bin/sh
exec gdbserver 0.0.0.0:1234 /usr/lib/xen/bin/qemu-system-i386 "$@"
# after xl create, do it fast (before timeout or xl create will fails)
target remote localhost:1234
c
bt full # when qemu stops
You should install also all needed dbg packages before, spice qemu ecc or
without package should be compiled with debug enabled (for xen and qemu
default in unstable).
The latest qemu crash with spice I saw was in 2.0-rc solved before 2.0.0
final, your qemu is at least 2.0.0 final?
http://git.qemu.org/?p=qemu.git;a=commit;h=dc491cfc14074064ed54a872b62cce6ca1330644
Kevin
Best Regards,
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 20853 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:[~2014-07-14 5:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 2:38 QXL problem: Xen 4.4.1 rc1 and xen 4.5 unstable kevin.zhang
2014-07-11 10:06 ` Fabio Fantoni
2014-07-14 2:26 ` kevin.zhang
2014-07-14 5:29 ` kevin.zhang [this message]
2014-07-14 7:59 ` Fabio Fantoni
2014-07-14 8:49 ` 回复: " kevin.zhang
2014-07-15 5:53 ` kevin.zhang
2014-07-15 8:09 ` Fabio Fantoni
2014-07-16 7:04 ` 回复: " kevin.zhang
2014-07-16 9:03 ` Fabio Fantoni
2014-07-17 1:48 ` kevin.zhang
2014-07-17 8:52 ` Fabio Fantoni
2014-07-18 2:01 ` kevin.zhang
2014-07-18 7:55 ` qemu crash on windows 7 resolution change on spice Fabio Fantoni
[not found] ` <53C8D2F7.1040705@m2r.biz>
2014-07-28 14:33 ` Fabio Fantoni
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=2014071413295244395449@octlink.com \
--to=kevin.zhang@octlink.com \
--cc=fabio.fantoni@m2r.biz \
--cc=xen-devel@lists.xen.org \
/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).