Hello Shriram,
Just comming back to Remus HA, three weeks ago I sent this thread and the situation hasn't changed. You are right,
remus works properly with --no-net option.
There is actually this tapdisk related error in the syslog file in the primary host:
Jan 17 17:28:58 xen-backup tapdisk2[5795]: remus: could not bind server socket 11 to 192.168.2.4:9000: 98 Address already in use
Also when I boot up the VM (Windows Server 2003) from NFS and without remus or disk replication, in both the primary and the backup
there is in fact a vif attached to it which is bind to the bridge in the two cases.
I have the sch_plug module installed correctly in both hosts and everything works perfect for Linux systems. But it just cannot come true
for Windows.
I attach xend.log and syslog from primary and backup if you'd like to see further information in order to help me.
Thank you a lot!!
Tony.
> From: rshriram@xxxxxxxxx
> Date: Fri, 13 Jan 2012 09:54:35 -0800
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> CC: dftonywhite@xxxxxxxxxxx
> Subject: Re: [Xen-users] Remus crashes only with Windows Server 2003
>
> On Fri, Jan 13, 2012 at 9:05 AM, <xen-users-request@xxxxxxxxxxxxxxxxxxx> wrote:
> > I have setup Remus on Debian Squeeze and kernel 3.1.5. Remus and disk replication works perfect for Ubuntu systems,
> > but when I start Remus for Windows Sever 2003 (running Microsoft Exchange Enterprise 2003) it crashes giving the
> > following error:
> >
>
> Is that Ubuntu VM a PV or HVM ?
> I presume that remus with --no-net works properly ?
>
> > root@neutrino:~/working-remus# xm create exchange-hvm.cfg
> > root@neutrino:~/working-remus# remus exchange-hvm 192.168.2.4
> > qemu logdirty mode: enable
> > xc: error: Error when writing to state file (4a) (errno 104) (104 = Connection reset by peer): Internal error
> > qemu logdirty mode: disable
> > PROF: resumed at 1326315866.106150
> > resuming QEMU
> > tc filter del dev vif3.0 parent ffff: proto ip pref 10 u32
> > RTNETLINK answers: Invalid argument
> > We have an error talking to the kernel
> > Exception xen.remus.util.PipeException: PipeException('tc failed: 2, No such file or directory',) in <bound method BufferedNIC.__del__ of <xen.remus.device.BufferedNIC object at 0x24b7510>> ignored
>
> This error tells me nothing. "Connection reset by peer" could result
> from a lot of issues.
> A. check the syslog in primary and backup, for errors related to tapdisk
> B. Check the xend.log file in backup
> C. If your system works with --no-net, then try to boot up the VM
> without remus, and make sure that
> there is a vif interface for the VM. And make sure that interface is
> on the bridge (if you have bridging enabled).
> Remus tries to install a network buffer (sch_plug) to the vif interface.
>
>
>
> > root@neutrino:~/working-remus#
> >
> > It seems that on the backup remus or Xen cannot assign a vif1.0 to the DomU since #ifconfig -a doesn't show a new vif there
> > when starting remus.
> >
> > Any help would be highly appreciated!
> >
> > Tony.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
