[Xen-users] Remus config error

[xelatex <yzt356@xxxxxxxxx>]

I have installed Xen 4.1.2 on CentOS 5.5 with Domain0 Kernel 2.6.32.48 and
DomainU CentOS 5.7 with kernel 2.6.18. The vm image is set on a nfs backend
storage. Xen is running successfully and the command "xm migrate" and "xm
migrate --live" can run successfully. 

The vm config file is this :
name            = "vm3-1-para"
vcpus           = 1
memory          = '256'
disk            = [ 'file:/nfs_xen/vm3-1-para.img,xvda,w']
on_reboot       = 'restart'
on_crash        = 'restart'
vif             = [ 'bridge=eth0' ]
#kernel                 = "/mnt/images/xen/vmlinuz"
#ramdisk                = "/mnt/images/xen/initrd.img"
acpi            = 0
apic            = 0
pae             = 0
vnc             = 1
vncviewer       = 0
ne2000          = 0

>From a remus reference from http://nss.cs.ubc.ca/remus/doc.html, I tried its
disk replication
disk = [ 'tap2:remus:10.0.0.3:9000|aio:/nfs_xen/vm3-1-para.img,xvda,w' ]
but get error: 
[root@SLOT1 XenImg]# xm start vm3-1-para
Error: Disk isn't accessible
when start vm.

When I run "remus" command, the error messages are below:

1. remus for HVM DomainU:
[root@SLOT1 ~]# remus vm1-1 10.0.0.3
Disk is not replicated: file:/nfs_xen/vm1-1.img,hda,w
tc qdisc add dev vif12.0 ingress
Cannot find device "vif12.0"
Traceback (most recent call last):
  File "/usr/bin/remus", line 219, in ?
    run(cfg)
  File "/usr/bin/remus", line 125, in run
    bufs.append(BufferedNIC(vif))
  File "usr/lib64/python2.4/site-packages/xen/remus/device.py", line 326, in
__init__
  File "usr/lib64/python2.4/site-packages/xen/remus/device.py", line 358, in
setup
  File "usr/lib64/python2.4/site-packages/xen/remus/device.py", line 181, in
install
xen.remus.util.PipeException: tc failed (errmsg: Cannot find device
"vif12.0"): 1, Operation not permitted

If I run remus without network, it caused segment fault:
[root@SLOT1 ~]# remus --no-net vm1-1 10.0.0.3
Disk is not replicated: file:/nfs_xen/vm1-1.img,hda,w
Segmentation fault

2. remus for paravirtualized DomainU
So I wonder if I should run remus with paravirtualized DomainU, so I run
such a VM called vm3-1-para and  errors shows below:

[root@SLOT1 ~]# remus vm3-1-para 10.0.0.3
Disk is not replicated: file:/nfs_xen/vm3-1-para.img,xvda,w
WARNING: suspend event channel unavailable, falling back to slow xenstore
signalling
PROF: suspending at 1323744888.135283
installing buffer on ifb0...  done.
PROF: resumed at 1323744888.179425
PROF: flushed memory at 1323744888.207391
PROF: suspending at 1323744888.368985
timeout polling fd
xc: error: Suspend request failed: Internal error
xc: error: Domain appears not to have suspended: Internal error
PROF: resumed at 1323744888.886730

And then, vm3-1-para has been migrated to the backup Domain0. I can find it
with "xm list" in 10.0.0.3.


With these errors, I have some questions with remus in Xen 4.x.
1. Does remus in Xen 4.x support HVM fully virtualized Domain0?
2. Should vm image of remus in Xen 4.x must be put in NAS or SAN backend
storage? Or should not do this?

Thank you.

--
View this message in context: 
http://xen.1045712.n5.nabble.com/Remus-config-error-tp5067030p5067030.html
Sent from the Xen - User mailing list archive at Nabble.com.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users