Date: Sun, 12 Aug 2012 11:12:41 -0500 From: Mark Felder <feld@feld.me> To: freebsd-xen@freebsd.org Subject: Re: Citrix Xenserver and FreeBSD migration/suspend scripts Message-ID: <op.wixrbfzh34t2sn@localhost> In-Reply-To: <000001cd7889$05e15ac0$11a41040$@ezwind.net> References: <61BCA99E-2574-4987-ACD9-E84A3AEBD2A3@ramattack.net> <20120810.034203.52110126.moto@kawasaki3.org> <69EAC334-C51A-4F12-98BE-C25674F10A36@ramattack.net> <20120810.103728.219947649.moto@kawasaki3.org> <C29A4285-989C-4F3F-BE5D-B92959E0BD92@ramattack.net> <op.wit1wntv34t2sn@me-pc> <000001cd7889$05e15ac0$11a41040$@ezwind.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 12 Aug 2012 07:50:16 -0500, Jay West <jwest@ezwind.net> wrote: > Questions: > 1) on the stock 64bit 9.0 & 9.1-beta XENHVM kernels, we still had the > boot > problem where after installing the kernel and rebooting, the boot failed > as > being unable to find the boot device. We had to pass a boot string of > ad0p2 > instead of the default ada0p2, and then edit fstab accordingly. I assume > others here had to do that as well? > Yes, but I think that's because with the XENHVM kernel the disks are using a different driver. There's a difference between the ad and ada drivers. > 2) I'm sure this will show a lack of understanding on my part, but I'm > just > curious about the xen-tools port that has been in the ports collection > for a > little while. As per the pdf on the migration/suspend scripts, this > needs to > be installed first. I would think the current port - being called > "xen-tools", would/should include these migration/suspend scripts. It's > not > xen-tools (in Citrix parlance) without that capability. So, is this a > case > of the new scripts just "finish off" the work that went into the current > xen-tools script and the xen-tools port in the ports collection is > functionally incomplete? I guess I'm unclear as to the > history/relationship/status of the xen-tools port and these > migration/suspend scripts. This is likely where it will show up. I've been talking to the ports@ team and it seems to make sense that we include it in that port. > > 3) In some of my googling on 64 bit XENHVM "how-to's", one of them (can't > find it at the moment) mentioned 64 bit Freebsd not working right under > Xen > with regards to SMP, and the how-to offered several patches to disable > SMP > amongst other related items. To run the new migration/suspend scripts, > did > other people here need to use those patches? > I have a feeling this is an old/resolved issue as I've not seen it yet.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wixrbfzh34t2sn>