Re: [Xen-devel] [PATCH] fix stubdom memory corruption

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

>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