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] First release candidate for Xen 3.4.0

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] First release candidate for Xen 3.4.0
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Fri, 10 Apr 2009 06:46:55 -0700 (PDT)
Cc:
Delivery-date: Fri, 10 Apr 2009 06:47:30 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1239371215; bh=enIzV0hlO51wd6QR9xkIsMajQeiLMZaK/FgCZNr1E18=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=riEVrEwPkNi+2EjzCxgwlUXbrA2+6WsbUATVJ2H68+sDYdzoUbI3YfgUXihFHiMDIfkrn4moRyKFuqgF/JsPjOfibsHggjXLq+xykOsLr547rYc27ksXvtzGcuixiniD6+7C28aLlaOycaOrReANwtWYrcNFVcjpNkCXa2a0sks=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=4S+EdhRO8aMPTGHgOybylwh0uWgPJmqgXGld/xX9OO2RhpVArAXq+Ox1TkUfyvoCi0xRwP1+FAsmbbx/QxdHlmKaDEBELaZlyZ/ZyTcB5arw58QyvotZmjT2pvmJmNXIqF6NL0aH1kSGquE1AXiz/hOIpZ6H0+vucQpKjV1gylg=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C6050192.872E%keir.fraser@xxxxxxxxxxxxx>
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>
Reply-to: bderzhavets@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Current environment:-

root@Server1:/etc/xen# xm info
host                   : Server1
release                : 2.6.27.5
version                : #2 SMP Sat Feb 14 13:48:51 EST 2009
machine                : x86_64
nr_cpus                : 2
nr_nodes               : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 3005
hw_caps                : bfebfbff:20100800:00000000:00000140:0008e3fd:00000000:00000001:00000000
virt_caps              : hvm
total_memory           : 8191
free_memory            : 1071
node_to_cpu            : node0:0-1
node_to_memory         : node0:1071
xen_major              : 3
xen_minor              : 4
xen_extra              : .0-rc2-pre
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Fri Apr 10 06:58:04 2009 +0100 19534:120d3c67951b
cc_compiler            : gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu12)
cc_compile_by          : root
cc_compile_domain      :
cc_compile_date        : Fri Apr 10 08:07:06 EDT 2009
xend_config_format     : 4

Start
# /usr/sbin/fs-backend &

Have two files under /etc/xen for RHEL stub domain
Fisrt:-

root@Server1:/etc/xen# cat RHELhvm-stubdom
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory =1024
name = "RHELhvm"
vif = [ 'type=ioemu, bridge=eth0' ]
device_model = "/usr/lib/xen/bin/stubdom-dm"
boot="d"
sdl=0
opengl=0
vnc=0
stdvga=0

Second:-

root@Server1:/etc/xen# cat RHELhvm-dm
kernel = "/usr/lib/xen/boot/ioemu-stubdom.gz"
vif = [ ' ', 'bridge=eth0']
# vfb = [ 'type=sdl' ]
vfb = [ 'type=vnc' ]
disk = ['phy:/dev/loop0,hdc:cdrom,r','phy:/dev/sdb8,hda,w']

root@Server1:/etc/xen# losetup -a
/dev/loop0: [081e]:2510141 (/home/boris/isos/rhel.iso)

root@Server1:/etc/xen# xm create RHELhvm-stubdom
Using config file "./RHELhvm-stubdom".
Started domain RHELhvm (id=4)

root@Server1:/etc/xen# xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  7019     2            r-----    278.0
RHELhvm                                    4  1024     1            ------      0.0

root@Server1:/etc/xen# netstat -a|grep 590
tcp        0      0 *:5901                  *:*                     LISTEN    

Nothing at 5900
Stub Domain fails to start .

Boris.


--- On Fri, 4/10/09, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] First release candidate for Xen 3.4.0
To: "bderzhavets@xxxxxxxxx" <bderzhavets@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Friday, April 10, 2009, 9:00 AM

What situation do you mean? HVM guest running with stubdom while dom0 is
running 2.6.27.5 kernel? I wouldn¹t expect dom0 kernel version to much
affect stubdom, since stubdom actually should make the qemu bits much less
dependent on dom0.

-- Keir

On 10/04/2009 13:20, "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
wrote:

> Do you expect stubdom in the most recent Xen Unstable ( changeset 19534)
> to work with xen-ified kernel different from 2.6.18-xen ?
> I've got same negative results for Suse's 2.6.27.5 kernel as a
month before.
> Boris
>
> --- On Fri, 4/10/09, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
>> From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
>> Subject: [Xen-devel] First release candidate for Xen 3.4.0
>> To: "xen-devel@xxxxxxxxxxxxxxxxxxx"
<xen-devel@xxxxxxxxxxxxxxxxxxx>
>> Date: Friday, April 10, 2009, 2:25 AM
>>
>> Folks,
>>
>> The first release candidate for Xen 3.4.0 is available at
>> http://xenbits.xensource.com/xen-unstable.hg, tagged as
'3.4.0-rc1'.
>>
>> Please test!
>>
>> --
>> Keir
>>
>>
>>
>> _______________________________________________
>> 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