All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre CABROL PERALES <alexandre.cabrol@artal.fr>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: HVM and WIndows NT
Date: Mon, 10 Aug 2009 10:17:18 +0200	[thread overview]
Message-ID: <4A7FD78E.9010907@artal.fr> (raw)
In-Reply-To: <4A7C9E55.6070807@artal.fr>

[-- Attachment #1: Type: text/plain, Size: 4210 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There is regression bug in QEMU on Cirrus Driver (-vga)
See mail attached from qemu mailing list.

I need CPUI configuration feature which is available only in xen 3.3 and
upper

but in need precedent version of ioemu-qemu-xen.

Can i build xen 3.3 with ioemu-qemu-xen of 3.2

To run Windows NT properly.

I tried to build and run xen-unstable but it fails.

moreover this is production use so i don't want to have unstable features.

Can you help me on this point please?

Alexandre CABROL PERALES a écrit :
> I continued to invistigate and found that in qemu:
> 
> Qemu version 0.10.3:
>   - Fix crash on resolution change -> screen dump -> vga redraw (Avi Kivity)
> 
> http://git.savannah.gnu.org/cgit/qemu.git/commit/?id=da95f49a9d0bc9597bd2c4ab5a7ee9bea7c4b01d
> 
> Fix crash on resolution change -> screen dump -> vga redraw (Avi Kivity)
> The vga screen dump function updates last_width and last_height, but
> does not change the DisplaySurface that these variables describe. A
> consequent vga_draw_graphic() will therefore fail to resize the surface
> and crash. Fix by invalidating the display state after a screen dump,
> forcing vga_draw_graphic() to reallocate the DisplaySurface.
> Signed-off-by: Avi Kivity
> diff --git a/hw/vga.c b/hw/vga.c
> index 2a9f4d9..709d6bb 100644
> --- a/hw/vga.c
> +++ b/hw/vga.c
> @@ -2678,4 +2678,5 @@ static void vga_screen_dump(void *opaque, const
> char *filename)
> vga_screen_dump_graphic(s, filename);
> else
> vga_screen_dump_text(s, filename);
> + vga_invalidate_display(s);
> }
> 
> I compared with xen-3.4 stable vga.c file
> xen-3.4.0/tools/ioemu-qemu-xen/hw/vga.c
> 
> And saw lot of differences.
> 
> Which version of qemu has been used to create xen 3.4.0 tools ?
> 
> Alexandre CABROL PERALES a écrit :
>> just made test with qemu and cirrus 0.9.1 and it works well with resolution.
> 
>> My question now is :
>> how can i use ioemu-qemu-0.9.1 in xen 3.4
> 
>> where can i get the corresponding version of ioemu-qemu?
> 
>> Alexandre CABROL PERALES a écrit :
>>> Can you send me an example please? about the bash sctip call in vm
>>> config file.
>>> Stefano Stabellini a écrit :
>>>> On Fri, 7 Aug 2009, Alexandre CABROL PERALES wrote:
>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>> Hash: SHA1
>>>>>
>>>>> I made the test with latest version of Qemu,
>>>>> and windows nt crash too on screen resol resize.
>>>>>
>>>>> I'm currently testing vmware graphic driver included in new qemu version.
>>>>>
>>>>> Is there anyway to use Bosch or Vmware driver in Xen ?
>>>>>
>>>> If you change your VM config file to call a bash script instead of
>>>> qemu-dm directly, then in your bash script you call qemu-dm yourself,
>>>> adding:
>>>> "-vga vmware" 
>>>> to the command line parameters, it may work.
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> http://lists.xensource.com/xen-devel
>>>> .
> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
>> .
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> .
> 
> 

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

.


- --
Alexandre CABROL PERALES
- --
Ingenieur Securite des Systemes d'Information
Mob. :    06.98.82.03.06
Mail :    alexandre.cabrol@artal.fr
Key fingerprint = 1E6B B8DF 5001 A6A8 E057  9D31 7B3B EAB1 4AE4 8953
- --
ARTAL Technologies

Rue Pierre-Gilles de Gennes
Ens."La Rue", Bat. 9, BP 38138
31681 Labege cedex

Tel. :    05.61.00.39.30
Fax :     05.61.00.20.43


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkp/144ACgkQezvqsUrkiVOc5ACgnJGhS7PRnT+xSKi+8kHFQyar
odIAnj0k58yJtbUc3pL4Y4XR+1ftINRs
=JzCm
-----END PGP SIGNATURE-----

[-- Attachment #2: Message joint --]
[-- Type: message/rfc822, Size: 4679 bytes --]

From: Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
To: Alexandre CABROL PERALES <alexandre.cabrol@artal.fr>, qemu-devel@nongnu.org
Cc: 
Subject: Re: [Qemu-devel] Video Card VMWare driver Windows NT
Date: Sat, 08 Aug 2009 12:14:52 +0100
Message-ID: <4A7D5E2C.5020608@siriusit.co.uk>

Alexandre CABROL PERALES wrote:

> i tried latest version of qemu with -vga and it crash on display
> resolution switch (eg. switch from 640x480 256bits to 1280x1024 65536bits)
> 
> i tried on 0.9.1 and it works well.
> 
> so maybe there is a bug.

I'm currently running an NT4 on kvm-86 for testing various bits and 
pieces, and that works fine for me - maybe it's a regression between 
kvm/qemu-kvm?

I was unable to get the standard NT4 VGA driver to work in anything 
other than 16 colours, however I did finally have success with the 
ReactOS driver VBEMP which can be found here: 
http://www.geocities.com/bearwindows/vbemp.htm


HTH,

Mark.

-- 
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063


.


[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

  reply	other threads:[~2009-08-10  8:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06  9:57 HVM and WIndows NT Alexandre CABROL PERALES
2009-08-06 10:34 ` mats petersson
2009-08-06 15:14   ` Alexandre CABROL PERALES
2009-08-06 15:46     ` Keir Fraser
2009-08-06 15:50     ` Alexandre CABROL PERALES
2009-08-06 16:15       ` Keir Fraser
2009-08-06 16:23         ` Alexandre CABROL PERALES
2009-08-06 16:47           ` Keir Fraser
2009-08-06 17:06             ` Alexandre CABROL PERALES
2009-08-07  9:30               ` Alexandre CABROL PERALES
2009-08-07 10:38               ` Stefano Stabellini
2009-08-06 16:56       ` Alexandre CABROL PERALES
2009-08-07 11:27         ` Stefano Stabellini
2009-08-07 12:26           ` Alexandre CABROL PERALES
2009-08-07  9:56   ` Cui, Dexuan
2009-08-07  9:48 ` Cui, Dexuan
2009-08-07 10:12   ` Alexandre CABROL PERALES
2009-08-07 10:15   ` Alexandre CABROL PERALES
2009-08-07 16:18     ` Alexandre CABROL PERALES
2009-08-07 16:26       ` Stefano Stabellini
2009-08-07 17:27         ` Alexandre CABROL PERALES
2009-08-07 18:25           ` Alexandre CABROL PERALES
2009-08-07 21:36             ` Alexandre CABROL PERALES
2009-08-10  8:17               ` Alexandre CABROL PERALES [this message]
2009-08-10  9:05                 ` Stefano Stabellini
2009-08-10 18:59                   ` Alexandre CABROL PERALES
2009-08-10 19:51                     ` Alexandre CABROL PERALES
2009-08-10 21:03                       ` Keir Fraser
2009-08-11  6:20                         ` Alexandre CABROL PERALES

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=4A7FD78E.9010907@artal.fr \
    --to=alexandre.cabrol@artal.fr \
    --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.