Re: XenServer and re0 watchdog timeout
Hi,
personally I prefer to use option 1.
# Rename the original QEMU script:
mv /usr/lib/xen/bin/qemu-dm /usr/lib/xen/bin/qemu-dm.orig
# Replace with a wrapper script:
echo '#!/bin/bash
oldstring=$@
newstring=${oldstring//rtl8139/e1000}
exec /usr/lib/xen/bin/qemu-dm.orig $newstring' /usr/lib/xen/bin/qemu-dm
# Make the wrapper script executable
chmod +x /usr/lib/xen/bin/qemu-dm
Regards,
Michael
On 16.11.12 18:53, Mike Larkin wrote:
On Fri, Nov 16, 2012 at 04:43:42PM +, Rodolfo Gouveia wrote:
Hi all,
Has anybody tested XenServer 6.0 with OpenBSD 5.2 amd64 as a guest?
Network doesn't work and I all get are re0 watchdog timeout
over and over...
p.s. no dmesg because I don't have network access
qemu's doing the device emulation and it does not implement the device's
watchdog timer. You need to switch to a different emulated nic, or
patch the re(4) driver so that it doesn't expect a watchdog.
Two ways:
1. Change the vif type in XenServer to be e1000 or ne2k
2. There is a patch for NetBSD that disables the watchdog timer. A quick
google search will find it for you. You might need to massage it a bit
to get it to apply to -current.
-ml
Re: XenServer and re0 watchdog timeout
e1k works great with OpenBSD whether regardless of what hypervisor framework is sitting in front of qemu. Until my plan to port the virtio NIC to OpenBSD grows beyond mere intent, its your best option. -S -- You know, I used to think it was awful that life was so unfair. Then I thought, wouldn't it be much worse if life were fair, and all the terrible things that happen to us come because we actually deserve them? So, now I take great comfort in the general hostility and unfairness of the universe.
Re: XenServer and re0 watchdog timeout
On Mon, Nov 19, 2012 at 1:54 PM, Stephen Spencer gladiat...@gmail.com wrote: e1k works great with OpenBSD whether regardless of what hypervisor framework is sitting in front of qemu. Until my plan to port the virtio NIC to OpenBSD grows beyond mere intent, its your best option. OpenBSD -current already has virtio network interface: see vio(4).
Re: XenServer and re0 watchdog timeout
On Mon, Nov 19, 2012 at 12:54:01PM +0100, bele...@bsdmail.de wrote: Hi, personally I prefer to use option 1. # Rename the original QEMU script: mv /usr/lib/xen/bin/qemu-dm /usr/lib/xen/bin/qemu-dm.orig I've encountered that fix too but that means upgrading XenServer would make return to the realtek config. Maybe there's a way of doing it in their CLI.
XenServer and re0 watchdog timeout
Hi all, Has anybody tested XenServer 6.0 with OpenBSD 5.2 amd64 as a guest? Network doesn't work and I all get are re0 watchdog timeout over and over... p.s. no dmesg because I don't have network access
Re: XenServer and re0 watchdog timeout
On Fri, Nov 16, 2012 at 04:43:42PM +, Rodolfo Gouveia wrote: Hi all, Has anybody tested XenServer 6.0 with OpenBSD 5.2 amd64 as a guest? Network doesn't work and I all get are re0 watchdog timeout over and over... p.s. no dmesg because I don't have network access qemu's doing the device emulation and it does not implement the device's watchdog timer. You need to switch to a different emulated nic, or patch the re(4) driver so that it doesn't expect a watchdog. Two ways: 1. Change the vif type in XenServer to be e1000 or ne2k 2. There is a patch for NetBSD that disables the watchdog timer. A quick google search will find it for you. You might need to massage it a bit to get it to apply to -current. -ml
