From dlbewley at lib.ucdavis.edu Tue Nov 4 19:06:11 2008 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Tue, 04 Nov 2008 11:06:11 -0800 Subject: [Fedora-xen] libvirt-0.4.6 for Fedora 8 ? In-Reply-To: <49088345.9030206@alamaison.fr> References: <20081029133914.GN7092@redhat.com> <4908705E.3090207@ispbrasil.com.br> <490872EE.5060406@redhat.com> <20081029144140.GG6138@redhat.com> <20081029151635.GT7092@redhat.com> <49088345.9030206@alamaison.fr> Message-ID: <1225825571.15522.19.camel@tofu.lib.ucdavis.edu> On Wed, 2008-10-29 at 16:37 +0100, Maxim Doucet wrote: > Fedora 8 is for now the latest Fedora distribution with a Xen dom0 : > * Fedora 9 doesn't have a dom0 according to > http://fedoraproject.org/wiki/Features/XenPvops#Release_Notes > * the next Fedora with a Xen dom0 will be Fedora 10, according to > http://docs.fedoraproject.org/release-notes/f9/en_US/sn-Virtualization.html > (20.1 Kernel Integration Improvements : "Xen Dom0 support will be added > back in Fedora 10") The relevant F10 release notes are also in progress here: http://fedoraproject.org/wiki/Docs/Beats/Virtualization Dom0 will not be there at release time: http://fedoraproject.org/wiki/FWN/Issue146#No_Dom0_Support_in_Fedora_10 Some Fedora users lack HVM extensions in hardware and are stuck with Xen and F8 for now. I think putting new releases in F8-test-only seems like a nice conservative compromise. I was hoping libvirt 0.4.6 would fix the issue of virsh losing track of domUs until xend is restarted, but after installing the test build on my F8 dom0 I found that wasn't the case. https://bugzilla.redhat.com/show_bug.cgi?id=453276 People can post their experiences with a build in Bodhi. https://admin.fedoraproject.org/updates/search/libvirt -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From stephen.johnston at talktalk.net Tue Nov 4 23:56:08 2008 From: stephen.johnston at talktalk.net (Stephen Johnston) Date: Tue, 04 Nov 2008 23:56:08 +0000 Subject: [Fedora-xen] Turning off virt-manager dhcp and dns Message-ID: <4910E118.1050508@talktalk.net> Hi I have virt-manager with a static ip'ed windows server 2003 and a win xp client so I can play with active directory etc for work. All under Fedora 10 beta. Can someone tell me if I can turn off the dhcp and dns in the virt-manager framework (vibr0) as it is handing out an ip to my client before the virtual windows server does. I believe this is confusing the issue when I try to join the client to my virtual windows domain. I only wish the virt-manager to nat vibr0 to my physical nic so i can provide the other config items from within my virtual network. Thank you. Stephen -- Stephen Johnston 8 Lime Grove Tel. +44 (0)1506 437766 Craigshill Mob. 07786 733 150 Livingston West Lothian EH54 5FB From rodrigomenezes12 at yahoo.com.br Wed Nov 5 00:01:18 2008 From: rodrigomenezes12 at yahoo.com.br (Rodrigo Menezes) Date: Tue, 04 Nov 2008 22:01:18 -0200 Subject: [Fedora-xen] Beginner in Xen In-Reply-To: <4910E118.1050508@talktalk.net> References: <4910E118.1050508@talktalk.net> Message-ID: <4910E24E.6070602@yahoo.com.br> Guys, My name is Rodrigo Menezes, I'm Fedora Ambassador from Brazil and love virtualization. I never used Xen, always worked with VirtualBox, Vmware and MS Virtual Server. Now I'd like to dedicate my time to work with Xen Server. My first assign is to create a leacture to present in events in Brazil, but I wanna start from the begining. Can you provide me some important documentation to start studying? Cheers, Rodrigo Menezes __________________________________________________ Fa?a liga??es para outros computadores com o novo Yahoo! Messenger http://br.beta.messenger.yahoo.com/ From glommer at gmail.com Wed Nov 5 00:04:55 2008 From: glommer at gmail.com (Glauber Costa) Date: Tue, 4 Nov 2008 22:04:55 -0200 Subject: [Fedora-xen] Beginner in Xen In-Reply-To: <4910E24E.6070602@yahoo.com.br> References: <4910E118.1050508@talktalk.net> <4910E24E.6070602@yahoo.com.br> Message-ID: <5d6222a80811041604l371e8f8g14c0dd0a3cd5cf66@mail.gmail.com> On Tue, Nov 4, 2008 at 10:01 PM, Rodrigo Menezes wrote: > Guys, > > My name is Rodrigo Menezes, I'm Fedora Ambassador from Brazil and love > virtualization. I never used Xen, always worked with VirtualBox, Vmware and > MS Virtual Server. Now I'd like to dedicate my time to work with Xen Server. > > My first assign is to create a leacture to present in events in Brazil, but > I wanna start from the begining. Can you provide me some important > documentation to start studying? Sure, http://kvm.qumranet.com/kvmwiki http://virt.kernelnewbies.org/KVM > Cheers, > > Rodrigo Menezes > __________________________________________________ > Fa?a liga??es para outros computadores com o novo Yahoo! Messenger > http://br.beta.messenger.yahoo.com/ > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- Glauber Costa. "Free as in Freedom" http://glommer.net "The less confident you are, the more serious you have to act." From deshantm at gmail.com Wed Nov 5 01:57:00 2008 From: deshantm at gmail.com (Todd Deshane) Date: Tue, 4 Nov 2008 20:57:00 -0500 Subject: [Fedora-xen] Beginner in Xen In-Reply-To: <4910E24E.6070602@yahoo.com.br> References: <4910E118.1050508@talktalk.net> <4910E24E.6070602@yahoo.com.br> Message-ID: <1e16a9ed0811041757x1caa0792v8e728545abe07000@mail.gmail.com> On Tue, Nov 4, 2008 at 7:01 PM, Rodrigo Menezes wrote: > Guys, > > My name is Rodrigo Menezes, I'm Fedora Ambassador from Brazil and love > virtualization. I never used Xen, always worked with VirtualBox, Vmware and > MS Virtual Server. Now I'd like to dedicate my time to work with Xen Server. > > My first assign is to create a leacture to present in events in Brazil, but > I wanna start from the begining. Can you provide me some important > documentation to start studying? > Running Xen: A Hands-on Guide to the Art of Virtualization (http://runningxen.com) http://xen.org http://blog.xen.org http://wiki.xensource.com/xenwiki/ http://wiki.xensource.com/xenwiki/Books (other Xen books) http://runningxen.com/resources http://www.xen.org/community/xensummit.html http://xen.cosi.clarkson.edu/ http://todddeshane.net/research/xen_drive/ Cheers, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com From sakaia at jp.fujitsu.com Wed Nov 5 03:16:36 2008 From: sakaia at jp.fujitsu.com (Atsushi SAKAI) Date: Wed, 05 Nov 2008 12:16:36 +0900 Subject: [Fedora-xen] Beginner in Xen In-Reply-To: <4910E24E.6070602@yahoo.com.br> References: <4910E24E.6070602@yahoo.com.br> Message-ID: <20081105031638.717CC18047@m025.s.css.fujitsu.com> Hello May be you know Xen supports up to Fedora 8. After that, Fedora does not support Xen.(Fedora 9 and 10) More strictly speaking it supports Hypervisor and DomU only, Dom0(Privileged Domain) is not supported. If you want to run Xen on Fedora, You should install upstream Xen manually or wait until "Dom0 paravirt_ops is merged into Linux." Thanks Atsushi SAKAI Rodrigo Menezes wrote: > Guys, > > My name is Rodrigo Menezes, I'm Fedora Ambassador from Brazil and love > virtualization. I never used Xen, always worked with VirtualBox, Vmware > and MS Virtual Server. Now I'd like to dedicate my time to work with Xen > Server. > > My first assign is to create a leacture to present in events in Brazil, > but I wanna start from the begining. Can you provide me some important > documentation to start studying? > > Cheers, > > Rodrigo Menezes > __________________________________________________ > Fa? liga?es para outros computadores com o novo Yahoo! Messenger > http://br.beta.messenger.yahoo.com/ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From deshantm at gmail.com Wed Nov 5 03:25:40 2008 From: deshantm at gmail.com (Todd Deshane) Date: Tue, 4 Nov 2008 22:25:40 -0500 Subject: [Fedora-xen] Beginner in Xen In-Reply-To: <20081105031638.717CC18047@m025.s.css.fujitsu.com> References: <4910E24E.6070602@yahoo.com.br> <20081105031638.717CC18047@m025.s.css.fujitsu.com> Message-ID: <1e16a9ed0811041925s76b7d43bg87ecf691c460752b@mail.gmail.com> 2008/11/4 Atsushi SAKAI : > Hello > > May be you know Xen supports up to Fedora 8. > After that, Fedora does not support Xen.(Fedora 9 and 10) > More strictly speaking it supports Hypervisor and DomU only, > Dom0(Privileged Domain) is not supported. > > If you want to run Xen on Fedora, > You should install upstream Xen manually or > wait until "Dom0 paravirt_ops is merged into Linux." > > Right. Fedora users are encouraged to use CentOS/RHEL. Cheers, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com From maxim at alamaison.fr Wed Nov 5 14:05:12 2008 From: maxim at alamaison.fr (Maxim Doucet) Date: Wed, 05 Nov 2008 15:05:12 +0100 Subject: [Fedora-xen] libvirt-0.4.6 for Fedora 8 ? In-Reply-To: <1225825571.15522.19.camel@tofu.lib.ucdavis.edu> References: <20081029133914.GN7092@redhat.com> <4908705E.3090207@ispbrasil.com.br> <490872EE.5060406@redhat.com> <20081029144140.GG6138@redhat.com> <20081029151635.GT7092@redhat.com> <49088345.9030206@alamaison.fr> <1225825571.15522.19.camel@tofu.lib.ucdavis.edu> Message-ID: <4911A818.1020901@alamaison.fr> Dale Bewley a ?crit : > The relevant F10 release notes are also in progress here: > http://fedoraproject.org/wiki/Docs/Beats/Virtualization > > Dom0 will not be there at release time: > http://fedoraproject.org/wiki/FWN/Issue146#No_Dom0_Support_in_Fedora_10 > Thanks for those links -- Maxim Doucet (maxim at alamaison.fr) sys engineer @ la maison +33 (0)1 41 12 2000 www.alamaison.fr From dlbewley at lib.ucdavis.edu Thu Nov 6 03:49:10 2008 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Wed, 05 Nov 2008 19:49:10 -0800 Subject: [Fedora-xen] Beginner in Xen In-Reply-To: <1e16a9ed0811041925s76b7d43bg87ecf691c460752b@mail.gmail.com> References: <4910E24E.6070602@yahoo.com.br> <20081105031638.717CC18047@m025.s.css.fujitsu.com> <1e16a9ed0811041925s76b7d43bg87ecf691c460752b@mail.gmail.com> Message-ID: <1225943350.3378.3.camel@seitan.home.bewley.net> On Tue, 2008-11-04 at 22:25 -0500, Todd Deshane wrote: > Right. Fedora users are encouraged to use CentOS/RHEL. Making them CentOS/RHEL users. ;) If you need a Fedora dom0, you can keep using F8 until it is EOL, and the updates stop flowing. That should be a month after F10 comes out. If you're lucky, the upstream pv_ops work may be done soon after that time. That's what I'm crossing my fingers for. :) From bill at bfccomputing.com Thu Nov 6 18:09:24 2008 From: bill at bfccomputing.com (Bill McGonigle) Date: Thu, 6 Nov 2008 13:09:24 -0500 Subject: [Fedora-xen] Beginner in Xen In-Reply-To: <1225943350.3378.3.camel@seitan.home.bewley.net> References: <4910E24E.6070602@yahoo.com.br> <20081105031638.717CC18047@m025.s.css.fujitsu.com> <1e16a9ed0811041925s76b7d43bg87ecf691c460752b@mail.gmail.com> <1225943350.3378.3.camel@seitan.home.bewley.net> Message-ID: On Nov 5, 2008, at 10:49 PM, Dale Bewley wrote: > If you're lucky, the upstream pv_ops work may be done soon after that > time. That's what I'm crossing my fingers for. :) I was roughly guessing February on that based on past release schedules. It would be swell if Fedora would at least handle f8 kernel security updates for its Xen users until then (everything else can be moved into domU). I think the solution now is to hope we don't get pwned in the meantime. That's pretty weak. Say, is there a compatibility matrix between RHEL/Fedora dom0 versions and domU's somewhere? I'm trying to move an f8 DomU to Centos 5.2 Dom0, and not having luck yet. I probably ought to verify it's possible before spending too much time on it. -Bill ----- Bill McGonigle, Owner Work: 603.448.4440 BFC Computing, LLC Home: 603.448.1668 bill at bfccomputing.com Cell: 603.252.2606 http://www.bfccomputing.com/ Page: 603.442.1833 Blog: http://blog.bfccomputing.com/ VCard: http://bfccomputing.com/vcard/bill.vcf From pasik at iki.fi Fri Nov 7 08:08:02 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Fri, 7 Nov 2008 10:08:02 +0200 Subject: [Fedora-xen] Beginner in Xen In-Reply-To: References: <4910E24E.6070602@yahoo.com.br> <20081105031638.717CC18047@m025.s.css.fujitsu.com> <1e16a9ed0811041925s76b7d43bg87ecf691c460752b@mail.gmail.com> <1225943350.3378.3.camel@seitan.home.bewley.net> Message-ID: <20081107080802.GA1691@edu.joroinen.fi> On Thu, Nov 06, 2008 at 01:09:24PM -0500, Bill McGonigle wrote: > On Nov 5, 2008, at 10:49 PM, Dale Bewley wrote: > > >If you're lucky, the upstream pv_ops work may be done soon after that > >time. That's what I'm crossing my fingers for. :) > > I was roughly guessing February on that based on past release > schedules. It would be swell if Fedora would at least handle f8 > kernel security updates for its Xen users until then (everything else > can be moved into domU). I think the solution now is to hope we > don't get pwned in the meantime. That's pretty weak. > > Say, is there a compatibility matrix between RHEL/Fedora dom0 > versions and domU's somewhere? I'm trying to move an f8 DomU to > Centos 5.2 Dom0, and not having luck yet. I probably ought to verify > it's possible before spending too much time on it. > I've been running Fedora 8 and Fedora 9 domU's on CentOS 5.x dom0 without any problems. This was x86 32bit PAE. -- Pasi From pasik at iki.fi Wed Nov 12 12:38:37 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 12 Nov 2008 14:38:37 +0200 Subject: [Fedora-xen] [Xen-devel] Re: Status of Xen in vanilla?] / pv_ops dom0 support in Linux Message-ID: <20081112123837.GD1691@edu.joroinen.fi> ----- Forwarded message from Jeremy Fitzhardinge ----- From: Jeremy Fitzhardinge To: LKML Cc: Xen-devel Date: Tue, 11 Nov 2008 10:53:37 -0800 Subject: [Xen-devel] Re: Status of Xen in vanilla? Maximilian Wilhelm wrote: >Hi! > >I'm wondering about the status of Xen support in the vanilla kernel. >I know that DomU support is inside the kernel an evolving, but I did >not find an up-to-date hint about the status of Dom0 support. > >A while ago I read that it should be included in 2.6.28, but I do not >find any current pointer about the status of this. > .28 was a bit optimistic; .29 seems reasonable. The current dom0 kernel patches can boot up to a fully functional dom0 usersmode, and you can start xend to see that domain 0 is running. I *think* in theory you can create a deviceless domain, but I haven't tried it. I'm currently working on blktap support. I really need to put together a proper status update. Now that dom0 usermode is working, its a much better base for other people start contributing. J _______________________________________________ Xen-devel mailing list Xen-devel at lists.xensource.com http://lists.xensource.com/xen-devel ----- End forwarded message ----- From guillaume.chardin at gmail.com Thu Nov 13 14:34:03 2008 From: guillaume.chardin at gmail.com (Guillaume) Date: Thu, 13 Nov 2008 15:34:03 +0100 Subject: [Fedora-xen] supported vt hardware Message-ID: hi, Maybe someone can help me choosing new hardware for xen hvm test. I need a motherboard fully suportting intel vt with intel "core 2 quad processor". Does someone already using some recent hardware and was able to correctly set-up this kind of things, and can give me some advices. for information, in the end, my computer will run linux as dom0, 1 domU (debian) and 2 windows OS. thanks. -- Guillaume From bill at bfccomputing.com Thu Nov 13 19:54:08 2008 From: bill at bfccomputing.com (Bill McGonigle) Date: Thu, 13 Nov 2008 14:54:08 -0500 Subject: [Fedora-xen] supported vt hardware In-Reply-To: References: Message-ID: <491C85E0.4050006@bfccomputing.com> Guillaume wrote: > Maybe someone can help me choosing new hardware for xen hvm test. > I need a motherboard fully suportting intel vt with intel "core 2 quad > processor". Does someone already using some recent hardware and was > able to correctly set-up this kind of things, and can give me some > advices. I just put into production a new low-power (65-105W) 1/2U server I built using the SuperMicro X7SBA: http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&DEPA=0&Order=BESTMATCH&Description=supermicro+x7sba&x=0&y=0 and a 45nm Core2Duo. Centos 5.2 Dom0, DomU is Fedora 8 (for the moment). I haven't tried any of the Hyper-V stuff yet, but it's supported in the BIOS and detected by Xen. The latest BIOS update is essential for proper disk geometry detection. -Bill From pasik at iki.fi Thu Nov 13 20:07:32 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 13 Nov 2008 22:07:32 +0200 Subject: [Fedora-xen] [PATCH 00 of 38] xen: add more Xen dom0 support Message-ID: <20081113200731.GI1691@edu.joroinen.fi> ----- Forwarded message from Jeremy Fitzhardinge ----- From: Jeremy Fitzhardinge To: Ingo Molnar Cc: linux-kernel at vger.kernel.org, Xen-devel , the arch/x86 maintainers , Ian Campbell Date: Thu, 13 Nov 2008 11:09:58 -0800 Subject: [PATCH 00 of 38] xen: add more Xen dom0 support Hi Ingo, Here's the chunk of patches to add Xen Dom0 support (it's probably worth creating a new xen/dom0 topic branch for it). A dom0 Xen domain is basically the same as a normal domU domain, but it has extra privileges to directly access hardware. There are two issues to deal with: - translating to and from the domain's pseudo-physical addresses and real machine addresses (for ioremap and setting up DMA) - routing hardware interrupts into the domain ioremap is relatively easy to deal with. An earlier patch introduced the _PAGE_IOMAP pte flag, which we use to distinguish between a regular pseudo-physical mapping and a real machine mapping. Everything falls out pretty cleanly. A consequence is that the various pieces of table-parsing code - DMI, ACPI, MP, etc - work out of the box. Similarly, the series adds hooks into swiotlb so that architectures can allocate the swiotlb memory appropriately; on the x86/xen side, Xen hooks these allocation functions to make special hypercalls to guarantee that the allocated memory is contiguous in machine memory. Interrupts are a very different affair. The descriptions in each patch describe how it all fits together in detail, but the overview is: 1. Xen owns the local APICs; the dom0 kernel controls the IO APICs 2. Hardware interrupts are delivered on event channels like everything else 3. To set this up, we intercept at pcibios_enable_irq: - given a dev+pin, we use ACPI to get a gsi - hook acpi_register_gsi to call xen_register_gsi, which - allocates an irq (generally not 1:1 with the gsi) - asks Xen for a vector and event channel for the irq - program the IO APIC to deliver the hardware interrupt to the allocated vector The upshot is that the device driver gets an irq, and when the hardware raises an interrupt, it gets delivered on that irq. We maintain our own irq allocation space, since the hardware-bound event channel irqs are intermixed with all the other normal Xen event channel irqs (inter-domain, timers, IPIs, etc). For compatibility the irqs 0-15 are reserved for legacy device interrupts, but the rest of the range is dynamically allocated. Initialization also requires care. The dom0 kernel parses the ACPI tables as usual, in order to discover the local and IO APICs, and all the rest of the ACPI-provided data the kernel requires. However, because the kernel doesn't own the local APICs and can't directly map the IO APICs, we must be sure to avoid actually touching the hardware when running under Xen. TODO: work out how to fit MSI into all this. So, in summary, this series contains: - dom0 console support - dom0 xenbus support - CPU features and IO access for a privleged domain - mtrrs - making ioremap work on machine addresses - swiotlb allocation hooks - interrupts - introduce PV io_apic operations - add Xen-specific IRQ allocator - switch to using all-Xen event delivery - add pirq Xen interrupt type - table parsing and setup - intercept driver interrupt registration All this code will compile away to nothing when CONFIG_XEN_DOM0 is not enabled. If it is enabled, it will only have an effect if booted as a dom0 kernel; normal native execution and domU execution should be unaffected. Thanks, J -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo at vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ----- End forwarded message ----- From cto at hostbigger.com Sat Nov 15 06:08:44 2008 From: cto at hostbigger.com (HostBigger Admin) Date: Fri, 14 Nov 2008 23:08:44 -0700 Subject: [Fedora-xen] New to Xen - Need Help Please! Message-ID: <200811150625.mAF6PAfE012568@mx3.redhat.com> Hello All: I am new to Xen and have been having some problems getting it running. I had posted on the xen-users list but they recommended that I direct my questions to this list. So I apologize if this is misdirected. I am just trying to find a solution to the issue I am having. I have read and followed several tutorials and tried different fixes for this issue but have had no luck. Here is my server setup first: Dual Core - Dual Processor Xeon 5120 2GB RAM Virtualization support in bios is enabled CentOS 5.2 No direct console access, only remote access via SSH2 I have used the tutorial located at http://www.howtoforge.com/centos_5.0_xen Everything works up until I run virt-install to create the domU. I run virt-install with the -nographics switch and get the following No console available for domain Domain installation still in progress. You can reconnect to the console to complete the installation process. I then tried to connect to the console using Xm console 5 And I get: xenconsole: Could not read tty from store: No such file or directory I looked at the qemu log in /var/log/xen And this is what I see domid: 5 qemu: the number of cpus is 1 *** image /local/domain/0/backend/vbd/5/768 format raw driver 0x80e7940 *** image /local/domain/0/backend/vbd/5/5632 format raw driver 0x80e7940 Watching /local/domain/5/logdirty/next-active Could not initialize SDL - exiting I am however unable to find any information on this error. So basically I am in need of help in getting a domU started and running. Can someone please give me some advice, point me in the right direction etc? Thanks in advance Jason -------------- next part -------------- An HTML attachment was scrubbed... URL: From crobinso at redhat.com Mon Nov 17 17:19:48 2008 From: crobinso at redhat.com (Cole Robinson) Date: Mon, 17 Nov 2008 12:19:48 -0500 Subject: [Fedora-xen] New to Xen - Need Help Please! In-Reply-To: <200811150625.mAF6PAfE012568@mx3.redhat.com> References: <200811150625.mAF6PAfE012568@mx3.redhat.com> Message-ID: <4921A7B4.5000606@redhat.com> HostBigger Admin wrote: > Hello All: > > I am new to Xen and have been having some problems getting it running. I had > posted on the xen-users list but they recommended that I direct my questions > to this list. So I apologize if this is misdirected. I am just trying to > find a solution to the issue I am having. I have read and followed several > tutorials and tried different fixes for this issue but have had no luck. > > Here is my server setup first: > > Dual Core - Dual Processor Xeon 5120 > 2GB RAM > Virtualization support in bios is enabled > CentOS 5.2 > No direct console access, only remote access via SSH2 > > I have used the tutorial located at http://www.howtoforge.com/centos_5.0_xen > > Everything works up until I run virt-install to create the domU. I run > virt-install with the -nographics switch and get the following > > No console available for domain > > Domain installation still in progress. You can reconnect to the console to > complete the installation process. > > > I then tried to connect to the console using > > Xm console 5 > > > And I get: > > xenconsole: Could not read tty from store: No such file or directory > > I looked at the qemu log in /var/log/xen > > And this is what I see > > domid: 5 > > qemu: the number of cpus is 1 > > *** image /local/domain/0/backend/vbd/5/768 format raw driver > 0x80e7940 > > *** image /local/domain/0/backend/vbd/5/5632 format raw driver > 0x80e7940 Watching /local/domain/5/logdirty/next-active > > Could not initialize SDL - exiting > This is actually a known bug: xen doesn't abide nographics and tries to init SDL. This will almost always fail if run through 5.2 libvirt. This bug will be fixed in 5.3. What you can try in the interim is specify --vnc to the virt-install command line. This should prevent the guest from crashing, and you can continue as normal with 'xm console' which should just work for a PV guest. - Cole From pasik at iki.fi Fri Nov 21 15:51:00 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Fri, 21 Nov 2008 17:51:00 +0200 Subject: [Fedora-xen] [Xen-devel] Linux 2.6.27 temporary tree on xenbits Message-ID: <20081121155100.GN1691@edu.joroinen.fi> ----- Forwarded message from Keir Fraser ----- From: Keir Fraser To: "xen-devel at lists.xensource.com" Cc: "Dugger, Donald D" Date: Fri, 21 Nov 2008 13:02:26 +0000 Subject: [Xen-devel] Linux 2.6.27 temporary tree on xenbits As a stop-gap measure until full dom0 support is ready in pv_ops, I've placed a Linux 2.6.27 tree at http://xenbits.xensource.com/ext/linux-2.6.27-xen.hg Actually this is a Novell-patched 2.6.27 kernel -- see 00-README in the repo for more details. The intention is to give a single source tree to develop and test against for those developers who need a more modern 2.6 kernel for advanced platform work such as power management. Regular test and maintenance will continue to focus on 2.6.18, with a grand switchover when pv_ops in kernel.org is considered sufficiently ready. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel at lists.xensource.com http://lists.xensource.com/xen-devel ----- End forwarded message ----- From dlbewley at lib.ucdavis.edu Sat Nov 22 21:21:35 2008 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Sat, 22 Nov 2008 13:21:35 -0800 Subject: [Fedora-xen] Fedora 10 Release and Virtualization News Message-ID: <1227388895.6032.35.camel@seitan.home.bewley.net> Sorry for the annoying cross post. The next Fedora Weekly News[1] will be published Monday, one day before the release of Fedora 10. I would like dedicate a special section of the Virtualization Beat[2] to touting the advances and new features in F10. As with the release notes[3], I am seeking your input. (A little late, I know.) I'm interested not only in the new virtualization features and breakthroughs found in the F10 release, but also any updates that might be right around the corner in f10-updates. Perhaps you have some special insight into the upstream progress of pv_ops, or maybe you know about a almost complete implementation of a libvirt API feature into virt-manager or... I'm sorry if this is a little scattershot. For sometime, I've considered trying to present questions in interview style to each of these lists, but I just haven't gotten that together. The publication deadline is Sunday night, but I'll be able to use anything in the next edition of FWN. Please contribute, even if you read this on Monday. [1] http://fedoraproject.org/wiki/FWN [2] http://fedoraproject.org/wiki/FWN/Beats/Virtualization [3] http://fedoraproject.org/wiki/Docs/Beats/Virtualization -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From fcxen at itsbeen.sent.com Tue Nov 25 20:58:17 2008 From: fcxen at itsbeen.sent.com (fcxen user) Date: Tue, 25 Nov 2008 12:58:17 -0800 Subject: [Fedora-xen] Fedora 10 Release and Virtualization News In-Reply-To: <1227388895.6032.35.camel@seitan.home.bewley.net> References: <1227388895.6032.35.camel@seitan.home.bewley.net> Message-ID: <492C66E9.80905@itsbeen.sent.com> Hi, Dale, great stuff. This question is a little late for your release, but I know it will be coming up alot soon, so I hope you can add it to your docs: Is it possible to run a Fedora 10 pv domU on a Fedora 8 dom0 ? And if it is, what steps are necessary to be able to install the F10 domU with virt-install and manage it with xm/virsh/etc that differ from what is required to do the same for F7/8/9,etc domUs? With the standard yum package: python-virtinst-0.300.2-4.fc8 one gets: ValueError: Invalid URL location given: http://mirror.x.y/pub/fedora/linux/releases/10/Fedora/x86_64/os/images/xen/vmlinuz [Errno 14] HTTP Error 404: Not Found when trying to install a Fedora 10 domU due to the integration of the Xen kernel with the normal kernel and virt-install not knowing where to get the kernel. (AFAIK) Also, as the December EOL for Fedora 8 gets closer, people will have more questions about their options for dom0s - maybe people could submit pros and cons for each option and it could be added to the wiki (maybe as a table/matrix) - so that there is one place to refer people to when the questions arise. Thanks. Dale Bewley wrote: > Sorry for the annoying cross post. > > The next Fedora Weekly News[1] will be published Monday, one day before > the release of Fedora 10. I would like dedicate a special section of the > Virtualization Beat[2] to touting the advances and new features in F10. > > As with the release notes[3], I am seeking your input. (A little late, I > know.) I'm interested not only in the new virtualization features and > breakthroughs found in the F10 release, but also any updates that might > be right around the corner in f10-updates. > > Perhaps you have some special insight into the upstream progress of > pv_ops, or maybe you know about a almost complete implementation of a > libvirt API feature into virt-manager or... > > I'm sorry if this is a little scattershot. For sometime, I've considered > trying to present questions in interview style to each of these lists, > but I just haven't gotten that together. > > The publication deadline is Sunday night, but I'll be able to use > anything in the next edition of FWN. Please contribute, even if you read > this on Monday. > > [1] http://fedoraproject.org/wiki/FWN > [2] http://fedoraproject.org/wiki/FWN/Beats/Virtualization > [3] http://fedoraproject.org/wiki/Docs/Beats/Virtualization > > -- > Dale Bewley - Unix Administrator - Shields Library - UC Davis > GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From franz.vonhahn at yahoo.de Tue Nov 25 21:12:50 2008 From: franz.vonhahn at yahoo.de (Franz Von Hahn) Date: Tue, 25 Nov 2008 21:12:50 +0000 (GMT) Subject: AW: [Fedora-xen] Fedora 10 Release and Virtualization News References: <1227388895.6032.35.camel@seitan.home.bewley.net> <492C66E9.80905@itsbeen.sent.com> Message-ID: <353341.19962.qm@web28211.mail.ukl.yahoo.com> Hey! You could propably use CentOS 5.2 als a dom0. It is shipped with a kernel-xen package 2.6.18.x. It works fine for me but i haven't tried F10 so far since i'm acutally downloading the iso image of F10 which takes a long time when using a 1024kpb/s line, you know ;) Combinations known to work: Dom0: kernel-xen-2.6.21 from Fedora 8 --- or --- kernel-xen-2.6.18 from CentOS 5.2 DomU: Fedora 6 Fedora 7 Fedora 8 Fedora 9 CentOS 5.2 ----- Urspr?ngliche Mail ---- Von: fcxen user An: Dale Bewley CC: libvir-list at redhat.com; et-mgmt-tools at redhat.com; fedora-xen at redhat.com Gesendet: Dienstag, den 25. November 2008, 21:58:17 Uhr Betreff: Re: [Fedora-xen] Fedora 10 Release and Virtualization News Hi, Dale, great stuff. This question is a little late for your release, but I know it will be coming up alot soon, so I hope you can add it to your docs: Is it possible to run a Fedora 10 pv domU on a Fedora 8 dom0 ? And if it is, what steps are necessary to be able to install the F10 domU with virt-install and manage it with xm/virsh/etc that differ from what is required to do the same for F7/8/9,etc domUs? With the standard yum package: python-virtinst-0.300.2-4.fc8 one gets: ValueError: Invalid URL location given: http://mirror.x.y/pub/fedora/linux/releases/10/Fedora/x86_64/os/images/xen/vmlinuz [Errno 14] HTTP Error 404: Not Found when trying to install a Fedora 10 domU due to the integration of the Xen kernel with the normal kernel and virt-install not knowing where to get the kernel. (AFAIK) Also, as the December EOL for Fedora 8 gets closer, people will have more questions about their options for dom0s - maybe people could submit pros and cons for each option and it could be added to the wiki (maybe as a table/matrix) - so that there is one place to refer people to when the questions arise. Thanks. Dale Bewley wrote: > Sorry for the annoying cross post. > > The next Fedora Weekly News[1] will be published Monday, one day before > the release of Fedora 10. I would like dedicate a special section of the > Virtualization Beat[2] to touting the advances and new features in F10. > > As with the release notes[3], I am seeking your input. (A little late, I > know.) I'm interested not only in the new virtualization features and > breakthroughs found in the F10 release, but also any updates that might > be right around the corner in f10-updates. > > Perhaps you have some special insight into the upstream progress of > pv_ops, or maybe you know about a almost complete implementation of a > libvirt API feature into virt-manager or... > > I'm sorry if this is a little scattershot. For sometime, I've considered > trying to present questions in interview style to each of these lists, > but I just haven't gotten that together. > > The publication deadline is Sunday night, but I'll be able to use > anything in the next edition of FWN. Please contribute, even if you read > this on Monday. > > [1] http://fedoraproject.org/wiki/FWN > [2] http://fedoraproject.org/wiki/FWN/Beats/Virtualization > [3] http://fedoraproject.org/wiki/Docs/Beats/Virtualization > > -- > Dale Bewley - Unix Administrator - Shields Library - UC Davis > GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From pasik at iki.fi Tue Nov 25 21:44:40 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 25 Nov 2008 23:44:40 +0200 Subject: [Fedora-xen] Updating out-of-date Fedora XenPvopsDom0 wiki page Message-ID: <20081125214440.GH15052@edu.joroinen.fi> Hi! http://fedoraproject.org/wiki/Features/XenPvopsDom0 Could someone with wiki access update that page.. it contains a lot of out-of-date information. That page is also referenced in F10 release notes.. Things like: - "Work on getting Dom0 support in the upstream kernel has pretty much stalled for the last number of months so this feature is postponed until work upstream restarts." - "Last updated: 2008-07-30" - "x86_64 Dom0 No active work yet...." And many more things are out-of-date, because they're based on earlier work by Redhat/Fedora people.. Upstream (Xensource) is actively working on pv_ops dom0 now, and it's getting close to being included upstream. latest pv_ops dom0 patches: http://xenbits.xen.org/paravirt_ops/patches.hg/ Xen wiki pv_ops status page: http://wiki.xensource.com/xenwiki/XenParavirtOps -- Pasi From dlbewley at lib.ucdavis.edu Tue Nov 25 22:23:11 2008 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Tue, 25 Nov 2008 14:23:11 -0800 Subject: [Fedora-xen] Updating out-of-date Fedora XenPvopsDom0 wiki page In-Reply-To: <20081125214440.GH15052@edu.joroinen.fi> References: <20081125214440.GH15052@edu.joroinen.fi> Message-ID: <1227651791.28887.2.camel@tofu.lib.ucdavis.edu> I quickly made the changes you pointed out. I can give it some more love a little later. Thanks -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From dlbewley at lib.ucdavis.edu Wed Nov 26 02:39:12 2008 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Tue, 25 Nov 2008 18:39:12 -0800 Subject: [Fedora-xen] Updating out-of-date Fedora XenPvopsDom0 wiki page In-Reply-To: <20081125214440.GH15052@edu.joroinen.fi> References: <20081125214440.GH15052@edu.joroinen.fi> Message-ID: <1227667152.28887.26.camel@tofu.lib.ucdavis.edu> I made a few more changes to the "Current Status" section. Note it is still at a seemingly arbitrary 30% complete. I didn't try to touch the details under "Scope". Pasi, are you saying the status and scope details are obsolete and the work previously done at redhat (and enumerated on this page) is now done at xensource? If so, can you provide more details to replace what's on this page? Are the feature owners working on these kernel patches? Is this totally upstream, and outside of Fedora until committed to the kernel? If the feature owners could provide a more thorough update of this page, it may be helpful to users. http://fedoraproject.org/wiki/Features/XenPvopsDom0 -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From pasik at iki.fi Wed Nov 26 09:16:58 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 26 Nov 2008 11:16:58 +0200 Subject: [Fedora-xen] Updating out-of-date Fedora XenPvopsDom0 wiki page In-Reply-To: <1227667152.28887.26.camel@tofu.lib.ucdavis.edu> References: <20081125214440.GH15052@edu.joroinen.fi> <1227667152.28887.26.camel@tofu.lib.ucdavis.edu> Message-ID: <20081126091658.GI15052@edu.joroinen.fi> On Tue, Nov 25, 2008 at 06:39:12PM -0800, Dale Bewley wrote: > I made a few more changes to the "Current Status" section. Note it is > still at a seemingly arbitrary 30% complete. > Good. > I didn't try to touch the details under "Scope". > Yep. Also I think the "i386 Dom0" chapter is out of date.. it is not based on the current patches. "Status update" two weeks ago or so: http://lists.xensource.com/archives/html/xen-devel/2008-11/msg00205.html "The current dom0 kernel patches can boot up to a fully functional dom0 usersmode, and you can start xend to see that domain 0 is running. I *think* in theory you can create a deviceless domain, but I haven't tried it. I'm currently working on blktap support." So maybe remove both the "i386 dom0" and "x86_64 Dom0" chapters and replace them with something more up to date.. > Pasi, are you saying the status and scope details are obsolete and the > work previously done at redhat (and enumerated on this page) is now done > at xensource? If so, can you provide more details to replace what's on > this page? > Yes, that's what I'm saying. Afaik "Scope" is based on earlier work by redhat/fedora, and most of that information is now obsolete. Jeremy Fitzhardinge of Xensource is now working on completing Xen pv_ops dom0 support. Afaik it was started from the work done by redhat/fedora. pv_ops dom0 patches posted to lkml by Jeremy Fitzhardinge: http://lkml.org/lkml/2008/11/13/272 > Are the feature owners working on these kernel patches? Is this totally > upstream, and outside of Fedora until committed to the kernel? > Afaik it is totally upstream now.. ie. Xensource is doing this work, and Fedora is just waiting for upstream (vanilla) Linux kernels to get this support merged in.. > If the feature owners could provide a more thorough update of this page, > it may be helpful to users. > > http://fedoraproject.org/wiki/Features/XenPvopsDom0 > Yep, it would be nice to get comments from others too. And thanks to you for updating the page! -- Pasi From markmc at redhat.com Wed Nov 26 09:34:17 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Wed, 26 Nov 2008 09:34:17 +0000 Subject: [Fedora-xen] Updating out-of-date Fedora XenPvopsDom0 wiki page In-Reply-To: <20081126091658.GI15052@edu.joroinen.fi> References: <20081125214440.GH15052@edu.joroinen.fi> <1227667152.28887.26.camel@tofu.lib.ucdavis.edu> <20081126091658.GI15052@edu.joroinen.fi> Message-ID: <1227692057.9579.29.camel@blaa> Hi, Thanks for poking at this - I've updated the page to remove any tracking of the in-progress kernel support, since it's all better tracked elsewhere now. My advice to anyone wanting to help this along is to build and test Jeremy's work and iron out any issues with Fedora's xen userland running on it. Apart from the upstream kernel work, we also need to make sure that the hypervisor can boot bzImage kernels. Currently only the libxc DomU domain builder has bzImage support. The issue with Dom0 is the hypervisor currently doesn't gunzip the vmlinuz kernel ... it's actually grub that does that but it doesn't make sense for grub to gunzip bzImage kernels. The only Fedora specific piece remaining is to add a way for new-kernel-pkg to know that it should set up grub.conf with xen.gz. Thanks, Mark. From pasik at iki.fi Wed Nov 26 09:48:23 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 26 Nov 2008 11:48:23 +0200 Subject: [Fedora-xen] Updating out-of-date Fedora XenPvopsDom0 wiki page In-Reply-To: <1227692057.9579.29.camel@blaa> References: <20081125214440.GH15052@edu.joroinen.fi> <1227667152.28887.26.camel@tofu.lib.ucdavis.edu> <20081126091658.GI15052@edu.joroinen.fi> <1227692057.9579.29.camel@blaa> Message-ID: <20081126094823.GJ15052@edu.joroinen.fi> On Wed, Nov 26, 2008 at 09:34:17AM +0000, Mark McLoughlin wrote: > Hi, > Thanks for poking at this - I've updated the page to remove any > tracking of the in-progress kernel support, since it's all better > tracked elsewhere now. > Ok. Although "i386 Dom0", "x86_64 Dom0" and "Scope" sections still need heavy editing.. Also, it might be a good idea to mention about this temporary Linux 2.6.27 Xenlinux repository with dom0 support included (with a patch from Suse): http://xenbits.xensource.com/ext/linux-2.6.27-xen.hg That 2.6.27 kernel is NOT based on pv_ops, but to a forward-port from 2.6.18 Xenlinux kernel. It is just a temporary tree until pv_ops dom0 is ready. Announcement about that temporary 2.6.27 Xenlinux tree: http://lists.xensource.com/archives/html/xen-devel/2008-11/msg00600.html > My advice to anyone wanting to help this along is to build and test > Jeremy's work and iron out any issues with Fedora's xen userland running > on it. > Yes, that would be a good idea. Does someone want to build some testing RPMs? :) -- Pasi From markmc at redhat.com Wed Nov 26 09:57:26 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Wed, 26 Nov 2008 09:57:26 +0000 Subject: [Fedora-xen] Updating out-of-date Fedora XenPvopsDom0 wiki page In-Reply-To: <20081126094823.GJ15052@edu.joroinen.fi> References: <20081125214440.GH15052@edu.joroinen.fi> <1227667152.28887.26.camel@tofu.lib.ucdavis.edu> <20081126091658.GI15052@edu.joroinen.fi> <1227692057.9579.29.camel@blaa> <20081126094823.GJ15052@edu.joroinen.fi> Message-ID: <1227693446.9579.38.camel@blaa> On Wed, 2008-11-26 at 11:48 +0200, Pasi K?rkk?inen wrote: > On Wed, Nov 26, 2008 at 09:34:17AM +0000, Mark McLoughlin wrote: > > Hi, > > Thanks for poking at this - I've updated the page to remove any > > tracking of the in-progress kernel support, since it's all better > > tracked elsewhere now. > > > > Ok. > > Although "i386 Dom0", "x86_64 Dom0" and "Scope" sections still need heavy > editing.. I removed them - maybe you missed my updates? > Also, it might be a good idea to mention about this temporary Linux 2.6.27 > Xenlinux repository with dom0 support included (with a patch from Suse): > > http://xenbits.xensource.com/ext/linux-2.6.27-xen.hg > > That 2.6.27 kernel is NOT based on pv_ops, but to a forward-port from 2.6.18 > Xenlinux kernel. It is just a temporary tree until pv_ops dom0 is ready. > > Announcement about that temporary 2.6.27 Xenlinux tree: > http://lists.xensource.com/archives/html/xen-devel/2008-11/msg00600.html It's not really relevant to Fedora - we're not going back to the bad old days of having a separate Xen kernel. We made the call in Fedora 9 to no longer waste effort on any forwarded ported 2.6.18 tree and focus all efforts on upstream pv_ops, since that's where the future lies. Personally, I'm disappointed to see this linux-2.6.27-xen.hg tree appear. Any effort invested in this tree is effort that could be spent on helping with the upstream pv_ops work. > > My advice to anyone wanting to help this along is to build and test > > Jeremy's work and iron out any issues with Fedora's xen userland running > > on it. > > > > Yes, that would be a good idea. > > Does someone want to build some testing RPMs? :) A volunteer to do this would be very welcome indeed :-) Cheers, Mark. From m.a.young at durham.ac.uk Wed Nov 26 10:06:36 2008 From: m.a.young at durham.ac.uk (M A Young) Date: Wed, 26 Nov 2008 10:06:36 +0000 (GMT) Subject: AW: [Fedora-xen] Fedora 10 Release and Virtualization News In-Reply-To: <353341.19962.qm@web28211.mail.ukl.yahoo.com> References: <1227388895.6032.35.camel@seitan.home.bewley.net> <492C66E9.80905@itsbeen.sent.com> <353341.19962.qm@web28211.mail.ukl.yahoo.com> Message-ID: On Tue, 25 Nov 2008, Franz Von Hahn wrote: > You could propably use CentOS 5.2 als a dom0. It is shipped with a > kernel-xen package 2.6.18.x. It works fine for me but i haven't tried > F10 so far since i'm acutally downloading the iso image of F10 which > takes a long time when using a 1024kpb/s line, you know ;) I believe you need Centos 5.3 for F10 xen guest clients which, as RHEL5.3 beta has only just appeared, probably won't be available until after Fedora 8 has EOLed. Michael Young From pasik at iki.fi Wed Nov 26 10:17:56 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 26 Nov 2008 12:17:56 +0200 Subject: [Fedora-xen] Updating out-of-date Fedora XenPvopsDom0 wiki page In-Reply-To: <1227693446.9579.38.camel@blaa> References: <20081125214440.GH15052@edu.joroinen.fi> <1227667152.28887.26.camel@tofu.lib.ucdavis.edu> <20081126091658.GI15052@edu.joroinen.fi> <1227692057.9579.29.camel@blaa> <20081126094823.GJ15052@edu.joroinen.fi> <1227693446.9579.38.camel@blaa> Message-ID: <20081126101756.GL15052@edu.joroinen.fi> On Wed, Nov 26, 2008 at 09:57:26AM +0000, Mark McLoughlin wrote: > On Wed, 2008-11-26 at 11:48 +0200, Pasi K?rkk?inen wrote: > > On Wed, Nov 26, 2008 at 09:34:17AM +0000, Mark McLoughlin wrote: > > > Hi, > > > Thanks for poking at this - I've updated the page to remove any > > > tracking of the in-progress kernel support, since it's all better > > > tracked elsewhere now. > > > > > > > Ok. > > > > Although "i386 Dom0", "x86_64 Dom0" and "Scope" sections still need heavy > > editing.. > > I removed them - maybe you missed my updates? > Oh, now it seems to be OK. I guess I refreshed before you submitted your changes, or then my browser cached the old page. Anyway, now it's better. > > Also, it might be a good idea to mention about this temporary Linux 2.6.27 > > Xenlinux repository with dom0 support included (with a patch from Suse): > > > > http://xenbits.xensource.com/ext/linux-2.6.27-xen.hg > > > > That 2.6.27 kernel is NOT based on pv_ops, but to a forward-port from 2.6.18 > > Xenlinux kernel. It is just a temporary tree until pv_ops dom0 is ready. > > > > Announcement about that temporary 2.6.27 Xenlinux tree: > > http://lists.xensource.com/archives/html/xen-devel/2008-11/msg00600.html > > It's not really relevant to Fedora - we're not going back to the bad old > days of having a separate Xen kernel. We made the call in Fedora 9 to no > longer waste effort on any forwarded ported 2.6.18 tree and focus all > efforts on upstream pv_ops, since that's where the future lies. > I know. But it might be relevant for people who want to build their own dom0 kernel.. before pv_ops dom0 is ready. > Personally, I'm disappointed to see this linux-2.6.27-xen.hg tree > appear. Any effort invested in this tree is effort that could be spent > on helping with the upstream pv_ops work. > Yep.. The tree is based on work done by Suse for SLES11. Xensource just imported their patches to that temporary tree. I don't think Xensource will be putting much (if any) effort into that tree. > > > My advice to anyone wanting to help this along is to build and test > > > Jeremy's work and iron out any issues with Fedora's xen userland running > > > on it. > > > > > > > Yes, that would be a good idea. > > > > Does someone want to build some testing RPMs? :) > > A volunteer to do this would be very welcome indeed :-) > :) -- Pasi From pasik at iki.fi Wed Nov 26 10:31:31 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 26 Nov 2008 12:31:31 +0200 Subject: AW: [Fedora-xen] Fedora 10 Release and Virtualization News / RHEL5/CentOS5 dom0 support for F10 guest domUs In-Reply-To: References: <1227388895.6032.35.camel@seitan.home.bewley.net> <492C66E9.80905@itsbeen.sent.com> <353341.19962.qm@web28211.mail.ukl.yahoo.com> Message-ID: <20081126103131.GM15052@edu.joroinen.fi> On Wed, Nov 26, 2008 at 10:06:36AM +0000, M A Young wrote: > On Tue, 25 Nov 2008, Franz Von Hahn wrote: > > >You could propably use CentOS 5.2 als a dom0. It is shipped with a > >kernel-xen package 2.6.18.x. It works fine for me but i haven't tried > >F10 so far since i'm acutally downloading the iso image of F10 which > >takes a long time when using a 1024kpb/s line, you know ;) > > I believe you need Centos 5.3 for F10 xen guest clients which, as RHEL5.3 > beta has only just appeared, probably won't be available until after > Fedora 8 has EOLed. > Yeah.. I believe RHEL 5.2 and CentOS 5.2 has too old python-virtinst to handle/install F10 guests.. RHEL 5.3 will contain updated python-virtinst that supports F10 guests. It is already included in RHEL 5.3 beta. http://www.nabble.com/Re%3A-rawhide-domU-on-RHEL5.2-dom0--p19833725.html https://bugzilla.redhat.com/show_bug.cgi?id=460585 If you can't try RHEL 5.3 beta dom0, you could try with installing python-virtinst-0.300.2-10.el5 or newer to your RHEL 5.2 / CentOS 5.2 dom0.. it should add support for F10 domUs. For more information check that bugzilla link above. RHEL 5.3 beta announcement: https://www.redhat.com/archives/rhelv5-announce/2008-October/msg00000.html contains: python-virtinst-0.300.2-11.el5 -- Pasi From pasik at iki.fi Wed Nov 26 10:38:29 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 26 Nov 2008 12:38:29 +0200 Subject: AW: [Fedora-xen] Fedora 10 Release and Virtualization News / RHEL5/CentOS5 dom0 support for F10 guest domUs In-Reply-To: <20081126103131.GM15052@edu.joroinen.fi> References: <1227388895.6032.35.camel@seitan.home.bewley.net> <492C66E9.80905@itsbeen.sent.com> <353341.19962.qm@web28211.mail.ukl.yahoo.com> <20081126103131.GM15052@edu.joroinen.fi> Message-ID: <20081126103829.GN15052@edu.joroinen.fi> On Wed, Nov 26, 2008 at 12:31:31PM +0200, Pasi K?rkk?inen wrote: > On Wed, Nov 26, 2008 at 10:06:36AM +0000, M A Young wrote: > > On Tue, 25 Nov 2008, Franz Von Hahn wrote: > > > > >You could propably use CentOS 5.2 als a dom0. It is shipped with a > > >kernel-xen package 2.6.18.x. It works fine for me but i haven't tried > > >F10 so far since i'm acutally downloading the iso image of F10 which > > >takes a long time when using a 1024kpb/s line, you know ;) > > > > I believe you need Centos 5.3 for F10 xen guest clients which, as RHEL5.3 > > beta has only just appeared, probably won't be available until after > > Fedora 8 has EOLed. > > > > Yeah.. I believe RHEL 5.2 and CentOS 5.2 has too old python-virtinst > to handle/install F10 guests.. > > RHEL 5.3 will contain updated python-virtinst that supports F10 guests. > It is already included in RHEL 5.3 beta. > > http://www.nabble.com/Re%3A-rawhide-domU-on-RHEL5.2-dom0--p19833725.html > https://bugzilla.redhat.com/show_bug.cgi?id=460585 > > If you can't try RHEL 5.3 beta dom0, you could try with installing > python-virtinst-0.300.2-10.el5 or newer to your RHEL 5.2 / CentOS 5.2 dom0.. > it should add support for F10 domUs. For more information check that > bugzilla link above. > > RHEL 5.3 beta announcement: > https://www.redhat.com/archives/rhelv5-announce/2008-October/msg00000.html > > contains: > python-virtinst-0.300.2-11.el5 > Oh, and it seems you also need newer libxc: "RHEL5.3 xen: include support for booting Fedora 10 DomU (i.e. bzImage support)": https://bugzilla.redhat.com/show_bug.cgi?id=457199 -- Pasi From franz.vonhahn at yahoo.de Wed Nov 26 10:49:41 2008 From: franz.vonhahn at yahoo.de (Franz Von Hahn) Date: Wed, 26 Nov 2008 10:49:41 +0000 (GMT) Subject: AW: AW: [Fedora-xen] Fedora 10 Release and Virtualization News References: <1227388895.6032.35.camel@seitan.home.bewley.net> <492C66E9.80905@itsbeen.sent.com> <353341.19962.qm@web28211.mail.ukl.yahoo.com> Message-ID: <113606.68395.qm@web28204.mail.ukl.yahoo.com> AFAIK (!) CentOS 5.2 updates will be available until the EOL of RHEL 5 which is March 31 2014. I haven't tried to update a Fedora 9 domU to F10 on a CentOS 5.2 host since an online-update from Fedora 8 to F9 failed the last time. even root couldn't read his own home directory. Fortunately a backup of the filesystem image was created beforehand. ----- Urspr?ngliche Mail ---- Von: M A Young An: fedora-xen at redhat.com Gesendet: Mittwoch, den 26. November 2008, 11:06:36 Uhr Betreff: Re: AW: [Fedora-xen] Fedora 10 Release and Virtualization News On Tue, 25 Nov 2008, Franz Von Hahn wrote: > You could propably use CentOS 5.2 als a dom0. It is shipped with a kernel-xen package 2.6.18..x. It works fine for me but i haven't tried F10 so far since i'm acutally downloading the iso image of F10 which takes a long time when using a 1024kpb/s line, you know ;) I believe you need Centos 5.3 for F10 xen guest clients which, as RHEL5.3 beta has only just appeared, probably won't be available until after Fedora 8 has EOLed. Michael Young -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From berrange at redhat.com Wed Nov 26 10:57:01 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 26 Nov 2008 10:57:01 +0000 Subject: AW: [Fedora-xen] Fedora 10 Release and Virtualization News / RHEL5/CentOS5 dom0 support for F10 guest domUs In-Reply-To: <20081126103829.GN15052@edu.joroinen.fi> References: <1227388895.6032.35.camel@seitan.home.bewley.net> <492C66E9.80905@itsbeen.sent.com> <353341.19962.qm@web28211.mail.ukl.yahoo.com> <20081126103131.GM15052@edu.joroinen.fi> <20081126103829.GN15052@edu.joroinen.fi> Message-ID: <20081126105701.GG16540@redhat.com> On Wed, Nov 26, 2008 at 12:38:29PM +0200, Pasi K?rkk?inen wrote: > On Wed, Nov 26, 2008 at 12:31:31PM +0200, Pasi K?rkk?inen wrote: > > On Wed, Nov 26, 2008 at 10:06:36AM +0000, M A Young wrote: > > > On Tue, 25 Nov 2008, Franz Von Hahn wrote: > > > > > > >You could propably use CentOS 5.2 als a dom0. It is shipped with a > > > >kernel-xen package 2.6.18.x. It works fine for me but i haven't tried > > > >F10 so far since i'm acutally downloading the iso image of F10 which > > > >takes a long time when using a 1024kpb/s line, you know ;) > > > > > > I believe you need Centos 5.3 for F10 xen guest clients which, as RHEL5.3 > > > beta has only just appeared, probably won't be available until after > > > Fedora 8 has EOLed. > > > > > > > Yeah.. I believe RHEL 5.2 and CentOS 5.2 has too old python-virtinst > > to handle/install F10 guests.. > > > > RHEL 5.3 will contain updated python-virtinst that supports F10 guests. > > It is already included in RHEL 5.3 beta. > > > > http://www.nabble.com/Re%3A-rawhide-domU-on-RHEL5.2-dom0--p19833725.html > > https://bugzilla.redhat.com/show_bug.cgi?id=460585 > > > > If you can't try RHEL 5.3 beta dom0, you could try with installing > > python-virtinst-0.300.2-10.el5 or newer to your RHEL 5.2 / CentOS 5.2 dom0.. > > it should add support for F10 domUs. For more information check that > > bugzilla link above. > > > > RHEL 5.3 beta announcement: > > https://www.redhat.com/archives/rhelv5-announce/2008-October/msg00000.html > > > > contains: > > python-virtinst-0.300.2-11.el5 > > > > Oh, and it seems you also need newer libxc: Yes, that is correct - RHEL-5.2 Xen doesn't understand the new bzImage style kernels. 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 fcxen at itsbeen.sent.com Wed Nov 26 12:29:19 2008 From: fcxen at itsbeen.sent.com (fcxen user) Date: Wed, 26 Nov 2008 04:29:19 -0800 Subject: AW: [Fedora-xen] Fedora 10 Release and Virtualization News / RHEL5/CentOS5 dom0 support for F10 guest domUs In-Reply-To: <20081126105701.GG16540@redhat.com> References: <1227388895.6032.35.camel@seitan.home.bewley.net> <492C66E9.80905@itsbeen.sent.com> <353341.19962.qm@web28211.mail.ukl.yahoo.com> <20081126103131.GM15052@edu.joroinen.fi> <20081126103829.GN15052@edu.joroinen.fi> <20081126105701.GG16540@redhat.com> Message-ID: <492D411F.4010701@itsbeen.sent.com> Daniel P. Berrange wrote: > On Wed, Nov 26, 2008 at 12:38:29PM +0200, Pasi K?rkk?inen wrote: >> On Wed, Nov 26, 2008 at 12:31:31PM +0200, Pasi K?rkk?inen wrote: >>> On Wed, Nov 26, 2008 at 10:06:36AM +0000, M A Young wrote: >>>> On Tue, 25 Nov 2008, Franz Von Hahn wrote: >>>> >>>>> You could propably use CentOS 5.2 als a dom0. It is shipped with a >>>>> kernel-xen package 2.6.18.x. It works fine for me but i haven't tried >>>>> F10 so far since i'm acutally downloading the iso image of F10 which >>>>> takes a long time when using a 1024kpb/s line, you know ;) >>>> I believe you need Centos 5.3 for F10 xen guest clients which, as RHEL5.3 >>>> beta has only just appeared, probably won't be available until after >>>> Fedora 8 has EOLed. >>>> >>> Yeah.. I believe RHEL 5.2 and CentOS 5.2 has too old python-virtinst >>> to handle/install F10 guests.. >>> >>> RHEL 5.3 will contain updated python-virtinst that supports F10 guests. >>> It is already included in RHEL 5.3 beta. >>> >>> http://www.nabble.com/Re%3A-rawhide-domU-on-RHEL5.2-dom0--p19833725.html >>> https://bugzilla.redhat.com/show_bug.cgi?id=460585 >>> >>> If you can't try RHEL 5.3 beta dom0, you could try with installing >>> python-virtinst-0.300.2-10.el5 or newer to your RHEL 5.2 / CentOS 5.2 dom0.. >>> it should add support for F10 domUs. For more information check that >>> bugzilla link above. >>> >>> RHEL 5.3 beta announcement: >>> https://www.redhat.com/archives/rhelv5-announce/2008-October/msg00000.html >>> >>> contains: >>> python-virtinst-0.300.2-11.el5 >>> >> Oh, and it seems you also need newer libxc: > > Yes, that is correct - RHEL-5.2 Xen doesn't understand the new bzImage > style kernels. > > Daniel So is there any way to get F10 domU running on F8 dom0 ? I don't want to have to downgrade all my dom0s to RHEL or CentOS ... From pasik at iki.fi Wed Nov 26 13:17:58 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 26 Nov 2008 15:17:58 +0200 Subject: AW: [Fedora-xen] Fedora 10 Release and Virtualization News / Fedora 8 dom0 support for F10 guest domUs In-Reply-To: <492D411F.4010701@itsbeen.sent.com> References: <1227388895.6032.35.camel@seitan.home.bewley.net> <492C66E9.80905@itsbeen.sent.com> <353341.19962.qm@web28211.mail.ukl.yahoo.com> <20081126103131.GM15052@edu.joroinen.fi> <20081126103829.GN15052@edu.joroinen.fi> <20081126105701.GG16540@redhat.com> <492D411F.4010701@itsbeen.sent.com> Message-ID: <20081126131758.GQ15052@edu.joroinen.fi> On Wed, Nov 26, 2008 at 04:29:19AM -0800, fcxen user wrote: > Daniel P. Berrange wrote: > >On Wed, Nov 26, 2008 at 12:38:29PM +0200, Pasi K?rkk?inen wrote: > >>On Wed, Nov 26, 2008 at 12:31:31PM +0200, Pasi K?rkk?inen wrote: > >>>On Wed, Nov 26, 2008 at 10:06:36AM +0000, M A Young wrote: > >>>>On Tue, 25 Nov 2008, Franz Von Hahn wrote: > >>>> > >>>>>You could propably use CentOS 5.2 als a dom0. It is shipped with a > >>>>>kernel-xen package 2.6.18.x. It works fine for me but i haven't tried > >>>>>F10 so far since i'm acutally downloading the iso image of F10 which > >>>>>takes a long time when using a 1024kpb/s line, you know ;) > >>>>I believe you need Centos 5.3 for F10 xen guest clients which, as > >>>>RHEL5.3 beta has only just appeared, probably won't be available until > >>>>after Fedora 8 has EOLed. > >>>> > >>>Yeah.. I believe RHEL 5.2 and CentOS 5.2 has too old python-virtinst > >>>to handle/install F10 guests.. > >>> > >>>RHEL 5.3 will contain updated python-virtinst that supports F10 guests. > >>>It is already included in RHEL 5.3 beta. > >>> > >>>http://www.nabble.com/Re%3A-rawhide-domU-on-RHEL5.2-dom0--p19833725.html > >>>https://bugzilla.redhat.com/show_bug.cgi?id=460585 > >>> > >>>If you can't try RHEL 5.3 beta dom0, you could try with installing > >>>python-virtinst-0.300.2-10.el5 or newer to your RHEL 5.2 / CentOS 5.2 > >>>dom0.. > >>>it should add support for F10 domUs. For more information check that > >>>bugzilla link above. > >>> > >>>RHEL 5.3 beta announcement: > >>>https://www.redhat.com/archives/rhelv5-announce/2008-October/msg00000.html > >>> > >>>contains: > >>>python-virtinst-0.300.2-11.el5 > >>> > >>Oh, and it seems you also need newer libxc: > > > >Yes, that is correct - RHEL-5.2 Xen doesn't understand the new bzImage > >style kernels. > > > >Daniel > > So is there any way to get F10 domU running on F8 dom0 ? > > I don't want to have to downgrade all my dom0s to RHEL or CentOS ... > Based on https://bugzilla.redhat.com/show_bug.cgi?id=457199 "And we're including that patch now in F-8, F-9 and F-10" libxc bzImage support should be fine in Fedora 8 (with all the updates installed). Then there's the problem with python-virtinst.. I guess python-virtinst in Fedora 8 cannot handle F10 guests? Latest version in F8 updates seems to be: python-virtinst-0.300.2-4.fc8 Which looks too old to support F10 guests.. So maybe you have to update python-virtinst in F8 and then try again? -- Pasi From crobinso at redhat.com Wed Nov 26 14:50:04 2008 From: crobinso at redhat.com (Cole Robinson) Date: Wed, 26 Nov 2008 09:50:04 -0500 Subject: [Fedora-xen] Fedora 10 Release and Virtualization News In-Reply-To: <492C66E9.80905@itsbeen.sent.com> References: <1227388895.6032.35.camel@seitan.home.bewley.net> <492C66E9.80905@itsbeen.sent.com> Message-ID: <492D621C.1050308@redhat.com> fcxen user wrote: > Hi, > > Dale, great stuff. This question is a little late for your release, but I know > it will be coming up alot soon, so I hope you can add it to your docs: > > Is it possible to run a Fedora 10 pv domU on a Fedora 8 dom0 ? > And if it is, what steps are necessary to be able to install the F10 domU with > virt-install and manage it with xm/virsh/etc that differ from what is required > to do the same for F7/8/9,etc domUs? > > With the standard yum package: python-virtinst-0.300.2-4.fc8 > one gets: > ValueError: Invalid URL location given: > http://mirror.x.y/pub/fedora/linux/releases/10/Fedora/x86_64/os/images/xen/vmlinuz > [Errno 14] HTTP Error 404: Not Found > That version of virt-install doesn't know how to find the xen kernel in F10 install trees: https://bugzilla.redhat.com/show_bug.cgi?id=458164 I built a fixed package for this yesterday though, which should now be in updates-testing: http://koji.fedoraproject.org/koji/buildinfo?buildID=71125 So give that a shot and see if it works for you. Thanks, Cole From crobinso at redhat.com Wed Nov 26 14:54:13 2008 From: crobinso at redhat.com (Cole Robinson) Date: Wed, 26 Nov 2008 09:54:13 -0500 Subject: AW: [Fedora-xen] Fedora 10 Release and Virtualization News / Fedora 8 dom0 support for F10 guest domUs In-Reply-To: <20081126131758.GQ15052@edu.joroinen.fi> References: <1227388895.6032.35.camel@seitan.home.bewley.net> <492C66E9.80905@itsbeen.sent.com> <353341.19962.qm@web28211.mail.ukl.yahoo.com> <20081126103131.GM15052@edu.joroinen.fi> <20081126103829.GN15052@edu.joroinen.fi> <20081126105701.GG16540@redhat.com> <492D411F.4010701@itsbeen.sent.com> <20081126131758.GQ15052@edu.joroinen.fi> Message-ID: <492D6315.8000803@redhat.com> Pasi K?rkk?inen wrote: > On Wed, Nov 26, 2008 at 04:29:19AM -0800, fcxen user wrote: >> Daniel P. Berrange wrote: >>> On Wed, Nov 26, 2008 at 12:38:29PM +0200, Pasi K?rkk?inen wrote: >>>> On Wed, Nov 26, 2008 at 12:31:31PM +0200, Pasi K?rkk?inen wrote: >>>>> On Wed, Nov 26, 2008 at 10:06:36AM +0000, M A Young wrote: >>>>>> On Tue, 25 Nov 2008, Franz Von Hahn wrote: >>>>>> >>>>>>> You could propably use CentOS 5.2 als a dom0. It is shipped with a >>>>>>> kernel-xen package 2.6.18.x. It works fine for me but i haven't tried >>>>>>> F10 so far since i'm acutally downloading the iso image of F10 which >>>>>>> takes a long time when using a 1024kpb/s line, you know ;) >>>>>> I believe you need Centos 5.3 for F10 xen guest clients which, as >>>>>> RHEL5.3 beta has only just appeared, probably won't be available until >>>>>> after Fedora 8 has EOLed. >>>>>> >>>>> Yeah.. I believe RHEL 5.2 and CentOS 5.2 has too old python-virtinst >>>>> to handle/install F10 guests.. >>>>> >>>>> RHEL 5.3 will contain updated python-virtinst that supports F10 guests. >>>>> It is already included in RHEL 5.3 beta. >>>>> >>>>> http://www.nabble.com/Re%3A-rawhide-domU-on-RHEL5.2-dom0--p19833725.html >>>>> https://bugzilla.redhat.com/show_bug.cgi?id=460585 >>>>> >>>>> If you can't try RHEL 5.3 beta dom0, you could try with installing >>>>> python-virtinst-0.300.2-10.el5 or newer to your RHEL 5.2 / CentOS 5.2 >>>>> dom0.. >>>>> it should add support for F10 domUs. For more information check that >>>>> bugzilla link above. >>>>> >>>>> RHEL 5.3 beta announcement: >>>>> https://www.redhat.com/archives/rhelv5-announce/2008-October/msg00000.html >>>>> >>>>> contains: >>>>> python-virtinst-0.300.2-11.el5 >>>>> >>>> Oh, and it seems you also need newer libxc: >>> Yes, that is correct - RHEL-5.2 Xen doesn't understand the new bzImage >>> style kernels. >>> >>> Daniel >> So is there any way to get F10 domU running on F8 dom0 ? >> >> I don't want to have to downgrade all my dom0s to RHEL or CentOS ... >> > > Based on https://bugzilla.redhat.com/show_bug.cgi?id=457199 > "And we're including that patch now in F-8, F-9 and F-10" libxc bzImage > support should be fine in Fedora 8 (with all the updates installed). > > Then there's the problem with python-virtinst.. > > I guess python-virtinst in Fedora 8 cannot handle F10 guests? > > Latest version in F8 updates seems to be: python-virtinst-0.300.2-4.fc8 > > Which looks too old to support F10 guests.. > > So maybe you have to update python-virtinst in F8 and then try again? I posted this elsewhere in the thread, but just yesterday I built a new F8 virtinst which should allow installing F10 xen guests: http://koji.fedoraproject.org/koji/buildinfo?buildID=71125 https://bugzilla.redhat.com/show_bug.cgi?id=458164 It should be in updates testing now. Give it a +1 in bodhi if it works for you, and the package will eventually make it to the plain updates repo: https://admin.fedoraproject.org/updates/F8/FEDORA-2008-10394 Thanks, Cole From pasik at iki.fi Wed Nov 26 16:45:55 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 26 Nov 2008 18:45:55 +0200 Subject: AW: [Fedora-xen] Fedora 10 Release and Virtualization News / Fedora 8 dom0 support for F10 guest domUs In-Reply-To: <492D6315.8000803@redhat.com> References: <1227388895.6032.35.camel@seitan.home.bewley.net> <492C66E9.80905@itsbeen.sent.com> <353341.19962.qm@web28211.mail.ukl.yahoo.com> <20081126103131.GM15052@edu.joroinen.fi> <20081126103829.GN15052@edu.joroinen.fi> <20081126105701.GG16540@redhat.com> <492D411F.4010701@itsbeen.sent.com> <20081126131758.GQ15052@edu.joroinen.fi> <492D6315.8000803@redhat.com> Message-ID: <20081126164555.GS15052@edu.joroinen.fi> On Wed, Nov 26, 2008 at 09:54:13AM -0500, Cole Robinson wrote: > Pasi K?rkk?inen wrote: > > On Wed, Nov 26, 2008 at 04:29:19AM -0800, fcxen user wrote: > >> Daniel P. Berrange wrote: > >>> On Wed, Nov 26, 2008 at 12:38:29PM +0200, Pasi K?rkk?inen wrote: > >>>> On Wed, Nov 26, 2008 at 12:31:31PM +0200, Pasi K?rkk?inen wrote: > >>>>> On Wed, Nov 26, 2008 at 10:06:36AM +0000, M A Young wrote: > >>>>>> On Tue, 25 Nov 2008, Franz Von Hahn wrote: > >>>>>> > >>>>>>> You could propably use CentOS 5.2 als a dom0. It is shipped with a > >>>>>>> kernel-xen package 2.6.18.x. It works fine for me but i haven't tried > >>>>>>> F10 so far since i'm acutally downloading the iso image of F10 which > >>>>>>> takes a long time when using a 1024kpb/s line, you know ;) > >>>>>> I believe you need Centos 5.3 for F10 xen guest clients which, as > >>>>>> RHEL5.3 beta has only just appeared, probably won't be available until > >>>>>> after Fedora 8 has EOLed. > >>>>>> > >>>>> Yeah.. I believe RHEL 5.2 and CentOS 5.2 has too old python-virtinst > >>>>> to handle/install F10 guests.. > >>>>> > >>>>> RHEL 5.3 will contain updated python-virtinst that supports F10 guests. > >>>>> It is already included in RHEL 5.3 beta. > >>>>> > >>>>> http://www.nabble.com/Re%3A-rawhide-domU-on-RHEL5.2-dom0--p19833725.html > >>>>> https://bugzilla.redhat.com/show_bug.cgi?id=460585 > >>>>> > >>>>> If you can't try RHEL 5.3 beta dom0, you could try with installing > >>>>> python-virtinst-0.300.2-10.el5 or newer to your RHEL 5.2 / CentOS 5.2 > >>>>> dom0.. > >>>>> it should add support for F10 domUs. For more information check that > >>>>> bugzilla link above. > >>>>> > >>>>> RHEL 5.3 beta announcement: > >>>>> https://www.redhat.com/archives/rhelv5-announce/2008-October/msg00000.html > >>>>> > >>>>> contains: > >>>>> python-virtinst-0.300.2-11.el5 > >>>>> > >>>> Oh, and it seems you also need newer libxc: > >>> Yes, that is correct - RHEL-5.2 Xen doesn't understand the new bzImage > >>> style kernels. > >>> > >>> Daniel > >> So is there any way to get F10 domU running on F8 dom0 ? > >> > >> I don't want to have to downgrade all my dom0s to RHEL or CentOS ... > >> > > > > Based on https://bugzilla.redhat.com/show_bug.cgi?id=457199 > > "And we're including that patch now in F-8, F-9 and F-10" libxc bzImage > > support should be fine in Fedora 8 (with all the updates installed). > > > > Then there's the problem with python-virtinst.. > > > > I guess python-virtinst in Fedora 8 cannot handle F10 guests? > > > > Latest version in F8 updates seems to be: python-virtinst-0.300.2-4.fc8 > > > > Which looks too old to support F10 guests.. > > > > So maybe you have to update python-virtinst in F8 and then try again? > > I posted this elsewhere in the thread, but just yesterday I built a new > F8 virtinst which should allow installing F10 xen guests: > > http://koji.fedoraproject.org/koji/buildinfo?buildID=71125 > https://bugzilla.redhat.com/show_bug.cgi?id=458164 > > It should be in updates testing now. Give it a +1 in bodhi if it works > for you, and the package will eventually make it to the plain updates repo: > > https://admin.fedoraproject.org/updates/F8/FEDORA-2008-10394 > Thanks for the links. I think it would be a good idea to add a note to F10 release notes that if you want to use Fedora 8 as dom0 to run F10 guests, you need to have all the latest updates installed to your F8 dom0, plus you need to have that python-virtinst-0.300.2-5.fc8.noarch.rpm from updates-testing. -- Pasi From dlbewley at lib.ucdavis.edu Wed Nov 26 20:19:09 2008 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Wed, 26 Nov 2008 12:19:09 -0800 Subject: AW: [Fedora-xen] Fedora 10 Release and Virtualization News / Fedora 8 dom0 support for F10 guest domUs In-Reply-To: <20081126164555.GS15052@edu.joroinen.fi> References: <1227388895.6032.35.camel@seitan.home.bewley.net> <492C66E9.80905@itsbeen.sent.com> <353341.19962.qm@web28211.mail.ukl.yahoo.com> <20081126103131.GM15052@edu.joroinen.fi> <20081126103829.GN15052@edu.joroinen.fi> <20081126105701.GG16540@redhat.com> <492D411F.4010701@itsbeen.sent.com> <20081126131758.GQ15052@edu.joroinen.fi> <492D6315.8000803@redhat.com> <20081126164555.GS15052@edu.joroinen.fi> Message-ID: <1227730749.15273.4.camel@seitan.home.bewley.net> On Wed, 2008-11-26 at 18:45 +0200, Pasi K?rkk?inen wrote: > > I think it would be a good idea to add a note to F10 release notes > that if > you want to use Fedora 8 as dom0 to run F10 guests, you need to have > all the > latest updates installed to your F8 dom0, plus you need to have that > python-virtinst-0.300.2-5.fc8.noarch.rpm from updates-testing. > > -- Pasi I tossed it on the common bugs page http://fedoraproject.org/wiki/Common_F10_bugs From m.a.young at durham.ac.uk Fri Nov 28 14:31:27 2008 From: m.a.young at durham.ac.uk (M A Young) Date: Fri, 28 Nov 2008 14:31:27 +0000 (GMT) Subject: [Fedora-xen] Should kernel 2.6.27.5-41.fc9 boot as xen guest? Message-ID: I was trying to get a NVIDIA video driver working with the Fedora 9 kernel 2.6.27.5-41.fc9 (on x86_64) and it refused because it decided it was a xen kernel, so I thought I would check this claim out. My attempts to boot a xen guest with that kernel failed, though it got past the boot loader stage, and I know Fedora 9 has kernel-xen packages, but I was wondering whether this kernel would be expected to work or not. Michael Young From markmc at redhat.com Fri Nov 28 14:53:04 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Fri, 28 Nov 2008 14:53:04 +0000 Subject: [Fedora-xen] Should kernel 2.6.27.5-41.fc9 boot as xen guest? In-Reply-To: References: Message-ID: <1227883984.3643.34.camel@blaa> On Fri, 2008-11-28 at 14:31 +0000, M A Young wrote: > I was trying to get a NVIDIA video driver working with the Fedora 9 kernel > 2.6.27.5-41.fc9 (on x86_64) and it refused because it decided it was a xen > kernel, so I thought I would check this claim out. > My attempts to boot a xen guest with that kernel failed, though it got > past the boot loader stage, and I know Fedora 9 has kernel-xen packages, > but I was wondering whether this kernel would be expected to work or not. The F-9 kernel-xen packages are the only ones expected to work for an F-9 Xen DomU, but it does appear the F-9 2.6.27 kernels (32 and 64 bit x86) are being built with CONFIG_XEN ... so, they may well work. Cheers, Mark. From princeofporsche at gmail.com Sun Nov 30 00:47:14 2008 From: princeofporsche at gmail.com (ADITYA KRISHNAN) Date: Sat, 29 Nov 2008 19:47:14 -0500 Subject: [Fedora-xen] Re: Compiling Xen-3.0.-testing.hg from source on FC5[general protection fault 000[1]] In-Reply-To: <71d179310811282118n42322caer51775be83a925ea2@mail.gmail.com> References: <71d179310811282118n42322caer51775be83a925ea2@mail.gmail.com> Message-ID: <71d179310811291647w2a93f2cbg52023a1bd714258e@mail.gmail.com> Hi, > > > I am working on x86_64 amd opetron cluster which runs fc5. I wanted to > install the older version of Xen i.e xen 3.0-testing.hg for academic > purposes. I wanted to compile the xen kernel with debug info. Hence I tried > to compile it from source. It compiled successfully and I made corresponding > entries to the grub.conf file. Is there any rpm package for xen with debug > info available on fc5 for x86_64 ? > Please let me know. For now directly compiling from the source gives the > following error: > > root (hd0,0) > Filesystem type is ext2fs, partition type 0x83 > kernel /xen-3.0.2-3.gz console=com2,vga com2=19200,8n1 sync_console > [Multiboot-elf, <0x100000:0xed530:0x39ad0>, shtab=0x227078, > entry=0x100000] [0H0000] [06;00 __ __ _____ ___ ____ > _____ > . > . . (XEN) 3... 2... 1... > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input > to Xen). > kernel direct mapping tables up to f087e000 @ ea2000-ea2000 > Bootdata ok (command line is ro root=LABEL=/ console=ttyS1,19200n8 3 > selinux=0) > Linux version 2.6.16.13-xen (root at opt13) (gcc version 4.1.0 20060304 (Red > Hat 4.1.0-3)) #1 SMP Thu Nov 20 21:45:06 EST 2008 > ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) > ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled) > ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled) > ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0]) > IOAPIC[0]: apic_id 4, version 17, address 0xfec00000, GSI 0-23 > ACPI: IOAPIC (id[0x05] address[0xfebff000] gsi_base[24]) > IOAPIC[1]: apic_id 5, version 17, address 0xfebff000, GSI 24-27 > ACPI: IOAPIC (id[0x06] address[0xfebfe000] gsi_base[28]) > IOAPIC[2]: apic_id 6, version 17, address 0xfebfe000, GSI 28-31 > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > Setting APIC routing to xen > Using ACPI (MADT) for SMP configuration information > Allocating PCI resources starting at fc400000 (gap: fc000000:3780000) > Built 1 zonelists > Kernel command line: ro root=LABEL=/ console=ttyS1,19200n8 3 selinux=0 > Initializing CPU#0 > PID hash table entries: 4096 (order: 12, 131072 bytes) > Xen reported: 1793.340 MHz processor. > Console: colour VGA+ 80x25 > Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) > Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) > Software IO TLB enabled: > Aperture: 64 megabytes > Kernel range: 0xffff8800058d1000 - 0xffff8800098d1000 > PCI-DMA: Using software bounce buffering for IO (SWIOTLB) > Memory: 3783548k/3940856k available (2415k kernel code, 148460k reserved, > 904k data, 164k init) > Calibrating delay using timer specific routine.. 3588.10 BogoMIPS > (lpj=17940514) > Security Framework v1.0.0 initialized > Capability LSM initialized > Mount-cache hash table entries: 256 > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > CPU: L2 Cache: 1024K (64 bytes/line) > Initializing CPU#1 > Initializing CPU#2 > Brought up 4 CPUs > Initializing CPU#3 > migration_cost=309 > checking if image is initramfs... it is > Freeing initrd memory: 2177k freed > DMI 2.3 present. > Grant table initialized > NET: Registered protocol family 16 > ACPI: bus type pci registered > PCI: Using configuration type 1 > ACPI: Subsystem revision 20060127 > ACPI: Interpreter enabled > ACPI: Using IOAPIC for interrupt routing > ACPI: PCI Root Bridge [PCI0] (0000:00) > ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) > ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) > ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) > ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) > xen_mem: Initialising balloon driver. > SCSI subsystem initialized > usbcore: registered new driver usbfs > usbcore: registered new driver hub > PCI: Using ACPI for IRQ routing > PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a > report > PCI: Bridge: 0000:00:06.0 > IO window: 9000-bfff > MEM window: fc900000-feafffff > PREFETCH window: disabled. > PCI: Bridge: 0000:00:0a.0 > IO window: disabled. > MEM window: fc800000-fc8fffff > PREFETCH window: ff500000-ff5fffff > PCI: Bridge: 0000:00:0b.0 > IO window: disabled. > MEM window: disabled. > PREFETCH window: disabled. > IA-32 Microcode Update Driver: v1.14-xen > IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $ > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > Initializing Cryptographic API > io scheduler noop registered > io scheduler anticipatory registered (default) > io scheduler deadline registered > io scheduler cfq registered > PCI: MSI quirk detected. pci_msi_quirk set. > PCI: MSI quirk detected. pci_msi_quirk set. > Real Time Clock Driver v1.12ac > serio: i8042 AUX port at 0x60,0x64 irq 12 > serio: i8042 KBD port at 0x60,0x64 irq 1 > isa bounce pool size: 16 pages > RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize > Xen virtual console successfully installed as ttyS0 > Event-channel device installed. > blkif_init: reqs=64, pages=704, mmap_vstart=0xffff8800ef800000 > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > AMD8111: IDE controller at PCI slot 0000:00:07.1 > AMD8111: chipset revision 3 > AMD8111: not 100% native mode: will probe irqs later > AMD8111: 0000:00:07.1 (rev 03) UDMA133 controller > ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio > ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio > hdc: SR244W, ATAPI CD/DVD-ROM drive > ide1 at 0x170-0x177,0x376 on irq 15 > hdc: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33) > Uniform CD-ROM driver Revision: 3.20 > ide-floppy driver 0.99.newide > usbmon: debugfs is not available > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > mice: PS/2 mouse device common for all mice > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: bitmap version 4.39 > NET: Registered protocol family 2 > IP route cache hash table entries: 131072 (order: 8, 1048576 bytes) > TCP established hash table entries: 262144 (order: 10, 4194304 bytes) > TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) > TCP: Hash tables configured (established 262144 bind 65536) > TCP reno registered > Initializing IPsec netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > Red Hat nash version 5.0.32 startinginput: AT Translated Set 2 keyboard as > /class/input/input0 > > Mounting proc filesystem > Mounting sysfs filesystem > Creating /dev > Creating initial device nodes > Setting up hotplug. > Creating block device nodes. > Loading sata_sil.ko module > GSI 16 sharing vector 0x98 and IRQ 16 > ACPI: PCI Interrupt 0000:03:05.0[A] -> GSI 19 (level, low) -> IRQ 16 > ata1: SATA max UDMA/100 cmd 0xFFFFC20000004C80 ctl 0xFFFFC20000004C8A bmdma > 0xFFFFC20000004C00 irq 16 > ata2: SATA max UDMA/100 cmd 0xFFFFC20000004CC0 ctl 0xFFFFC20000004CCA bmdma > 0xFFFFC20000004C08 irq 16 > ata3: SATA max UDMA/100 cmd 0xFFFFC20000004E80 ctl 0xFFFFC20000004E8A bmdma > 0xFFFFC20000004E00 irq 16 > ata4: SATA max UDMA/100 cmd 0xFFFFC20000004EC0 ctl 0xFFFFC20000004ECA bmdma > 0xFFFFC20000004E08 irq 16 > ata1: SATA link up 1.5 Gbps (SStatus 113) > ata1: dev 0 ATA-7, max UDMA/133, 156301488 sectors: LBA48 > ata1: dev 0 configured for UDMA/100 > scsi0 : sata_sil > ata2: SATA link down (SStatus 0) > scsi1 : sata_sil > ata3: SATA link down (SStatus 0) > scsi2 : sata_sil > ata4: SATA link down (SStatus 0) > scsi3 : sata_sil > Vendor: ATA Model: WDC WD800JD-22LS Rev: 06.0 > Type: Direct-Access ANSI SCSI revision: 05 > SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB) > sda: Write Protect is off > SCSI device sda: drive cache: write back > SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB) > sda: Write Protect is off > SCSI device sda: drive cache: write back > sda: sda1 sda2 sda3 sda4 < sda5 sda6 > > sd 0:0:0:0: Attached scsi disk sda > Loading jbd.ko module > Loading ext3.ko module > Creating root device. > Mounting root filesystem. > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > Setting up other filesystems. > Setting up new root fs > no fstab.sys, mounting internal defaults > Switching to new root and running init. > unmounting old /dev > unmounting old /proc > unmounting old /sys > INIT: version 2.86 booting > Welcome to Fedora Core > Press 'I' to enter interactive startup. > Setting clock (localtime): Thu Nov 27 22:38:38 EST 2008 [ OK ] > Starting udev: general protection fault: 0000 [1] SMP > CPU 1 > Modules linked in: tg3 i2c_core ext3 jbd sata_sil > Pid: 457, comm: modprobe Not tainted 2.6.16.13-xen #1 > RIP: e030:[] {create_dir+34} > RSP: e02b:ffff8800ef3cfc28 EFLAGS: 00010296 > RAX: ffffffff88039010 RBX: ffff8800efd12400 RCX: ffff8800ef3cfc60 > RDX: ffff8800efd12400 RSI: 90666690666666c3 RDI: ffff8800efd123f8 > RBP: ffff8800efd123f8 R08: 00000000fffffffe R09: ffff8800eff2b889 > R10: ffff8800efd12000 R11: 0000000000000000 R12: 0000000000000000 > R13: ffff8800efd123e8 R14: ffffffff88039010 R15: ffffffff804049e0 > FS: 00002b49a3774210(0000) GS:ffffffff804a9080(0000) > knlGS:0000000000000000 > CS: e033 DS: 0000 ES: 0000 > Process modprobe (pid: 457, threadinfo ffff8800ef3ce000, task > ffff8800efcc09b0) > Stack: ffff8800efd123f8 ffff8800efd123e8 0000000000000000 ffff8800efd123e8 > ffffffff88039010 ffffffff801c4b28 ffffffff88039010 0000000000000000 > ffff8800efd123f8 ffffffff801f52ea > Call Trace: {:tg3:tg3_disable_ints+0} > {sysfs_create_dir+88} > {:tg3:tg3_disable_ints+0} > {kobject_add+234} > {:tg3:tg3_write32+0} > {class_device_add+185} > {netdev_register_sysfs+81} > {netdev_run_todo+242} > {register_netdev+100} > {:tg3:tg3_init_one+3175} > {__wake_up+67} > {pci_device_probe+89} > {driver_probe_device+101} > {__driver_attach+0} > {__driver_attach+96} > {__driver_attach+0} > {bus_for_each_dev+73} > {bus_add_driver+136} > {__pci_register_driver+128} > {sys_init_module+258} > {system_call+134} > {system_call+0} > > Code: 48 8b 7e 10 49 89 cc 49 89 f6 48 81 c7 c0 00 00 00 e8 88 33 > RIP {create_dir+34} RSP > udevd-event[456]: run_program: '/sbin/modprobe' abnormal exit > eepro100.c:v1.09j-t 9/29/99 Donald Becker > http://www.scyld.com/network/eepro100.html > eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin < > saw at saw.sw.com.sg> and others > sd 0:0:0:0: Attached scsi generic sg0 type 0 > Unable to handle kernel paging request at ffffffff8807c000 RIP: > > Please let me know if I have apply any FC5 related patches to the xen > source. > Please help. > > Thanks, > > Aditya > Graduate student > princeofporsche at gmail.com > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: