WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Upstreaming Debian patches for Xen Qemu DM

To: Christian Motschke <christian@xxxxxxxxxxx>
Subject: Re: [Xen-devel] Upstreaming Debian patches for Xen Qemu DM
From: Martinx - ジェームズ <thiagocmartinsc@xxxxxxxxx>
Date: Mon, 29 Mar 2010 16:32:58 -0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, Bastian Blank <waldi@xxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Samuel Thibault <sthibault@xxxxxxxxxx>, Thomas Goirand <thomas@xxxxxxxxxx>
Delivery-date: Mon, 29 Mar 2010 12:35:32 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:received:message-id:subject:to:cc:content-type; bh=vm6VUaX1HoTLeBXZLxg+O4LQ0JWzjrBgmq0iy6kUHAA=; b=dBne7TnNZvRPi79dRwtegEBNDhbr5pNYIvhrmvvq7pxOgSuiLjdIyDRvqS6JH6skxH GhMtYWXl9+iLLIjcw1tdRh5twgUNwiAexVo+Q+70s9vs67DEVpAZoTvod6sL2PV2hGYU 8I9XJqjfv2WarOKVHOfkCOrVTZJc0g3/92XqE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=A7dL9R0wsilgDmf9l2rzVg+nEDNblcCNUhKXXT5/Bl4ldPcDjVSxxADjR/AAcQ/8DZ DammcE1aitv7z0WuVOEhGUiFWPy6KEvjoJmic68WfiVWVoJ27VI2UQLY2eX3CJ2Cuj4c trDp9+HV0TEC/fPZ0PggDs2y0kBxvVFU3R0Qo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A056319B-237A-4411-B1A5-E93A5F7DA840@xxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4BA88FFF.6060403@xxxxxxxxxx> <20100324230527.GA30472@xxxxxxxxxxxxxxxxxxxxxxx> <A056319B-237A-4411-B1A5-E93A5F7DA840@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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 <christian@xxxxxxxxxxx> 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 ?= .
>> -XEN_ROOT ?= $(QEMU_ROOT)/../xen-unstable.hg
>> -include $(XEN_ROOT)/tools/Rules.mk
>> +XEN_ROOT ?= /nonexistant
>> +include $(QEMU_ROOT)/Rules.mk
>>
>> ifdef CONFIG_STUBDOM
>> TARGET_DIRS=i386-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=-lvdeplug" >> $config_mak
>> fi
>> +if ! test -z "$audio_card_list"; then
>> +  echo "CONFIG_AUDIO=yes" >> $config_mak
>> +fi
>> for card in $audio_card_list; do
>>     def=CONFIG_`echo $card | tr '[:lower:]' '[:upper:]'`
>>     echo "$def=yes" >> $config_mak
>
> Audio for a server?

I have some existing configurations of virtualized Windows XP machines that 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 too (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 recording software, that only worked, when a sound card was installed. Maybe I should use better software, but … ;-)

>
>> --- 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
>> .\" ========================================================================
>> .\"
>> -.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@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>