From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-2022-JP?B?TWFydGlueCAtIBskQiU4JSchPCVgJTobKEI=?= Subject: Re: Upstreaming Debian patches for Xen Qemu DM Date: Mon, 29 Mar 2010 16:32:58 -0300 Message-ID: <6b7f6eb1003291232v20352de5pec0bb368a64b67b9@mail.gmail.com> References: <4BA88FFF.6060403@goirand.fr> <20100324230527.GA30472@wavehammer.waldi.eu.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0091436138==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Christian Motschke Cc: xen-devel@lists.xensource.com, Stefano Stabellini , Bastian Blank , Ian Jackson , Samuel Thibault , Thomas Goirand List-Id: xen-devel@lists.xenproject.org --===============0091436138== Content-Type: multipart/alternative; boundary=001636833958c71e820482f59527 --001636833958c71e820482f59527 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi! Someone knows if the Debian Squeeze will have the paravirt_ops dom0 based on 2.6.32.10 from Jeremy's tree, HVM normal domains and HVM stubdomains? Thanks! Thiago On 25 March 2010 07:09, Christian Motschke wrote: > Am 25.03.2010 um 00:05 schrieb Bastian Blank: > > > On Tue, Mar 23, 2010 at 05:55:11PM +0800, Thomas Goirand wrote: > >> --- a/xen-config-host.mak > >> +++ b/xen-config-host.mak > >> @@ -1,6 +1,6 @@ > >> QEMU_ROOT ?=3D . > >> -XEN_ROOT ?=3D $(QEMU_ROOT)/../xen-unstable.hg > >> -include $(XEN_ROOT)/tools/Rules.mk > >> +XEN_ROOT ?=3D /nonexistant > >> +include $(QEMU_ROOT)/Rules.mk > >> > >> ifdef CONFIG_STUBDOM > >> TARGET_DIRS=3Di386-stubdom > > > > This looks rather similar to my patch. Please explain why this would be > > applicable to upstream. > > > >> --- a/configure 2010-03-23 17:08:39.000000000 +0800 > >> +++ b/configure 2010-03-23 17:09:30.000000000 +0800 > >> @@ -1382,6 +1382,9 @@ > >> echo "#define CONFIG_VDE 1" >> $config_h > >> echo "VDE_LIBS=3D-lvdeplug" >> $config_mak > >> fi > >> +if ! test -z "$audio_card_list"; then > >> + echo "CONFIG_AUDIO=3Dyes" >> $config_mak > >> +fi > >> for card in $audio_card_list; do > >> def=3DCONFIG_`echo $card | tr '[:lower:]' '[:upper:]'` > >> echo "$def=3Dyes" >> $config_mak > > > > Audio for a server? > > I have some existing configurations of virtualized Windows XP machines th= at > are configured with sound hardware (yes, I know, that it is not needed). = And > I know a company, that has configured some of its VMs with a sound card t= oo > (maybe they don't even know it, that it is not neccessary). If we do not > want to break some existing setups, we should support sound hardware with > qemu-dm (the 3.2.1 lenny version had it too). 2nd, I used a screen record= ing > software, that only worked, when a sound card was installed. Maybe I shou= ld > use better software, but =85 ;-) > > > > >> --- a/xen-config-host.h 2010-01-06 14:18:11.000000000 +0800 > >> +++ b/xen-config-host.h 2010-01-06 14:25:11.000000000 +0800 > >> @@ -32,8 +32,8 @@ > >> extern int xen_pause_requested; > >> extern int vcpus; > >> > >> -#define DEFAULT_NETWORK_SCRIPT "/etc/xen/qemu-ifup" > >> -#define DEFAULT_NETWORK_DOWN_SCRIPT "/etc/xen/qemu-ifdown" > >> +#define DEFAULT_NETWORK_SCRIPT "/etc/xen/scripts/qemu-ifup" > >> +#define DEFAULT_NETWORK_DOWN_SCRIPT "/etc/xen/scripts/qemu-ifdown" > >> > >> #ifdef CONFIG_STUBDOM > >> #define bdrv_host_device bdrv_raw > > > > Debian specific. > > > >> --- qemu-img-xen.1.orig 2009-12-24 00:51:05.000000000 +0800 > >> +++ qemu-img-xen.1 2009-12-24 00:56:11.000000000 +0800 > >> @@ -123,17 +123,17 @@ > >> .rm #[ #] #H #V #F C > >> .\" > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >> .\" > >> -.IX Title "QEMU-IMG 1" > >> -.TH QEMU-IMG 1 "2009-12-24" " " " " > >> +.IX Title "qemu-img-xen 1" > >> +.TH qemu-img-xen 1 "2009-12-24" " " " " > > > > This tool is called qemu-img and included in qemu-utils. > > > > Bastian > > > > -- > > Those who hate and fight must stop themselves -- otherwise it is not > stopped. > > -- Spock, "Day of the Dove", stardate unknown > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > --001636833958c71e820482f59527 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi!

=A0Someone knows if the Debian Squeeze will have the= paravirt_ops dom0 based on 2.6.32.10 from Jeremy's tree, HVM normal do= mains and HVM stubdomains?

Thanks!
Thiag= o

On 25 March 2010 07:09, Christian Motschke <= span dir=3D"ltr"><christian@mot= schke.de> wrote:
Am 25.03.2010 um 00:05 schrieb Bastian Blank:

> On Tue, Mar 23, 2010 at 05:55:11PM +0800, Thomas Goirand wrote:
>> --- a/xen-config-host.mak
>> +++ b/xen-config-host.mak
>> @@ -1,6 +1,6 @@
>> QEMU_ROOT ?=3D .
>> -XEN_ROOT ?=3D $(QEMU_ROOT)/../xen-unstable.hg
>> -include $(XEN_ROOT)/tools/Rules.mk
>> +XEN_ROOT ?=3D /nonexistant
>> +include $(QEMU_ROOT)/Rules.mk
>>
>> ifdef CONFIG_STUBDOM
>> TARGET_DIRS=3Di386-stubdom
>
> This looks rather similar to my patch. Please explain why this would b= e
> applicable to upstream.
>
>> --- a/configure =A0 =A0 =A02010-03-23 17:08:39.000000000 +0800
>> +++ b/configure =A0 =A0 =A02010-03-23 17:09:30.000000000 +0800
>> @@ -1382,6 +1382,9 @@
>> =A0 echo "#define CONFIG_VDE 1" >> $config_h
>> =A0 echo "VDE_LIBS=3D-lvdeplug" >> $config_mak
>> fi
>> +if ! test -z "$audio_card_list"; then
>> + =A0echo "CONFIG_AUDIO=3Dyes" >> $config_mak
>> +fi
>> for card in $audio_card_list; do
>> =A0 =A0 def=3DCONFIG_`echo $card | tr '[:lower:]' '[:u= pper:]'`
>> =A0 =A0 echo "$def=3Dyes" >> $config_mak
>
> Audio for a server?

I have some existing configurations of virtualized Windows XP m= achines that are configured with sound hardware (yes, I know, that it is no= t needed). And I know a company, that has configured some of its VMs with a= sound card too (maybe they don't even know it, that it is not neccessa= ry). If we do not want to break some existing setups, we should support sou= nd hardware with qemu-dm (the 3.2.1 lenny version had it too). 2nd, I used = a screen recording software, that only worked, when a sound card was instal= led. Maybe I should use better software, but =85 ;-)

>
>> --- a/xen-config-host.h =A0 =A0 =A02010-01-06 14:18:11.000000000 += 0800
>> +++ b/xen-config-host.h =A0 =A0 =A02010-01-06 14:25:11.000000000 += 0800
>> @@ -32,8 +32,8 @@
>> extern int xen_pause_requested;
>> extern int vcpus;
>>
>> -#define DEFAULT_NETWORK_SCRIPT "/etc/xen/qemu-ifup"
>> -#define DEFAULT_NETWORK_DOWN_SCRIPT "/etc/xen/qemu-ifdown&qu= ot;
>> +#define DEFAULT_NETWORK_SCRIPT "/etc/xen/scripts/qemu-ifup&q= uot;
>> +#define DEFAULT_NETWORK_DOWN_SCRIPT "/etc/xen/scripts/qemu-i= fdown"
>>
>> #ifdef CONFIG_STUBDOM
>> #define bdrv_host_device bdrv_raw
>
> Debian specific.
>
>> --- qemu-img-xen.1.orig =A0 =A0 =A02009-12-24 00:51:05.000000000 += 0800
>> +++ qemu-img-xen.1 =A0 2009-12-24 00:56:11.000000000 +0800
>> @@ -123,17 +123,17 @@
>> .rm #[ #] #H #V #F C
>> .\" =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D
>> .\"
>> -.IX Title "QEMU-IMG 1"
>> -.TH QEMU-IMG 1 "2009-12-24" " " " "=
>> +.IX Title "qemu-img-xen 1"
>> +.TH qemu-img-xen 1 "2009-12-24" " " " &q= uot;
>
> This tool is called qemu-img and included in qemu-utils.
>
> Bastian
>
> --
> Those who hate and fight must stop themselves -- otherwise it is not s= topped.
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 -- Spock, "Day of the Dove", sta= rdate unknown


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

--001636833958c71e820482f59527-- --===============0091436138== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0091436138==--