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] [PATCH] fix stubdom memory corruption

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] fix stubdom memory corruption
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Wed, 15 Apr 2009 06:59:47 -0700 (PDT)
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 15 Apr 2009 07:00:22 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1239803987; bh=0ZH6/XPuOvdSMY/l27fsA+CFkzKEM3/B+2qFtc1ig/Q=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=IeDkuNJQUGP4ef+xYblTFyV9Q9XNzsdqyx3QjYiOM6KISlTHyLL/XsIvivfrO8ey8QiXxkXcW305nw38cT4AE9NUJ9j8uvI+EIKgjx74Vd4+ci71a9zixtorfGhIx3cgOXunW+y6VtXSpUbijBpk+3Xk7aQLhIZ0E4LSfE/l/j0=
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:Cc:In-Reply-To:MIME-Version:Content-Type; b=uZVkTHjxoVf5B5xj65JpddfXKL0u20kZaBa6ZGRmbyZ/eIkom6qiZUwbRFsG9aCrAvX3Lysc3cdTxpFRi+rdY92nx2aTojhN9jO+AQcMXtcA/Ncp5Zb2aofSm7iSYGa6a9+2KIj0TFMve73s3OgX8icVP2s71ym536RlPCuVUpM=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49E5E2FF.3060401@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
>if this is the only error you get, it seems to be unrelated to stubdoms.
Yes

>Could you please try to start a stubdom without autoconnect (no -c)?

Sorry , what means "-c" ?
After fs-backend start i run in different terminal session :-

xm create RHELhvm-stubdom
vncviewer localhost:0

Maybe i follow outdated instructions.
Files RHELhvm-stubdom, RHELhvm-dm are located under /etc/xen

[root@ServerXen 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

[root@ServerXen 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']

Boris.

--- On Wed, 4/15/09, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> wrote:
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] fix stubdom memory corruption
To: "bderzhavets@xxxxxxxxx" <bderzhavets@xxxxxxxxx>
Cc: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Wednesday, April 15, 2009, 9:37 AM

Boris Derzhavets wrote:

> root@ServerXen331:/etc/xen# xm list
> Name ID Mem VCPUs State
> Time(s)
> Domain-0 0 7019 2 r-----
702.0
> RHELhvm 7 1024 1 ------
0.0
>
> ************************
> Three logs generated
> ************************
>
> root@ServerXen331:/var/log/xen# cat qemu-dm-RHELhvm-dm.log
> domid: 9
> Warning: vlan 0 is not connected to host network
> Watching /local/domain/0/device-model/9/logdirty/next-active
> Watching /local/domain/0/device-model/9/command
> char device redirected to /dev/pts/3
> /usr/src/xen-unstable.hg/tools/ioemu-dir/hw/xen_blktap.c:628: Init
> blktap pipes
> xs_read(): vncpasswd get error.
> /vm/3f8762a5-b806-dca4-6442-0dfeb7da0917/vncpasswd.
> medium change watch on `hdc' (index: 0): /dev/loop0
> root@ServerXen331:/var/log/xen# cat qemu-dm-RHELhvm-dm.log.1
> domid: 8
> Warning: vlan 0 is not connected to host network
> Watching /local/domain/0/device-model/8/logdirty/next-active
> Watching /local/domain/0/device-model/8/command
> char device redirected to /dev/pts/3
> /usr/src/xen-unstable.hg/tools/ioemu-dir/hw/xen_blktap.c:628: Init
> blktap pipes
> xs_read(): vncpasswd get error.
> /vm/3f8762a5-b806-dca4-6442-0dfeb7da0917/vncpasswd.
> medium change watch on `hdc' (index: 0): /dev/loop0
> root@ServerXen331:/var/log/xen# cat qemu-dm-RHELhvm.log
> Using config file "/etc/xen/RHELhvm-dm".
> Started domain RHELhvm-dm (id=8)
> Using config file "/etc/xen/RHELhvm-dm".
> Unexpected error: <type 'exceptions.OSError'>
>
> Please report to xen-devel@xxxxxxxxxxxxxxxxxxx
> Traceback (most recent call last):
> File "/usr/sbin/xm", line 7, in <module>
> main.main(sys.argv)
> File "usr/lib/python2.5/site-packages/xen/xm/main.py", line
2980, in main
> _, rc = _run_cmd(cmd, cmd_name, args)
> File "usr/lib/python2.5/site-packages/xen/xm/main.py", line
3004, in
> _run_cmd
> return True, cmd(args)
> File "<string>", line 1, in <lambda>
> File "usr/lib/python2.5/site-packages/xen/xm/main.py", line
1360, in
> xm_importcommand
> cmd.main([command] + args)
> File "usr/lib/python2.5/site-packages/xen/xm/create.py", line
1370, in
> main
> do_console(sxp.child_value(config, 'name', -1))
> File "usr/lib/python2.5/site-packages/xen/xm/create.py", line
1397, in
> do_console
> (p, rv) = os.waitpid(cpid, os.WNOHANG)
> OSError: [Errno 10] No child processes

If this is the only error you get, it seems to be unrelated to stubdoms.
Could you please try to start a stubdom without autoconnect (no -c)?


_______________________________________________
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