Date: Tue, 08 Sep 2015 17:06:29 +0100 From: Karl Pielorz <kpielorz_lst@tdx.co.uk> To: Adam McDougall <mcdouga9@egr.msu.edu>, freebsd-xen@freebsd.org Subject: Re: XenServer 6.5(SP1) - HVM 're0: watchdog timeout' errors... Message-ID: <762F895FF087C3BBB6DB94DA@[10.12.30.106]> In-Reply-To: <55EDC55B.8000004@egr.msu.edu> References: <9CC4073DE17E3C8BD01EF7D3@[10.12.30.106]> <55EDA470.1000007@citrix.com> <C1F8BAECAFA8EB8C9A97D5FA@[10.12.30.106]> <55EDC55B.8000004@egr.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--On 07 September 2015 13:11 -0400 Adam McDougall <mcdouga9@egr.msu.edu> wrote: > Try this: > http://discussions.citrix.com/topic/329848-openbsd-with-message-watchdog- > timeout/ > > I've used it before for an OpenBSD guest VM. If that patch is in place > on any XenServer you migrate to, it should set e1000 for the NIC type if > you set NicEmulation in the Custom Fields as described in step 2. > > A cleaner patch would just let you specify any driver you want, but this > one is semi-hardcoded for e1000. You could also try 'virtio' with: > argv = [arg.replace('rtl8139','virtio') for arg in argv] Hi, Thanks for the link. I patched both our in-house XenServers [6.5SP1+Hotfixes] with this - it appeared to work OK (i.e. the DomU's came up with em0 NIC's - rather than Realtek). They seem to work OK for pushing traffic - but if I try and migrate a guest VM using Intel NIC's with XenServer - it fails miserably and kills it :( XenServer logs: "Migrating VM 'FreeBSD (SWR)' from 'Xen1' to 'Xen2' Internal error: Xenops_interface.Internal_error("Unix.Unix_error(2\"open\",\"/var/lib/xen/qemu-save.36\")")" Other VM's not using the Intel NIC's seem OK. I made sure both the 'source' and 'destination' XenServers are patch (there's only two in the pool). -Karl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?762F895FF087C3BBB6DB94DA>