From alex at davz.net Fri Sep 5 20:37:03 2008 From: alex at davz.net (Alex Davies) Date: Fri, 5 Sep 2008 22:37:03 +0200 Subject: [Fedora-xen] Xen - large virtual machines Message-ID: <5fb622120809051337l6cfdbbe6ue128348ec06b7460@mail.gmail.com> Hi Everyone, I'm looking for a solution to run some Xen VM's with fairly significant(up to ~30TB) local storage volumes. We plan to use two Sun "Thumper" x4540's with 48*1TB drives (8 controllers). I have a few questions, and would appreciate feedback before I try to achieve something dumb or impossible :) - Has Xen been tested / does Xen support very large volumes? We will probably end up using ext3 (as it seems its the only supported option), so no single volume in a VM will exceed ~16TB, but we will be at this end of the spectrum on several volumes. - Can anyone suggest a better option than creating 7 RAID5 arrays of 6 disks each (1 per controller); using the remaining 6 drives for RAID-10 for DomU and hot spares and then adding the 7 RAID5 volumes to a LVM group, creating a LV per Xen VM block device? Has anybody used mdadm and/or LVM to handle this number of drives? - We are required to be able to bring up VMs on one machine on another within a reasonable period of time (this is defined as days, not hours) and to keep the backup copy reasonably in sync (again, days not hours). Can anyone comment on the suitability of rsync to copy such massive block devices? We would use version 3, which I know has improved performance for this sort of move, but is it going to literally take forever to checksum 48TB? If anyone is able to give example of rsync performance (same switch or crossover - whichever we conclude is fastest) over gigabit Ethernet, that would be a bonus. We expect there to be significant spare resources available to domU at night for checksumming if required. - I know XFS is not supported by RHEL, but does it work - and/or well? I've seen several reports that suggest it performs far better (best summary http://hepix.caspur.it/storage/hep_pdf/2007/Spring/Petkus_HEPiX_Spring06.storageeval.pdf) but what is it like for reliability? - Does anyone has any suggestions / improvements to this plan? Has anybody done this before - with similar hardware? - [An alternative scenario, if we can get it, would be a third Thumper - in which case we would run half the VMs on each of two Thumpers running RAID-10 (8 RAID-1 volumes, each a PV) for ~24TB per machine, and use the third Thumper, partitioned as above with RAID-5 for more like RAID-5 levels of storage efficiency, for backups of VMs and disaster recovery. Comments on this would be fantastic too.] The VMs are expected to be quite IO-heavy, hence the requirement for local storage (not iSCSI) and para virtualization. Any comments much appreciated. Many thanks, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From pasik at iki.fi Mon Sep 8 06:24:37 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 8 Sep 2008 09:24:37 +0300 Subject: [Fedora-xen] [PATCH 0 of 7] x86: lay groundwork for Xen domain 0 support Message-ID: <20080908062437.GS13941@edu.joroinen.fi> ----- Forwarded message from Jeremy Fitzhardinge ----- From: Jeremy Fitzhardinge To: Ingo Molnar Cc: linux-kernel at vger.kernel.org, "H. Peter Anvin" , Xen Devel , Andi Kleen Date: Sun, 07 Sep 2008 15:21:12 -0700 Subject: [PATCH 0 of 7] x86: lay groundwork for Xen domain 0 support Hi Ingo, This series begins to lay the groundwork for Xen domain 0 support. Domain 0 is much like a normal Xen domain, but it is also allowed to have direct access to the underlying hardware (including both IO space and various BIOS tables), so it can run device drivers, etc. This means that we need to be able to distinguish between a Xen domain's normal pseudo-physical address space, and the real machine physical address space. This series: - Adds a new pte flag - _PAGE_IOMAP - used to indicate that a mapping is intended to map an IO device, and the physical address is actually a real machine physical address rather than a pseudo-physical address. This is exposed as PAGE_KERNEL_IO and so on. ioremap() and early_ioremap() are modified to set this flag, as they (should) always be used to map IO devices and not other memory. By default __supported_pte_mask masks this flag out, so it won't end up in the final pagetable. The Xen (and any other) code which cares about this flag unmask it from __supported_pte_mask. - Add early_memremap() to deal with the cases where early_ioremap() actually being used to map normal memory. - Remove a bogus check in x86-64's implementation of set_pte_vaddr_pud(), which prevents memory mappings from being updated. - Convert __acpi_map_table to use early_ioremap(), rather than have its own implementation. - Make __acpi_map_table always map the memory rather than assuming that the linear map maps some of the acpi tables. This won't be true in the virtual case, and always mapping doesn't hurt in the native case. I've tested these patches on both 32 and 64 native booting, and it all works for me. Thanks, J From paul at xelerance.com Mon Sep 8 17:43:04 2008 From: paul at xelerance.com (Paul Wouters) Date: Mon, 8 Sep 2008 13:43:04 -0400 (EDT) Subject: [Fedora-xen] [PATCH 0 of 7] x86: lay groundwork for Xen domain 0 support In-Reply-To: <20080908062437.GS13941@edu.joroinen.fi> References: <20080908062437.GS13941@edu.joroinen.fi> Message-ID: On Mon, 8 Sep 2008, Pasi K?rkk?inen wrote: > Subject: [Fedora-xen] [PATCH 0 of 7] x86: lay groundwork for Xen domain 0 > support > > ----- Forwarded message from Jeremy Fitzhardinge ----- > > From: Jeremy Fitzhardinge > To: Ingo Molnar > Cc: linux-kernel at vger.kernel.org, "H. Peter Anvin" , > Xen Devel , > Andi Kleen > Date: Sun, 07 Sep 2008 15:21:12 -0700 > Subject: [PATCH 0 of 7] x86: lay groundwork for Xen domain 0 support Is anyone going to build kernel and/or xen rpms with these patches for testing? Paul From berrange at redhat.com Mon Sep 8 18:48:31 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 8 Sep 2008 19:48:31 +0100 Subject: [Fedora-xen] [PATCH 0 of 7] x86: lay groundwork for Xen domain 0 support In-Reply-To: References: <20080908062437.GS13941@edu.joroinen.fi> Message-ID: <20080908184831.GA3052@redhat.com> On Mon, Sep 08, 2008 at 01:43:04PM -0400, Paul Wouters wrote: > On Mon, 8 Sep 2008, Pasi K?rkk?inen wrote: > > > Subject: [Fedora-xen] [PATCH 0 of 7] x86: lay groundwork for Xen domain 0 > > support > > > > ----- Forwarded message from Jeremy Fitzhardinge ----- > > > > From: Jeremy Fitzhardinge > > To: Ingo Molnar > > Cc: linux-kernel at vger.kernel.org, "H. Peter Anvin" , > > Xen Devel , > > Andi Kleen > > Date: Sun, 07 Sep 2008 15:21:12 -0700 > > Subject: [PATCH 0 of 7] x86: lay groundwork for Xen domain 0 support > > Is anyone going to build kernel and/or xen rpms with these patches for > testing? No, because they don't provide a Dom0. The provide the *groundwork* on which Xen dom0 kernel patches will be laid. The plan for Dom0 will be to incorporate them in rawhide when they are merged in whatever LKML dev tree lines with with rawhide at that time. Jeremy's patches have been flowing into LKML tree pretty quickly in recent times, so if the patches are approved by upstream kernel devs, it shouldn't be too much of a time-lag before they make their work into rawhide Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From crobinso at redhat.com Wed Sep 10 20:21:42 2008 From: crobinso at redhat.com (Cole Robinson) Date: Wed, 10 Sep 2008 16:21:42 -0400 Subject: [Fedora-xen] ANNOUNCE: New release virt-manager 0.6.0 Message-ID: <48C82C56.4000904@redhat.com> I'm happy to announce a new virt-manager release, version 0.6.0. The release can be downloaded from: http://virt-manager.org/download.html The direct download link is: http://virt-manager.org/download/sources/virt-manager/virt-manager-0.6.0.tar.gz This release includes: - Remote storage management and provisioning: View, add, remove, and provision libvirt managed storage. Attach managed storage to a remote VM. - Remote VM installation support: Install from managed media (cdrom) or PXE. Simple install time storage provisioning. - VM details and console windows merged: each VM is now represented by a single tabbed window. - Use Avahi to list libvirtd instances on network. - Hypervisor Autoconnect: Option to connect to hypervisor at virt-manager start up. - Option to add sound device emulation when creating new guests. - Virtio and USB options when adding a disk device. - Allow viewing and removing VM sound, serial, parallel, and console devices. - Specifying a specific keymap when adding display device. - Allow app to keep running with only a VM window open. - Allow limiting amount of stored stats history. - Numerous bug fixes and minor improvements. Thanks to everyone who has contributed to this release through testing, bug reporting, submitting patches, and otherwise sending in feedback! Thanks, Cole From crobinso at redhat.com Wed Sep 10 20:23:27 2008 From: crobinso at redhat.com (Cole Robinson) Date: Wed, 10 Sep 2008 16:23:27 -0400 Subject: [Fedora-xen] ANNOUNCE: New release virtinst 0.400.0 Message-ID: <48C82CBF.4080807@redhat.com> I'm happy to announce a new virtinst release, version 0.400.0. It can be downloaded at: http://virt-manager.org/download.html The direct link is: http://virt-manager.org/download/sources/virtinst/virtinst-0.400.0.tar.gz New in this release: - New tool 'virt-convert': Allows converting between different types of virt configuration files. Currently only supports vmx -> virt-image. - New tool 'virt-pack': Converts virt-image xml format to vmx and packs in a tar.gz. (Note this will likely be merged with virt-convert in the future). - virt-install: Support for remote VM installation. Can use install media and disk images on remote host if shared via libvirt. Allows provisioning storage on remote pools. - virt-install new options: new --wait option, allows putting a hard time limit on installs. new --sound option, to create VM with soundcard emulation. new --disk option, allows specifying media as a path, storage volume, or a pool to provision storage on, device type, and several other options. Deprecates --file, --size, --nonsparse. new --prompt option. Input prompting is no longer the default, this option turns it back on. - virt-install: allow setting cpu pinning information for qemu/kvm VMs. - virt-install: numa support via --cpuset=auto option. - virt-image: --replace option to overwrite existing VM image file. - virt-image: support multiple network interfaces in virt-image format. - use virtio disk/net drivers if chosen os entry supports it (Fedora 9/10, Ubuntu Hardy). - Numerous bug fixes and minor improvements. Thanks to everyone who has contributed to this release whether by testing, bug reporting, submitting patches, and otherwise sending feedback! Thanks, Cole From ask at develooper.com Thu Sep 11 04:55:57 2008 From: ask at develooper.com (=?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?=) Date: Wed, 10 Sep 2008 21:55:57 -0700 Subject: [Fedora-xen] Xen - large virtual machines In-Reply-To: <5fb622120809051337l6cfdbbe6ue128348ec06b7460@mail.gmail.com> References: <5fb622120809051337l6cfdbbe6ue128348ec06b7460@mail.gmail.com> Message-ID: <87617A35-301D-4A8B-87A4-05278E6722E7@develooper.com> On Sep 5, 2008, at 13:37, Alex Davies wrote: > using the remaining 6 drives for RAID-10 for DomU Unless you meant "for Dom0", then beware that software RAID-10, LVM and Xen doesn't work: https://bugzilla.redhat.com/show_bug.cgi?id=223947 https://bugzilla.redhat.com/show_bug.cgi?id=224077 -- http://develooper.com/ - http://askask.com/ From pavankris at gmail.com Thu Sep 11 19:18:39 2008 From: pavankris at gmail.com (pavan krishnamurthy) Date: Thu, 11 Sep 2008 12:18:39 -0700 Subject: [Fedora-xen] Xen Fedora image for DOMU In-Reply-To: <1a8679940809111207le61ddb9ub8b8024653813d7f@mail.gmail.com> References: <1a8679940809111207le61ddb9ub8b8024653813d7f@mail.gmail.com> Message-ID: <1a8679940809111218x73e72ca5k4ebf9fbdb42db86f@mail.gmail.com> Hi , Can anyone point me to the link where i can download bare minimum setup of fedora image for xen. I have the one which is like 16gb, but i dont have that big space so it would be great if i am able to get a smaller version of it . Thanks Pavan From guillaume.chardin at gmail.com Fri Sep 12 14:44:19 2008 From: guillaume.chardin at gmail.com (Guillaume) Date: Fri, 12 Sep 2008 16:44:19 +0200 Subject: [Fedora-xen] About daemon in Guest Message-ID: Hi, I create VMs by copying files from my original fedora install to a partition i'll use for para-virt. guest OS root (domU "/") Can i disable in this guest OS all xen daemon all xen libs and so forth ? Or they must be running in the guest OS too ? thanks for your reply. -- Guillaume -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul at xelerance.com Fri Sep 12 15:06:09 2008 From: paul at xelerance.com (Paul Wouters) Date: Fri, 12 Sep 2008 11:06:09 -0400 (EDT) Subject: [Fedora-xen] About daemon in Guest In-Reply-To: References: Message-ID: On Fri, 12 Sep 2008, Guillaume wrote: > I create VMs by copying files from my original fedora install to a partition i'll use for para-virt. guest OS root (domU > "/") > Can i disable in this guest OS all xen daemon all xen libs and so forth ? Or they must be running in the guest OS too ? > > thanks for your reply. Nope. Only the dom0 needs the xen service. Paul From marco.guazzone at gmail.com Sat Sep 13 10:14:21 2008 From: marco.guazzone at gmail.com (Marco Guazzone) Date: Sat, 13 Sep 2008 12:14:21 +0200 Subject: [Fedora-xen] kernel-xen-2.6.25.3-2.fc9.x86_64 don't boot Message-ID: Hi, I've just installed the kernel-xen-2.6.25.3-2.fc9.x86_64 on my FC9 for experimenting with XEN. Unfortunately when I boot from grub with this kernel (as a host system) the system reboot after the message: --- [snip] --- XEN relinquishing vga console --- [/snip] --- I've found a previous email where was suggested to change the boot parameters: * add the noreboot * remove the quiet but even doing so, nothing has changed. Can someone help me? Thank you very much!! Cheers -- Marco -------------- next part -------------- An HTML attachment was scrubbed... URL: From felix.schwarz at web.de Sat Sep 13 11:45:29 2008 From: felix.schwarz at web.de (Felix Schwarz) Date: Sat, 13 Sep 2008 13:45:29 +0200 Subject: [Fedora-xen] Re: kernel-xen-2.6.25.3-2.fc9.x86_64 don't boot In-Reply-To: References: Message-ID: <48CBA7D9.8070600@web.de> Marco Guazzone schrieb: > I've just installed the kernel-xen-2.6.25.3-2.fc9.x86_64 on my FC9 for > experimenting with XEN. > > Unfortunately when I boot from grub with this kernel (as a host system) the > system reboot after the message: > --- [snip] --- > XEN relinquishing vga console > --- [/snip] --- kernel-xen from FC9 does not provide Dom0 ("host") functionality. Currently there is no usable Xen Dom0 in Fedora (besides Fedora 8 where support will be dropped in a few months). If you want to have a stable Xen Dom0, you should go for CentOS oder RHEL. If you just want "virtualization", you should look at KVM which is the upcoming "standard" virtualization for RHEL. Red Hat announced a few days ago that they think about dropping Xen completely when RHEL 5 is not supported any longer (2014). fs -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3312 bytes Desc: S/MIME Cryptographic Signature URL: From Alex.Upton at instinet.com Sat Sep 13 12:02:34 2008 From: Alex.Upton at instinet.com (Alex.Upton at instinet.com) Date: Sat, 13 Sep 2008 08:02:34 -0400 Subject: [Fedora-xen] AUTO: Alex Upton is out of the office (returning 09/15/2008) Message-ID: I am out of the office until 09/15/2008. I'm out of the office, please direct any support related issues to the "TSG SA" team. Any issues in need of escalation should be sent directly to Bob Sinko during this time. Thank you, Alex Note: This is an automated response to your message "[Fedora-xen] Re: kernel-xen-2.6.25.3-2.fc9.x86_64 don't boot" sent on 9/13/2008 7:45:29 AM. This is the only notification you will receive while this person is away. ***************************************************************** <<>> In compliance with applicable rules and regulations, Instinet reviews and archives incoming and outgoing email communications, copies of which may be produced at the request of regulators. This message is intended only for the personal and confidential use of the recipients named above. If the reader of this email is not the intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and permanently delete the copy you received. Instinet accepts no liability for any content contained in the email, or any errors or omissions arising as a result of email transmission. Any opinions contained in this email constitute the sender's best judgment at this time and are subject to change without notice. Instinet does not make recommendations of a particular security and the information contained in this email should not be considered as a recommendation, an offer or a solicitation of an offer to buy and sell securities. ***************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From marco.guazzone at gmail.com Sat Sep 13 13:55:15 2008 From: marco.guazzone at gmail.com (Marco Guazzone) Date: Sat, 13 Sep 2008 15:55:15 +0200 Subject: [Fedora-xen] Re: Re: kernel-xen-2.6.25.3-2.fc9.x86_64 don't boot Message-ID: On Sat, Sep 13, 2008 at 12:14 PM, Felix Schwarz wrote: >> Marco Guazzone schrieb: >> >> I've just installed the kernel-xen-2.6.25.3-2.fc9.x86_64 on my FC9 for >> experimenting with XEN. >> >> Unfortunately when I boot from grub with this kernel (as a host system) the >> system reboot after the message: >> --- [snip] --- >> XEN relinquishing vga console >> --- [/snip] --- >> > kernel-xen from FC9 does not provide Dom0 ("host") functionality. Currently there is no usable Xen Dom0 in Fedora (besides Fedora 8 where support will be dropped in a few months). > > If you want to have a stable Xen Dom0, you should go for CentOS oder RHEL. > > If you just want "virtualization", you should look at KVM which is the upcoming "standard" virtualization for RHEL. Red Hat announced a few days ago that they think about dropping Xen completely when RHEL 5 is not supported any longer (2014). > > fs Thank you for the info... I didn't know that. Sorry for the question but if I understand the kernel-xen RPM is unusable, is it? If so, why does it exist? If not, how can be used? Thank you so much! Cheers, -- Marco From fedora-ml at fapi.de Sat Sep 13 15:47:46 2008 From: fedora-ml at fapi.de (Falko Pilz) Date: Sat, 13 Sep 2008 17:47:46 +0200 Subject: [Fedora-xen] Re: Re: kernel-xen-2.6.25.3-2.fc9.x86_64 don't boot In-Reply-To: References: Message-ID: <20080913174746.3e77c381@f9alpha.fapi.de> Am Sat, 13 Sep 2008 15:55:15 +0200 schrieb "Marco Guazzone" : > Sorry for the question but if I understand the kernel-xen RPM is > unusable, is it? > If so, why does it exist? > If not, how can be used? It is not useable as a Dom0 but it is needed to run a DomU or in other words: this kernel is not for use as a control for Xen. It is to use in a virtual maschine. This kernel uses paravirtops to send syscalls to the xen hypervisor. Regards Falko -- From felix.schwarz at web.de Sat Sep 13 15:53:50 2008 From: felix.schwarz at web.de (Felix Schwarz) Date: Sat, 13 Sep 2008 17:53:50 +0200 Subject: [Fedora-xen] Re: Re: kernel-xen-2.6.25.3-2.fc9.x86_64 don't boot In-Reply-To: References: Message-ID: <48CBE20E.3010201@web.de> Marco Guazzone schrieb: > Sorry for the question but if I understand the kernel-xen RPM is > unusable, is it? ... It's not "unusable". It just provides DomU functionality so with kernel-xen you can run a virtualized Fedora as *guest* on a Xen Dom0 which runs under Fedora 8 oder CentOS/RHEL 5. There's work going on to get Xen's Dom0 functionality in the main Linux kernel. Then Xen support will re-appear in Fedora (probably even a bit earlier). Please consult the archives if you want to learn more about that. fs PS: Part of the problem is the behavior of the Xen developers which had other priorities than keeping up with the latest Linux kernel versions/getting their code into the vanilla kernel. Therefore they put an enormous maintenance burden on distributors which Red Hat was not willing to do anymore. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3312 bytes Desc: S/MIME Cryptographic Signature URL: From alex at davz.net Sun Sep 14 16:16:45 2008 From: alex at davz.net (Alex Davies) Date: Sun, 14 Sep 2008 18:16:45 +0200 Subject: [Fedora-xen] Xen - large virtual machines In-Reply-To: <87617A35-301D-4A8B-87A4-05278E6722E7@develooper.com> References: <5fb622120809051337l6cfdbbe6ue128348ec06b7460@mail.gmail.com> <87617A35-301D-4A8B-87A4-05278E6722E7@develooper.com> Message-ID: <5fb622120809140916j4b1eecb8mbaca39742cb3396f@mail.gmail.com> Thank-you everyone for your suggestions; some extremely useful points have been raised for which I am very grateful. To answer Erin's questions: we are running RHEL/Xen because we have a business requirement for a decent number of RHEL virtual machines (~30). We could run ESX (or KVM, or...) but we (I) am also keen to try to use Xen for real - i've used ESX a lot. There are also licensing benefits for my company that make Xen on RHEL > ESX / KVM. I would love to use ZFS, but unfortunately my Solaris foo is ~0, and consequently we shall have to stick to Linux/ext3. RedHat assure me that if I keep each filesystem to <10T this is supported and encouraged. Based on feedback from this post (and elsewhere), we have decided to go for 2 ISCSI boxes and 2 Thumpers. Two of our virtual machines require >30T of storage, and no redundancy, so we will run one VM on each Thumper (with local storage). The other ~30 VMs will run using the ISCSI volumes to allow live migration. I'm sure i'll be posting here when it comes to getting this lot working, but if anyone has any advice for this setup please let me know! Many thanks, Alex On Thu, Sep 11, 2008 at 6:55 AM, Ask Bj?rn Hansen wrote: > > On Sep 5, 2008, at 13:37, Alex Davies wrote: > >> using the remaining 6 drives for RAID-10 for DomU > > Unless you meant "for Dom0", then beware that software RAID-10, LVM and Xen > doesn't work: > > https://bugzilla.redhat.com/show_bug.cgi?id=223947 > https://bugzilla.redhat.com/show_bug.cgi?id=224077 > > -- > http://develooper.com/ - http://askask.com/ > > > -- Alex Davies This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender immediately by e-mail and delete this e-mail permanently. From ask at develooper.com Sun Sep 14 23:05:54 2008 From: ask at develooper.com (=?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?=) Date: Sun, 14 Sep 2008 16:05:54 -0700 Subject: [Fedora-xen] Xen - large virtual machines In-Reply-To: <5fb622120809140916j4b1eecb8mbaca39742cb3396f@mail.gmail.com> References: <5fb622120809051337l6cfdbbe6ue128348ec06b7460@mail.gmail.com> <87617A35-301D-4A8B-87A4-05278E6722E7@develooper.com> <5fb622120809140916j4b1eecb8mbaca39742cb3396f@mail.gmail.com> Message-ID: <34F0ABAD-8BA8-490A-A787-2ADFBB99051D@develooper.com> On Sep 14, 2008, at 9:16, Alex Davies wrote: > Two of our virtual machines require >30T of storage, and no > redundancy, so we will run one VM on each Thumper (with local > storage). Are you replacing the 500GB disks with 1TB disks in the Thumbers? Unless "no redundancy" really truly means "it's fine if it breaks a lot", then please keep in mind the numbers. 40+ disks are that many times more likely to fail than one disk. Don't just stripe all the disks into one big volume. Either keep them as separate devices so they fail individually or use RAID5 or (better) RAID6 and keep plenty spares ready. Your plan of doing RAID in sets of 8 or so disks is probably about right. - ask -- http://develooper.com/ - http://askask.com/ From guillaume.chardin at gmail.com Mon Sep 15 15:44:47 2008 From: guillaume.chardin at gmail.com (Guillaume) Date: Mon, 15 Sep 2008 17:44:47 +0200 Subject: [Fedora-xen] problem with virtual interface in DomU Message-ID: hi, I finally achieve a goal to start a para-VM with xen. But i still experience problem with networking inside the vm (domU). There are no network interface shown. Maybe kernel module is not loaded for the emulated NIC. In domU i'm only able to see loopback interface. But, in dom0 i can see all bridge interface and networking is OK. Can someone help me ? thanks. -- Guillaume -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume.chardin at gmail.com Mon Sep 15 21:36:30 2008 From: guillaume.chardin at gmail.com (Guillaume) Date: Mon, 15 Sep 2008 23:36:30 +0200 Subject: [Fedora-xen] problem with virtual interface in DomU In-Reply-To: <4502be8f0809151224h152e3b76i50697f44307a2740@mail.gmail.com> References: <4502be8f0809151224h152e3b76i50697f44307a2740@mail.gmail.com> Message-ID: 2008/9/15 lamont cranston > > 1) verify that the virtualization extensions are turned on in the BIOS (in my case, a HP prolient server, the selection was actually named "virtualization") It is not an HVM "build" so, i tought virtualization extensions are useless ? And i don't have intel-VT on my system. > 2) when you get to the end of your install of the guest OS, you should have the option to "share" the network device I did not use any wizard to create the vm (i made a copy of an actual system to an image file, and create the "xm" config file) > 3) easiest way to verify the guest IP is to ask the guest - you can reason it out from the host ifconfig, but just asking the guest is a lot simplier and just "feels" right :) I'm not so good in English, what do you mean ? :-D -- Guillaume From guillaume.chardin at gmail.com Tue Sep 16 14:53:41 2008 From: guillaume.chardin at gmail.com (Guillaume) Date: Tue, 16 Sep 2008 16:53:41 +0200 Subject: [Fedora-xen] problem with virtual interface in DomU In-Reply-To: <4502be8f0809152104p3b4f8d61o958da839c1b7e56@mail.gmail.com> References: <4502be8f0809151224h152e3b76i50697f44307a2740@mail.gmail.com> <4502be8f0809152104p3b4f8d61o958da839c1b7e56@mail.gmail.com> Message-ID: >> It is not an HVM "build" so, i tought virtualization extensions are >> useless ? And i don't have intel-VT on my system. > > That may be the entire problem. > My understanding is that the paravirtualized kernel needs those extensions > so that the supervisor calls do not have to go through the hypervisor. For me it wasn't =) ! For my knowledge, HVM extension was needed by xen only for fully-virtualized OS. (like Microsoft OS and other closed source OS ; because no modification can't be made to their kernel to make them aware of "xen".). But maybe i'm wrong ! And if you're right, it will explain why networking don't work (and will never on my system) --> but keep in mind that xen exist a "long time" before hvm extension do. And I thought that other people made networking works in their xen VM. So, I tought that i can get rid of this problem without hvm set on. Someone can light me more about it ? thanks -- Guillaume From paul at xelerance.com Tue Sep 16 16:42:11 2008 From: paul at xelerance.com (Paul Wouters) Date: Tue, 16 Sep 2008 12:42:11 -0400 (EDT) Subject: [Fedora-xen] problem with virtual interface in DomU In-Reply-To: References: <4502be8f0809151224h152e3b76i50697f44307a2740@mail.gmail.com> <4502be8f0809152104p3b4f8d61o958da839c1b7e56@mail.gmail.com> Message-ID: On Tue, 16 Sep 2008, Guillaume wrote: >>> It is not an HVM "build" so, i tought virtualization extensions are >>> useless ? And i don't have intel-VT on my system. >> >> That may be the entire problem. >> My understanding is that the paravirtualized kernel needs those extensions >> so that the supervisor calls do not have to go through the hypervisor. > For me it wasn't =) ! > For my knowledge, HVM extension was needed by xen only for > fully-virtualized OS. (like Microsoft OS and other closed source OS ; > because no modification can't be made to their kernel to make them > aware of "xen".). But maybe i'm wrong ! > And if you're right, it will explain why networking don't work (and > will never on my system) > --> but keep in mind that xen exist a "long time" before hvm > extension do. And I thought that other people made networking works in > their xen VM. So, I tought that i can get rid of this problem without > hvm set on. > > Someone can light me more about it ? I agree that things have gotten confusing in area of virtualisation. This is what I understand: - Xen hypervisor for para_virt guests does not need HVM. Problem here is that Fedora 8 is the last release to support this setup on x86_64, though work is in progress to add this support to Fedora 9/10. Para_virt guests are booted via kernel= and rootfs images, or via pygrub, which is just a wrapper for grabbing kernel from bootable disk images. - Qemu is a software emulator for various architectures including PC hardware. It requires no HVM instructions, but it can use them if they exist via the kernel "kvm" code. This is how Fedora9 does its VM's via the libvirt and virt-install. This does NOT not use or require a xen hypervisor. - Xenner is a software emulation for the Xen hypervisor. It requires HVM because it uses the kernel "kvm" code. The idea behind Xenner is that you can run VM's based on kernel-xen kernels (eg migration from Fedora8) These are the main virtualisation techniques used in Fedora. There are others, such as VirtualBox/Vmx, lguest, uml, virtuoso, openvz, and many more. See http://virt.kernelnewbies.org/TechComparison Paul From paul at xelerance.com Tue Sep 16 16:57:15 2008 From: paul at xelerance.com (Paul Wouters) Date: Tue, 16 Sep 2008 12:57:15 -0400 (EDT) Subject: [Fedora-xen] problem with virtual interface in DomU In-Reply-To: References: Message-ID: On Mon, 15 Sep 2008, Guillaume wrote: > I finally achieve a goal to start a para-VM with xen. But i still > experience problem with networking inside the vm (domU). > There are no network interface shown. Maybe kernel module is not loaded > for the emulated NIC. > In domU i'm only able to see loopback interface. But, in dom0 i can see > all bridge interface and networking is OK. > Can someone help me ? You are probably re-using the initrd from the dom0 to use in a guest. You need to create a new initrd for the domU guests using mkinitrd --preload=xenblk --with=xennet. Or if your image boots, you might get away with just 'modprobe xennet'. See: http://www.mail-archive.com/fedora-xen at redhat.com/msg00609.html Paul From guillaume.chardin at gmail.com Tue Sep 16 18:15:02 2008 From: guillaume.chardin at gmail.com (Guillaume) Date: Tue, 16 Sep 2008 20:15:02 +0200 Subject: [Fedora-xen] problem with virtual interface in DomU In-Reply-To: References: Message-ID: 2008/9/16 Paul Wouters : > On Mon, 15 Sep 2008, Guillaume wrote: > >> I finally achieve a goal to start a para-VM with xen. But i still >> experience problem with networking inside the vm (domU). >> There are no network interface shown. Maybe kernel module is not loaded >> for the emulated NIC. >> In domU i'm only able to see loopback interface. But, in dom0 i can see >> all bridge interface and networking is OK. >> Can someone help me ? > > You are probably re-using the initrd from the dom0 to use in a guest. > > You need to create a new initrd for the domU guests using mkinitrd > --preload=xenblk --with=xennet. Or if your image boots, you might > get away with just 'modprobe xennet'. Yes i use a modified initrd to support disk drivers (where I specified "xenblk" ), but no xennet. I'll test it tomorrow but im sure it will works ! thanks -- Guillaume From pekka.panula at netservant.fi Wed Sep 17 10:18:34 2008 From: pekka.panula at netservant.fi (pekka.panula at netservant.fi) Date: Wed, 17 Sep 2008 13:18:34 +0300 Subject: [Fedora-xen] virt-manager 0.6.0 under CentOS 5.2 (64-bit) gives Python syntax error (invalid syntax) with domain.py, line 669 Message-ID: Hi I updated virt-manager 0.6.0 and python-virtinst 0.400.0 and when i am trying to start virt-manager i am getting Python syntax error: --------------------8<-------------- Traceback (most recent call last): File "/usr/share/virt-manager/virt-manager.py", line 346, in ? main() File "/usr/share/virt-manager/virt-manager.py", line 287, in main from virtManager.engine import vmmEngine File "/usr/share/virt-manager/virtManager/engine.py", line 31, in ? from virtManager.connection import vmmConnection File "/usr/share/virt-manager/virtManager/connection.py", line 36, in ? from virtManager.domain import vmmDomain File "/usr/share/virt-manager/virtManager/domain.py", line 669 finally: ^ SyntaxError: invalid syntax --------------------8<-------------- CentOS using default python (RPM = python-2.4.3-21.el5): Python 2.4.3 (#1, May 24 2008, 13:57:05) [GCC 4.1.2 20070626 (Red Hat 4.1.2-14)] on linux2 My python skills are somewhat non-existent so can anyone give any help how to fix this? Terveisin/Regards, Pekka Panula, Net Servant Oy -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Wed Sep 17 10:35:59 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 17 Sep 2008 11:35:59 +0100 Subject: [Fedora-xen] virt-manager 0.6.0 under CentOS 5.2 (64-bit) gives Python syntax error (invalid syntax) with domain.py, line 669 In-Reply-To: References: Message-ID: <20080917103559.GH10471@redhat.com> On Wed, Sep 17, 2008 at 01:18:34PM +0300, pekka.panula at netservant.fi wrote: > Hi > > I updated virt-manager 0.6.0 and python-virtinst 0.400.0 and when i am > trying to start virt-manager i am getting Python syntax error: > --------------------8<-------------- > Traceback (most recent call last): > File "/usr/share/virt-manager/virt-manager.py", line 346, in ? > main() > File "/usr/share/virt-manager/virt-manager.py", line 287, in main > from virtManager.engine import vmmEngine > File "/usr/share/virt-manager/virtManager/engine.py", line 31, in ? > from virtManager.connection import vmmConnection > File "/usr/share/virt-manager/virtManager/connection.py", line 36, in ? > from virtManager.domain import vmmDomain > File "/usr/share/virt-manager/virtManager/domain.py", line 669 > finally: > ^ > SyntaxError: invalid syntax > --------------------8<-------------- Looks like a python 2.5-ism crept into the codebase - there's a try, except, finally all together. For python 2.4 you can either a try + except or a try + finally, but not both. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From pavankris at gmail.com Thu Sep 11 18:09:44 2008 From: pavankris at gmail.com (pavankris) Date: Thu, 11 Sep 2008 11:09:44 -0700 (PDT) Subject: [Fedora-xen] Xen Fedora image Message-ID: <19440926.post@talk.nabble.com> Can anybody please point me to the link where i can download fedora xen image. I just need a bare minimum setup not the full package . Thanks Pavan -- View this message in context: http://www.nabble.com/Xen-Fedora-image-tp19440926p19440926.html Sent from the Fedora Xen mailing list archive at Nabble.com. From mail at liro.ch Fri Sep 12 14:12:11 2008 From: mail at liro.ch (LiRo) Date: Fri, 12 Sep 2008 16:12:11 +0200 Subject: [Fedora-xen] Running F8 DomU on Centos52 Dom0 Message-ID: <1221228731.7488.4.camel@wks01.liro.local> Hi Guys After this message from Andy Burns (and the already know issues with Dom0 support) I tried moving my running and working F8_DomU image to a Centos5.2 Dom0 system...unfortunately I was not able to start the domain there...Please see the errors I got: Setting up hotplug. Creating block device nodes. Loading ehci-hcd.ko module Loading ohci-hcd.ko module Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading mbcache.ko module Loading jbd.ko module Loading ext3.ko module Loading xenblk.ko module xen-vbd: registered block device major 202 xvda: xvda1 xvda2 xvda3 Creating root device. Mounting root filesystem. VFS: Can't find ext3 filesystem on dev xvda2. mount: error mounting /dev/root on /sysroot as ext3: Invalid argument Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Booting has failed. This seems like, the guest cannot find its root partition (even its there...I use a .img-File which is the Guest installation...) Anybody else had troubles moving a F8 DomU to Centos? Or I am missing something? Thanks for every help! Best regards, Rolf Linder -------- Weitergeleitete Nachricht -------- Von: Andy Burns An: fedora-xen at redhat.com Betreff: Re: [Fedora-xen] Is it possible to run F8-DomUs under Fedora 10-Dom0? Datum: Sat, 30 Aug 2008 18:25:27 +0100 2008/8/30 Franz Von Hahn : > I'm a bit confused, if it will be possible to run a F8-DomU on top of a Fedora10-Dom0? At the moment it looks unlikely that there will be an F10 dom0 (just like there is currently no F9 dom0) you might want to consider moving your dom0 to CentOS 5.2 instead of F10 -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From Webmaster at fapi.de Sat Sep 13 15:35:13 2008 From: Webmaster at fapi.de (Falko Pilz) Date: Sat, 13 Sep 2008 17:35:13 +0200 Subject: [Fedora-xen] Re: Re: kernel-xen-2.6.25.3-2.fc9.x86_64 don't boot In-Reply-To: References: Message-ID: <20080913173513.71031bc6@f9alpha.fapi.de> Am Sat, 13 Sep 2008 15:55:15 +0200 schrieb "Marco Guazzone" : > Sorry for the question but if I understand the kernel-xen RPM is > unusable, is it? > If so, why does it exist? > If not, how can be used? It is not useable as a Dom0 but it is needed to run a DomU or in other words: this kernel is not for use as a control for Xen. It is to use in a virtual maschine. This kernel uses paravirtops to send syscalls to the xen hypervisor. Regards Falko From fnbrier at gmail.com Sat Sep 13 21:36:22 2008 From: fnbrier at gmail.com (Fred Brier) Date: Sat, 13 Sep 2008 14:36:22 -0700 (PDT) Subject: [Fedora-xen] problems with f9 guest on f8 dom0 In-Reply-To: References: <48581710.3020607@fi.muni.cz> <1213831749.5295.7.camel@tofu.lib.ucdavis.edu> <1502121513.597141214584203310.JavaMail.root@zebra.lib.ucdavis.edu> <1214602419.16631.35.camel@tofu.lib.ucdavis.edu> <1309857660.613961214680806547.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: <19474894.post@talk.nabble.com> I am using 32 bit and have the same issue you were. Did you ever solve the problem? If so, how? Or should I just run Fedora 8 domU(s). Thank you. Fred Matt Cowan wrote: > > > On Sat, 28 Jun 2008, Dale Bewley wrote: >> I opened a bug and noticed the same effect for f8 domUs as well as >> f9 domUs while gathering info. Anyone else seeing that too? > ... > > I haven't had any problems with f8 domU. My usual symptom is slightly > different than what you seem to experience. When I shutdown an f9 > domU, resource display in virt-manager hangs for me, usually > displaying the problem domU as shutdown, and no longer updates the cpu > usage plots for remaining domu or dom0; although the virt-manager > interface itself (buttons,menus) seems responsive, and more painfully, > restarting xend and/or libvirtd doesn't help :( > > I do have *one* f9 domU on one of our test boxes installed by someone > else in my group, and shutting that one down seems to more closely > resemble your symptoms; the cpu charts in virt-manager keep running, > domU remains listed as running, but using no resources, but if I > disconnect and try to reconnect, or restart virt-manager; it can't > connect, and restaring xend and/or libvirtd doesn't help :( > > Looks like most of you responding to this thread are using x86_64; I'm > just running i686. > > -matt > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > -- View this message in context: http://www.nabble.com/problems-with-f9-guest-on-f8-dom0-tp17935902p19474894.html Sent from the Fedora Xen mailing list archive at Nabble.com. From guillaume.chardin at gmail.com Mon Sep 22 14:19:15 2008 From: guillaume.chardin at gmail.com (Guillaume) Date: Mon, 22 Sep 2008 16:19:15 +0200 Subject: [Fedora-xen] Long boot time (hwclock problem) Message-ID: Hi all, A new problem for me. Since I was able to run guests with Xen, I'm stuck with a time synchronization error each time system boot and stop. each time theses events occur, the VM seem to stop running (nothing is displayed on screen) and after 5-10 minutes, normal `init` go on and the system work fine. After some search, I saw that's the problem comes from `hwclock`. When i run it manually it display this error : hwclock from util-linux-ng 2.13 hwclock: Open of /dev/rtc failed, errno=19: No such device. <<<<< Using direct I/O instructions to ISA clock. Last drift adjustment done at 1423924190 seconds after 1969 Last calibration done at 1423924190 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in local time. Waiting for clock tick... I delete & recreate /dev/rtc but it does not solve the problem. Maybe this problem was discussed before on this list but i was unable to find any search tools on fedora/redhat website and manually search against the subject for the 6 last month did not return me any good answer. So, maybe a quick solution about this veeeerrrryyyy long boot time exist. Thanks for your help. -- Guillaume From cowan at bnl.gov Mon Sep 22 14:25:13 2008 From: cowan at bnl.gov (Matt Cowan) Date: Mon, 22 Sep 2008 10:25:13 -0400 (EDT) Subject: [Fedora-xen] problems with f9 guest on f8 dom0 In-Reply-To: <19474894.post@talk.nabble.com> References: <48581710.3020607@fi.muni.cz> <1213831749.5295.7.camel@tofu.lib.ucdavis.edu> <1502121513.597141214584203310.JavaMail.root@zebra.lib.ucdavis.edu> <1214602419.16631.35.camel@tofu.lib.ucdavis.edu> <1309857660.613961214680806547.JavaMail.root@zebra.lib.ucdavis.edu> <19474894.post@talk.nabble.com> Message-ID: On Sat, 13 Sep 2008, Fred Brier wrote: > Subject: Re: [Fedora-xen] problems with f9 guest on f8 dom0 > > I am using 32 bit and have the same issue you were. Did you ever solve the > problem? If so, how? Or should I just run Fedora 8 domU(s). Thank you. Haven't solved it yet, and have been totally unable to usefully run f9 domU on an f8 dom0. We can get an f9 domU to install and run, but once it's shutdown, dom0 needs a reboot for virt-install or virt-manager to function again, which is basically useless except for testing. 'xm' seems to continue funtioning fine. Just tried again last week after installing the latest round of xen related updates... still no luck. Gonna try 64bit next, and if that doesn't work, centos dom0 :( Is *anyone* out there running 32bit f8 dom0 and f9 domU without problems?! -matt > Matt Cowan wrote: >> On Sat, 28 Jun 2008, Dale Bewley wrote: >>> I opened a bug and noticed the same effect for f8 domUs as well as >>> f9 domUs while gathering info. Anyone else seeing that too? >> ... >> >> I haven't had any problems with f8 domU. My usual symptom is slightly >> different than what you seem to experience. When I shutdown an f9 >> domU, resource display in virt-manager hangs for me, usually >> displaying the problem domU as shutdown, and no longer updates the cpu >> usage plots for remaining domu or dom0; although the virt-manager >> interface itself (buttons,menus) seems responsive, and more painfully, >> restarting xend and/or libvirtd doesn't help :( >> >> I do have *one* f9 domU on one of our test boxes installed by someone >> else in my group, and shutting that one down seems to more closely >> resemble your symptoms; the cpu charts in virt-manager keep running, >> domU remains listed as running, but using no resources, but if I >> disconnect and try to reconnect, or restart virt-manager; it can't >> connect, and restaring xend and/or libvirtd doesn't help :( >> >> Looks like most of you responding to this thread are using x86_64; I'm >> just running i686. From paul at xelerance.com Mon Sep 22 14:58:51 2008 From: paul at xelerance.com (Paul Wouters) Date: Mon, 22 Sep 2008 10:58:51 -0400 (EDT) Subject: [Fedora-xen] Xen Fedora image In-Reply-To: <19440926.post@talk.nabble.com> References: <19440926.post@talk.nabble.com> Message-ID: On Thu, 11 Sep 2008, pavankris wrote: > Can anybody please point me to the link where i can download fedora xen > image. I just need a bare minimum setup not the full package . http://www.jailtime.org/download:fedora:fc9 Paul From dlbewley at lib.ucdavis.edu Sun Sep 28 01:52:34 2008 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Sat, 27 Sep 2008 18:52:34 -0700 (PDT) Subject: [Fedora-xen] problems with f9 guest on f8 dom0 In-Reply-To: <31207952.161222566179428.JavaMail.javamailuser@localhost> Message-ID: <31849123.181222566750183.JavaMail.javamailuser@localhost> ----- "Matt Cowan" wrote: > On Sat, 13 Sep 2008, Fred Brier wrote: > > Subject: Re: [Fedora-xen] problems with f9 guest on f8 dom0 > > > > I am using 32 bit and have the same issue you were. Did you ever > solve the > > problem? If so, how? Or should I just run Fedora 8 domU(s). Thank > you. > > Haven't solved it yet, and have been totally unable to usefully run f9 > domU on an f8 dom0. > > We can get an f9 domU to install and run, but once it's shutdown, > dom0 > needs a reboot for virt-install or virt-manager to function again, > which is basically useless except for testing. 'xm' seems to > continue > funtioning fine. Just tried again last week after installing the > latest > round of xen related updates... still no luck. > > Gonna try 64bit next, and if that doesn't work, centos dom0 :( > Is *anyone* out there running 32bit f8 dom0 and f9 domU without > problems?! > -matt I'm continuing to run 64b F8 dom0 and F9 domU without any need to reboot the dom0 after bouncing a domU, but I do have to restart xend. My problem also affects F8 domUs. I've noticed, it seems, if I use xm commands to shutdown and startup then virt-manager retains track of the domU. https://bugzilla.redhat.com/show_bug.cgi?id=453276 The last 2 libvirt updates have not been built for F8, so I'm not sure if there is any progress on the issue. https://www.redhat.com/archives/libvir-list/2008-September/msg00401.html I'm not interested in switching to CentOS or RHEL until I'm "forced" by circumstances or rationality. I'd prefer to support Fedora. Theoretically F8 still gets updates until around Dec, 25 2008 right now. https://fedoraproject.org/wiki/Schedule#Fedora_10_Release_Schedule There is a lot of impressive work going on with libvirt and virt in general from RedHat/Fedora, so I'm trying to be patient. I have a tenable workaround for now. Fingers crossed for F10. -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From david at hlacik.eu Tue Sep 30 19:25:45 2008 From: david at hlacik.eu (=?ISO-8859-2?Q?David_Hl=E1=E8ik?=) Date: Tue, 30 Sep 2008 21:25:45 +0200 Subject: [Fedora-xen] xen kernel with dom0 in Fedora 10? Message-ID: Hi , guys, I have found in Fedora 10 Features , that there is still a lot of work to provide xen kernel with dom0 support to Fedora 10 GA. For my future project, which at 90 percent depends on virtualization technology I am deciding between XEN or KVM virtualization. I am experienced XEN user, KVM is new for me. But as I am aware of, Qumranet was bought by RedHat which predicts something ... Thanks in advance! David From berrange at redhat.com Tue Sep 30 19:54:23 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 30 Sep 2008 20:54:23 +0100 Subject: [Fedora-xen] xen kernel with dom0 in Fedora 10? In-Reply-To: References: Message-ID: <20080930195423.GB15434@redhat.com> On Tue, Sep 30, 2008 at 09:25:45PM +0200, David Hl??ik wrote: > Hi , guys, I have found in Fedora 10 Features , that there is still a > lot of work to provide xen kernel with dom0 support to Fedora 10 GA. > For my future project, which at 90 percent depends on virtualization > technology I am deciding between XEN or KVM virtualization. I am > experienced XEN user, KVM is new for me. But as I am aware of, > Qumranet was bought by RedHat which predicts something ... There is pretty much zero chance that Fedora 10 will include a Xen Dom0 host. While upstream Xen developers are making good progress on porting Dom0 to paravirt_ops, there is simply too little time for this to be ready for Fedora 10. So if you need to use Fedora 10 as a host, then KVM is your only viable option at this time. If you can wait for Fedora 11 (or use RHEL-5 / CentOS-5) then Xen may be an option for you. I'll let other people comment on the pros/cons of Xen vs KVM outside the kernel availability issue. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From beres.laszlo at sys-admin.hu Tue Sep 30 20:15:43 2008 From: beres.laszlo at sys-admin.hu (Laszlo BERES) Date: Tue, 30 Sep 2008 22:15:43 +0200 Subject: [Fedora-xen] xen kernel with dom0 in Fedora 10? In-Reply-To: <20080930195423.GB15434@redhat.com> References: <20080930195423.GB15434@redhat.com> Message-ID: <48E288EF.8070804@sys-admin.hu> Daniel P. Berrange ?rta: > for this to be ready for Fedora 10. So if you need to use Fedora 10 > as a host, then KVM is your only viable option at this time. If > you can wait for Fedora 11 (or use RHEL-5 / CentOS-5) then Xen may > be an option for you. I'll let other people comment on the pros/cons > of Xen vs KVM outside the kernel availability issue. Aren't you planning to extend the lifecycle of Fedora 8 as the last available version with dom0 support? -- L?szl? B?RES RHCE, RHCX senior IT engineer, trainer Red Hat, Fedora, CentOS, SELinux: http://sys-admin.hu From berrange at redhat.com Tue Sep 30 20:26:49 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 30 Sep 2008 21:26:49 +0100 Subject: [Fedora-xen] xen kernel with dom0 in Fedora 10? In-Reply-To: <48E288EF.8070804@sys-admin.hu> References: <20080930195423.GB15434@redhat.com> <48E288EF.8070804@sys-admin.hu> Message-ID: <20080930202649.GE15434@redhat.com> On Tue, Sep 30, 2008 at 10:15:43PM +0200, Laszlo BERES wrote: > Daniel P. Berrange ?rta: > > >for this to be ready for Fedora 10. So if you need to use Fedora 10 > >as a host, then KVM is your only viable option at this time. If > >you can wait for Fedora 11 (or use RHEL-5 / CentOS-5) then Xen may > >be an option for you. I'll let other people comment on the pros/cons > >of Xen vs KVM outside the kernel availability issue. > > Aren't you planning to extend the lifecycle of Fedora 8 as the last > available version with dom0 support? Extending the Fedora 8 lifecycle would impose an extra support burden on all Fedora package maintainers that is not really practical. If you need a long term deployable Xen host, then really you should be looking at RHEL-5 or CentOS-5 depending on whether you need commercial support (RHEL) or not (CentOS). Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From Jean-Noel.Chardron at dr15.cnrs.fr Tue Sep 30 21:27:16 2008 From: Jean-Noel.Chardron at dr15.cnrs.fr (Jean-Noel Chardron) Date: Tue, 30 Sep 2008 23:27:16 +0200 Subject: [Fedora-xen] xen kernel with dom0 in Fedora 10? In-Reply-To: <20080930202649.GE15434@redhat.com> References: <20080930195423.GB15434@redhat.com> <48E288EF.8070804@sys-admin.hu> <20080930202649.GE15434@redhat.com> Message-ID: <48E299B4.5070208@dr15.cnrs.fr> Daniel P. Berrange a ?crit : > On Tue, Sep 30, 2008 at 10:15:43PM +0200, Laszlo BERES wrote: > >> Daniel P. Berrange ?rta: >> >> >>> for this to be ready for Fedora 10. So if you need to use Fedora 10 >>> as a host, then KVM is your only viable option at this time. If >>> you can wait for Fedora 11 (or use RHEL-5 / CentOS-5) then Xen may >>> be an option for you. I'll let other people comment on the pros/cons >>> of Xen vs KVM outside the kernel availability issue. >>> >> Aren't you planning to extend the lifecycle of Fedora 8 as the last >> available version with dom0 support? >> > > Extending the Fedora 8 lifecycle would impose an extra support burden > on all Fedora package maintainers that is not really practical. If you > need a long term deployable Xen host, then really you should be looking > at RHEL-5 or CentOS-5 depending on whether you need commercial support > (RHEL) or not (CentOS). > > Daniel > is there a way to do a upgrade from fedora 8 to RHEL5 or CentOS with the dvdrom of the distribution ? and as I ask about transition from one distribution to another, Is it possible to upgrade in the other side from CentOS-5 to fedora 9 or 10 ? thanks in advance From paul at xelerance.com Tue Sep 30 21:29:03 2008 From: paul at xelerance.com (Paul Wouters) Date: Tue, 30 Sep 2008 17:29:03 -0400 (EDT) Subject: [Fedora-xen] xen kernel with dom0 in Fedora 10? In-Reply-To: <48E299B4.5070208@dr15.cnrs.fr> References: <20080930195423.GB15434@redhat.com> <48E288EF.8070804@sys-admin.hu> <20080930202649.GE15434@redhat.com> <48E299B4.5070208@dr15.cnrs.fr> Message-ID: On Tue, 30 Sep 2008, Jean-Noel Chardron wrote: > > Extending the Fedora 8 lifecycle would impose an extra support burden on all > > Fedora package maintainers that is not really practical. If you > > need a long term deployable Xen host, then really you should be looking > > at RHEL-5 or CentOS-5 depending on whether you need commercial support > > (RHEL) or not (CentOS). > > > > Daniel > > > is there a way to do a upgrade from fedora 8 to RHEL5 or CentOS with the > dvdrom of the distribution ? don't you have your guests on a seperate partition? Then you'd only need that partition and /etc/xen. Your dom0 should not be doing anything else :) Paul From Jean-Noel.Chardron at dr15.cnrs.fr Tue Sep 30 22:06:59 2008 From: Jean-Noel.Chardron at dr15.cnrs.fr (Jean-Noel Chardron) Date: Wed, 01 Oct 2008 00:06:59 +0200 Subject: [Fedora-xen] xen kernel with dom0 in Fedora 10? In-Reply-To: References: <20080930195423.GB15434@redhat.com> <48E288EF.8070804@sys-admin.hu> <20080930202649.GE15434@redhat.com> <48E299B4.5070208@dr15.cnrs.fr> Message-ID: <48E2A303.8080001@dr15.cnrs.fr> Paul Wouters a ?crit : > On Tue, 30 Sep 2008, Jean-Noel Chardron wrote: > > >>> Extending the Fedora 8 lifecycle would impose an extra support burden on all >>> Fedora package maintainers that is not really practical. If you >>> need a long term deployable Xen host, then really you should be looking >>> at RHEL-5 or CentOS-5 depending on whether you need commercial support >>> (RHEL) or not (CentOS). >>> >>> Daniel >>> >>> >> is there a way to do a upgrade from fedora 8 to RHEL5 or CentOS with the >> dvdrom of the distribution ? >> > > don't you have your guests on a seperate partition? Then you'd only need that > partition and /etc/xen. Your dom0 should not be doing anything else :) > I wanted to say upgrade the dom0 not the domU, so I re-ask : Is there a way to upgrade the dom0 from fedora 8 to CentOS ? > Paul > From dlbewley at lib.ucdavis.edu Tue Sep 30 23:06:35 2008 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Tue, 30 Sep 2008 16:06:35 -0700 Subject: [Fedora-xen] xen kernel with dom0 in Fedora 10? In-Reply-To: <48E2A303.8080001@dr15.cnrs.fr> References: <20080930195423.GB15434@redhat.com> <48E288EF.8070804@sys-admin.hu> <20080930202649.GE15434@redhat.com> <48E299B4.5070208@dr15.cnrs.fr> <48E2A303.8080001@dr15.cnrs.fr> Message-ID: <1222815995.10294.10.camel@tofu.lib.ucdavis.edu> On Wed, 2008-10-01 at 00:06 +0200, Jean-Noel Chardron wrote: > I wanted to say upgrade the dom0 not the domU, so I re-ask : Is > there > a way to upgrade the dom0 from fedora 8 to CentOS ? There isn't really a concept of upgrading from on distribution to another. You'll have to migrate by installing a CentOS dom0 and then restore your domU images from backup. -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3