Hey All, I am contemplating an upgrade of my Xen-unstable host (using 2.0.x series code) to Xen-3.0.x, and had a couple of questions. 1.) Live Migration: Does it matter what sort of "backend" the DomU''s are using (i.e., physical drive, LVM, file-based)? I thought maybe it worked similar to VMware int hat it copied the file containing the system over, but of that is the case then that would not work for LVM-based systems, would it? 2.) MythTV: I saw one setup where someone was able to get a MythTV backend running on the 2.0.x series of the unstable code; is anyone running a MythTV backend on the 3.0.x series code (either stable or unstable)? Thanks, in advance! -Alan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 7/3/06, Alan Murrell <lists@murrell.ca> wrote:> Hey All, > > I am contemplating an upgrade of my Xen-unstable host (using 2.0.x > series code) to Xen-3.0.x, and had a couple of questions. > > 1.) Live Migration: Does it matter what sort of "backend" the DomU''s > are using (i.e., physical drive, LVM, file-based)? I thought maybe it > worked similar to VMware int hat it copied the file containing the > system over, but of that is the case then that would not work for > LVM-based systems, would it?All Filesystems, including / mounted by the domU must be network-filesystems - they must be available on the target in the same way as on the destination. Xen only copies RAM data over to the target and doesn''t care for the mounted filesystems. I am not sure if you can use a networked filesystem that takes care itself transparently for data consitency and is available on the target as device file as well. I guess maybe drbd does such things.> > 2.) MythTV: I saw one setup where someone was able to get a MythTV > backend running on the 2.0.x series of the unstable code; is anyone > running a MythTV backend on the 3.0.x series code (either stable or > unstable)?I think there are some message in the list archives. Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
My cousin has a writeup of his setup of MythTV using a 2.0 version of Xen here: http://narrow-band.net/index.php/MythTV I checked with my cousin, and he has successfully gotten this working with the Xen 3.0.2 code (something didn''t work in the PCI forwarding in 3.0.1 apparently that he said made it not work). He does have the howto updated to match 3.0.2 and he says that it should be up-to-date and functional. Mito -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Alan Murrell Sent: Monday, July 03, 2006 5:50 AM To: Xen List Subject: [Xen-users] Couple of questions Hey All, I am contemplating an upgrade of my Xen-unstable host (using 2.0.x series code) to Xen-3.0.x, and had a couple of questions. 1.) Live Migration: Does it matter what sort of "backend" the DomU''s are using (i.e., physical drive, LVM, file-based)? I thought maybe it worked similar to VMware int hat it copied the file containing the system over, but of that is the case then that would not work for LVM-based systems, would it? 2.) MythTV: I saw one setup where someone was able to get a MythTV backend running on the 2.0.x series of the unstable code; is anyone running a MythTV backend on the 3.0.x series code (either stable or unstable)? Thanks, in advance! -Alan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, I am the person running mythtv. I recently upgraded from Xen2 to Xen3 and MythTV carried on working just great (I have a dedicated mythtv domain) The only ''issue'' i had is that pci hiding works differently now - the pci devices are still visible in Dom0, but they still work in DomU. The other bonus of Xen3 is that the devers have included loads of kernel modules in the default build, so I didnt even have to make a custom kernel to use my Haupauage WinTV nova cards :) go for it :) g _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi George, Thanks for the response! :-) Yes, looking back on the How-To, I see you are the one :-) George Styles wrote:> I recently upgraded from Xen2 to Xen3 and MythTV carried on working > just great (I have a dedicated mythtv domain)Are you using the "stable" build or the "unstable" one, as you did with Xen3? > The only ''issue'' i had is that pci hiding works differently now - the > pci devices are still visible in Dom0, but they still work in DomU. Does that mean PCI devices can be used by more than one domain?> The other bonus of Xen3 is that the devers have included loads of > kernel modules in the default build, so I didnt even have to make a > custom kernel to use my Haupauage WinTV nova cards :)That sounds good. That''s one thing I didn''t like about Xen2 was that the default kernel builds included hardly anything that was really needed :-( I''ll go ahead and give it a try. Maybe I can run a Mandriva host system, but use the default kernel builds from the Xen site instead of the Mandriva RPMs and/or building my own kernel(s) :-) -Alan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users