Date: Sat, 22 Dec 2012 01:29:33 -0600 From: Mark Felder <feld@feld.me> To: Jay West <jwest@ezwind.net> Cc: freebsd-xen@freebsd.org Subject: Re: 9.1R? Message-ID: <20121222012933.5694d482@tech304> In-Reply-To: <000301cddfa8$b6af8b70$240ea250$@ezwind.net> References: <000301cddfa8$b6af8b70$240ea250$@ezwind.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 21 Dec 2012 12:26:36 -0600
Jay West <jwest@ezwind.net> wrote:
> All our FreeBSD use is now under Xenserver 6.1. I was curious, given =
the
> port of xe-guest-utilities that allows online migrations and such. =
after
> installing those tools (thus PVM/64), should we be changing our mount =
points
> to refer to the xen hd device (xbdX) or continue to use adX inside the =
VM
> for filesystem mounts (kinda like we need to change the network device =
{ex.
> bgeX} to xnX)? Just looking for a sanity check J
You'll notice that /dev/xbd* doesn't actually exist :-)
Also, if you aren't aware, here is my personal list of Xen bugs:
- Shutdown via Xen fails to poweroff. It doesn't issue any normal =
shutdown commands,
but tells the Xen code in the kernel to start a shutdown. It's broken =
on the kernel
side. kern/171118=20
Also, NetBSD's workaround for this is to enable powerd, but we can't
when we're running XENHVM and I suspect their powerd is a completely =
different beast.
- If you use PF with Xen HVM your performance will suck. Known bug.
kern/154428
Set net.inet.tcp.tso=3D0 as a workaround.
- "Deactivating" a network interface is an option after enabling the =
xe-guest-utilities scripts.
Please don't do that. It seems to cause a panic every time. kern/171138
Also, this happens when you try to change the VLAN assigned to an
interface.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121222012933.5694d482>