From: Boris Derzhavets Subject: Re: [PATCH] fix stubdom memory corruption Date: Wed, 15 Apr 2009 06:59:47 -0700 (PDT) Message-ID: <588970.5681.qm@web56103.mail.re3.yahoo.com> References: <49E5E2FF.3060401@eu.citrix.com> Reply-To: bderzhavets@yahoo.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1329871356==" Return-path: In-Reply-To: <49E5E2FF.3060401@eu.citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefano Stabellini Cc: xen-devel List-Id: xen-devel@lists.xenproject.org --===============1329871356== Content-Type: multipart/alternative; boundary="0-579365157-1239803987=:5681" --0-579365157-1239803987=:5681 Content-Type: text/plain; charset=us-ascii >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 wrote: From: Stefano Stabellini Subject: Re: [Xen-devel] [PATCH] fix stubdom memory corruption To: "bderzhavets@yahoo.com" Cc: "xen-devel" 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: > > Please report to xen-devel@lists.xensource.com > Traceback (most recent call last): > File "/usr/sbin/xm", line 7, in > 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 "", line 1, in > 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@lists.xensource.com http://lists.xensource.com/xen-devel --0-579365157-1239803987=:5681 Content-Type: text/html; charset=us-ascii
>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@eu.citrix.com> wrote:
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Xen-devel] [PATCH] fix stubdom memory corruption
To: "bderzhavets@yahoo.com" <bderzhavets@yahoo.com>
Cc: "xen-devel" <xen-devel@lists.xensource.com>
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 n etwork
> 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@lists.xensource.com
> 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@lists.xensource.com
http://lists.xensource.com/xen-devel

--0-579365157-1239803987=:5681-- --===============1329871356== 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 --===============1329871356==--