[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Remus crashes only with Windows Server 2003

  • To: Xen Users List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Antonio Colin <dftonywhite@xxxxxxxxxxx>
  • Date: Wed, 11 Jan 2012 16:49:41 -0600
  • Delivery-date: Wed, 11 Jan 2012 22:51:17 +0000
  • Importance: Normal
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello everyone,

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:

root@neutrino:~/working-remus# xm create exchange-hvm.cfg
root@neutrino:~/working-remus# remus exchange-hvm
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

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!


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.