xen-devel
Re: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- no newiss
It's weird that we have not reproduced the issue here. I always use VNC to a
remote host, and I see no colour issues with a newly-installed WinXP SP2
guest. Is this difference in observed behaviour explainable?
-- Keir
On 28/3/08 10:01, "Xu, Dongxiao" <dongxiao.xu@xxxxxxxxx> wrote:
> Hi, Samuel,
> Recently, I look into the bug 1180: Hvm windows guest shows abnormal
> color. I find that, if we use X window to boot a windows guest, the color is
> correct; and if we use vnc viewer to connect to the host and boot a windows
> guest, the color is abnormal. This issue comes from Xen C/S 17171.
>
> BTW, I set sdl=1 and vnc=0 in my configuration file. If set sdl=0 and vnc=1 in
> configuration file, both color from vnc viewer or X window are correct.
>
> Best regards,
> -- Dongxiao
>
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Samuel Thibault
> Sent: 2008年3月24日 18:15
> To: Li, Haicheng
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- no
> newissue
>
> Li, Haicheng, le Mon 24 Mar 2008 17:46:29 +0800, a écrit :
>> 2. Hvm windows guest shows abnormal color.
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1180
>
> Oh, it is really still present? I can't reproduce it any more
>
>> 5. HVM domain performance would downgrade, after doing save/restore.
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1143
>
> That also should have been fixed
>
> Thanks for testing!
> Samuel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- no new issue, Li, Haicheng
- Re: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- no new issue, Samuel Thibault
- RE: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- no newissue, Li, Haicheng
- RE: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- no newissue, Xu, Dongxiao
- Re: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- no newissue,
Keir Fraser <=
- Re: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- no newissue, Stefano Stabellini
- RE: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- no newissue, Xu, Dongxiao
- Re: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- no newissue, Keir Fraser
- Re: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- no newissue, Stefano Stabellini
- Re: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- no newissue, Keir Fraser
- RE: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- no newissue, Xu, Dongxiao
- Re: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- no newissue, Keir Fraser
Re: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- no new issue, Keir Fraser
|
|
|