From pbruna at it-linux.cl Sat Jul 1 03:32:03 2006 From: pbruna at it-linux.cl (Patricio Bruna V.) Date: Fri, 30 Jun 2006 23:32:03 -0400 Subject: [Fedora-xen] Xen/libVirt GUI app: "Virtual Machine Manager" In-Reply-To: <44A50C04.10102@adslpipe.co.uk> References: <20060628200826.GG28524@redhat.com> <20060630081917.GJ1483@redhat.com> <44A50C04.10102@adslpipe.co.uk> Message-ID: <200606302332.03326.pbruna@it-linux.cl> i must miss the mail, where i can download this? -- Patricio Bruna V. Red Hat Certified Engineer IT Linux Ltda. http://www.it-linux.cl Fono/Fax: (+56-2) 697 11 66 Cel: (+56-8) 288 51 95 From thomas.vonsteiger at bluewin.ch Sat Jul 1 04:20:15 2006 From: thomas.vonsteiger at bluewin.ch (thomas.vonsteiger at bluewin.ch) Date: Sat, 1 Jul 2006 06:20:15 +0200 Subject: AW: [Fedora-xen] Xen/libVirt GUI app: "Virtual Machine Manager" In-Reply-To: <200606302332.03326.pbruna@it-linux.cl> Message-ID: <001c01c69cc5$a75d2e70$3e01a8c0@athlon> http://people.redhat.com/berrange/virt-manager/index.html -----Urspr?ngliche Nachricht----- Von: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] Im Auftrag von Patricio Bruna V. Gesendet: Samstag, 1. Juli 2006 05:32 An: fedora-xen at redhat.com Betreff: Re: [Fedora-xen] Xen/libVirt GUI app: "Virtual Machine Manager" i must miss the mail, where i can download this? -- Patricio Bruna V. Red Hat Certified Engineer IT Linux Ltda. http://www.it-linux.cl Fono/Fax: (+56-2) 697 11 66 Cel: (+56-8) 288 51 95 -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.7/379 - Release Date: 29.06.2006 From thomas.vonsteiger at bluewin.ch Sat Jul 1 04:40:25 2006 From: thomas.vonsteiger at bluewin.ch (thomas.vonsteiger at bluewin.ch) Date: Sat, 1 Jul 2006 06:40:25 +0200 Subject: AW: [Fedora-xen] Xen/libVirt GUI app: "Virtual Machine Manager" In-Reply-To: <20060630173747.GA25122@redhat.com> Message-ID: <001d01c69cc8$78a79a40$3e01a8c0@athlon> You are right. virt-manager running well with libvirt-python from updates-testing. Thomas -----Urspr?ngliche Nachricht----- Von: Daniel P. Berrange [mailto:berrange at redhat.com] Gesendet: Freitag, 30. Juni 2006 19:38 An: thomas.vonsteiger at bluewin.ch Cc: fedora-xen at redhat.com Betreff: Re: [Fedora-xen] Xen/libVirt GUI app: "Virtual Machine Manager" On Fri, Jun 30, 2006 at 05:45:27PM +0200, thomas.vonsteiger at bluewin.ch wrote: > Hello Daniel, > > If have running success virt-manager on my FC5 xenbox with all available > features. > > FC5 has the stat of latest yum update's from original repo update. > From development.repo "yum install libvirt-python" > Disable development repo. > Add berrange-fedora.repo and "yum install virt-manager" I think the problem is that you took libvirt from the 'development' repository which is basically FC6test1. For FC5 you should use the 'updates-testing' repository as per the instructions on the download page: yum --enablerepo=updates-testing install virt-manager Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.7/379 - Release Date: 29.06.2006 From thomas.vonsteiger at bluewin.ch Sat Jul 1 05:15:54 2006 From: thomas.vonsteiger at bluewin.ch (thomas.vonsteiger at bluewin.ch) Date: Sat, 1 Jul 2006 07:15:54 +0200 Subject: [Fedora-xen] Direct kickstart for hvm guest not running without prompt ? Message-ID: <001e01c69ccd$6d9025f0$3e01a8c0@athlon> Hello, I try to kickstart a guest direct without prompt for boot options. With "extra" it get always a prompt and it need the bootoptions manual. Whats wrong ? # Automatically generated xen config file name = "rhel4_4" builder = "hvm" memory = "256" acpi = 0 apic = 0 pea = 0 vcpus = 1 disk = [ 'phy:/dev/xenvg/xenRHEL4_4,ioemu:hda,w' ] vif = [ 'type=ioemu,bridge=xenbr0,mac=00:16:3e:09:e8:f2' ] on_reboot = 'restart' on_crash = 'restart' kernel = '/usr/lib/xen/boot/hvmloader' device_model = '/usr/lib/xen/bin/qemu-dm' cdrom = '/archiv/iso/RHEL4-U3-i386-AS-disc1.iso' extra = 'linux ks=http://192.168.1.5/linux/ks/rhel44.cfg' boot = 'd' sdl = 1 # use SDL for graphics vnc = 0 # use VNC for graphics vncviewer = 0 # spawn vncviewer by default nographic = 0 # don't use graphics serial='pty' # enable serial console regards, Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcc28_x at yahoo.co.uk Sun Jul 2 15:07:30 2006 From: mcc28_x at yahoo.co.uk (Mark Curry) Date: Sun, 2 Jul 2006 15:07:30 +0000 (GMT) Subject: [Fedora-xen] Networking Message-ID: <20060702150730.8833.qmail@web25003.mail.ukl.yahoo.com> Hi, I have successfully installed xen on fc5 but have a problem with the network. When I boot into the xen0 kernel I cannot access the internet. Fedora's networking tool shows that eth0 is inative, if I click on activate I receive a short error message stating 'unsuccessful'. The output of ifconfig is: eth0 Link encap:Ethernet HWaddr 00:26:54:14:FA:B0 UP BROADCAST RUNNING MULTICAST MTU:0 Metric:1 RX packets:17 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4496 (4.3 KiB) TX bytes:432 (432.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:275 errors:0 dropped:0 overruns:0 frame:0 TX packets:275 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:34710 (33.8 KiB) TX bytes:34710 (33.8 KiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:80 errors:0 dropped:0 overruns:0 frame:0 TX packets:84 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:12856 (12.5 KiB) TX bytes:7250 (7.0 KiB) Interrupt:19 Base address:0x2000 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:20 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:432 (432.0 b) TX bytes:4734 (4.6 KiB) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:13 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4286 (4.1 KiB) TX bytes:468 (468.0 b) I assume it's either something to do with a driver for my nics not being present in the xen kernel or something to do with the bridging. Help appreciated. Mark ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Mark Curry mcc28_x at yahoo.co.uk ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcc28_x at yahoo.co.uk Sun Jul 2 16:56:37 2006 From: mcc28_x at yahoo.co.uk (Mark Curry) Date: Sun, 2 Jul 2006 16:56:37 +0000 (GMT) Subject: [Fedora-xen] Networking In-Reply-To: <000c01c69df0$c174b180$3201a8c0@ltlabo> Message-ID: <20060702165637.58659.qmail@web25006.mail.ukl.yahoo.com> Thanks Eric, that worked. Mark --- Original Message ---- From: Eric Marty To: Mark Curry Sent: Sunday, 2 July, 2006 5:01:18 PM Subject: RE: [Fedora-xen] Networking Hello, May be is necessary to give ip for the eth0 card Ifconfig 192.168.1.1 up eric De : fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] De la part de Mark Curry Envoy? : dimanche 2 juillet 2006 17:08 ? : fedora-xen at redhat.com Objet : [Fedora-xen] Networking Hi, I have successfully installed xen on fc5 but have a problem with the network. When I boot into the xen0 kernel I cannot access the internet. Fedora's networking tool shows that eth0 is inative, if I click on activate I receive a short error message stating 'unsuccessful'. The output of ifconfig is: eth0 Link encap:Ethernet HWaddr 00:26:54:14:FA:B0 UP BROADCAST RUNNING MULTICAST MTU:0 Metric:1 RX packets:17 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4496 (4.3 KiB) TX bytes:432 (432.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:275 errors:0 dropped:0 overruns:0 frame:0 TX packets:275 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:34710 (33.8 KiB) TX bytes:34710 (33.8 KiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:80 errors:0 dropped:0 overruns:0 frame:0 TX packets:84 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:12856 (12.5 KiB) TX bytes:7250 (7.0 KiB) Interrupt:19 Base address:0x2000 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:20 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:432 (432.0 b) TX bytes:4734 (4.6 KiB) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:13 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4286 (4.1 KiB) TX bytes:468 (468.0 b) I assume it's either something to do with a driver for my nics not being present in the xen kernel or something to do with the bridging. Help appreciated. Mark ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Mark Curry mcc28_x at yahoo.co.uk ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan.vilt at linux360.ro Mon Jul 3 17:55:07 2006 From: razvan.vilt at linux360.ro (Razvan Corneliu C.R. VILT) Date: Mon, 3 Jul 2006 20:55:07 +0300 (EEST) Subject: [Fedora-xen] XenGetty Message-ID: <55677.193.239.134.1.1151949307.squirrel@mail.linux360.ro> After using the FC5 I created a rather trivial bash script that can spawn either xenconsole or mingetty on a given console. In order to use-it you have to add/change inittab entries. For example, to have the Rawhide XenU on tty5 if it's available or mingetty if not, you would have to change the mingetty tty5 line to the following (without the quotes: "5:345:respawn:/usr/sbin/xengetty Rawhide tty5" Here is the script (it's assumed that you'll put-it into /usr/sbin under the xengetty name): --------BEGIN SCRIPT------ #!/bin/bash # Small wrapper around xm console. # It will start mingetty if the domain is not available DOMAIN=$1 TTY=$2 XM=/usr/sbin/xm GETTY=/sbin/mingetty DOMID=`$XM domid $DOMAIN 2>/dev/null` if [ -z $DOMID ]; then exec $GETTY $TTY else exec $XM console $DOMID < /dev/$TTY > /dev/$TTY 2> /dev/$TTY fi ------END OF SCRIPT----- I created the script as I needed the feature and, although trivial, I am sure that mentioning this in the wiki might be helpful for others as well... Cheers, Razvan From malexand at wu-wien.ac.at Mon Jul 3 22:13:37 2006 From: malexand at wu-wien.ac.at (Michael Alexander) Date: Tue, 4 Jul 2006 07:13:37 +0900 Subject: [Fedora-xen] 2nd Call for Papers - Workshop on XEN in HPC Cluster and Grid Computing Environments (XHPC) Message-ID: <98267F7F-5795-43C9-9637-D67E9BB7F4F5@wu-wien.ac.at> Apologies if you received multiple copies of this message. =============================================================== CALL FOR PAPERS (XHPC'06) Workshop on XEN in High-Performance Cluster and Grid Computing Environments as part of: The Fourth International Symposium on Parallel and Distributed Processing and Applications (ISPA'2006). Sorrento, Italy =============================================================== Date: 1-4 December 2006 ISPA'2006: http://www.ispa-conference.org/2006/ Workshop URL: http://xhpc.ai.wu-wien.ac.at/ws/ (due date: August 4, Abstracts Jul 17) Scope: The Xen virtual machine monitor is reaching wide-spread adoption in a variety of operating systems as well as scientific educational and operational usage areas. With its low overhead, Xen allows for concurrently running large numbers of virtual machines, providing each encapsulation, isolation and network-wide CPU migratability. Xen offers a network-wide abstraction layer of individual machine resources to OS environments, thereby opening whole new cluster-and grid high-performance computing (HPC) architectures and HPC services options. With Xen finding applications in HPC environments, this workshop aims to bring together researchers and practitioners active on Xen in high-performance cluster and grid computing environments. The workshop will be one day in length, composed of 20 min paper presentations, each followed by 10 min discussion sections. Presentations may be accompanied with interactive demonstrations. The workshop will end with a 30 min panel discussion by presenters. TOPICS Topics include, but are not limited to, the following subject matters: - Xen in cluster and grid environments - Workload characterizations for Xen-based clusters - Xen cluster and grid architectures - Cluster reliability, fault-tolerance, and security - Compute job entry and scheduling - Compute workload load levelling - Cluster and grid filesystems for Xen - Research and education use cases - VM cluster distribution algorithms - MPI, PVM on virtual machines - System sizing - High-speed interconnects in Xen - Xen extensions and utilities for cluster and grid computing - Network architectures for Xen clusters - Xen on large SMP machines - Measuring performance - Performance tuning of Xen domains - Xen performance tuning on various load types - Xen cluster/grid tools - Management of Xen clusters PAPER SUBMISSION Papers submitted to each workshop will be reviewed by at least three members of the program committee and external reviewers. Submissions should include abstract, key words, the e-mail address of the corresponding author, and must not exceed 15 pages, including tables and figures, and preferably be in LaTeX or FrameMaker, although submissions in the LNCS Word format will be accepted as well. Electronic submission through the submission website is strongly encouraged. Hardcopies will be accepted only if electronic submission is not possible. Submission of a paper should be regarded as a commitment that, should the paper be accepted, at least one of the authors will register and attend the conference to present the work. An award for best student paper will be given. https://edas.info/newPaper.php?c=4945&submit=0& Format should be according to the Springer LNCS Style http://www.springer.de/comp/lncs/authors.html It is expected that the proceedings of the workshop programs will be published by Springer's LNCS series or IEEE CS. IMPORTANT DATES July 17, 2006 - Abstract submissions due Paper submission due: August 4, 2006 Acceptance notification: September 1, 2006 Camera-ready due: September 20, 2006 Conference: December 1-4, 2006 CHAIR Michael Alexander (chair), WU Vienna, Austria Geyong Min (co-chair), University of Bradford, UK Gudula Ruenger (co-chair), Chemnitz University of Technology, Germany PROGRAM COMMITTEE Franck Cappello, INRIA, France Stephen Childs, Trinity College, Ireland Claudia Eckert, Fraunhofer-Institute, Germany Rob Gardner, HP Labs, USA Bill Gardner, University of Guelph, Cananda Marcus Hardt, Forschungszentrum Karlsruhe, Germany Sverre Jarp, CERN, Switzerland Thomas Lange, University of Cologne, Germany Ronald Luijten, IBM Research Laboratory, Zurich, Switzerland Klaus Ita, WU Vienna, Austria Franco Travostino, Nortel CTO Office, USA Andreas Unterkircher, CERN, Switzerland GENERAL INFORMATION This workshop will be held as part of ISPA 2006 in Sorrento, Italy - http://www.sorrentoinfo.com/sorrento/sorrento_italy.asp Pre-conference trip to the ESA ESRIN facility in Frascati on Nov. 30. From andreanaggi at gmail.com Tue Jul 4 16:17:37 2006 From: andreanaggi at gmail.com (Andrea Naggi) Date: Tue, 4 Jul 2006 18:17:37 +0200 Subject: [Fedora-xen] Xen dom-U network problem Message-ID: <83d3df300607040917w7947a39aned9cf920d1c503dc@mail.gmail.com> Dear All, I have a problem in my FC5 xen installation. I am using FC5 as dom-0 and everything works well here, the problem is in the FC5 dom-U. It can NOT see the eth0 device. Adding the line 'alias eth0 xennet' to /etc/modprobe.conf did not solve the problem, it still complains about the device not being ready... any suggestions? thankyou Andrea -------------- next part -------------- An HTML attachment was scrubbed... URL: From alseat at comcast.net Tue Jul 4 18:28:12 2006 From: alseat at comcast.net (Algie Seat) Date: Tue, 4 Jul 2006 13:28:12 -0500 Subject: [Fedora-xen] FC6 - TEST1 - Problem running Xen-domU guest Message-ID: <200607041903.k64J3FRd022416@mx3.redhat.com> I am trying to run a FC6 Xen guest under FC6. A xen-domU kernel was not included in the test1 ISOs I downloaded. I can run a FC5 guest under FC6 because there is a xen-domU kernel include in the ISOs. My FC6 kernel is 2.6.16-1.2289_FC6xen. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mads at kiilerich.com Tue Jul 4 19:17:36 2006 From: mads at kiilerich.com (Mads Kiilerich) Date: Tue, 04 Jul 2006 21:17:36 +0200 Subject: [Fedora-xen] Xen dom-U network problem In-Reply-To: <83d3df300607040917w7947a39aned9cf920d1c503dc@mail.gmail.com> References: <83d3df300607040917w7947a39aned9cf920d1c503dc@mail.gmail.com> Message-ID: <44AABED0.7020100@kiilerich.com> Andrea Naggi wrote: > I am using FC5 as dom-0 and everything works well here, the problem is > in the FC5 dom-U. > It can NOT see the eth0 device. Hi Andrea, I have a similar problem - see https://www.redhat.com/archives/fedora-xen/2006-June/msg00160.html I have not solved the problem yet, but hinted by http://www.debian-administration.org/articles/396 I ran mkinitrd for the dom0 kernel. After a reboot that gave me the xen network devices back, but the guest installer still doesn't work... /Mads From yunfeng.zhao at intel.com Wed Jul 5 02:07:25 2006 From: yunfeng.zhao at intel.com (Zhao, Yunfeng) Date: Wed, 5 Jul 2006 10:07:25 +0800 Subject: [Fedora-xen] FC6 - TEST1 - Problem running Xen-domU guest Message-ID: <08B1877B2880CE42811294894F33AD5C68C327@pdsmsx411.ccr.corp.intel.com> In FC6 Test1 xenu and xen0 share the same kernel and initrd. You need to modify the example config file and boot xenu with 2.6.16-1.2289_FC6xen. Thanks Yunfeng ________________________________________ From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Algie Seat Sent: 2006?7?5? 2:28 To: fedora-xen at redhat.com Subject: [Fedora-xen] FC6 - TEST1 - Problem running Xen-domU guest I am trying to run a FC6 Xen guest under FC6.? ?A xen-domU kernel was not included in the test1 ISOs I downloaded. I can run a FC5 guest under FC6 because there is a xen-domU kernel include in the ISOs. My FC6 kernel is 2.6.16-1.2289_FC6xen. ? From yunfeng.zhao at intel.com Wed Jul 5 02:13:36 2006 From: yunfeng.zhao at intel.com (Zhao, Yunfeng) Date: Wed, 5 Jul 2006 10:13:36 +0800 Subject: [Fedora-xen] xen changeset is not available Message-ID: <08B1877B2880CE42811294894F33AD5C68C328@pdsmsx411.ccr.corp.intel.com> Xen changeset is not available on FC6 Test1. And this info is very useful for fedora-xen user. Is it possible to build changeset number in xen binary of FC6? Thanks Yunfeng From lists-gawain at felicity-group.com Wed Jul 5 08:04:02 2006 From: lists-gawain at felicity-group.com (Gawain Lynch) Date: Wed, 05 Jul 2006 18:04:02 +1000 Subject: [Fedora-xen] xen changeset is not available In-Reply-To: <08B1877B2880CE42811294894F33AD5C68C328@pdsmsx411.ccr.corp.intel.com> References: <08B1877B2880CE42811294894F33AD5C68C328@pdsmsx411.ccr.corp.intel.com> Message-ID: <1152086642.5022.2.camel@legolas.felicity.net.au> On Wed, 2006-07-05 at 10:13 +0800, Zhao, Yunfeng wrote: > Xen changeset is not available on FC6 Test1. > And this info is very useful for fedora-xen user. > > Is it possible to build changeset number in xen binary of FC6? I have to agree with this one. It would be useful to me too. From katzj at redhat.com Wed Jul 5 14:01:16 2006 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 05 Jul 2006 10:01:16 -0400 Subject: [Fedora-xen] Re: xen changeset is not available In-Reply-To: <08B1877B2880CE42811294894F33AD5C68C328@pdsmsx411.ccr.corp.intel.com> References: <08B1877B2880CE42811294894F33AD5C68C328@pdsmsx411.ccr.corp.intel.com> Message-ID: <1152108076.20228.47.camel@aglarond.local> On Wed, 2006-07-05 at 10:13 +0800, Zhao, Yunfeng wrote: > Xen changeset is not available on FC6 Test1. > And this info is very useful for fedora-xen user. > > Is it possible to build changeset number in xen binary of FC6? There isn't just one changeset, though. The HV is one changeset of -unstable, the kernel patch comes from the hg tree that tracks Linus's tree (and thus doesn't have a directly applicable changeset) and the tools are a third. Although hopefully for releases, the tools are actually a _released_ version of the tools rather than random changeset of the day. So the single "one size fits all" changeset mentality of Xen doesn't really work. We do try to note the changeset in the spec files/changelogs when doing updates. Jeremy From alseat at comcast.net Wed Jul 5 15:45:47 2006 From: alseat at comcast.net (Algie Seat) Date: Wed, 5 Jul 2006 10:45:47 -0500 Subject: [Fedora-xen] FC6 - TEST1 - Problem running Xen-domU guest In-Reply-To: <08B1877B2880CE42811294894F33AD5C68C327@pdsmsx411.ccr.corp.intel.com> Message-ID: <200607051620.k65GKPoS015458@mx3.redhat.com> I am running the xenguest-install.py script to do the install of the FC6 guest. The kernel being booted for the install is 2.6.16-1.2289_FC6xen which is the same kernel running in Domain-0. The kernel boots fine and I answer the usual questions about keyboard and language. I then put in a static IP address on the same subnet as my NFS install server. Once I do this and hit enter, I get a message in about 5 seconds saying "that directory cannot be mounted from the server". I don't understand this because the NFS server name and Fedora Core Directory are accurate. They are filled in because I answered the question form the xenguest-install-py script about the location for the install being nfs:192.168.0.249:/install/fedora/xen/algie. I know the NFS install image on my NFS server is correct because I installed the base Domain-0 image from it. The guest being installed is para-virtualized and I can see that the bridge device for the domain being installed has been created (brctl show). I am using the exact same procedure to install a FC5 guest (different install image of course) and it works fine. I am totally up to date on all packages also. -----Original Message----- From: Zhao, Yunfeng [mailto:yunfeng.zhao at intel.com] Sent: Tuesday, July 04, 2006 9:07 PM To: Algie Seat; fedora-xen at redhat.com Subject: RE: [Fedora-xen] FC6 - TEST1 - Problem running Xen-domU guest In FC6 Test1 xenu and xen0 share the same kernel and initrd. You need to modify the example config file and boot xenu with 2.6.16-1.2289_FC6xen. Thanks Yunfeng ________________________________________ From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Algie Seat Sent: 2006?7?5? 2:28 To: fedora-xen at redhat.com Subject: [Fedora-xen] FC6 - TEST1 - Problem running Xen-domU guest I am trying to run a FC6 Xen guest under FC6. A xen-domU kernel was not included in the test1 ISOs I downloaded. I can run a FC5 guest under FC6 because there is a xen-domU kernel include in the ISOs. My FC6 kernel is 2.6.16-1.2289_FC6xen. From sennol at student.ethz.ch Wed Jul 5 18:04:08 2006 From: sennol at student.ethz.ch (Oliver Senn (D-INFK, ETH Zurich)) Date: Wed, 05 Jul 2006 20:04:08 +0200 Subject: [Fedora-xen] Error when booting with xen kernel: trap divide error Message-ID: <44ABFF18.7090003@student.ethz.ch> Hi, When I boot (with the xen kernel) I get the following error messages which fill the whole screen and then nothing happens afterwards: init[1] trap divide error rip:4296d7 rsp:7fffd49e7db0 error:0 I use a RAID configuration. May this cause this errors? thanks Oli From garysiao at gmail.com Thu Jul 6 15:14:01 2006 From: garysiao at gmail.com (Gary Siao) Date: Thu, 6 Jul 2006 11:14:01 -0400 Subject: [Fedora-xen] heeeeeeeelp on XEN Message-ID: hi gurus i'm a newbie to xen and like some guidance... i have an existing machine that has FC5 and i just installed XEN3.0.2.2.. was able to boot the machine using XEN... i know the next step is to create a guest domain but my problem is how do i create an image of the existing FC5 since it has some data already (would be nice if you can give me the actual command).. also once i created an image of the existing FC5, where do i dump th image file and have xen boot from it... thanks Gary -------------- next part -------------- An HTML attachment was scrubbed... URL: From bench at silentmedia.com Thu Jul 6 17:36:03 2006 From: bench at silentmedia.com (Ben) Date: Thu, 6 Jul 2006 10:36:03 -0700 Subject: [Fedora-xen] problem with 2.6.17-1.2145? Message-ID: After upgrading to 2.6.17-.2145_FC5xen0, I have problems with depmod: # /sbin/depmod -a WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/kernel/ intermodule.ko is not an elf object WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/lib/ crc16.ko is not an elf object WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/lib/crc- ccitt.ko is not an elf object WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/ video/cirrusfb.ko is not an elf object WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/ video/backlight/lcd.ko is not an elf object WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/usb/ serial/ir-usb.ko is not an elf object WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/usb/ serial/keyspan.ko is not an elf object WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/usb/ atm/usbatm.ko is not an elf object WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/usb/ misc/sisusbvga/sisusbvga.ko is not an elf object WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/net/tux/ tux.ko is not an elf object WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/sound/pci/ trident/snd-trident.ko is not an elf object Segmentation fault Has anybody else seen stuff like this? Unfortunately I can't seem to just roll back to my previous kernel, because xen was also upgraded (to 3.0.2-3) and doesn't apparently work with 2.6.16-1.2133 anymore. From bench at silentmedia.com Thu Jul 6 20:03:21 2006 From: bench at silentmedia.com (Ben) Date: Thu, 6 Jul 2006 13:03:21 -0700 Subject: [Fedora-xen] problem with 2.6.17-1.2145? In-Reply-To: References: Message-ID: <94FF2483-486F-4A37-A2E1-449F0351807E@silentmedia.com> FYI, I "fixed" this by removing and reinstalling the 2.6.17-1.2145_FC5xen0 rpm. To me, that implies that the previous rpm I installed was corrupted somehow. But how can that be? I thought rpms were all signed? On Jul 6, 2006, at 10:36 AM, Ben wrote: > After upgrading to 2.6.17-.2145_FC5xen0, I have problems with depmod: > > # /sbin/depmod -a > WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/kernel/ > intermodule.ko is not an elf object > WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/lib/ > crc16.ko is not an elf object > WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/lib/crc- > ccitt.ko is not an elf object > WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/ > video/cirrusfb.ko is not an elf object > WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/ > video/backlight/lcd.ko is not an elf object > WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/ > usb/serial/ir-usb.ko is not an elf object > WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/ > usb/serial/keyspan.ko is not an elf object > WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/ > usb/atm/usbatm.ko is not an elf object > WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/drivers/ > usb/misc/sisusbvga/sisusbvga.ko is not an elf object > WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/net/tux/ > tux.ko is not an elf object > WARNING: Module /lib/modules/2.6.17-1.2145_FC5xen0/kernel/sound/pci/ > trident/snd-trident.ko is not an elf object > Segmentation fault > > > Has anybody else seen stuff like this? Unfortunately I can't seem > to just roll back to my previous kernel, because xen was also > upgraded (to 3.0.2-3) and doesn't apparently work with > 2.6.16-1.2133 anymore. > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From aron at hp.com Thu Jul 6 20:49:11 2006 From: aron at hp.com (Aron Griffis) Date: Thu, 6 Jul 2006 16:49:11 -0400 Subject: [Fedora-xen] [PATCH] enable xen-ia64 in fedora kernel cvs Message-ID: <20060706204911.GA2551@vino.zko.hp.com> This patch enables xen-ia64 support in the fedora kernel. It applies to the cvs tree checked out according to the instructions at http://people.redhat.com/davej/ At this point I'm requesting this patch be applied. Until the hypervisor is updated to match the generic linux-2.6-xen.patch, it won't actually boot xen on ia64, but IMHO the changes are clean and there's no reason to believe they won't work when %includexen and %buildxen are re-enabled. (It has already been demonstrated previously on this list that the patches work in general and that fedora-xen-ia64 builds, boots and runs ;-) Breakdown of the changes: - Add $(CFG)-ia64-xen.config target to devel/Makefile.config - Add devel/configs/config-xen-ia64 override snippet - Add xen_flags, xen_target and xen_image to spec-file to genericize building of the hypervisor - Add two symlinks that are specific to building on ia64. These symlinks aren't required in xen-ia64-unstable upstream, so include shell conditionals to announce when they should be retired from the spec file Caveats: - As described earlier, we need Juan to start matching the hypervisor tarball to the xen-unstable changeset associated with linux-2.6-xen.patch. It breaks boot on ia64 presently, but could affect any architecture, so this is an important change in general. - As of 2.6.17, configs/config-ia64-generic needs CONFIG_PNPACPI=y to boot on systems without a graphics head. This is not related to xen so I didn't include it in this patch. I'll be sending a separate patch for this issue, cc'ing fedora-ia64 Signed-off-by: Aron Griffis devel/configs/config-xen-ia64 | 19 ++++++++++++ devel/Makefile.config | 18 ++++++++++-- devel/kernel-2.6.spec | 60 ++++++++++++++++++++++++++++------------ 3 files changed, 76 insertions(+), 21 deletions(-) diff -r da3fa23e3220 -r 08b309b90c4f devel/Makefile.config --- a/devel/Makefile.config Thu Jul 06 11:34:32 2006 -0400 +++ b/devel/Makefile.config Thu Jul 06 16:40:56 2006 -0400 @@ -13,7 +13,8 @@ CONFIGFILES = \ $(CFG)-ppc.config $(CFG)-ppc-smp.config \ $(CFG)-ppc64.config $(CFG)-ppc64-kdump.config $(CFG)-ia64.config \ $(CFG)-i686-xen-PAE.config \ - $(CFG)-i686-xen.config $(CFG)-x86_64-xen.config + $(CFG)-i686-xen.config $(CFG)-x86_64-xen.config \ + $(CFG)-ia64-xen.config PLATFORMS = x86 x86_64 powerpc powerpc32 powerpc64 s390 ia64 # sparc sparc64 TEMPFILES = $(addprefix temp-, $(addsuffix -generic, $(PLATFORMS))) @@ -21,8 +22,10 @@ configs: $(CONFIGFILES) configs: $(CONFIGFILES) @rm -f kernel-*-config @rm -f $(TEMPFILES) - @rm -f temp-xen-generic temp-x86-xen-generic temp-x86_64-xen-generic \ - temp-generic temp-x86_64-xen-generic-tmp + @rm -f temp-generic temp-xen-generic \ + temp-x86-xen-generic \ + temp-x86_64-xen-generic temp-x86_64-xen-generic-tmp \ + temp-ia64-xen-generic temp-ia64-xen-generic-tmp # Augment the clean target to clean up our own cruft clean :: @@ -69,6 +72,12 @@ temp-x86_64-xen-generic-tmp: configs/con perl scripts/merge.pl $^ > $@ temp-x86_64-xen-generic: configs/config-xen-x86_64 temp-x86_64-xen-generic-tmp + perl scripts/merge.pl $^ > $@ + +temp-ia64-xen-generic-tmp: configs/config-xen-generic temp-ia64-generic + perl scripts/merge.pl $^ > $@ + +temp-ia64-xen-generic: configs/config-xen-ia64 temp-ia64-xen-generic-tmp perl scripts/merge.pl $^ > $@ kernel-$(VERSION)-i686.config: configs/config-i686 temp-x86-generic @@ -134,3 +143,6 @@ kernel-$(VERSION)-x86_64-xen.config: con kernel-$(VERSION)-x86_64-xen.config: configs/config-xen-xen temp-x86_64-xen-generic perl scripts/merge.pl $^ x86_64 > $@ +kernel-$(VERSION)-ia64-xen.config: configs/config-xen-xen temp-ia64-xen-generic + perl scripts/merge.pl $^ ia64 > $@ + diff -r da3fa23e3220 -r 08b309b90c4f devel/kernel-2.6.spec --- a/devel/kernel-2.6.spec Thu Jul 06 11:34:32 2006 -0400 +++ b/devel/kernel-2.6.spec Thu Jul 06 16:40:56 2006 -0400 @@ -31,6 +31,9 @@ Summary: The Linux kernel (the core of t %define xen_version 20060610 %define make_target bzImage %define kernel_image x86 +%define xen_flags verbose=y debug=y crash_debug=y +%define xen_target vmlinuz +%define xen_image vmlinuz %define KVERREL %{PACKAGE_VERSION}-%{PACKAGE_RELEASE} @@ -50,10 +53,14 @@ Summary: The Linux kernel (the core of t %define all_arch_configs $RPM_SOURCE_DIR/kernel-%{kversion}-*.config %endif -# Xen and kdump only build on i686 and x86_64 ... +# kdump only builds on i686 and x86_64 %ifnarch i686 x86_64 +%define buildkdump 0 +%endif + +# Xen only builds on i686, x86_64 and ia64 ... +%ifnarch i686 x86_64 ia64 %define buildxen 0 -%define buildkdump 0 %endif %ifarch ppc64 @@ -127,11 +134,15 @@ Summary: The Linux kernel (the core of t %endif %ifarch ia64 -%define all_arch_configs $RPM_SOURCE_DIR/kernel-%{kversion}-ia64.config +%define all_arch_configs $RPM_SOURCE_DIR/kernel-%{kversion}-ia64*.config %define image_install_path boot/efi/EFI/redhat #define signmodules 1 %define make_target compressed %define kernel_image vmlinux.gz +# ia64 doesn't building with debug=y at the moment +%define xen_flags verbose=y crash_debug=y +%define xen_target compressed +%define xen_image vmlinux.gz %endif # @@ -230,6 +241,7 @@ Source34: kernel-%{kversion}-x86_64-xen. Source34: kernel-%{kversion}-x86_64-xen.config Source35: kernel-%{kversion}-i686-kdump.config Source36: kernel-%{kversion}-i686-xen-PAE.config +Source37: kernel-%{kversion}-ia64-xen.config #Source66: kernel-%{kversion}-sparc.config #Source67: kernel-%{kversion}-sparc64.config @@ -774,17 +786,29 @@ cd linux-%{kversion}.%{_target_cpu} # %patch950 -p1 -b .p.xen # -# ... and back out all the ia64-specific sections, as they currently prevent +# ... and back out all the tpm-specific sections, as they currently prevent # non-xen builds from working. -# Now also with tpm -# -for f in `find drivers/char/tpm arch/ia64/ include/asm-ia64/ include/xen/interface/arch-ia64.h* -type f -name "*.p.xen"` ; do \ +# +for f in `find drivers/char/tpm -type f -name "*.p.xen"` ; do \ g=`dirname $f`/`basename $f .p.xen`; \ mv "$f" "$g"; \ if [ ! -s "$g" ] ; then rm -f "$g" ; fi; \ done # Delete the rest of the backup files, they just confuse the build later find -name "*.p.xen" | xargs rm -f + +# These are fixed in xen-ia64-unstable, they will announce their retirement +# automatically when the changes propogate down the chain to Juan +if [[ ! -f arch/ia64/kernel/asm-offsets.c ]]; then + ln -sf ../../../../xen/include/asm-ia64/asm-xsi-offsets.h include/asm-ia64/xen/ +else + printf "*\n* please retire asm-xsi-offsets.h symlink from kernel-2.6.spec\n*\n" +fi +if grep -q xenia64_init drivers/xen/core/Makefile; then + ln -sf ../../../arch/ia64/xen/drivers/xenia64_init.c drivers/xen/core/ +else + printf "*\n* please retire xenia64_init.c symlink from kernel-2.6.spec\n*\n" +fi %patch951 -p1 %patch952 -p1 @@ -1192,15 +1216,15 @@ mkdir -p $RPM_BUILD_ROOT/boot %if %{includexen} %if %{buildxen} cd xen - mkdir -p $RPM_BUILD_ROOT/%{image_install_path} + mkdir -p $RPM_BUILD_ROOT/%{image_install_path} $RPM_BUILD_ROOT/boot %if %{buildxenPAE} - make debug=y verbose=y crash_debug=y pae=y - install -m 644 xen.gz $RPM_BUILD_ROOT/boot/xen.gz-%{KVERREL}-PAE + make %{?_smp_mflags} %{xen_flags} pae=y + install -m 644 xen.gz $RPM_BUILD_ROOT/%{image_install_path}/xen.gz-%{KVERREL}-PAE install -m 755 xen-syms $RPM_BUILD_ROOT/boot/xen-syms-%{KVERREL}-PAE make clean %endif - make debug=y verbose=y crash_debug=y - install -m 644 xen.gz $RPM_BUILD_ROOT/boot/xen.gz-%{KVERREL} + make %{?_smp_mflags} %{xen_flags} + install -m 644 xen.gz $RPM_BUILD_ROOT/%{image_install_path}/xen.gz-%{KVERREL} install -m 755 xen-syms $RPM_BUILD_ROOT/boot/xen-syms-%{KVERREL} cd .. %endif @@ -1222,11 +1246,11 @@ BuildKernel %make_target %kernel_image s %if %{includexen} %if %{buildxenPAE} -BuildKernel vmlinuz vmlinuz xen-PAE +BuildKernel %xen_target %xen_image xen-PAE %endif %if %{buildxen} -BuildKernel vmlinuz vmlinuz xen +BuildKernel %xen_target %xen_image xen %endif %endif @@ -1331,7 +1355,7 @@ fi %post xen [ ! -x /usr/sbin/module_upgrade ] || /usr/sbin/module_upgrade %{rpmversion}-%{release}-xen if [ -e /proc/xen/xsd_kva -o ! -d /proc/xen ]; then - /sbin/new-kernel-pkg --package kernel-xen --mkinitrd --depmod --install --multiboot=/boot/xen.gz-%{KVERREL} %{KVERREL}xen + /sbin/new-kernel-pkg --package kernel-xen --mkinitrd --depmod --install --multiboot=/%{image_install_path}/xen.gz-%{KVERREL} %{KVERREL}xen else /sbin/new-kernel-pkg --package kernel-xen --mkinitrd --depmod --install %{KVERREL}xen fi @@ -1348,7 +1372,7 @@ fi %post xen-PAE [ ! -x /usr/sbin/module_upgrade ] || /usr/sbin/module_upgrade %{rpmversion}-%{release}-xen-PAE if [ -e /proc/xen/xsd_kva ]; then - /sbin/new-kernel-pkg --package kernel-xen-PAE --mkinitrd --depmod --install --multiboot=/boot/xen.gz-%{KVERREL}-PAE %{KVERREL}xen-PAE + /sbin/new-kernel-pkg --package kernel-xen-PAE --mkinitrd --depmod --install --multiboot=/%{image_install_path}/xen.gz-%{KVERREL}-PAE %{KVERREL}xen-PAE else /sbin/new-kernel-pkg --package kernel-xen-PAE --mkinitrd --depmod --install %{KVERREL}xen-PAE fi @@ -1477,7 +1501,7 @@ fi /boot/symvers-%{KVERREL}xen.gz /boot/symsets-%{KVERREL}xen.tar.gz /boot/config-%{KVERREL}xen -/boot/xen.gz-%{KVERREL} +/%{image_install_path}/xen.gz-%{KVERREL} /boot/xen-syms-%{KVERREL} %dir /lib/modules/%{KVERREL}xen /lib/modules/%{KVERREL}xen/kernel @@ -1502,7 +1526,7 @@ fi /boot/symvers-%{KVERREL}xen-PAE.gz /boot/symsets-%{KVERREL}xen-PAE.tar.gz /boot/config-%{KVERREL}xen-PAE -/boot/xen.gz-%{KVERREL}-PAE +/%{image_install_path}/xen.gz-%{KVERREL}-PAE /boot/xen-syms-%{KVERREL}-PAE %dir /lib/modules/%{KVERREL}xen-PAE /lib/modules/%{KVERREL}xen-PAE/kernel diff -r da3fa23e3220 -r 08b309b90c4f devel/configs/config-xen-ia64 --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/devel/configs/config-xen-ia64 Thu Jul 06 16:40:56 2006 -0400 @@ -0,0 +1,19 @@ +# override i686 xen + +# CONFIG_X86 is not set +# CONFIG_X86_XEN is not set +CONFIG_IA64=y +CONFIG_XEN=y +CONFIG_XEN_IA64_DOM0_VP=y +CONFIG_XEN_DISABLE_SERIAL=y + +# override ia64 generic + +# CONFIG_IA64_GENERIC is not set +CONFIG_IA64_DIG=y +# CONFIG_DISCONTIGMEM_MANUAL is not set +CONFIG_FLATMEM_MANUAL=y +CONFIG_FORCE_MAX_ZONEORDER=11 + +# internal #defines conflict with xen-ia64 +# CONFIG_FB_NEOMAGIC is not set -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From aron at hp.com Thu Jul 6 20:57:29 2006 From: aron at hp.com (Aron Griffis) Date: Thu, 6 Jul 2006 16:57:29 -0400 Subject: [Fedora-xen] [RFC 2/3] libvirt.rpm patches In-Reply-To: <20060623152959.GG1330@redhat.com> References: <20060623152959.GG1330@redhat.com> Message-ID: <20060706205729.GA30663@vino.zko.hp.com> Hi Daniel, Daniel Veillard wrote: [Fri Jun 23 2006, 11:29:59AM EDT] > Initially xen didn't compiled on ia64, I will fix it, thanks for the > head-up ! It appears this hasn't been fixed yet. Here is the patch against the current src.rpm. Could you please apply it at this point? Thanks, Aron Signed-off-by: Aron Griffis --- a/SPECS/libvirt.spec Thu Jul 06 16:17:25 2006 -0400 +++ b/SPECS/libvirt.spec Thu Jul 06 16:56:45 2006 -0400 @@ -14,7 +14,7 @@ BuildRequires: libxml2-devel BuildRequires: libxml2-devel BuildRequires: readline-devel Obsoletes: libvir -ExclusiveArch: i386 x86_64 +ExclusiveArch: i386 x86_64 ia64 Patch0: chown.patch %description From aron at hp.com Thu Jul 6 21:01:44 2006 From: aron at hp.com (Aron Griffis) Date: Thu, 6 Jul 2006 17:01:44 -0400 Subject: [Fedora-xen] [RFC 3/3] xen.rpm patches In-Reply-To: References: Message-ID: <20060706210144.GB30663@vino.zko.hp.com> Here is the updated patch against xen-3.0.2-9.src.rpm. Could this be applied at this point? Signed-off-by: Aron Griffis xen.spec | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff -r e99d0fc56705 -r ca34d01a0d0b SPECS/xen.spec --- a/SPECS/xen.spec Thu Jul 06 16:22:00 2006 -0400 +++ b/SPECS/xen.spec Thu Jul 06 16:22:27 2006 -0400 @@ -27,20 +27,22 @@ BuildRequires: transfig libidn-devel zli BuildRequires: transfig libidn-devel zlib-devel texi2html SDL-devel curl-devel BuildRequires: libX11-devel python-devel ghostscript tetex-latex BuildRequires: ncurses-devel +%ifarch i386 x86_64 # for the VMX "bios" BuildRequires: dev86 +# so that x86_64 builds pick up glibc32 correctly +BuildRequires: /usr/include/gnu/stubs-32.h +%endif # for the docs BuildRequires: perl # so that the makefile knows to install udev rules BuildRequires: udev -# so that x86_64 builds pick up glibc32 correctly -BuildRequires: /usr/include/gnu/stubs-32.h Requires: bridge-utils Requires: python-abi = %(%{__python} -c "import sys ; print sys.version[:3]") Requires: udev >= 059 Requires: libvirt-python Prereq: chkconfig -ExclusiveArch: i386 x86_64 +ExclusiveArch: i386 x86_64 ia64 %description This package contains the Xen hypervisor and Xen tools, needed to @@ -152,9 +154,9 @@ rm -rf $RPM_BUILD_ROOT %{_libdir}/%{name} %{_libdir}/lib* %{_mandir}/man?/*.?.gz -%dir /usr/lib/xen -%dir /usr/lib/xen/boot +%ifarch i386 x86_64 /usr/lib/xen/boot/hvmloader +%endif %dir %{_datadir}/%{name}/qemu %{_datadir}/%{name}/qemu/keymaps/* %dir %{_localstatedir}/lib/%{name} From veillard at redhat.com Thu Jul 6 21:41:16 2006 From: veillard at redhat.com (Daniel Veillard) Date: Thu, 6 Jul 2006 17:41:16 -0400 Subject: [Fedora-xen] [RFC 2/3] libvirt.rpm patches In-Reply-To: <20060706205729.GA30663@vino.zko.hp.com> References: <20060623152959.GG1330@redhat.com> <20060706205729.GA30663@vino.zko.hp.com> Message-ID: <20060706214116.GM967@redhat.com> On Thu, Jul 06, 2006 at 04:57:29PM -0400, Aron Griffis wrote: > Hi Daniel, > > Daniel Veillard wrote: [Fri Jun 23 2006, 11:29:59AM EDT] > > Initially xen didn't compiled on ia64, I will fix it, thanks for the > > head-up ! > > It appears this hasn't been fixed yet. Here is the patch against the > current src.rpm. Could you please apply it at this point? It was applied, I had to roll it back since xen was not available on ia64 builds when I tried to push 0.1.2 on the build system on monday 15: paphio:~/libvirt -> cvs -z0 diff -r 1.14 -r 1.15 libvirt.spec.in Index: libvirt.spec.in =================================================================== RCS file: /data/cvs/libxen/libvirt.spec.in,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- libvirt.spec.in 3 Jul 2006 15:48:49 -0000 1.14 +++ libvirt.spec.in 4 Jul 2006 12:46:14 -0000 1.15 @@ -14,7 +14,7 @@ BuildRequires: libxml2-devel BuildRequires: readline-devel Obsoletes: libvir -ExclusiveArch: i386 x86_64 ia64 +ExclusiveArch: i386 x86_64 %description This C library provides an API to use the Xen virtualization framework, @@ -75,7 +75,7 @@ %doc %{_mandir}/man1/virsh.1* %{_bindir}/virsh %{_libdir}/lib*.so.* -%{_libexecdir}/libvirt_proxy +%attr(4755, root, root) %{_libexecdir}/libvirt_proxy %files devel %defattr(-, root, root) paphio:~/libvirt -> I really can't change it before xen itself is rebuilt and available for this architecture. Daniel -- Daniel Veillard | Red Hat http://redhat.com/ veillard at redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From aron at hp.com Thu Jul 6 21:54:06 2006 From: aron at hp.com (Aron Griffis) Date: Thu, 6 Jul 2006 17:54:06 -0400 Subject: [Fedora-xen] Re: xen changeset is not available In-Reply-To: <1152108076.20228.47.camel@aglarond.local> References: <08B1877B2880CE42811294894F33AD5C68C328@pdsmsx411.ccr.corp.intel.com> <1152108076.20228.47.camel@aglarond.local> Message-ID: <20060706215406.GD30663@vino.zko.hp.com> Jeremy Katz wrote: [Wed Jul 05 2006, 10:01:16AM EDT] > On Wed, 2006-07-05 at 10:13 +0800, Zhao, Yunfeng wrote: > > Xen changeset is not available on FC6 Test1. > > And this info is very useful for fedora-xen user. > > > > Is it possible to build changeset number in xen binary of FC6? > > There isn't just one changeset, though. The HV is one changeset of > -unstable, the kernel patch comes from the hg tree that tracks > Linus's tree (and thus doesn't have a directly applicable changeset) > and the tools are a third. Although hopefully for releases, the > tools are actually a _released_ version of the tools rather than > random changeset of the day. IMHO this is the wrong approach. It's already bitten ia64, and it's bound to bite other architectures at some point. See my comments at https://www.redhat.com/archives/fedora-xen/2006-June/msg00154.html along with Chris's response. Fedora should be using matched versions of hypervisor, xenlinux patch and tools, at least as much as possible. In any case, providing the xen-unstable changeset on which each is based would be helpful to all parties involved. Granted, the linux-2.6-xen.patch comes from linux-2.6.tip-xen rather than xen-unstable directly, but if you trace it back, you can find out the xen-unstable changeset on which it's based. At that point, snapshotting the hypervisor to match becomes relatively easy, and so does providing the changeset in the release/changelog/description/etc. Here's an example, if it's helpful: hg clone http://xenbits.xensource.com/ext/linux-2.6.tip-xen.hg cd linux-2.6.tip-xen.hg xen_unstable_cset=$(hg log -v | awk -F '[ :]' \ '/^xen-unstable changeset:/{print $(NF-1);exit}') So then, make a matched hypervisor: hg clone http://xenbits.xensource.com/ext/xen-unstable.hg cd xen-unstable.hg hg up -C $xen_unstable_cset tar cjf ../xen-$xen_unstable_cset.tar.bz2 xen Regards, Aron -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From aron at hp.com Thu Jul 6 22:35:13 2006 From: aron at hp.com (Aron Griffis) Date: Thu, 6 Jul 2006 18:35:13 -0400 Subject: [Fedora-ia64-list] Re: [Fedora-xen] [RFC 2/3] libvirt.rpm patches In-Reply-To: <20060706214116.GM967@redhat.com> References: <20060623152959.GG1330@redhat.com> <20060706205729.GA30663@vino.zko.hp.com> <20060706214116.GM967@redhat.com> Message-ID: <20060706223513.GD3957@vino.zko.hp.com> Daniel Veillard wrote: [Thu Jul 06 2006, 05:41:16PM EDT] > I really can't change it before xen itself is rebuilt and available for this > architecture. By xen, I assume you're referring to xen.rpm (tools) rather than the hypervisor... I've also requested that to be patched. See https://www.redhat.com/archives/fedora-xen/2006-July/msg00022.html Thanks for trying. Hopefully you can reapply the patch soon. Regards, Aron From mdehaan at redhat.com Fri Jul 7 20:18:18 2006 From: mdehaan at redhat.com (Michael DeHaan) Date: Fri, 07 Jul 2006 16:18:18 -0400 Subject: [Fedora-xen] heeeeeeeelp on XEN In-Reply-To: References: Message-ID: <44AEC18A.9090705@redhat.com> Gary Siao wrote: > hi gurus > > i'm a newbie to xen and like some guidance... > > i have an existing machine that has FC5 and i just installed > XEN3.0.2.2.. was able to boot the machine using XEN... i know the next > step is to create a guest domain but my problem is how do i create an > image of the existing FC5 since it has some data already (would be > nice if you can give me the actual command).. also once i created an > image of the existing FC5, where do i dump th image file and have xen > boot from it... > > thanks > Gary > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > AFAIK, there is no good way to clone an existing host system and make a matching domU (guest OS) from it automagically. What you can do is provision a new domU (see /usr/sbin/xenguest-install.py --help) and then rsync the relevant data between the dom0 (your host FC5 system) and the domU, and then possibly remove the duplicate data from the dom0. Chances are you only care about data in /home anyway... --Michael From alseat at comcast.net Sat Jul 8 14:07:46 2006 From: alseat at comcast.net (Algie Seat) Date: Sat, 8 Jul 2006 09:07:46 -0500 Subject: [Fedora-xen] Xen - FC6 VT install of Windows XP hangsl Message-ID: <200607081443.k68Eh7AT008915@mx3.redhat.com> I have a Dell 380 which is VT capable. I have installed FC6 as a VT (unmodified) Guest under FC6. I'm now trying to install Windows XP PRO as a VT guest. I'm doing the install from CD. It initially looks like it is going to work, but after The drivers are loaded, I get the standard "Setup is starting Windows" message, but nothing else after that. A "xm list" command shows the guest is gaining time rapidly so it must be in a loop. I saw some info about hitting F5 and choosing "standard PC" as the machine type. I did that but still have the same symptoms. I am completely up to date with all my packages on FC6. As I also mentioned above, a FC6 VT guest has been installed no problem. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sunzen at gmail.com Sun Jul 9 02:12:36 2006 From: sunzen at gmail.com (sunzen w.) Date: Sun, 9 Jul 2006 10:12:36 +0800 Subject: [Fedora-xen] X server problem when booting domain0 with kernel-xen0-2.6.17-1.2145_FC5 Message-ID: Hi, I'am a new Xen user. When i tried booting domain0 with kernel-xen0-2.6.17-1.2145_FC5, serveral kinds of exceptions happened. 1. X can't be started. 2. X can be started, but i). rather slow when starting X ii)Can't input when X logining iii)after X logining, X ''always' restarts The X log is as the following: --------------------------------------------------------------- X Window System Version 7.0.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 7.0 Build Operating System:Linux 2.6.9-34.ELsmp i686Red Hat, Inc. Current Operating System: Linux localhost.localdomain 2.6.17-1.2145_FC5xen0#1 SMP Sat Jul 1 13:38:11 EDT 2006 i686 Build Date: 30 June 2006 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (++) Log file: "/dev/null", Time: Sat Jul 8 15:03:54 2006 (++) Using config file: "/tmp/tmpZy0nMyxorg.config" *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Backtrace: 0: /usr/bin/Xorg(xf86SigHandler+0x87) [0x80b8727] 1: [0x993420] 2: /usr/lib/xorg/modules/libfb.so(fbOddStipple+0x152) [0x217002] 3: /usr/lib/xorg/modules/libfb.so(fbPolyFillRect+0x1be) [0x20cd9e] 4: /usr/bin/Xorg [0x8151f21] 5: /usr/bin/Xorg(CreateDefaultStipple+0x106) [0x8097fc6] 6: /usr/bin/Xorg(main+0x319) [0x8070069] 7: /lib/i686/nosegneg/libc.so.6(__libc_start_main+0xdc) [0x25e724] 8: /usr/bin/Xorg(FontFileCompleteXLFD+0xb1) [0x806f511] Fatal server error: Caught signal 8. Server aborting x53d724] 9: /usr/bin/Xorg(FontFileCompleteXLFD+0xb1) [0x806f511] Fatal server error: Caught signal 8. Server aborting ------------------------------------------------------------------- Signal 8 is floatpoint exception. How can it happen? Note: The domain0 can be successfully booted when i use runlevel 0. Any suggestion/advice is welcome. Thanks! -- sunzen -------------- next part -------------- An HTML attachment was scrubbed... URL: From cameron at freshtel.net Tue Jul 11 05:24:53 2006 From: cameron at freshtel.net (Cameron Pitt-Downton) Date: Tue, 11 Jul 2006 15:24:53 +1000 Subject: [Fedora-xen] Xen migration problems Message-ID: <971FA0386407DE4096E96382F4E3AD440D820F@Mail01.mel.au.office.freshtel.net> Hi, I've been trying to test out Xen migration, but keep running into a kernel Oops/crash. It might be my setup or I might be running into some other problem, but I've searched mailing lists/google and haven't found anything that has helped. I'm using 3 FC5 boxes all running the latest kernels, updates, etc: One box to export a mounted image file generated with xenguest-install.py via AoE using vblade (have also tried using NFS to export a directory containing the image file). The other 2 boxes are running Xen. The guest starts and runs on either Xen box without a problem, but when trying to do a migration or a live migration between the 2 Xen boxes, in either direction, I run into the kernel crash. The migration actually moves the guest from one box to the other, but it stops responding via the network, and when logging in using 'xm console' I see a kernel call trace. The guest kinda still works other than networking not working at all, so I tried doing a service network restart, but this causes the guest to totally lock up. If the guest is rebooted it works fine. Bellow is the kernel call trace and what is in the destination Xen server's xend.log. Thanks Cameron ------------------------- BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: d10c2c27 *pde = ma 00000000 pa fffff000 Oops: 0002 [#1] SMP Modules linked in: ipv6 autofs4 sunrpc xennet ip_conntrack_netbios_ns ipt_REJECT xt_state ip_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables dm_snapshot dm_zero dm_mirror dm_mod CPU: 0 EIP: 0061:[] Not tainted VLI EFLAGS: 00010046 (2.6.17-1.2145_FC5xenU #1) EIP is at backend_changed+0x15c/0x24d [xennet] eax: 00000000 ebx: cf608400 ecx: cf608498 edx: 00000000 esi: 00000001 edi: 00000000 ebp: 00000101 esp: c09cbf70 ds: 007b es: 007b ss: 0069 Process xenwatch (pid: 8, threadinfo=c09ca000 task=c06c6b30) Stack: <0>c09f2200 cf608000 00000000 cf608498 cf608488 c0898dc0 c09ca000 c0898dc0 c051d45e c051cdee c09f2200 00000002 00000002 00000000 c051d5aa c0898dc0 00000000 c06c6b30 c0429cd7 c09cbfbc c09cbfbc c0a43e7c c0429c16 00000000 Call Trace: xenwatch_thread+0x0/0x163 xenwatch_handle_callback+0x12/0x45 xenwatch_thread+0x14c/0x163 autoremove_wake_function+0x0/0x3a kthread+0xa0/0xcd kthread+0x0/0xcd kernel_thread_helper+0x5/0xb Code: 08 8b 47 60 01 43 18 ff 43 10 45 81 fd 01 01 00 00 0f 85 35 ff ff ff 8b 44 24 08 89 43 68 8b 53 74 be 01 00 00 00 31 ff 8b 43 68 <89> 02 8b 84 b3 f8 04 00 00 3d ff ff ff bf 76 58 8b 80 98 00 00 EIP: [] backend_changed+0x15c/0x24d [xennet] SS:ESP 0069:c09cbf70 <3>BUG: sleeping function called from invalid context at include/linux/rwsem.h:43 in_atomic():0, irqs_disabled():1 blocking_notifier_call_chain+0x11/0x48 profile_task_exit+0x10/0x14 do_exit+0x1b/0x78b die+0x1c0/0x27b die+0x255/0x27b do_page_fault+0x0/0x70f do_page_fault+0x60f/0x70f do_page_fault+0x0/0x70f error_code+0x2b/0x30 backend_changed+0x15c/0x24d [xennet] xenwatch_thread+0x0/0x163 xenwatch_handle_callback+0x12/0x45 xenwatch_thread+0x14c/0x163 autoremove_wake_function+0x0/0x3a kthread+0xa0/0xcd kthread+0x0/0xcd kernel_thread_helper+0x5/0xb BUG: xenwatch/8, lock held at task exit time! [c06083e0] {xenwatch_mutex} .. held by: xenwatch: 8 [c06c6b30, 110] ... acquired at: xenwatch_thread+0x95/0x163 ------------------------ [2006-07-10 12:42:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:260) XendDomainInfo.restore(['domain', ['domid', '5'], ['uuid', '08cd716d-1deb-00f4-77b2-66f14244bc16'], ['vcpus', '1'], ['vcpu_avail', '1'], ['cpu_weight', '1.0'], ['memory', '256'], ['maxmem', '256'], ['bootloader', '/usr/bin/pygrub'], ['features'], ['name', 'xen.guest.migration.test'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['image', ['linux', ['ramdisk', '/var/lib/xen/initrd.ihUbbw'], ['kernel', '/var/lib/xen/vmlinuz.4kwzZ2'], ['args', 'ro root=/dev/VolGroup00/LogVol00']]], ['device', ['vif', ['backend', '0'], ['script', 'vif-bridge'], ['mac', '00:16:3e:09:8a:dc']]], ['device', ['vbd', ['backend', '0'], ['dev', 'xvda'], ['uname', 'phy:etherd/e0.2'], ['mode', 'w']]], ['state', '-b----'], ['shutdown_reason', 'poweroff'], ['cpu_time', '0.142407299'], ['online_vcpus', '1'], ['up_time', '508.123579025'], ['start_time', '1152498812.32'], ['store_mfn', '613739'], ['console_mfn', '613738']]) [2006-07-10 12:42:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:291) parseConfig: config is ['domain', ['domid', '5'], ['uuid', '08cd716d-1deb-00f4-77b2-66f14244bc16'], ['vcpus', '1'], ['vcpu_avail', '1'], ['cpu_weight', '1.0'], ['memory', '256'], ['maxmem', '256'], ['bootloader', '/usr/bin/pygrub'], ['features'], ['name', 'xen.guest.migration.test'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['image', ['linux', ['ramdisk', '/var/lib/xen/initrd.ihUbbw'], ['kernel', '/var/lib/xen/vmlinuz.4kwzZ2'], ['args', 'ro root=/dev/VolGroup00/LogVol00']]], ['device', ['vif', ['backend', '0'], ['script', 'vif-bridge'], ['mac', '00:16:3e:09:8a:dc']]], ['device', ['vbd', ['backend', '0'], ['dev', 'xvda'], ['uname', 'phy:etherd/e0.2'], ['mode', 'w']]], ['state', '-b----'], ['shutdown_reason', 'poweroff'], ['cpu_time', '0.142407299'], ['online_vcpus', '1'], ['up_time', '508.123579025'], ['start_time', '1152498812.32'], ['store_mfn', '613739'], ['console_mfn', '613738']] [2006-07-10 12:42:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:390) parseConfig: result is {'uuid': '08cd716d-1deb-00f4-77b2-66f14244bc16', 'on_crash': 'restart', 'on_reboot': 'restart', 'image': ['linux', ['ramdisk', '/var/lib/xen/initrd.ihUbbw'], ['kernel', '/var/lib/xen/vmlinuz.4kwzZ2'], ['args', 'ro root=/dev/VolGroup00/LogVol00']], 'on_poweroff': 'destroy', 'bootloader_args': None, 'cpus': None, 'name': 'xen.guest.migration.test', 'backend': [], 'vcpus': 1, 'cpu_weight': 1.0, 'features': None, 'vcpu_avail': 1, 'memory': 256, 'device': [('vif', ['vif', ['backend', '0'], ['script', 'vif-bridge'], ['mac', '00:16:3e:09:8a:dc']]), ('vbd', ['vbd', ['backend', '0'], ['dev', 'xvda'], ['uname', 'phy:etherd/e0.2'], ['mode', 'w']])], 'bootloader': '/usr/bin/pygrub', 'cpu': None, 'maxmem': 256} [2006-07-10 12:42:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:1216) XendDomainInfo.construct: None [2006-07-10 12:42:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:701) Storing VM details: {'name': 'xen.guest.migration.test', 'on_reboot': 'restart', 'image': "(linux (ramdisk /var/lib/xen/initrd.ihUbbw) (kernel /var/lib/xen/vmlinuz.4kwzZ2) (args 'ro root=/dev/VolGroup00/LogVol00'))", 'on_poweroff': 'destroy', 'uuid': '08cd716d-1deb-00f4-77b2-66f14244bc16', 'on_crash': 'restart', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'maxmem': '256'} [2006-07-10 12:42:00 xend] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'mac': '00:16:3e:09:8a:dc', 'handle': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/6/0'} to /local/domain/6/device/vif/0. [2006-07-10 12:42:00 xend] DEBUG (DevController:112) DevController: writing {'mac': '00:16:3e:09:8a:dc', 'state': '1', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'frontend-id': '6', 'domain': 'xen.guest.migration.test', 'frontend': '/local/domain/6/device/vif/0'} to /local/domain/0/backend/vif/6/0. [2006-07-10 12:42:00 xend] DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' [2006-07-10 12:42:00 xend] DEBUG (DevController:110) DevController: writing {'virtual-device': '51712', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/6/51712'} to /local/domain/6/device/vbd/51712. [2006-07-10 12:42:00 xend] DEBUG (DevController:112) DevController: writing {'domain': 'xen.guest.migration.test', 'frontend': '/local/domain/6/device/vbd/51712', 'dev': 'xvda', 'state': '1', 'params': 'etherd/e0.2', 'mode': 'w', 'frontend-id': '6', 'type': 'phy'} to /local/domain/0/backend/vbd/6/51712. [2006-07-10 12:42:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing domain details: {'console/port': '2', 'name': 'xen.guest.migration.test', 'console/limit': '1048576', 'vm': '/vm/08cd716d-1deb-00f4-77b2-66f14244bc16', 'domid': '6', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/port': '1'} [2006-07-10 12:42:00 xend] DEBUG (balloon:128) Balloon: free 746; need 265; done. [2006-07-10 12:42:00 xend] DEBUG (XendCheckpoint:155) [xc_restore]: /usr/lib/xen/bin/xc_restore 10 15 6 67584 1 2 [2006-07-10 12:42:00 xend] ERROR (XendCheckpoint:234) xc_linux_restore start: max_pfn = 10800 [2006-07-10 12:42:00 xend] ERROR (XendCheckpoint:234) Increased domain reservation by 42000 KB [2006-07-10 12:42:00 xend] ERROR (XendCheckpoint:234) Reloading memory pages: 0% [2006-07-10 12:42:03 xend] ERROR (XendCheckpoint:234) Received all pages (0 races) [2006-07-10 12:42:03 xend] ERROR (XendCheckpoint:2100% [2006-07-10 12:42:03 xend] ERROR (XendCheckpoint:234) Memory reloaded. [2006-07-10 12:42:03 xend] ERROR (XendCheckpoint:234) Decreased reservation by 2101 pages [2006-07-10 12:42:03 xend] ERROR (XendCheckpoint:234) Domain ready to be built. [2006-07-10 12:42:03 xend] ERROR (XendCheckpoint:234) Restore exit with rc=0 [2006-07-10 12:42:03 xend] DEBUG (XendCheckpoint:207) store-mfn 59373 [2006-07-10 12:42:03 xend] DEBUG (XendCheckpoint:207) console-mfn 59372 [2006-07-10 12:42:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:664) XendDomainInfo.completeRestore [2006-07-10 12:42:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing domain details: {'console/ring-ref': '59372', 'console/port': '2', 'name': 'xen.guest.migration.test', 'console/limit': '1048576', 'vm': '/vm/08cd716d-1deb-00f4-77b2-66f14244bc16', 'domid': '6', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '59373', 'store/port': '1'} [2006-07-10 12:42:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:674) XendDomainInfo.completeRestore done [2006-07-10 12:42:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:919) XendDomainInfo.handleShutdownWatch From phil at pricom.com.au Wed Jul 12 03:02:24 2006 From: phil at pricom.com.au (Philip Rhoades) Date: Wed, 12 Jul 2006 13:02:24 +1000 Subject: [Fedora-xen] floppy.ko & lightweight FC5 guests Message-ID: <1152673344.3848.4.camel@prix.pricom.com.au> People, I want to install lightweight FC5 guests using RULE (http://www.rule-project.org) so I need floppy disk access but there is no floppy.ko in 2.6.17-1.2139_FC5xen0 . . how do I fix this? Thanks, Phil. -- Philip Rhoades Pricom Pty Limited (ACN 003 252 275 ABN 91 003 252 275) GPO Box 3411 Sydney NSW 2001 Australia Mobile: +61:(0)411-185-652 Fax: +61:(0)2-8221-9599 E-mail: phil at pricom.com.au From katzj at redhat.com Wed Jul 12 11:26:09 2006 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 12 Jul 2006 07:26:09 -0400 Subject: [Fedora-xen] floppy.ko & lightweight FC5 guests In-Reply-To: <1152673344.3848.4.camel@prix.pricom.com.au> References: <1152673344.3848.4.camel@prix.pricom.com.au> Message-ID: <1152703569.2860.49.camel@aglarond.local> On Wed, 2006-07-12 at 13:02 +1000, Philip Rhoades wrote: > I want to install lightweight FC5 guests using RULE > (http://www.rule-project.org) so I need floppy disk access but there is > no floppy.ko in 2.6.17-1.2139_FC5xen0 . . how do I fix this? That's because Xen guests don't have floppy drives. RULE will almost certainly need changes to understand some of the quirks of PV Xen guests in comparison to real physical systems Jeremy From garysiao at gmail.com Wed Jul 12 16:12:17 2006 From: garysiao at gmail.com (Gary Siao) Date: Wed, 12 Jul 2006 12:12:17 -0400 Subject: [Fedora-xen] no kernel specified on config file Message-ID: hi gurus i an createing the first guest domain using the xenguest-install.py on FC5.. the install completed ok but when i run xm create -c domain1, i get no kernel specified... i am lost here... how do i know which kernel i will put in the config file for the first domain... need help badly thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Wed Jul 12 21:46:12 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 12 Jul 2006 22:46:12 +0100 Subject: [Fedora-xen] Updated snapshot of virt-manager GUI application Message-ID: <20060712214612.GA6681@redhat.com> I have just pushed out RPM / tar.gz of a new development (alpha) snapshot of the virt-manager GUI application. The changes in this snapshot are: * Fixed DBus service activation & general brokeness * Added a display of virtual CPU count in summary view * Fixed alignment of status label in details page * Make hardware config panel resizeable * Switch detailed graph rendering to use sparkline code instead of matplotlib, removing a huge RPM dependancy chain * Switch to use filled sparkline graphs instead of outline Although I didn't increment the RPM dependancy, I strongly recommend using libvirt 0.1.3 if your host is running > 5 guest domains. This reduces the number of HTTP GETs made by an order of magnitude, improving the response time / scalability of the virt-manager refresh. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From dgreen at CLEMSON.EDU Fri Jul 14 02:09:44 2006 From: dgreen at CLEMSON.EDU (dgreen at CLEMSON.EDU) Date: Thu, 13 Jul 2006 22:09:44 -0400 (EDT) Subject: [Fedora-xen] FC5 domU network connectivity Message-ID: <50935.65.12.113.44.1152842984.squirrel@wm.clemson.edu> Trying to set up my domUs with network connectivity. I am running FC5 on dom0 and FC5 on my two domUs. My dom0 has a static eth0 and I run the 'network bridge' and 'vif bridge' in the script at startup. My ifconfig shows (edited for length...): eth0 Link encap:Ethernet HWaddr 00:E0:81:5D:B1:70 inet addr:130.127.XX.XXX Bcast:130.127.XX.XXX Mask:255.255.254.0 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link Questions/Comments: 1) How would I set up my bridge to give out automatic DHCP info to the domUs? Do I have to run DHCP services on dom0? 2) I would like to keep my 130.127 address on eth0 so I can still connect to the network, can this still be done and give private 192.168.12.X addresses to my domUs? Thanks for any help you can give. Vince From ManognaR_C at infosys.com Fri Jul 14 05:33:52 2006 From: ManognaR_C at infosys.com (Manogna Ramakrishna Chebiyyam) Date: Fri, 14 Jul 2006 11:03:52 +0530 Subject: [Fedora-xen] FW: error..please help me Message-ID: I am working on FC5 [root at blrkec38274d ~]# xm list Error: Error connecting to xend: No such file or directory. Is xend running? THE LOG FILE xend.log is below.... [2006-06-28 18:22:59 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-06-28 18:22:59 xend] INFO (SrvDaemon:289) Xend changeset: unavailable . [2006-06-28 18:23:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:201) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 32149393054L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 464232, 'maxmem_kb': -4, 'max_vcpu_id': 1, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 2, 'blocked': 0}) [2006-06-28 18:23:00 xend.XendDomainInfo] INFO (XendDomainInfo:213) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [2006-06-28 18:23:00 xend.XendDomainInfo] WARNING (XendDomainInfo:235) No vm path in store for existing domain 0 [2006-06-28 18:23:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:673) Storing VM details: {'ssidref': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'on_poweroff': 'destroy', 'name': 'Domain-0', 'vcpus': '2', 'vcpu_avail': '3', 'memory': '454', 'on_crash': 'restart', 'maxmem': '454'} [2006-06-28 18:23:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:698) Storing domain details: {'cpu/0/availability': 'online', 'memory/target': '464896', 'cpu/1/availability': 'online', 'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'} [2006-06-28 18:23:00 xend] DEBUG (XendDomain:152) number of vcpus to use is 0 [2006-06-28 18:23:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:882) XendDomainInfo.handleShutdownWatch [2006-07-06 12:25:35 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-06 12:25:35 xend] ERROR (SrvDaemon:299) Exception starting xend ((22, 'Invalid argument')) Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 288, in run xinfo = xc.xeninfo() error: (22, 'Invalid argument') [2006-07-06 12:25:35 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-06 12:28:35 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-06 12:28:35 xend] ERROR (SrvDaemon:299) Exception starting xend ((22, 'Invalid argument')) Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 288, in run xinfo = xc.xeninfo() error: (22, 'Invalid argument') [2006-07-06 12:28:35 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-13 17:27:47 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-13 17:27:47 xend] ERROR (SrvDaemon:299) Exception starting xend ((22, 'Invalid argument')) Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 288, in run xinfo = xc.xeninfo() error: (22, 'Invalid argument') [2006-07-13 17:27:47 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-13 17:29:45 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-13 17:29:45 xend] ERROR (SrvDaemon:299) Exception starting xend ((22, 'Invalid argument')) Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 288, in run xinfo = xc.xeninfo() error: (22, 'Invalid argument') [2006-07-13 17:29:45 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-13 17:30:44 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-13 17:30:44 xend] ERROR (SrvDaemon:299) Exception starting xend ((22, 'Invalid argument')) Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 288, in run xinfo = xc.xeninfo() error: (22, 'Invalid argument') [2006-07-13 17:30:44 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-13 17:33:03 xend] INFO (SrvDaemon:285) Xend Daemon started @ [2006-07-13 17:33:03 xend] ERROR (SrvDaemon:299) Exception starting xend ((22, 'Invalid argument')) Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 288, in run xinfo = xc.xeninfo() error: (22, 'Invalid argument') [2006-07-13 17:33:03 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-13 17:34:02 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-13 17:34:02 xend] ERROR (SrvDaemon:299) Exception starting xend ((22, 'Invalid argument')) Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 288, in run xinfo = xc.xeninfo() error: (22, 'Invalid argument') [2006-07-13 17:34:02 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-13 17:36:08 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-13 17:36:08 xend] ERROR (SrvDaemon:299) Exception starting xend ((22, 'Invalid argument')) Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 288, in run xinfo = xc.xeninfo() error: (22, 'Invalid argument') [2006-07-13 17:36:08 xend] INFO (SrvDaemon:185) Xend exited with status 1. Manogna Employee ID-53967 High Performance Computing SETLabs Infosys Technologies Limited Bangalore **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS*** From kzak at redhat.com Fri Jul 14 13:43:35 2006 From: kzak at redhat.com (Karel Zak) Date: Fri, 14 Jul 2006 15:43:35 +0200 Subject: [Fedora-xen] announce: gnome-applet-vm-0.1.0rc1 Message-ID: <20060714134335.GB2857@petra.dvoda.cz> I have just pushed out a new version of the VM Applet. The changes/features are: - D-BUS support and integration with virt-manager - console helper support for privileged operations - fixed a lot of bugs - new icons - better GUI - the applet internally supports multiple libvirt connection (in future it will be useful for monitoring remote virtual machines) Web page (with screenshot of course:-): http://people.redhat.com/kzak/gnome-applet-vm/ Please, help me found bugs and improve this application. Karel -- Karel Zak From c.reiter at gmx.net Fri Jul 14 17:01:52 2006 From: c.reiter at gmx.net (Christian Reiter) Date: Fri, 14 Jul 2006 19:01:52 +0200 Subject: [Fedora-xen] How much VCPUs should be assigned to my VMs Message-ID: <44B7CE00.9080904@gmx.net> Hello! I am quite unsure about how much VCPUs should be asssigned to my domU-VMs. I have here an 4-way SMP Box running 3 to 4 Guests. Mit freundlichen Gr??en, /// Kind Regards, Christian Reiter -- Christian Reiter ||| c.reiter at gmx.net -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2840 bytes Desc: S/MIME Cryptographic Signature URL: From techjedi at gmail.com Fri Jul 14 21:31:11 2006 From: techjedi at gmail.com (Chris McKeever) Date: Fri, 14 Jul 2006 16:31:11 -0500 Subject: [Fedora-xen] howto? - run a different OS on FC5-xen Message-ID: does anyone have a howto or summary on creating a different Xen guest on a FC5 Xen build? i have tried using the images from jailtime.org, but can't seem to get the network running. Ideally I would like to get a guest domain of FC4 thanks -- ---------------------------------- please respond to the list .. if you need to contact me direct cgmckeever is the account prupref.com is the domain Simply Chicago Real Estate From shobha.ranganathan at intel.com Fri Jul 14 22:27:05 2006 From: shobha.ranganathan at intel.com (Ranganathan, Shobha) Date: Fri, 14 Jul 2006 15:27:05 -0700 Subject: [Fedora-xen] compiling oprofile in FC5 for setting up xenoprof Message-ID: I am trying to compile oprofile 0.9.1 after applying patches xenoprof-2.0-oprofile-0.9.1.patch in FC5. After I run ./configure, I did a make I get the error . Has some one seen this before ? make[2]: Entering directory `/root/oprofile-0.9.1/libpp' if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I ../libop -I ../libutil -I ../libdb -I ../libopt++ -I ../libutil++ -I ../libop++ -I ../libregex -W -Wall -fno-common -ftemplate-depth-50 -g -O2 -MT arrange_profiles.o -MD -MP -MF ".deps/arrange_profiles.Tpo" -c -o arrange_profiles.o arrange_profiles.cpp; \ then mv -f ".deps/arrange_profiles.Tpo" ".deps/arrange_profiles.Po"; else rm -f ".deps/arrange_profiles.Tpo"; exit 1; fi arrange_profiles.cpp:93: error: definition of 'bool profile_classes::matches(const profile_classes&)' is not in namespace enclosing 'profile_classes' make[2]: *** [arrange_profiles.o] Error 1 make[2]: Leaving directory `/root/oprofile-0.9.1/libpp' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/oprofile-0.9.1' make: *** [all] Error 2 I have already built xen0 and xenU kernels. I am trying to get xenoprof to run... System details --- P6 processor and following OS details root at setst-p6y-02:~/oprofile-0.9.1# uname -a Linux setst-p6y-02 2.6.15-1.2054_FC5smp #1 SMP Tue Mar 14 16:05:46 EST 2006 i686 i686 i386 GNU/Linux root at setst-p6y-02:~/oprofile-0.9.1# uname -r 2.6.15-1.2054_FC5smp Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein -------------- next part -------------- An HTML attachment was scrubbed... URL: From riel at redhat.com Sun Jul 16 03:14:20 2006 From: riel at redhat.com (Rik van Riel) Date: Sat, 15 Jul 2006 23:14:20 -0400 Subject: [Fedora-xen] How much VCPUs should be assigned to my VMs In-Reply-To: <44B7CE00.9080904@gmx.net> References: <44B7CE00.9080904@gmx.net> Message-ID: <44B9AF0C.6030107@redhat.com> Christian Reiter wrote: > I am quite unsure about how much VCPUs should be asssigned to my domU-VMs. > I have here an 4-way SMP Box running 3 to 4 Guests. How much CPU time does each guest use? A guest that occasionally needs all 4 CPUs might benefit from having 4 VCPUs, but a guest that uses very little CPU might hurt from doing cross-cpu synchronization internally. From henning_sprang at gmx.de Sun Jul 16 12:57:56 2006 From: henning_sprang at gmx.de (Henning Sprang) Date: Sun, 16 Jul 2006 14:57:56 +0200 Subject: [Fedora-xen] FW: error..please help me In-Reply-To: References: Message-ID: <5bb00b3f0607160557v2a71f63p43e83475114bae3c@mail.gmail.com> On 7/14/06, Manogna Ramakrishna Chebiyyam wrote: > I am working on FC5 > [root at blrkec38274d ~]# xm list > Error: Error connecting to xend: No such file or directory. Is xend > running? > > THE LOG FILE xend.log is below.... > [...] It would be more useful if you'd give a better description of what version of xen you are using , how you installed it, and if you ever got xend working or never at all. You seem to have some problem with starting xend, not with xm list, so your installation is not intact. Henning From armbru at pond.sub.org Mon Jul 17 09:43:22 2006 From: armbru at pond.sub.org (Markus Armbruster) Date: Mon, 17 Jul 2006 11:43:22 +0200 Subject: [Fedora-xen] compiling oprofile in FC5 for setting up xenoprof In-Reply-To: (Shobha Ranganathan's message of "Fri, 14 Jul 2006 15:27:05 -0700") References: Message-ID: <878xmsa7np.fsf@pike.pond.sub.org> "Ranganathan, Shobha" writes: > > > I am trying to compile oprofile 0.9.1 after applying patches > xenoprof-2.0-oprofile-0.9.1.patch in FC5. > > After I run ./configure, I did a make > > I get the error . Has some one seen this before ? I see such errors when I try to compile *unpatched* upstream oprofile-0.9.1. The Fedora stuff compiles fine for me, with and without Xen patch. Have you tried that? From mito-lists at mitopia.net Mon Jul 17 13:51:58 2006 From: mito-lists at mitopia.net (Mito Tranin - Lists) Date: Mon, 17 Jul 2006 09:51:58 -0400 Subject: [Fedora-xen] howto? - run a different OS on FC5-xen In-Reply-To: References: Message-ID: <44BB95FE.2000602@mitopia.net> Chris McKeever wrote: > does anyone have a howto or summary on creating a different Xen guest > on a FC5 Xen build? > > i have tried using the images from jailtime.org, but can't seem to get > the network running. > > Ideally I would like to get a guest domain of FC4 > > thanks Actually, that's exactly what I did in my howto, a FC4 guest on a FC5 host. http://mitopia.net/index.php/Xen_3.0.2_Setup That, and NAT networking, but you don't have to do those steps if you don't need them... Mito -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From techjedi at gmail.com Tue Jul 18 15:35:21 2006 From: techjedi at gmail.com (Chris McKeever) Date: Tue, 18 Jul 2006 10:35:21 -0500 Subject: [Fedora-xen] command line kernel parameters Message-ID: I am trying to set some networking options via the kernel command line -- I have recompiled the kernel to support IP_PNP (IP: kernel level autoconfiguration) but I dont even think I have gotten to the need of that part, xm create doesn't even seem to pass the arguements to the kernel: xen 3.0.2 source compile FC5 conf: kernel="/boot/vmlinuz-2.6.16-xen" memory=128 name="fedora.fc4" vif = [ 'ip=192.168.1.61, mac=00:16:3E:3E:30:C8' ] disk=['file:/xen/fc4/image,sda1,w', 'file:/xen/fc4/swap,sda2,w'] #dhcp = "dhcp" <-- tried as commented out and "off" netmask="255.255.255.0" gateway="192.168.1.1" hostname="ds-1" root="/dev/sda1 ro" # xm create -n conf Using config file "conf". (vm (name fedora.fc4) (memory 128) (vcpus 1) (image (linux (kernel /boot/vmlinuz-2.6.16-xen) (root '/dev/sda1 ro'))) (device (vbd (uname file:/xen/fc4/image) (dev sda1) (mode w))) (device (vbd (uname file:/xen/fc4/swap) (dev sda2) (mode w))) (device (vif (ip 192.168.1.61) (mac 00:16:3E:3E:30:C8))) ) from the console: # dmesg | grep command Kernel command line: root=/dev/sda1 ro so - it seems the command line isnt being passed what aI *think* it should be passed - any ideas?? -- ---------------------------------- please respond to the list .. if you need to contact me direct cgmckeever is the account prupref.com is the domain Simply Chicago Real Estate From c.reiter at gmx.net Tue Jul 18 16:17:44 2006 From: c.reiter at gmx.net (Christian Reiter) Date: Tue, 18 Jul 2006 18:17:44 +0200 Subject: [Fedora-xen] How much VCPUs should be assigned to my VMs In-Reply-To: <44B9AF0C.6030107@redhat.com> References: <44B7CE00.9080904@gmx.net> <44B9AF0C.6030107@redhat.com> Message-ID: <44BD09A8.8000405@gmx.net> Hello Rik! Rik van Riel schrieb: > How much CPU time does each guest use? I am not abolutely sure at this time.... > A guest that occasionally needs all 4 CPUs might benefit > from having 4 VCPUs, but a guest that uses very little > CPU might hurt from doing cross-cpu synchronization > internally. > So i assume assigning VCPUs to a guest is just the same as configuring a real SMP system? Mit freundlichen Gr??en, /// Kind Regards, Christian Reiter -- Christian Reiter ||| c.reiter at gmx.net -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2840 bytes Desc: S/MIME Cryptographic Signature URL: From techjedi at gmail.com Tue Jul 18 17:02:56 2006 From: techjedi at gmail.com (Chris McKeever) Date: Tue, 18 Jul 2006 12:02:56 -0500 Subject: [Fedora-xen] howto? - run a different OS on FC5-xen In-Reply-To: <44BB95FE.2000602@mitopia.net> References: <44BB95FE.2000602@mitopia.net> Message-ID: > Actually, that's exactly what I did in my howto, a FC4 guest on a FC5 host. > > http://mitopia.net/index.php/Xen_3.0.2_Setup Mito - I went through your HOWTO - Excellently put together, really got me on track for some things - ran into some items, not sure if I just followed it wrong, or if there are inconsistencies... It seems that you compiled xen to create a xenU and xen0 kernel, but for both your instances, you use the full compiled xen kernel (which can be used by either prov or unpriv) >From the README: "It will build the xen binary (xen.gz), and a linux kernel and modules that can be used in both dom0 and an unprivileged guest kernel (vmlinuz-2.6.x-xen)," CONF: # Your domain's name name = "it-works" # Kernel to use kernel = "/boot/vmlinuz-2.6.16-xen" GRUB: title Xen 3.0.2 / XenLinux 2.6.16 root (hd0,0) kernel /xen-3.0.gz dom0_mem=65536 module /vmlinuz-2.6.16-xen ro root=/dev/md2 If you are just using the full kernel - you can theoretically take out both compile steps for building your xen0 and xenU kernels (Compile dom0 Kernel | Compile domU Kernel) - This is actually the path I took and why I noticed this - it would up being easier to build the one universal kernel -- plus I ran into some compile issue when just doing the xen0 compile. I am not sure the performance benefit of using a stripped down xenU kernel for the guests, but for my current needs - it got me up and running using the full compile - from the README: "vmlinuz-2.6.x-xen0 and vmlinuz-2.6.x-xenU. These are smaller builds with just selected modules, intended primarily for developers that don't like to wait for a -xen kernel to build. " With that, I also learned that FC5 by default uses lvm (?) for the root partition, so I needed to create the initrd - outside of that, I dont think I would have needed that step. For your guest, you list some xen configs (which are documented, but I couldn't get them to work): vif=[ 'ip=10.0.0.2' ] dhcp="off" netmask="255.255.0.0" gateway="10.0.0.254" hostname = "mail" One thing to note, is that for this type of config your guest kernel needs to be compiled with: IP: kernel level autoconfiguration http://tlug.up.ac.za/old/guides/lkcg/net_ipv4.html I however could not get xen to pass these as kernel command line arguments, and actually needed to pass them using this format (extras variable): ip=:::::: That let me boot and set the network options from the config file. Finally - building your image with QEMU - I didnt completely walk through this, as I quickly learned your host machine needs X (would be great if anaconda could have been kicked off) -- but the good news is that, after a source xen install, setting the initrd so it sees that logical drive, I was very easily able to get the FC4 image to boot from jailtime.org So - for the most part I have a fully functional xen-fc4 within fc5 and outside of your inconsistency with the kernel definitions in GRUB and the XEN conf -- great job, and thanks!! > That, and NAT networking, but you don't have to do those steps if you > don't need them... > > Mito > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From yongkang.you at intel.com Tue Jul 18 22:54:42 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Wed, 19 Jul 2006 06:54:42 +0800 Subject: [Fedora-xen] command line kernel parameters Message-ID: <094BCE01AFBE9646AF220B0B3F367AAB0950AE@pdsmsx413.ccr.corp.intel.com> I think you want to add some kernel booting parameter to a XenU domain. You can try to add "extra=booting_parameter" in XenU configuration file. Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Chris McKeever >Sent: 2006?7?18? 23:35 >To: fedora-xen at redhat.com >Subject: [Fedora-xen] command line kernel parameters > >I am trying to set some networking options via the kernel command line -- >I have recompiled the kernel to support IP_PNP (IP: kernel level >autoconfiguration) >but I dont even think I have gotten to the need of that part, xm >create doesn't even seem to pass the arguements to the kernel: > >xen 3.0.2 source compile >FC5 > >conf: >kernel="/boot/vmlinuz-2.6.16-xen" >memory=128 >name="fedora.fc4" >vif = [ 'ip=192.168.1.61, mac=00:16:3E:3E:30:C8' ] >disk=['file:/xen/fc4/image,sda1,w', 'file:/xen/fc4/swap,sda2,w'] >#dhcp = "dhcp" <-- tried as commented out and "off" >netmask="255.255.255.0" >gateway="192.168.1.1" >hostname="ds-1" >root="/dev/sda1 ro" > ># xm create -n conf >Using config file "conf". >(vm > (name fedora.fc4) > (memory 128) > (vcpus 1) > (image (linux (kernel /boot/vmlinuz-2.6.16-xen) (root '/dev/sda1 ro'))) > (device (vbd (uname file:/xen/fc4/image) (dev sda1) (mode w))) > (device (vbd (uname file:/xen/fc4/swap) (dev sda2) (mode w))) > (device (vif (ip 192.168.1.61) (mac 00:16:3E:3E:30:C8))) >) > >from the console: ># dmesg | grep command >Kernel command line: root=/dev/sda1 ro > >so - it seems the command line isnt being passed what aI *think* it >should be passed - any ideas?? > > >-- >---------------------------------- >please respond to the list .. if you need to contact me direct >cgmckeever is the account >prupref.com is the domain > >Simply Chicago Real Estate > >-- >Fedora-xen mailing list >Fedora-xen at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen From techjedi at gmail.com Tue Jul 18 23:50:40 2006 From: techjedi at gmail.com (Chris McKeever) Date: Tue, 18 Jul 2006 18:50:40 -0500 Subject: [Fedora-xen] command line kernel parameters In-Reply-To: <094BCE01AFBE9646AF220B0B3F367AAB0950AE@pdsmsx413.ccr.corp.intel.com> References: <094BCE01AFBE9646AF220B0B3F367AAB0950AE@pdsmsx413.ccr.corp.intel.com> Message-ID: On 7/18/06, You, Yongkang wrote: > I think you want to add some kernel booting parameter to a XenU domain. > You can try to add "extra=booting_parameter" in XenU configuration file. that works, but it seems like the config files themselves should handle building out the cmmand line string: http://www.nabble.com/IP-configuration-for-domU-ignored-t1779301.html which in my case - it doesnt > > Best Regards, > Yongkang (Kangkang) ?? > > >-----Original Message----- > >From: fedora-xen-bounces at redhat.com > >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Chris McKeever > >Sent: 2006?7?18? 23:35 > >To: fedora-xen at redhat.com > >Subject: [Fedora-xen] command line kernel parameters > > > >I am trying to set some networking options via the kernel command line -- > >I have recompiled the kernel to support IP_PNP (IP: kernel level > >autoconfiguration) > >but I dont even think I have gotten to the need of that part, xm > >create doesn't even seem to pass the arguements to the kernel: > > > >xen 3.0.2 source compile > >FC5 > > > >conf: > >kernel="/boot/vmlinuz-2.6.16-xen" > >memory=128 > >name="fedora.fc4" > >vif = [ 'ip=192.168.1.61, mac=00:16:3E:3E:30:C8' ] > >disk=['file:/xen/fc4/image,sda1,w', 'file:/xen/fc4/swap,sda2,w'] > >#dhcp = "dhcp" <-- tried as commented out and "off" > >netmask="255.255.255.0" > >gateway="192.168.1.1" > >hostname="ds-1" > >root="/dev/sda1 ro" > > > ># xm create -n conf > >Using config file "conf". > >(vm > > (name fedora.fc4) > > (memory 128) > > (vcpus 1) > > (image (linux (kernel /boot/vmlinuz-2.6.16-xen) (root '/dev/sda1 ro'))) > > (device (vbd (uname file:/xen/fc4/image) (dev sda1) (mode w))) > > (device (vbd (uname file:/xen/fc4/swap) (dev sda2) (mode w))) > > (device (vif (ip 192.168.1.61) (mac 00:16:3E:3E:30:C8))) > >) > > > >from the console: > ># dmesg | grep command > >Kernel command line: root=/dev/sda1 ro > > > >so - it seems the command line isnt being passed what aI *think* it > >should be passed - any ideas?? > > > > > >-- > >---------------------------------- > >please respond to the list .. if you need to contact me direct > >cgmckeever is the account > >prupref.com is the domain > > > >Simply Chicago Real Estate > > > >-- > >Fedora-xen mailing list > >Fedora-xen at redhat.com > >https://www.redhat.com/mailman/listinfo/fedora-xen > From shobha_ranganathan at yahoo.com Wed Jul 19 23:59:57 2006 From: shobha_ranganathan at yahoo.com (shobha ranganathan) Date: Wed, 19 Jul 2006 16:59:57 -0700 (PDT) Subject: [Fedora-xen] FC5-- building xen-unstable to get xenoprof built...-- get compilation errors Message-ID: <20060719235958.24190.qmail@web55914.mail.re3.yahoo.com> I am trying to get xenoprof built in Xen environment. I downloaded the xen-unstable-src.tar in FC5 x86 system where I have both xen0 and xenU kernel built and up in running. I did the following cd xen-unstable Now I need to invoke "make menuconfig" to setup options for Profiling in kernel and then do "make world" and "make install". I do not find linux-2.6.x.x-xen directory to run "make menuconfig".. Also when I do the steps cd xen-unstable make KERNELS=linux-2.6-xen world make[3]: Entering directory `/root/xen-unstable/xen/arch/x86' gcc -Wdeclaration-after-statement -nostdinc -fno-builtin -fno-common -fno-strict-aliasing -iwithprefix include -Wall -Werror -Wno-pointer-arith -pipe -I/root/xen-unstable/xen/include -I/root/xen-unstable/xen/include/asm-x86/mach-generic -I/root/xen-unstable/xen/include/asm-x86/mach-default -O3 -fomit-frame-pointer -msoft-float -m32 -march=i686 -DNDEBUG -S -o asm-offsets.s x86_32/asm-offsets.c cc1: warnings being treated as errors In file included from /root/xen-unstable/xen/include/asm/mpspec.h:5, from /root/xen-unstable/xen/include/asm/smp.h:18, from /root/xen-unstable/xen/include/xen/smp.h:13, from /root/xen-unstable/xen/include/xen/sched.h:8, from x86_32/asm-offsets.c:9: /root/xen-unstable/xen/include/asm/mpspec_def.h:78: warning: ?packed? attribute ignored for field of type ?unsigned char[5u]? make[3]: *** [asm-offsets.s] Error 1 make[3]: Leaving directory `/root/xen-unstable/xen/arch/x86' make[2]: *** [/root/xen-unstable/xen/xen] Error 2 make[2]: Leaving directory `/root/xen-unstable/xen' make[1]: *** [install-xen] Error 2 make[1]: Leaving directory `/root/xen-unstable' make: *** [world] Erro What am I doing wrong here ? thanks Shobha --------------------------------- Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2?/min or less. -------------- next part -------------- An HTML attachment was scrubbed... URL: From takebe_akio at jp.fujitsu.com Thu Jul 20 01:37:39 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Thu, 20 Jul 2006 10:37:39 +0900 Subject: [Fedora-xen] [RFC] Using linux-2.6.tip-xen on IA64 Message-ID: <8C6AB9D160FFEtakebe_akio@jp.fujitsu.com> Hi, all We can success booting domU with linux-2.6.tip-xen. (This is FedoraCore work.) The build step is the below. I think the step is almost same as Aron's step. (http://free.linux.hp.com/~agriffis/fedora-kernel-ia64/.) We used linux-2.6.tip-xen.hg(cset #30476) and xen-unstable.hg(cset #10474). 1. hg clone http://xenbits.xensource.com/ext/linux-2.6.tip-xen.hg 2. copy xen/include/asm-ia64/asm-xsi-offsets.h from xen-ia64-unstable.hg to linux-2.6.tip-xen.hg/include/asm-ia64/xen/ 3. copy .config from xen-ia64-unstable.hg/buildconfigs/linux-defconfig_xen_ia64 to linux-2.6.tip-xen/.config 4. make oldconfig (All answers are default) 5. copy linux-2.6.tip-xen.hg/arch/ia64/kernel/gate.S from linux-2.6.16.13.tar.bz2 6. cd linux-2.6.tip-xen.hg make & copy vmlinuz & mkinitrd 7. build xen-unstable.hg (cset #10474) hg clone xen-unstable.hg xen-unstable.hg-match-linux-2.6.tip cd xen-unstable.hg-match-linux.2.6.tip hg up -C 10474 make 8. copy xen.gz to under /boot/efi/ 9. make install-tools But I found some problem. Please comments. A. We cannot compile the latest linux-2.6.tip-xen(#32966). Is fixing linux-2.6.tip-xen fc6's or xen-ia64's contribution? Or is anyone already working for that? B. linux-2.6.tip-xen don't have arch/ia64/kernel/gate.S. Why? Best Regards, Akio Takebe From armbru at redhat.com Thu Jul 20 06:57:20 2006 From: armbru at redhat.com (Markus Armbruster) Date: Thu, 20 Jul 2006 08:57:20 +0200 Subject: [Fedora-xen] FC5-- building xen-unstable to get xenoprof built...-- get compilation errors In-Reply-To: <20060719235958.24190.qmail@web55914.mail.re3.yahoo.com> (shobha ranganathan's message of "Wed, 19 Jul 2006 16:59:57 -0700 (PDT)") References: <20060719235958.24190.qmail@web55914.mail.re3.yahoo.com> Message-ID: <87ac74vk4v.fsf@pike.pond.sub.org> shobha ranganathan writes: > I am trying to get xenoprof built in Xen environment. > I downloaded the xen-unstable-src.tar in FC5 x86 system where I have both xen0 > and xenU kernel built and up in running. Is this a tarball from XenSource? If yes, their mailing lists may well be a better place for questions. What about building from Fedora source rpms instead? [...] From berrange at redhat.com Thu Jul 20 20:32:01 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 20 Jul 2006 21:32:01 +0100 Subject: [Fedora-xen] Virtual Machine Manager 0.1.5 release Message-ID: <20060720203201.GF1390@redhat.com> I've just pushed out another snapshot of the Virtual Machine Manager GUI application for managing Xen machines via libvirt. A summary of the changes in this 0.1.5 release[1]: * Integration with GNOME keyring for the VNC console to avoid need to remember passwords when accessing the guest domain's console * Use cairo to render a '50% alpha gray wash' over the screenshot to give appearance of a 'dimmed' display when paused. Also render the word 'paused' in big letters. * Initial cut of code for saving & restoring domain snapshots to disk * Added icons for buttons which were missing graphics * Miscellaneous RPM spec file fixes to comply with rpmlint * Update status icons to match those in the gnome-applet-vm * Added domain ID and # VCPUs to summary view * Misc bug fixes The next priority target for development is some UI for creating new VM instances (a GUI equivalent of xenguest-install.py script shipping with current Fedora Xen packages) and implenenting the UI for editing domain configuration / hardware. In addition there is now a more permanent home for the application's web pages: http://virt-manager.et.redhat.com/index.html And the Mercurial repository is now published for anonymous read-only access at: http://hg.et.redhat.com/virt/applications/virt-manager--devel Patches are welcome either as traditional unified diffs, or as mercurial changeset bundles - see the following page for details on exporting bundles using hg: http://virt-manager.et.redhat.com/scmrepo.html Regards, Dan. [1] There was a 0.1.4 but it had a fatal flaw in it breaking the console -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From adam at kupsta.com Fri Jul 21 22:30:37 2006 From: adam at kupsta.com (Adam Kupsta) Date: Fri, 21 Jul 2006 18:30:37 -0400 Subject: [Fedora-xen] FC 5 Xen 3.0.2 Dom0 Network Problem Message-ID: <6B812F45366DC045BA7361DB7B0CA74A049A8C@oakgex02.kupsta.net> Hi Everyone, I'm having some issues with FC5/XEN and network functionality in dom0. Here's what I did: - Installed FC5 off the DVD iso available from the Redhat site; (did a vanilla server install - no X, added dev tools) - Setup my eth0 interface. I can access network / internet no probs. - I did a 'yum update' to get all latest patches. Installed, no probs. (updates current as of 7/21/06) - I did a 'yum install kernel-xen0' as per the FC XEN HowTo. Installed no probs. Rebooted into the xen0 kernel and I discovered that I can't ping or access any network outside the system itself. I can ping the IP I assigned to eth0 but all other pings are being returned as" ". This tells me that there's some sort of routing / firewall issue, however I have SELINUX and the firewall both disabled in Linux. I Googled for a solution and ensured that both the IPROUTE and BRIDGING packages are installed. Here's something I did find. If I stop the network-bridge script (/etc/xen/scripts/network-bridge stop) networking returns. I know I'll need the bridge interface up for what I need this box to do. Please help. Thanks for your assistance, Adam. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aron at hp.com Sat Jul 22 13:31:24 2006 From: aron at hp.com (Aron Griffis) Date: Sat, 22 Jul 2006 09:31:24 -0400 Subject: [Fedora-xen] Four ways RH could help with xen-ia64 Message-ID: <20060722133124.GB12649@mustard> Hi guys, There are four ways you could be a big help to the xen-ia64 effort. I have mentioned these in the past but never pulled them together into a single request. 1. Publish Juan's tree which is the result of his merge of linux-2.6.tip-xen, linux-2.6 and linux-2.6-xen. How about http://people.redhat.com/quintela/linux-2.6.tip-xen-fedora.hg? As things stand right now, it's very difficult for ia64 devs to contribute to Juan's patch, for 2 reasons: (1) we never see it until after a new kernel rpm is published, (2) all we get is the final result, lacking the extremely helpful changeset history. 2. Use matched xenlinux/hypervisor pairs. At the OLS Xen mini-summit there was some discussion of compatibility. The statements were: - old domU should run on new hypervisor - new domU NOT guaranteed to run on old hypervisor - dom0 and hypervisor should be MATCHED Presently (kernel-2.6.17-1.2432.fc6.src.rpm) it appears that the hypervisor and xen patch are both dated 20060719. That's a good sign! :-) It would be great if you could provide some indication of your intent to continue using matched pairs. Are they actually based on the same xen-unstable changeset? We, the users, can't tell because the tarball is dated instead of cset-stamped, and Juan's tree isn't available. See #1 ;-) 3. Apply my kernel.spec and config changes at the end of this email. This would make it much easier for the ia64 developers to do test builds and track down failures. Presently it's a pain for me to maintain this out of tree. 4. Apply the xen.spec and libvirt.spec changes. https://www.redhat.com/archives/fedora-xen/2006-July/msg00022.html https://www.redhat.com/archives/fedora-xen/2006-July/msg00021.html Regarding libvirt.spec, I've talked with Daniel and he's just waiting for xen.spec to be ia64-enabled... Objections/comments? I'll attempt to update any relevant BZs today. Thanks, Aron b/devel/configs/config-xen-ia64 | 20 ++++++++++++++++ devel/Makefile.config | 18 ++++++++++++-- devel/kernel-2.6.spec | 50 +++++++++++++++++++++++++++++----------- 3 files changed, 72 insertions(+), 16 deletions(-) diff -r 658c33aa557a -r 250cc32cdde6 devel/Makefile.config --- a/devel/Makefile.config Sat Jul 22 09:19:48 2006 -0400 +++ b/devel/Makefile.config Sat Jul 22 09:25:25 2006 -0400 @@ -12,7 +12,8 @@ CONFIGFILES = \ $(CFG)-s390.config $(CFG)-s390x.config \ $(CFG)-ppc.config $(CFG)-ppc-smp.config \ $(CFG)-ppc64.config $(CFG)-ppc64-kdump.config $(CFG)-ia64.config \ - $(CFG)-i686-xen.config $(CFG)-x86_64-xen.config + $(CFG)-i686-xen.config $(CFG)-x86_64-xen.config \ + $(CFG)-ia64-xen.config PLATFORMS = x86 x86_64 powerpc powerpc32 powerpc64 s390 ia64 # sparc sparc64 TEMPFILES = $(addprefix temp-, $(addsuffix -generic, $(PLATFORMS))) @@ -20,8 +21,10 @@ configs: $(CONFIGFILES) configs: $(CONFIGFILES) @rm -f kernel-*-config @rm -f $(TEMPFILES) - @rm -f temp-xen-generic temp-x86-xen-generic temp-x86_64-xen-generic \ - temp-generic temp-x86_64-xen-generic-tmp + @rm -f temp-generic temp-xen-generic \ + temp-x86-xen-generic \ + temp-x86_64-xen-generic temp-x86_64-xen-generic-tmp \ + temp-ia64-xen-generic temp-ia64-xen-generic-tmp # Augment the clean target to clean up our own cruft clean :: @@ -67,6 +70,12 @@ temp-x86_64-xen-generic-tmp: configs/con perl merge.pl $^ > $@ temp-x86_64-xen-generic: configs/config-xen-x86_64 temp-x86_64-xen-generic-tmp + perl merge.pl $^ > $@ + +temp-ia64-xen-generic-tmp: configs/config-xen-generic temp-ia64-generic + perl merge.pl $^ > $@ + +temp-ia64-xen-generic: configs/config-xen-ia64 temp-ia64-xen-generic-tmp perl merge.pl $^ > $@ kernel-$(VERSION)-i686.config: configs/config-i686 temp-x86-generic @@ -132,3 +141,6 @@ kernel-$(VERSION)-x86_64-xen.config: con kernel-$(VERSION)-x86_64-xen.config: configs/config-x86_64 temp-x86_64-xen-generic perl merge.pl $^ x86_64 > $@ +kernel-$(VERSION)-ia64-xen.config: configs/config-xen-xen temp-ia64-xen-generic + perl merge.pl $^ ia64 > $@ + diff -r 658c33aa557a -r 250cc32cdde6 devel/kernel-2.6.spec --- a/devel/kernel-2.6.spec Sat Jul 22 09:19:48 2006 -0400 +++ b/devel/kernel-2.6.spec Sat Jul 22 09:25:25 2006 -0400 @@ -36,6 +36,9 @@ Summary: The Linux kernel (the core of t %define xen_version 20060719 %define make_target bzImage %define kernel_image x86 +%define xen_flags verbose=y debug=y crash_debug=y pae=y +%define xen_target vmlinuz +%define xen_image vmlinuz %define KVERREL %{PACKAGE_VERSION}-%{PACKAGE_RELEASE} @@ -56,10 +59,14 @@ Summary: The Linux kernel (the core of t %define all_arch_configs $RPM_SOURCE_DIR/kernel-%{kversion}-*.config %endif -# Xen and kdump only build on i686 and x86_64 ... +# kdump only builds on i686 and x86_64 %ifnarch i686 x86_64 +%define buildkdump 0 +%endif + +# Xen only builds on i686, x86_64 and ia64 ... +%ifnarch i686 x86_64 ia64 %define buildxen 0 -%define buildkdump 0 %endif %ifarch ppc64 @@ -134,11 +141,15 @@ Summary: The Linux kernel (the core of t %endif %ifarch ia64 -%define all_arch_configs $RPM_SOURCE_DIR/kernel-%{kversion}-ia64.config +%define all_arch_configs $RPM_SOURCE_DIR/kernel-%{kversion}-ia64*.config %define image_install_path boot/efi/EFI/redhat #define signmodules 1 %define make_target compressed %define kernel_image vmlinux.gz +# ia64 doesn't building with debug=y at the moment +%define xen_flags verbose=y crash_debug=y +%define xen_target compressed +%define xen_image vmlinux.gz %endif # @@ -237,6 +248,7 @@ Source33: kernel-%{kversion}-i686-xen.co Source33: kernel-%{kversion}-i686-xen.config Source34: kernel-%{kversion}-x86_64-xen.config Source35: kernel-%{kversion}-i686-kdump.config +Source36: kernel-%{kversion}-ia64-xen.config #Source66: kernel-%{kversion}-sparc.config #Source67: kernel-%{kversion}-sparc64.config @@ -785,17 +797,29 @@ cd linux-%{kversion}.%{_target_cpu} # %patch950 -p1 -b .p.xen # -# ... and back out all the ia64-specific sections, as they currently prevent +# ... and back out all the tpm-specific sections, as they currently prevent # non-xen builds from working. -# Now also with tpm -# -for f in `find drivers/char/tpm arch/ia64/ include/asm-ia64/ include/xen/interface/arch-ia64.h* -type f -name "*.p.xen"` ; do \ +# +for f in `find drivers/char/tpm -type f -name "*.p.xen"` ; do \ g=`dirname $f`/`basename $f .p.xen`; \ mv "$f" "$g"; \ if [ ! -s "$g" ] ; then rm -f "$g" ; fi; \ done # Delete the rest of the backup files, they just confuse the build later find -name "*.p.xen" | xargs rm -f + +# These are fixed in xen-ia64-unstable, they will announce their retirement +# automatically when the changes propogate down the chain to Juan +if [[ ! -f arch/ia64/kernel/asm-offsets.c ]]; then + ln -sf ../../../../xen/include/asm-ia64/asm-xsi-offsets.h include/asm-ia64/xen/ +else + printf "*\n* please retire asm-xsi-offsets.h symlink from kernel-2.6.spec\n*\n" +fi +if grep -q xenia64_init drivers/xen/core/Makefile; then + ln -sf ../../../arch/ia64/xen/drivers/xenia64_init.c drivers/xen/core/ +else + printf "*\n* please retire xenia64_init.c symlink from kernel-2.6.spec\n*\n" +fi %patch951 -p1 %patch952 -p1 @@ -1235,9 +1259,9 @@ mkdir -p $RPM_BUILD_ROOT/boot %if %{includexen} %if %{buildxen} cd xen - mkdir -p $RPM_BUILD_ROOT/%{image_install_path} - make debug=y verbose=y crash_debug=y pae=y - install -m 644 xen.gz $RPM_BUILD_ROOT/boot/xen.gz-%{KVERREL} + mkdir -p $RPM_BUILD_ROOT/%{image_install_path} $RPM_BUILD_ROOT/boot + make %{?_smp_mflags} %{xen_flags} + install -m 644 xen.gz $RPM_BUILD_ROOT/%{image_install_path}/xen.gz-%{KVERREL} install -m 755 xen-syms $RPM_BUILD_ROOT/boot/xen-syms-%{KVERREL} cd .. mkdir -p $RPM_BUILD_ROOT/usr/src/kernels/%{KVERREL}-xen-%{_target_cpu} @@ -1261,7 +1285,7 @@ BuildKernel %make_target %kernel_image s %if %{includexen} %if %{buildxen} -BuildKernel vmlinuz vmlinuz xen +BuildKernel %xen_target %xen_image xen %endif %endif @@ -1432,7 +1456,7 @@ fi %post xen [ ! -x /usr/sbin/module_upgrade ] || /usr/sbin/module_upgrade %{rpmversion}-%{release}-xen if [ -e /proc/xen/xsd_kva -o ! -d /proc/xen ]; then - /sbin/new-kernel-pkg --package kernel-xen --mkinitrd --depmod --install --multiboot=/boot/xen.gz-%{KVERREL} %{KVERREL}xen + /sbin/new-kernel-pkg --package kernel-xen --mkinitrd --depmod --install --multiboot=/%{image_install_path}/xen.gz-%{KVERREL} %{KVERREL}xen else /sbin/new-kernel-pkg --package kernel-xen --mkinitrd --depmod --install %{KVERREL}xen fi @@ -1565,7 +1589,7 @@ fi /boot/symvers-%{KVERREL}xen.gz /boot/symsets-%{KVERREL}xen.tar.gz /boot/config-%{KVERREL}xen -/boot/xen.gz-%{KVERREL} +/%{image_install_path}/xen.gz-%{KVERREL} /boot/xen-syms-%{KVERREL} %dir /lib/modules/%{KVERREL}xen /lib/modules/%{KVERREL}xen/kernel diff -r 658c33aa557a -r 250cc32cdde6 devel/configs/config-xen-ia64 --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/devel/configs/config-xen-ia64 Sat Jul 22 09:25:25 2006 -0400 @@ -0,0 +1,20 @@ +# override i686 xen + +# CONFIG_X86 is not set +# CONFIG_X86_XEN is not set +CONFIG_IA64=y +CONFIG_XEN=y +CONFIG_XEN_IA64_DOM0_VP=y +CONFIG_XEN_DISABLE_SERIAL=y + +# override ia64 generic + +# CONFIG_IA64_GENERIC is not set +CONFIG_IA64_DIG=y +# CONFIG_DISCONTIGMEM_MANUAL is not set +# CONFIG_SPARSEMEM_MANUAL is not set +CONFIG_FLATMEM_MANUAL=y +CONFIG_FORCE_MAX_ZONEORDER=11 + +# internal #defines conflict with xen-ia64 +# CONFIG_FB_NEOMAGIC is not set From chrisw at sous-sol.org Fri Jul 21 21:52:48 2006 From: chrisw at sous-sol.org (Chris Wright) Date: Fri, 21 Jul 2006 14:52:48 -0700 Subject: [Fedora-xen] Re: [RFC] Using linux-2.6.tip-xen on IA64 In-Reply-To: <8C6AB9D160FFEtakebe_akio@jp.fujitsu.com> References: <8C6AB9D160FFEtakebe_akio@jp.fujitsu.com> Message-ID: <20060721215248.GO2654@sequoia.sous-sol.org> * Akio Takebe (takebe_akio at jp.fujitsu.com) wrote: > We can success booting domU with linux-2.6.tip-xen. > (This is FedoraCore work.) > The build step is the below. > I think the step is almost same as Aron's step. > (http://free.linux.hp.com/~agriffis/fedora-kernel-ia64/.) > We used linux-2.6.tip-xen.hg(cset #30476) and > xen-unstable.hg(cset #10474). > > 1. hg clone http://xenbits.xensource.com/ext/linux-2.6.tip-xen.hg > 2. copy xen/include/asm-ia64/asm-xsi-offsets.h > from xen-ia64-unstable.hg > to linux-2.6.tip-xen.hg/include/asm-ia64/xen/ > 3. copy .config > from xen-ia64-unstable.hg/buildconfigs/linux-defconfig_xen_ia64 > to linux-2.6.tip-xen/.config > 4. make oldconfig > (All answers are default) > 5. copy linux-2.6.tip-xen.hg/arch/ia64/kernel/gate.S Hmm, I figured this might be an issue. > from linux-2.6.16.13.tar.bz2 > 6. cd linux-2.6.tip-xen.hg > make & copy vmlinuz & mkinitrd > 7. build xen-unstable.hg (cset #10474) > hg clone xen-unstable.hg xen-unstable.hg-match-linux-2.6.tip > cd xen-unstable.hg-match-linux.2.6.tip > hg up -C 10474 > make > 8. copy xen.gz to under /boot/efi/ > 9. make install-tools > > But I found some problem. Please comments. > A. We cannot compile the latest linux-2.6.tip-xen(#32966). > Is fixing linux-2.6.tip-xen fc6's or xen-ia64's contribution? > Or is anyone already working for that? I have not tried compiling it on ia64. Could you show us the compile errors? Or if you know the problem, send a patch? > B. linux-2.6.tip-xen don't have arch/ia64/kernel/gate.S. Why? This is likely a merge error. The merge thought the file was dropped from upstream Linux. Feel free to send the proper patch. thanks, -chris From prarit at redhat.com Sat Jul 22 13:40:32 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Sat, 22 Jul 2006 09:40:32 -0400 Subject: [Fedora-xen] Re: Four ways RH could help with xen-ia64 In-Reply-To: <20060722133124.GB12649@mustard> References: <20060722133124.GB12649@mustard> Message-ID: <44C22AD0.6050509@redhat.com> > > > 4. Apply the xen.spec and libvirt.spec changes. > https://www.redhat.com/archives/fedora-xen/2006-July/msg00022.html > https://www.redhat.com/archives/fedora-xen/2006-July/msg00021.html > > Regarding libvirt.spec, I've talked with Daniel and he's just > waiting for xen.spec to be ia64-enabled... > > Objections/comments? I'll attempt to update any relevant BZs today. > > Aron, Fedora has moved forward to 2.6.18. We'll have to port forward the 2.6.17 ia64 changes and then apply the kernel.rpm patch below. The BZs I've opened are: 199683 Fedora Core NEW normal enable xen-ia64 in fedora kernel cvs 199684 Fedora Core NEW normal Forward port 2.6.17 ia64 xen to 2.6.18 199685 Fedora Core NEW normal enable ia64 builds for libvirt 199686 Fedora Core NEW normal enable ia64 builds for the xen rpm P. > Thanks, > Aron > > b/devel/configs/config-xen-ia64 | 20 ++++++++++++++++ > devel/Makefile.config | 18 ++++++++++++-- > devel/kernel-2.6.spec | 50 +++++++++++++++++++++++++++++----------- > 3 files changed, 72 insertions(+), 16 deletions(-) > > diff -r 658c33aa557a -r 250cc32cdde6 devel/Makefile.config > --- a/devel/Makefile.config Sat Jul 22 09:19:48 2006 -0400 > +++ b/devel/Makefile.config Sat Jul 22 09:25:25 2006 -0400 > @@ -12,7 +12,8 @@ CONFIGFILES = \ > $(CFG)-s390.config $(CFG)-s390x.config \ > $(CFG)-ppc.config $(CFG)-ppc-smp.config \ > $(CFG)-ppc64.config $(CFG)-ppc64-kdump.config $(CFG)-ia64.config \ > - $(CFG)-i686-xen.config $(CFG)-x86_64-xen.config > + $(CFG)-i686-xen.config $(CFG)-x86_64-xen.config \ > + $(CFG)-ia64-xen.config > > PLATFORMS = x86 x86_64 powerpc powerpc32 powerpc64 s390 ia64 # sparc sparc64 > TEMPFILES = $(addprefix temp-, $(addsuffix -generic, $(PLATFORMS))) > @@ -20,8 +21,10 @@ configs: $(CONFIGFILES) > configs: $(CONFIGFILES) > @rm -f kernel-*-config > @rm -f $(TEMPFILES) > - @rm -f temp-xen-generic temp-x86-xen-generic temp-x86_64-xen-generic \ > - temp-generic temp-x86_64-xen-generic-tmp > + @rm -f temp-generic temp-xen-generic \ > + temp-x86-xen-generic \ > + temp-x86_64-xen-generic temp-x86_64-xen-generic-tmp \ > + temp-ia64-xen-generic temp-ia64-xen-generic-tmp > > # Augment the clean target to clean up our own cruft > clean :: > @@ -67,6 +70,12 @@ temp-x86_64-xen-generic-tmp: configs/con > perl merge.pl $^ > $@ > > temp-x86_64-xen-generic: configs/config-xen-x86_64 temp-x86_64-xen-generic-tmp > + perl merge.pl $^ > $@ > + > +temp-ia64-xen-generic-tmp: configs/config-xen-generic temp-ia64-generic > + perl merge.pl $^ > $@ > + > +temp-ia64-xen-generic: configs/config-xen-ia64 temp-ia64-xen-generic-tmp > perl merge.pl $^ > $@ > > kernel-$(VERSION)-i686.config: configs/config-i686 temp-x86-generic > @@ -132,3 +141,6 @@ kernel-$(VERSION)-x86_64-xen.config: con > kernel-$(VERSION)-x86_64-xen.config: configs/config-x86_64 temp-x86_64-xen-generic > perl merge.pl $^ x86_64 > $@ > > +kernel-$(VERSION)-ia64-xen.config: configs/config-xen-xen temp-ia64-xen-generic > + perl merge.pl $^ ia64 > $@ > + > diff -r 658c33aa557a -r 250cc32cdde6 devel/kernel-2.6.spec > --- a/devel/kernel-2.6.spec Sat Jul 22 09:19:48 2006 -0400 > +++ b/devel/kernel-2.6.spec Sat Jul 22 09:25:25 2006 -0400 > @@ -36,6 +36,9 @@ Summary: The Linux kernel (the core of t > %define xen_version 20060719 > %define make_target bzImage > %define kernel_image x86 > +%define xen_flags verbose=y debug=y crash_debug=y pae=y > +%define xen_target vmlinuz > +%define xen_image vmlinuz > > %define KVERREL %{PACKAGE_VERSION}-%{PACKAGE_RELEASE} > > @@ -56,10 +59,14 @@ Summary: The Linux kernel (the core of t > %define all_arch_configs $RPM_SOURCE_DIR/kernel-%{kversion}-*.config > %endif > > -# Xen and kdump only build on i686 and x86_64 ... > +# kdump only builds on i686 and x86_64 > %ifnarch i686 x86_64 > +%define buildkdump 0 > +%endif > + > +# Xen only builds on i686, x86_64 and ia64 ... > +%ifnarch i686 x86_64 ia64 > %define buildxen 0 > -%define buildkdump 0 > %endif > > %ifarch ppc64 > @@ -134,11 +141,15 @@ Summary: The Linux kernel (the core of t > %endif > > %ifarch ia64 > -%define all_arch_configs $RPM_SOURCE_DIR/kernel-%{kversion}-ia64.config > +%define all_arch_configs $RPM_SOURCE_DIR/kernel-%{kversion}-ia64*.config > %define image_install_path boot/efi/EFI/redhat > #define signmodules 1 > %define make_target compressed > %define kernel_image vmlinux.gz > +# ia64 doesn't building with debug=y at the moment > +%define xen_flags verbose=y crash_debug=y > +%define xen_target compressed > +%define xen_image vmlinux.gz > %endif > > # > @@ -237,6 +248,7 @@ Source33: kernel-%{kversion}-i686-xen.co > Source33: kernel-%{kversion}-i686-xen.config > Source34: kernel-%{kversion}-x86_64-xen.config > Source35: kernel-%{kversion}-i686-kdump.config > +Source36: kernel-%{kversion}-ia64-xen.config > > #Source66: kernel-%{kversion}-sparc.config > #Source67: kernel-%{kversion}-sparc64.config > @@ -785,17 +797,29 @@ cd linux-%{kversion}.%{_target_cpu} > # > %patch950 -p1 -b .p.xen > # > -# ... and back out all the ia64-specific sections, as they currently prevent > +# ... and back out all the tpm-specific sections, as they currently prevent > # non-xen builds from working. > -# Now also with tpm > -# > -for f in `find drivers/char/tpm arch/ia64/ include/asm-ia64/ include/xen/interface/arch-ia64.h* -type f -name "*.p.xen"` ; do \ > +# > +for f in `find drivers/char/tpm -type f -name "*.p.xen"` ; do \ > g=`dirname $f`/`basename $f .p.xen`; \ > mv "$f" "$g"; \ > if [ ! -s "$g" ] ; then rm -f "$g" ; fi; \ > done > # Delete the rest of the backup files, they just confuse the build later > find -name "*.p.xen" | xargs rm -f > + > +# These are fixed in xen-ia64-unstable, they will announce their retirement > +# automatically when the changes propogate down the chain to Juan > +if [[ ! -f arch/ia64/kernel/asm-offsets.c ]]; then > + ln -sf ../../../../xen/include/asm-ia64/asm-xsi-offsets.h include/asm-ia64/xen/ > +else > + printf "*\n* please retire asm-xsi-offsets.h symlink from kernel-2.6.spec\n*\n" > +fi > +if grep -q xenia64_init drivers/xen/core/Makefile; then > + ln -sf ../../../arch/ia64/xen/drivers/xenia64_init.c drivers/xen/core/ > +else > + printf "*\n* please retire xenia64_init.c symlink from kernel-2.6.spec\n*\n" > +fi > > %patch951 -p1 > %patch952 -p1 > @@ -1235,9 +1259,9 @@ mkdir -p $RPM_BUILD_ROOT/boot > %if %{includexen} > %if %{buildxen} > cd xen > - mkdir -p $RPM_BUILD_ROOT/%{image_install_path} > - make debug=y verbose=y crash_debug=y pae=y > - install -m 644 xen.gz $RPM_BUILD_ROOT/boot/xen.gz-%{KVERREL} > + mkdir -p $RPM_BUILD_ROOT/%{image_install_path} $RPM_BUILD_ROOT/boot > + make %{?_smp_mflags} %{xen_flags} > + install -m 644 xen.gz $RPM_BUILD_ROOT/%{image_install_path}/xen.gz-%{KVERREL} > install -m 755 xen-syms $RPM_BUILD_ROOT/boot/xen-syms-%{KVERREL} > cd .. > mkdir -p $RPM_BUILD_ROOT/usr/src/kernels/%{KVERREL}-xen-%{_target_cpu} > @@ -1261,7 +1285,7 @@ BuildKernel %make_target %kernel_image s > > %if %{includexen} > %if %{buildxen} > -BuildKernel vmlinuz vmlinuz xen > +BuildKernel %xen_target %xen_image xen > %endif > %endif > > @@ -1432,7 +1456,7 @@ fi > %post xen > [ ! -x /usr/sbin/module_upgrade ] || /usr/sbin/module_upgrade %{rpmversion}-%{release}-xen > if [ -e /proc/xen/xsd_kva -o ! -d /proc/xen ]; then > - /sbin/new-kernel-pkg --package kernel-xen --mkinitrd --depmod --install --multiboot=/boot/xen.gz-%{KVERREL} %{KVERREL}xen > + /sbin/new-kernel-pkg --package kernel-xen --mkinitrd --depmod --install --multiboot=/%{image_install_path}/xen.gz-%{KVERREL} %{KVERREL}xen > else > /sbin/new-kernel-pkg --package kernel-xen --mkinitrd --depmod --install %{KVERREL}xen > fi > @@ -1565,7 +1589,7 @@ fi > /boot/symvers-%{KVERREL}xen.gz > /boot/symsets-%{KVERREL}xen.tar.gz > /boot/config-%{KVERREL}xen > -/boot/xen.gz-%{KVERREL} > +/%{image_install_path}/xen.gz-%{KVERREL} > /boot/xen-syms-%{KVERREL} > %dir /lib/modules/%{KVERREL}xen > /lib/modules/%{KVERREL}xen/kernel > diff -r 658c33aa557a -r 250cc32cdde6 devel/configs/config-xen-ia64 > --- /dev/null Thu Jan 01 00:00:00 1970 +0000 > +++ b/devel/configs/config-xen-ia64 Sat Jul 22 09:25:25 2006 -0400 > @@ -0,0 +1,20 @@ > +# override i686 xen > + > +# CONFIG_X86 is not set > +# CONFIG_X86_XEN is not set > +CONFIG_IA64=y > +CONFIG_XEN=y > +CONFIG_XEN_IA64_DOM0_VP=y > +CONFIG_XEN_DISABLE_SERIAL=y > + > +# override ia64 generic > + > +# CONFIG_IA64_GENERIC is not set > +CONFIG_IA64_DIG=y > +# CONFIG_DISCONTIGMEM_MANUAL is not set > +# CONFIG_SPARSEMEM_MANUAL is not set > +CONFIG_FLATMEM_MANUAL=y > +CONFIG_FORCE_MAX_ZONEORDER=11 > + > +# internal #defines conflict with xen-ia64 > +# CONFIG_FB_NEOMAGIC is not set > From quintela at redhat.com Sat Jul 22 14:33:50 2006 From: quintela at redhat.com (Juan Quintela) Date: Sat, 22 Jul 2006 16:33:50 +0200 Subject: [Fedora-xen] Re: Four ways RH could help with xen-ia64 In-Reply-To: <20060722133124.GB12649@mustard> References: <20060722133124.GB12649@mustard> Message-ID: <1153578830.2461.13.camel@anano.mitica> On Sat, 2006-07-22 at 09:31 -0400, Aron Griffis wrote: > Hi guys, > > There are four ways you could be a big help to the xen-ia64 effort. > I have mentioned these in the past but never pulled them together into > a single request. Sorry for getting so long in answering you, but A PAE bug and getting linux-2.6-xen working on 2.6.18-rc2 have required all my attention :( > 1. Publish Juan's tree which is the result of his merge of > linux-2.6.tip-xen, linux-2.6 and linux-2.6-xen. How about > http://people.redhat.com/quintela/linux-2.6.tip-xen-fedora.hg? > As things stand right now, it's very difficult for ia64 devs to > contribute to Juan's patch, for 2 reasons: (1) we never see it > until after a new kernel rpm is published, (2) all we get is the > final result, lacking the extremely helpful changeset history. It is based on 2.6.18-rc2. It is on: http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora It is public only since Tuesday (I was waiting for a place where to publish it). Tree will not work on ia64, I didn't forward ported the ia64 changes, noly x86 & x86_64 (and it was painfull enough, time source, smp-alternatives x86_64, irqtrace, vDSO on x86 & friends meaned that I had to go back & re-apply series of patches one at a time to find a coulpe of bugs). > 2. Use matched xenlinux/hypervisor pairs. At the OLS Xen mini-summit > there was some discussion of compatibility. The statements were: Believe me that we _try_, and very hard. > - old domU should run on new hypervisor Agreed. I normally test plain fc5 domU on all my new kernels. > - new domU NOT guaranteed to run on old hypervisor We have found that lately this "normally" works, versus bugs. > - dom0 and hypervisor should be MATCHED Guess why HV on fedora is on the same package that the kernel, and they have indeed the same version number? > Presently (kernel-2.6.17-1.2432.fc6.src.rpm) it appears that the > hypervisor and xen patch are both dated 20060719. That's a good > sign! :-) It would be great if you could provide some indication > of your intent to continue using matched pairs. Are they actually > based on the same xen-unstable changeset? We, the users, can't > tell because the tarball is dated instead of cset-stamped, and > Juan's tree isn't available. See #1 ;-) Normally I add cset numbers in the changelog, but will try to put them into the HV version number (it maks as much sense as the date, actually). About the source tree, it is already public. It hasn't been published sooner due to lack of somobdy setting up a server. Now it is done. > 3. Apply my kernel.spec and config changes at the end of this email. > This would make it much easier for the ia64 developers to do test > builds and track down failures. Presently it's a pain for me to > maintain this out of tree. Will do today. Will send one email once this is done. > 4. Apply the xen.spec and libvirt.spec changes. > https://www.redhat.com/archives/fedora-xen/2006-July/msg00022.html > https://www.redhat.com/archives/fedora-xen/2006-July/msg00021.html > > Regarding libvirt.spec, I've talked with Daniel and he's just > waiting for xen.spec to be ia64-enabled... Will talk with daniel when he is back from OLS. > Objections/comments? I'll attempt to update any relevant BZs today. Will comment on the patches in a follow-up. Later, Juan. From quintela at redhat.com Sat Jul 22 15:08:35 2006 From: quintela at redhat.com (Juan Quintela) Date: Sat, 22 Jul 2006 17:08:35 +0200 Subject: [Fedora-xen] Re: Four ways RH could help with xen-ia64 In-Reply-To: <20060722133124.GB12649@mustard> References: <20060722133124.GB12649@mustard> Message-ID: <1153580915.2461.17.camel@anano.mitica> On Sat, 2006-07-22 at 09:31 -0400, Aron Griffis wrote: > Hi guys, Hi Aron > 3. Apply my kernel.spec and config changes at the end of this email. > This would make it much easier for the ia64 developers to do test > builds and track down failures. Presently it's a pain for me to > maintain this out of tree. Applied everything except this two bits: > @@ -56,10 +59,14 @@ Summary: The Linux kernel (the core of t > %define all_arch_configs $RPM_SOURCE_DIR/kernel-%{kversion}-*.config > %endif > > -# Xen and kdump only build on i686 and x86_64 ... > +# kdump only builds on i686 and x86_64 > %ifnarch i686 x86_64 > +%define buildkdump 0 > +%endif > + > +# Xen only builds on i686, x86_64 and ia64 ... > +%ifnarch i686 x86_64 ia64 > %define buildxen 0 > -%define buildkdump 0 > %endif Not enable ia64 until I know that it compiles at least :p > %ifarch ppc64 > @@ -785,17 +797,29 @@ cd linux-%{kversion}.%{_target_cpu} > # > %patch950 -p1 -b .p.xen > # > -# ... and back out all the ia64-specific sections, as they currently prevent > +# ... and back out all the tpm-specific sections, as they currently prevent > # non-xen builds from working. > -# Now also with tpm > -# > -for f in `find drivers/char/tpm arch/ia64/ include/asm-ia64/ include/xen/interface/arch-ia64.h* -type f -name "*.p.xen"` ; do \ > +# > +for f in `find drivers/char/tpm -type f -name "*.p.xen"` ; do \ > g=`dirname $f`/`basename $f .p.xen`; \ > mv "$f" "$g"; \ > if [ ! -s "$g" ] ; then rm -f "$g" ; fi; \ > done > # Delete the rest of the backup files, they just confuse the build later > find -name "*.p.xen" | xargs rm -f > + > +# These are fixed in xen-ia64-unstable, they will announce their retirement > +# automatically when the changes propogate down the chain to Juan > +if [[ ! -f arch/ia64/kernel/asm-offsets.c ]]; then > + ln -sf ../../../../xen/include/asm-ia64/asm-xsi-offsets.h include/asm-ia64/xen/ > +else > + printf "*\n* please retire asm-xsi-offsets.h symlink from kernel-2.6.spec\n*\n" > +fi > +if grep -q xenia64_init drivers/xen/core/Makefile; then > + ln -sf ../../../arch/ia64/xen/drivers/xenia64_init.c drivers/xen/core/ > +else > + printf "*\n* please retire xenia64_init.c symlink from kernel-2.6.spec\n*\n" > +fi > > %patch951 -p1 > %patch952 -p1 I need this to get plain ia64 compiling. I will get an account in an ia64 machine at some point next week. Once that I check that plain ia64 compiles out of my tree, I remove this bit. Fair enough? Comments? Later, Juan. From mickeyboa at sbcglobal.net Mon Jul 24 15:13:00 2006 From: mickeyboa at sbcglobal.net (jim tate) Date: Mon, 24 Jul 2006 11:13:00 -0400 Subject: [Fedora-xen] Xen0 not booting into Login console Message-ID: <44C4E37C.60907@sbcglobal.net> kernel-2.6.17-1.2157_FC5xen0 will boot up and install running damons, but won't get to Login Console so as to login. Jim From mickeyboa at sbcglobal.net Mon Jul 24 21:57:26 2006 From: mickeyboa at sbcglobal.net (jim tate) Date: Mon, 24 Jul 2006 17:57:26 -0400 Subject: [Fedora-xen] Xen0 not booting into Login console In-Reply-To: <44C4E37C.60907@sbcglobal.net> References: <44C4E37C.60907@sbcglobal.net> Message-ID: <44C54246.6040909@sbcglobal.net> jim tate wrote: > kernel-2.6.17-1.2157_FC5xen0 will boot up and install running damons, > but won't get to Login Console so as to login. > > Jim > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > I checked /var/log/messages and messages has 809 lines in it so I couldn't list all of it in this email, but I can list the last lines of /var/log/messages, and I listed all of xend.debug.log, xend.log. Thanks Jim /var/log/messages Jul 24 16:57:08 FC5-X86-64 kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.1 Jul 24 16:57:08 FC5-X86-64 kernel: SELinux: initialized (dev autofs, type autofs), uses genfs_contexts Jul 24 16:57:08 FC5-X86-64 kernel: audit(1153774628.858:4): avc: denied { read write } for pid=2513 comm="xend" name="0" dev=devpts ino=2 scontext=system_u:system_r:xend_t:s0 tcontext=system_u:object_r:initrc_devpts_t:s0 tclass=chr_file Jul 24 16:57:08 FC5-X86-64 kernel: audit(1153774628.858:5): avc: denied { read write } for pid=2513 comm="xend" name="0" dev=devpts ino=2 scontext=system_u:system_r:xend_t:s0 tcontext=system_u:object_r:initrc_devpts_t:s0 tclass=chr_file Jul 24 16:57:08 FC5-X86-64 kernel: audit(1153774628.858:6): avc: denied { read write } for pid=2513 comm="xend" name="0" dev=devpts ino=2 scontext=system_u:system_r:xend_t:s0 tcontext=system_u:object_r:initrc_devpts_t:s0 tclass=chr_file Jul 24 16:57:10 FC5-X86-64 xenstored: Checking store ... Jul 24 16:57:11 FC5-X86-64 xenstored: Checking store complete. Jul 24 16:57:11 FC5-X86-64 xenstored: Checking store ... Jul 24 16:57:11 FC5-X86-64 xenstored: Checking store complete. Jul 24 16:57:14 FC5-X86-64 kernel: Bridge firewalling registered Jul 24 16:57:15 FC5-X86-64 NET[2678]: /sbin/dhclient-script : updated /etc/resolv.conf Jul 24 16:57:15 FC5-X86-64 avahi-daemon[2429]: Withdrawing address record for 172.16.1.37 on eth0. Jul 24 16:57:15 FC5-X86-64 avahi-daemon[2429]: Leaving mDNS multicast group on interface eth0.IPv4 with address 172.16.1.37. Jul 24 16:57:15 FC5-X86-64 avahi-daemon[2429]: IP_DROP_MEMBERSHIP failed: No such device Jul 24 16:57:15 FC5-X86-64 avahi-daemon[2429]: iface.c: interface_mdns_mcast_join() called but no local address available. Jul 24 16:57:15 FC5-X86-64 avahi-daemon[2429]: Interface eth0.IPv4 no longer relevant for mDNS. Jul 24 16:57:16 FC5-X86-64 kernel: sky2 eth0: disabling interface Jul 24 16:57:16 FC5-X86-64 kernel: device vif0.0 entered promiscuous mode Jul 24 16:57:16 FC5-X86-64 kernel: audit(1153774636.398:7): dev=vif0.0 prom=256 old_prom=0 auid=4294967295 Jul 24 16:57:16 FC5-X86-64 kernel: xenbr0: port 1(vif0.0) entering learning state Jul 24 16:57:16 FC5-X86-64 kernel: sky2 peth0: enabling interface Jul 24 16:57:16 FC5-X86-64 kernel: xenbr0: topology change detected, propagating Jul 24 16:57:16 FC5-X86-64 kernel: xenbr0: port 1(vif0.0) entering forwarding state Jul 24 16:57:17 FC5-X86-64 kernel: device peth0 entered promiscuous mode Jul 24 16:57:17 FC5-X86-64 kernel: audit(1153774637.254:8): dev=peth0 prom=256 old_prom=0 auid=4294967295 Jul 24 16:57:17 FC5-X86-64 kernel: xenbr0: port 2(peth0) entering learning state Jul 24 16:57:17 FC5-X86-64 kernel: xenbr0: topology change detected, propagating Jul 24 16:57:17 FC5-X86-64 kernel: xenbr0: port 2(peth0) entering forwarding state Jul 24 16:57:18 FC5-X86-64 kernel: sky2 peth0: Link is up at 100 Mbps, full duplex, flow control none Jul 24 16:57:18 FC5-X86-64 kernel: audit(1153774638.186:9): avc: denied { write } for pid=2725 comm="ifup-eth" name="dhclient-eth0.conf" dev=hda1 ino=15206186 scontext=system_u:system_r:xend_t:s0 tcontext=system_u:object_r:dhcp_etc_t:s0 tclass=file Jul 24 16:57:18 FC5-X86-64 kernel: audit(1153774638.186:10): avc: denied { write } for pid=2725 comm="ifup-eth" name="dhclient-eth0.conf" dev=hda1 ino=15206186 scontext=system_u:system_r:xend_t:s0 tcontext=system_u:object_r:dhcp_etc_t:s0 tclass=file Jul 24 16:57:18 FC5-X86-64 kernel: audit(1153774638.186:11): avc: denied { getattr } for pid=2725 comm="ifup-eth" name="dhclient-eth0.conf" dev=hda1 ino=15206186 scontext=system_u:system_r:xend_t:s0 tcontext=system_u:object_r:dhcp_etc_t:s0 tclass=file Jul 24 16:57:18 FC5-X86-64 kernel: audit(1153774638.186:12): avc: denied { append } for pid=2725 comm="ifup-eth" name="dhclient-eth0.conf" dev=hda1 ino=15206186 scontext=system_u:system_r:xend_t:s0 tcontext=system_u:object_r:dhcp_etc_t:s0 tclass=file Jul 24 16:57:18 FC5-X86-64 kernel: audit(1153774638.186:13): avc: denied { append } for pid=2725 comm="ifup-eth" name="dhclient-eth0.conf" dev=hda1 ino=15206186 scontext=system_u:system_r:xend_t:s0 tcontext=system_u:object_r:dhcp_etc_t:s0 tclass=file Jul 24 16:57:18 FC5-X86-64 kernel: audit(1153774638.386:14): avc: denied { getattr } for pid=2725 comm="ifup-eth" name="dhclient-eth0.conf" dev=hda1 ino=15206186 scontext=system_u:system_r:xend_t:s0 tcontext=system_u:object_r:dhcp_etc_t:s0 tclass=file Jul 24 16:57:18 FC5-X86-64 avahi-daemon[2429]: New relevant interface eth0.IPv4 for mDNS. Jul 24 16:57:18 FC5-X86-64 avahi-daemon[2429]: Joining mDNS multicast group on interface eth0.IPv4 with address 172.16.1.37. Jul 24 16:57:18 FC5-X86-64 avahi-daemon[2429]: Registering new address record for 172.16.1.37 on eth0. Jul 24 16:57:19 FC5-X86-64 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jul 24 16:57:21 FC5-X86-64 dhclient: DHCPACK from 172.16.0.1 Jul 24 16:57:22 FC5-X86-64 NET[2868]: /sbin/dhclient-script : updated /etc/resolv.conf Jul 24 16:57:22 FC5-X86-64 dhclient: bound to 172.16.1.37 -- renewal in 1658 seconds. Jul 24 16:57:22 FC5-X86-64 kernel: audit(1153774642.646:15): avc: denied { create } for pid=2895 comm="python" name="xend" scontext=system_u:system_r:xend_t:s0 tcontext=system_u:object_r:var_run_t:s0 tclass=dir xend-debug.log: /etc/sysconfig/network-scripts/ifup-eth: line 156: /etc/dhclient-eth0.conf: Permission denied Exception in thread Thread-3: Traceback (most recent call last): File "/usr/lib64/python2.4/threading.py", line 442, in __bootstrap self.run() File "/usr/lib64/python2.4/threading.py", line 422, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.4/site-packages/xen/xend/server/XMLRPCServer.py", line 94, in run self.server = UnixXMLRPCServer(XML_RPC_SOCKET, False) File "/usr/lib64/python2.4/site-packages/xen/util/xmlrpclib2.py", line 152, in __init__ os.makedirs(parent, stat.S_IRWXU) File "/usr/lib64/python2.4/os.py", line 159, in makedirs mkdir(name, mode) OSError: [Errno 13] Permission denied: '/var/run/xend' Xend.log [2006-07-24 09:50:01 xend] INFO (SrvDaemon:283) Xend Daemon started [2006-07-24 09:50:01 xend] INFO (SrvDaemon:287) Xend changeset: unavailable . [2006-07-24 09:50:01 xend.XendDomainInfo] DEBUG (XendDomainInfo:207) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 26024179800L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 956048, 'maxmem_kb': 17179869180, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 1, 'blocked': 0}) [2006-07-24 09:50:01 xend.XendDomainInfo] INFO (XendDomainInfo:219) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [2006-07-24 09:50:01 xend.XendDomainInfo] WARNING (XendDomainInfo:241) No vm path in store for existing domain 0 [2006-07-24 09:50:01 xend.XendDomainInfo] DEBUG (XendDomainInfo:701) Storing VM details: {'name': 'Domain-0', 'on_reboot': 'restart', 'on_poweroff': 'destroy', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_crash': 'restart', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '934', 'maxmem': '934'} [2006-07-24 09:50:01 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing domain details: {'cpu/0/availability': 'online', 'memory/target': '956416', 'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'} [2006-07-24 09:50:01 xend] DEBUG (XendDomain:153) number of vcpus to use is 0 [2006-07-24 09:50:01 xend.XendDomainInfo] DEBUG (XendDomainInfo:919) XendDomainInfo.handleShutdownWatch [2006-07-24 09:52:19 xend] INFO (SrvDaemon:283) Xend Daemon started [2006-07-24 09:52:19 xend] INFO (SrvDaemon:287) Xend changeset: unavailable . [2006-07-24 09:52:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:207) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 28368961029L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 956048, 'maxmem_kb': 17179869180, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 1, 'blocked': 0}) [2006-07-24 09:52:19 xend.XendDomainInfo] INFO (XendDomainInfo:219) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [2006-07-24 09:52:19 xend.XendDomainInfo] WARNING (XendDomainInfo:241) No vm path in store for existing domain 0 [2006-07-24 09:52:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:701) Storing VM details: {'name': 'Domain-0', 'on_reboot': 'restart', 'on_poweroff': 'destroy', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_crash': 'restart', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '934', 'maxmem': '934'} [2006-07-24 09:52:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing domain details: {'cpu/0/availability': 'online', 'memory/target': '956416', 'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'} [2006-07-24 09:52:19 xend] DEBUG (XendDomain:153) number of vcpus to use is 0 [2006-07-24 09:52:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:919) XendDomainInfo.handleShutdownWatch [2006-07-24 10:43:22 xend] INFO (SrvDaemon:283) Xend Daemon started [2006-07-24 10:43:22 xend] INFO (SrvDaemon:287) Xend changeset: unavailable . [2006-07-24 10:43:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:207) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 29584039681L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 956048, 'maxmem_kb': 17179869180, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 1, 'blocked': 0}) [2006-07-24 10:43:23 xend.XendDomainInfo] INFO (XendDomainInfo:219) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [2006-07-24 10:43:23 xend.XendDomainInfo] WARNING (XendDomainInfo:241) No vm path in store for existing domain 0 [2006-07-24 10:43:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:701) Storing VM details: {'name': 'Domain-0', 'on_reboot': 'restart', 'on_poweroff': 'destroy', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_crash': 'restart', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '934', 'maxmem': '934'} [2006-07-24 10:43:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing domain details: {'cpu/0/availability': 'online', 'memory/target': '956416', 'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'} [2006-07-24 10:43:23 xend] DEBUG (XendDomain:153) number of vcpus to use is 0 [2006-07-24 10:43:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:919) XendDomainInfo.handleShutdownWatch [2006-07-24 16:27:46 xend] INFO (SrvDaemon:283) Xend Daemon started [2006-07-24 16:27:46 xend] INFO (SrvDaemon:287) Xend changeset: unavailable . [2006-07-24 16:27:47 xend.XendDomainInfo] DEBUG (XendDomainInfo:207) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 29453124281L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 956048, 'maxmem_kb': 17179869180, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 1, 'blocked': 0}) [2006-07-24 16:27:47 xend.XendDomainInfo] INFO (XendDomainInfo:219) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [2006-07-24 16:27:47 xend.XendDomainInfo] WARNING (XendDomainInfo:241) No vm path in store for existing domain 0 [2006-07-24 16:27:47 xend.XendDomainInfo] DEBUG (XendDomainInfo:701) Storing VM details: {'name': 'Domain-0', 'on_reboot': 'restart', 'on_poweroff': 'destroy', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_crash': 'restart', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '934', 'maxmem': '934'} [2006-07-24 16:27:47 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing domain details: {'cpu/0/availability': 'online', 'memory/target': '956416', 'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'} [2006-07-24 16:27:47 xend] DEBUG (XendDomain:153) number of vcpus to use is 0 [2006-07-24 16:27:47 xend.XendDomainInfo] DEBUG (XendDomainInfo:919) XendDomainInfo.handleShutdownWatch [2006-07-24 16:57:11 xend] INFO (SrvDaemon:283) Xend Daemon started [2006-07-24 16:57:11 xend] INFO (SrvDaemon:287) Xend changeset: unavailable . [2006-07-24 16:57:11 xend.XendDomainInfo] DEBUG (XendDomainInfo:207) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 29781387850L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 956048, 'maxmem_kb': 17179869180, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 1, 'blocked': 0}) [2006-07-24 16:57:11 xend.XendDomainInfo] INFO (XendDomainInfo:219) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [2006-07-24 16:57:11 xend.XendDomainInfo] WARNING (XendDomainInfo:241) No vm path in store for existing domain 0 [2006-07-24 16:57:11 xend.XendDomainInfo] DEBUG (XendDomainInfo:701) Storing VM details: {'name': 'Domain-0', 'on_reboot': 'restart', 'on_poweroff': 'destroy', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_crash': 'restart', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '934', 'maxmem': '934'} [2006-07-24 16:57:11 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing domain details: {'cpu/0/availability': 'online', 'memory/target': '956416', 'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'} [2006-07-24 16:57:11 xend] DEBUG (XendDomain:153) number of vcpus to use is 0 [2006-07-24 16:57:11 xend.XendDomainInfo] DEBUG (XendDomainInfo:919) XendDomainInfo.handleShutdownWatch From takebe_akio at jp.fujitsu.com Tue Jul 25 09:28:51 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Tue, 25 Jul 2006 18:28:51 +0900 Subject: [Fedora-xen] Re: [Fedora-ia64-list] Re: Four ways RH could help with xen-ia64 In-Reply-To: <1153578830.2461.13.camel@anano.mitica> References: <1153578830.2461.13.camel@anano.mitica> Message-ID: <48C6AFCCBDAB97takebe_akio@jp.fujitsu.com> Hi, Juan, Aron and all I fix Juan's http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora to build on ia64. But I have not booted linux kernel (not xen), and there are many compile warnings. I'm fixing the tree now. I used the attach config. Please check them. My fix patcheds are the blew. Please comments. 1. build_ia64_add_files.patch simple import gate.S, gate.ld.S, patch.c into arch/ia64/kernel (these are from linux-2.6.18-rc2) 2. build_ia64.patch some fix (resend_irq, ioremap, and so on) Signed-off-by: Akio Takebe Best Regards, Akio Takebe -------------- next part -------------- A non-text attachment was scrubbed... Name: build_patches.tar.bz2 Type: application/octet-stream Size: 26669 bytes Desc: not available URL: From aron at hp.com Tue Jul 25 16:07:46 2006 From: aron at hp.com (Aron Griffis) Date: Tue, 25 Jul 2006 12:07:46 -0400 Subject: [Fedora-xen] Re: Four ways RH could help with xen-ia64 In-Reply-To: <1153578830.2461.13.camel@anano.mitica> References: <20060722133124.GB12649@mustard> <1153578830.2461.13.camel@anano.mitica> Message-ID: <20060725160746.GA3851@vino.zko.hp.com> Juan Quintela wrote: [Sat Jul 22 2006, 10:33:50AM EDT] > > 1. Publish Juan's tree which is the result of his merge of > > linux-2.6.tip-xen, linux-2.6 and linux-2.6-xen. How about > > http://people.redhat.com/quintela/linux-2.6.tip-xen-fedora.hg? > > As things stand right now, it's very difficult for ia64 devs to > > contribute to Juan's patch, for 2 reasons: (1) we never see it > > until after a new kernel rpm is published, (2) all we get is the > > final result, lacking the extremely helpful changeset history. > > It is based on 2.6.18-rc2. It is on: > > http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora Thanks Juan, this is a huge help. > > 2. Use matched xenlinux/hypervisor pairs. At the OLS Xen mini-summit > > there was some discussion of compatibility. The statements were: > > Believe me that we _try_, and very hard. Thanks, that is good to know. Until now I hadn't heard a statement from RH regarding that. I posted a message a while back containing a method for absolutely matching the hypervisor to the kernel patch: https://www.redhat.com/archives/fedora-xen/2006-July/msg00024.html Is that approximately what you're doing now? > > - old domU should run on new hypervisor > > Agreed. I normally test plain fc5 domU on all my new kernels. > > > - new domU NOT guaranteed to run on old hypervisor > > We have found that lately this "normally" works, versus bugs. I'm sorry, your response confuses me here. :-( Just to be clear: These three bullet points I posted are the stated goals of Xen upstream. Fedora should assume that a new domU will NOT run on an old hypervisor, regardless of empirical evidence... > > - dom0 and hypervisor should be MATCHED > > Guess why HV on fedora is on the same package that the kernel, and they > have indeed the same version number? :-) Thanks, Aron From Patrick.Petit at Sun.COM Tue Jul 25 16:54:07 2006 From: Patrick.Petit at Sun.COM (Patrick Petit) Date: Tue, 25 Jul 2006 18:54:07 +0200 Subject: [Fedora-xen] trouble starting xend Message-ID: <44C64CAF.1070309@sun.com> Hi There, After upgrading from 'kernel-xen0-2.6.17-1.2139_FC5' to 'kernel-xen0-2.6.17-1.2157_FC5' I am seeing the following error when I start xend # uname -a Linux jesma55 2.6.17-1.2157_FC5xen0 #1 SMP Wed Jul 12 00:28:36 EDT 2006 i686 athlon i386 GNU/Linux # cat /var/log/xend.log [2006-07-25 16:29:50 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-25 16:49:49 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-25 16:49:49 xend] ERROR (SrvDaemon:299) Exception starting xend ((22, 'Invalid argument')) Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 288, in run xinfo = xc.xeninfo() error: (22, 'Invalid argument') [2006-07-25 16:49:49 xend] INFO (SrvDaemon:185) Xend exited with status 1. I use Python 2.4.2 Any help appreciated. Thanks - Patrick From swcodfather at gmail.com Tue Jul 25 17:06:57 2006 From: swcodfather at gmail.com (Nick) Date: Tue, 25 Jul 2006 18:06:57 +0100 Subject: [Fedora-xen] Problem installing a Domu instance with lastest FC5 kernel Message-ID: Hi, I have searched the mailist archives, and i have not found anything that directly addresses this issue. I'm using a Dell 360 workstation with 1 Gig of Ram. I have installed successfully the Domain_0 kernel 2.6.17-1.2157_FC5xen0, upgraded all packages and restarted the box with this new kernel. when I run xm list, it shows this domain running happily. I have built a guest OS install tree, with the new guest Domain_u kernel image, appropriate for this latest kernel. This tree exists on a separate server, and not on the intended xen server. I then type the following: /usr/sbin/xenguest-install.py What is the name of your virtual machine? nick How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /vmmachines/nick How large would you like the disk to be (in gigabytes)? 5 What is the install location? http://xxx.xxx.8.193:8000 I have reduced the amount of memory used by Domain_0 to allow for this 256meg Guest. I get this error message after typing in the networking details during the install. loader received SIGSEGV!. Backtrace: [0x8049865] [0x8047420] [0x8063ca0] [0x805e5e1] [0x804ad21] [0x80cae75] [0x8048131] install exited abnormally sending termination signals...done sending kill signals...done disabling swap... unmounting filesystems... /proc done /dev/pts done /sys done /tmp/ramfs done you may safely reboot your system rebooting system Restarting system. Does anyone have any suggestions on this one? Thanks in advance Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From anthony.xu at intel.com Wed Jul 26 09:30:49 2006 From: anthony.xu at intel.com (Xu, Anthony) Date: Wed, 26 Jul 2006 17:30:49 +0800 Subject: [Fedora-xen] RE: [Xen-ia64-devel] Re: [Fedora-ia64-list] Re: Four ways RH could helpwith xen-ia64 Message-ID: <01913ADC4FF97E40AE0E2B001574AEE12DBBDD@pdsmsx412.ccr.corp.intel.com> Hi Akio, Is this merge based on linux-2.6.18-rc2? When I diff linux-2.6-xen-fedora with linux-2.6.18-rc2, There are some modifications which are not marked by #ifdef CONFIG_XEN Thanks, Anthony >-----Original Message----- >From: xen-ia64-devel-bounces at lists.xensource.com >[mailto:xen-ia64-devel-bounces at lists.xensource.com] On Behalf Of Akio Takebe >Sent: 2006?7?25? 17:29 >To: ia64 Fedora Core Development; Aron Griffis; Juan Quintela >Cc: Chris Wright; xen-ia64-devel at lists.xensource.com; fedora-xen at redhat.com >Subject: [Xen-ia64-devel] Re: [Fedora-ia64-list] Re: Four ways RH could >helpwith xen-ia64 > >Hi, Juan, Aron and all > >I fix Juan's http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora >to build on ia64. >But I have not booted linux kernel (not xen), >and there are many compile warnings. >I'm fixing the tree now. > >I used the attach config. >Please check them. > >My fix patcheds are the blew. Please comments. >1. build_ia64_add_files.patch > simple import gate.S, gate.ld.S, patch.c into arch/ia64/kernel > (these are from linux-2.6.18-rc2) >2. build_ia64.patch > some fix (resend_irq, ioremap, and so on) > >Signed-off-by: Akio Takebe > >Best Regards, > >Akio Takebe From takebe_akio at jp.fujitsu.com Wed Jul 26 10:20:31 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Wed, 26 Jul 2006 19:20:31 +0900 Subject: [Fedora-xen] RE: [Xen-ia64-devel] Re: [Fedora-ia64-list] Re: Four ways RH could helpwith xen-ia64 In-Reply-To: <01913ADC4FF97E40AE0E2B001574AEE12DBBDD@pdsmsx412.ccr.corp.intel.com> References: <01913ADC4FF97E40AE0E2B001574AEE12DBBDD@pdsmsx412.ccr.corp.intel.com> Message-ID: <2CC6B09D1F7E33takebe_akio@jp.fujitsu.com> Hi, Anthony, Juan and Aron Hmm.. I don't know. I have thought that merge base is linux-2.6.18-rc2, because of reading the following mail. Juan and Aron, am I wrong? If necessary, I'll update my patches. My patches work good on RHEL4 as native linux. Now I'm updating my fedora system by yum. After update, I'll try my patches on FC6. ----- Juan's wrote ------------------------------ It is based on 2.6.18-rc2. It is on: http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora It is public only since Tuesday (I was waiting for a place where to publish it). Tree will not work on ia64, I didn't forward ported the ia64 changes, noly x86 & x86_64 (and it was painfull enough, time source, smp-alternatives x86_64, irqtrace, vDSO on x86 & friends meaned that I had to go back & re-apply series of patches one at a time to find a coulpe of bugs). ------------------------------------------------- Best Regards, Akio Takebe >Hi Akio, > >Is this merge based on linux-2.6.18-rc2? >When I diff linux-2.6-xen-fedora with linux-2.6.18-rc2, >There are some modifications which are not marked by #ifdef CONFIG_XEN > >Thanks, >Anthony > >>-----Original Message----- >>From: xen-ia64-devel-bounces at lists.xensource.com >>[mailto:xen-ia64-devel-bounces at lists.xensource.com] On Behalf Of Akio Takebe >>Sent: 2006?7?25? 17:29 >>To: ia64 Fedora Core Development; Aron Griffis; Juan Quintela >>Cc: Chris Wright; xen-ia64-devel at lists.xensource.com; fedora-xen at redhat.com >>Subject: [Xen-ia64-devel] Re: [Fedora-ia64-list] Re: Four ways RH could >>helpwith xen-ia64 >> >>Hi, Juan, Aron and all >> >>I fix Juan's http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora >>to build on ia64. >>But I have not booted linux kernel (not xen), >>and there are many compile warnings. >>I'm fixing the tree now. >> >>I used the attach config. >>Please check them. >> >>My fix patcheds are the blew. Please comments. >>1. build_ia64_add_files.patch >> simple import gate.S, gate.ld.S, patch.c into arch/ia64/kernel >> (these are from linux-2.6.18-rc2) >>2. build_ia64.patch >> some fix (resend_irq, ioremap, and so on) >> >>Signed-off-by: Akio Takebe >> >>Best Regards, >> >>Akio Takebe From takebe_akio at jp.fujitsu.com Wed Jul 26 10:31:25 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Wed, 26 Jul 2006 19:31:25 +0900 Subject: [Fedora-xen] RE: [Xen-ia64-devel] Re: [Fedora-ia64-list] Re: Four ways RH could helpwith xen-ia64 In-Reply-To: <2CC6B09D1F7E33takebe_akio@jp.fujitsu.com> References: <01913ADC4FF97E40AE0E2B001574AEE12DBBDD@pdsmsx412.ccr.corp.intel.com> <2CC6B09D1F7E33takebe_akio@jp.fujitsu.com> Message-ID: <2DC6B09EA56DACtakebe_akio@jp.fujitsu.com> Hi, Anthony I found the base version in Makefile. ----------------------------- VERSION = 2 PATCHLEVEL = 6 SUBLEVEL = 18 EXTRAVERSION = -rc2 NAME=Crazed Snow-Weasel # *DOCUMENTATION* # To see a list of typical targets execute "make help" # More info can be located in ./README # Comments in this file are [snip...] ----------------------------- Best Regards, Akio Takebe >Hi, Anthony, Juan and Aron > >Hmm.. I don't know. >I have thought that merge base is linux-2.6.18-rc2, >because of reading the following mail. >Juan and Aron, am I wrong? >If necessary, I'll update my patches. > >My patches work good on RHEL4 as native linux. >Now I'm updating my fedora system by yum. >After update, I'll try my patches on FC6. > >----- Juan's wrote ------------------------------ >It is based on 2.6.18-rc2. It is on: > >http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora > >It is public only since Tuesday (I was waiting for a place where to >publish it). Tree will not work on ia64, I didn't forward ported the >ia64 changes, noly x86 & x86_64 (and it was painfull enough, time >source, smp-alternatives x86_64, irqtrace, vDSO on x86 & friends meaned >that I had to go back & re-apply series of patches one at a time to find >a coulpe of bugs). >------------------------------------------------- > >Best Regards, > >Akio Takebe > >>Hi Akio, >> >>Is this merge based on linux-2.6.18-rc2? >>When I diff linux-2.6-xen-fedora with linux-2.6.18-rc2, >>There are some modifications which are not marked by #ifdef CONFIG_XEN >> >>Thanks, >>Anthony >> >>>-----Original Message----- >>>From: xen-ia64-devel-bounces at lists.xensource.com >>>[mailto:xen-ia64-devel-bounces at lists.xensource.com] On Behalf Of Akio >>>Takebe >>>Sent: 2006?7?25? 17:29 >>>To: ia64 Fedora Core Development; Aron Griffis; Juan Quintela >>>Cc: Chris Wright; xen-ia64-devel at lists.xensource.com; fedora-xen at redhat.com >>>Subject: [Xen-ia64-devel] Re: [Fedora-ia64-list] Re: Four ways RH could >>>helpwith xen-ia64 >>> >>>Hi, Juan, Aron and all >>> >>>I fix Juan's http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora >>>to build on ia64. >>>But I have not booted linux kernel (not xen), >>>and there are many compile warnings. >>>I'm fixing the tree now. >>> >>>I used the attach config. >>>Please check them. >>> >>>My fix patcheds are the blew. Please comments. >>>1. build_ia64_add_files.patch >>> simple import gate.S, gate.ld.S, patch.c into arch/ia64/kernel >>> (these are from linux-2.6.18-rc2) >>>2. build_ia64.patch >>> some fix (resend_irq, ioremap, and so on) >>> >>>Signed-off-by: Akio Takebe >>> >>>Best Regards, >>> >>>Akio Takebe From quintela at redhat.com Wed Jul 26 10:35:23 2006 From: quintela at redhat.com (Juan Quintela) Date: Wed, 26 Jul 2006 12:35:23 +0200 Subject: [Fedora-xen] RE: [Xen-ia64-devel] Re: [Fedora-ia64-list] Re: Four ways RH could helpwith xen-ia64 In-Reply-To: <01913ADC4FF97E40AE0E2B001574AEE12DBBDD@pdsmsx412.ccr.corp.intel.com> References: <01913ADC4FF97E40AE0E2B001574AEE12DBBDD@pdsmsx412.ccr.corp.intel.com> Message-ID: <1153910124.2508.10.camel@anano.mitica> On Wed, 2006-07-26 at 17:30 +0800, Xu, Anthony wrote: > Hi Akio, > > Is this merge based on linux-2.6.18-rc2? > When I diff linux-2.6-xen-fedora with linux-2.6.18-rc2, > There are some modifications which are not marked by #ifdef CONFIG_XEN Hi There are several changes not marked as CONFIG_XEN: * tsc timer -> fixed since them with other solution * TPM -> don't ask me, tpm code is evil. And to make things more interesting xen code & linux upstream code has diverged so much that it is not funny. * things marked CONFIG_X86_NO_TSS & CONFIG_X86_NO_IDT (already on unstable tree) * anything that touchs a Task segment is disabled by default (already on unstable tree) * HAVE_SHARED_KERNEL_PMD changes, already on unstable tree * some patches to oprofile to make xenoprof work. * __FIXADDR_TOP already on xen unstable, and more things with vDSO integration. I haven't really examined neither i64 or powerpec bits. If you have any concern about any particular piece of code, please, let me know. Later, Juan. From takebe_akio at jp.fujitsu.com Tue Jul 25 08:58:16 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Tue, 25 Jul 2006 17:58:16 +0900 Subject: [Fedora-xen] Re: [Fedora-ia64-list] Re: Four ways RH could help with xen-ia64 In-Reply-To: <1153578830.2461.13.camel@anano.mitica> References: <1153578830.2461.13.camel@anano.mitica> Message-ID: <47C6AFC877DAB0takebe_akio@jp.fujitsu.com> Hi, Juan, Aron and all I fix Juan's http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora to build on ia64. But I have not booted linux kernel (not xen), and there are many compile warnings. I'm fixing the tree now. I used the attach config. Please check them. My fix patcheds are the blew. Please comments. 1. build_ia64_add_files.patch simple import gate.S, gate.ld.S, patch.c into arch/ia64/kernel (these are from linux-2.6.18-rc2) 2. build_ia64.patch some fix (resend_irq, ioremap, and so on) Signed-off-by: Akio Takebe Best Regards, Akio Takebe >On Sat, 2006-07-22 at 09:31 -0400, Aron Griffis wrote: >> Hi guys, >> >> There are four ways you could be a big help to the xen-ia64 effort. >> I have mentioned these in the past but never pulled them together into >> a single request. > >Sorry for getting so long in answering you, but A PAE bug and getting >linux-2.6-xen working on 2.6.18-rc2 have required all my attention :( > >> 1. Publish Juan's tree which is the result of his merge of >> linux-2.6.tip-xen, linux-2.6 and linux-2.6-xen. How about >> http://people.redhat.com/quintela/linux-2.6.tip-xen-fedora.hg? >> As things stand right now, it's very difficult for ia64 devs to >> contribute to Juan's patch, for 2 reasons: (1) we never see it >> until after a new kernel rpm is published, (2) all we get is the >> final result, lacking the extremely helpful changeset history. > >It is based on 2.6.18-rc2. It is on: > >http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora > >It is public only since Tuesday (I was waiting for a place where to >publish it). Tree will not work on ia64, I didn't forward ported the >ia64 changes, noly x86 & x86_64 (and it was painfull enough, time >source, smp-alternatives x86_64, irqtrace, vDSO on x86 & friends meaned >that I had to go back & re-apply series of patches one at a time to find >a coulpe of bugs). > >> 2. Use matched xenlinux/hypervisor pairs. At the OLS Xen mini-summit >> there was some discussion of compatibility. The statements were: > >Believe me that we _try_, and very hard. > >> - old domU should run on new hypervisor > >Agreed. I normally test plain fc5 domU on all my new kernels. > >> - new domU NOT guaranteed to run on old hypervisor > >We have found that lately this "normally" works, versus bugs. > >> - dom0 and hypervisor should be MATCHED > >Guess why HV on fedora is on the same package that the kernel, and they >have indeed the same version number? > >> Presently (kernel-2.6.17-1.2432.fc6.src.rpm) it appears that the >> hypervisor and xen patch are both dated 20060719. That's a good >> sign! :-) It would be great if you could provide some indication >> of your intent to continue using matched pairs. Are they actually >> based on the same xen-unstable changeset? We, the users, can't >> tell because the tarball is dated instead of cset-stamped, and >> Juan's tree isn't available. See #1 ;-) > >Normally I add cset numbers in the changelog, but will try to put them >into the HV version number (it maks as much sense as the date, >actually). > >About the source tree, it is already public. It hasn't been published >sooner due to lack of somobdy setting up a server. Now it is done. > >> 3. Apply my kernel.spec and config changes at the end of this email. >> This would make it much easier for the ia64 developers to do test >> builds and track down failures. Presently it's a pain for me to >> maintain this out of tree. > >Will do today. Will send one email once this is done. > >> 4. Apply the xen.spec and libvirt.spec changes. >> https://www.redhat.com/archives/fedora-xen/2006-July/msg00022.html >> https://www.redhat.com/archives/fedora-xen/2006-July/msg00021.html >> >> Regarding libvirt.spec, I've talked with Daniel and he's just >> waiting for xen.spec to be ia64-enabled... > >Will talk with daniel when he is back from OLS. > >> Objections/comments? I'll attempt to update any relevant BZs today. > >Will comment on the patches in a follow-up. > >Later, Juan. > >-- >Fedora-ia64-list mailing list >Fedora-ia64-list at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-ia64-list -------------- next part -------------- A non-text attachment was scrubbed... Name: kernel-2.6.18-rc2_ia64.config Type: application/octet-stream Size: 55871 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: kernel-2.6.18-rc2_xen_ia64.config Type: application/octet-stream Size: 55953 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: build_ia64_add_files.patch Type: application/octet-stream Size: 20986 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: build_ia64.patch Type: application/octet-stream Size: 3279 bytes Desc: not available URL: From patraylo at unity.ncsu.edu Tue Jul 25 16:04:34 2006 From: patraylo at unity.ncsu.edu (Paul Traylor) Date: Tue, 25 Jul 2006 12:04:34 -0400 Subject: [Fedora-xen] Xen high memory usage/X programs running poorly Message-ID: <44C64112.1060309@unity.ncsu.edu> 'xm top' shows Dom0 to be using 2846916k of memory (about 90.5 %) 'free -k' shows Dom0 to be using 447192k of memory 'uname -r' shows 2.6.17-1.2157_FC5xen0 X programs running over ssh are extremely slow (such as http://virt-manager.et.redhat.com/ and http://xenman.sourceforge.net/) to the point where they are mostly unusable. When using the non-xen kernel, X programs seem to run fine over ssh. I did a standard install of FC5. I changed the size of / to 20gb so that I could create other LV for the domUs. I installed the basic webserver package to start off with. I installed http://webmin.com/ to make it easier to configure the iptables, and switched ssh to use a different port. I then ran 'yum update' and disabled SELinux by editing /etc/selinux/config and setting SELINUX=disabled. Lastly, I set 'DEFAULTKERNEL=kernel-xen0' in /etc/sysconfig/kernel and installed the xen kernel with 'yum install kernel-xen0' as directed by http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 and rebooted. Am I missing something that is causing memory usage to be so high and causing X programs to run so poorly? Paul Traylor From prarit at redhat.com Wed Jul 26 11:14:11 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Wed, 26 Jul 2006 07:14:11 -0400 Subject: [Fedora-xen] Re: [Xen-ia64-devel] Re: [Fedora-ia64-list] Re: Four ways RH could helpwith xen-ia64 In-Reply-To: <1153910124.2508.10.camel@anano.mitica> References: <01913ADC4FF97E40AE0E2B001574AEE12DBBDD@pdsmsx412.ccr.corp.intel.com> <1153910124.2508.10.camel@anano.mitica> Message-ID: <44C74E83.7060807@redhat.com> Juan Quintela wrote: > On Wed, 2006-07-26 at 17:30 +0800, Xu, Anthony wrote: > >> Hi Akio, >> >> Is this merge based on linux-2.6.18-rc2? >> When I diff linux-2.6-xen-fedora with linux-2.6.18-rc2, >> There are some modifications which are not marked by #ifdef CONFIG_XEN >> > > Let's not push this into linux-2.6-xen-fedora. We've been working with a patch in BZ 199684 which includes many of these changes. That patch, hopefully, will be submitted today at some point. Status is even after applying the patch the Xen kernels do not boot. The non-Xen kernels do boot. P. > Hi > > There are several changes not marked as CONFIG_XEN: > > * tsc timer -> fixed since them with other solution > * TPM -> don't ask me, tpm code is evil. And to make things more > interesting xen code & linux upstream code has diverged so much that it > is not funny. > * things marked CONFIG_X86_NO_TSS & CONFIG_X86_NO_IDT (already on > unstable tree) > * anything that touchs a Task segment is disabled by default (already on > unstable tree) > * HAVE_SHARED_KERNEL_PMD changes, already on unstable tree > * some patches to oprofile to make xenoprof work. > * __FIXADDR_TOP already on xen unstable, and more things with vDSO > integration. > > I haven't really examined neither i64 or powerpec bits. > > If you have any concern about any particular piece of code, please, let > me know. > > Later, Juan. > > -- > Fedora-ia64-list mailing list > Fedora-ia64-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-ia64-list > > From aron at hp.com Wed Jul 26 13:00:19 2006 From: aron at hp.com (Aron Griffis) Date: Wed, 26 Jul 2006 09:00:19 -0400 Subject: [Fedora-xen] Re: [Xen-ia64-devel] Re: [Fedora-ia64-list] Re: Four ways RH could helpwith xen-ia64 In-Reply-To: <30C6B0ACC956EDtakebe_akio@jp.fujitsu.com> References: <01913ADC4FF97E40AE0E2B001574AEE12DBBDD@pdsmsx412.ccr.corp.intel.com> <2CC6B09D1F7E33takebe_akio@jp.fujitsu.com> <44C74CB9.3010209@redhat.com> <30C6B0ACC956EDtakebe_akio@jp.fujitsu.com> Message-ID: <20060726130019.GA16091@mustard.flatmonk> Akio Takebe wrote: [Wed Jul 26 2006, 08:12:38AM EDT] > Thank you for your reply. > I'm still a little confused about the way of FC6-xen/IPF contribution. I'm sorry, I know that it's confusing. There are multiple ways to work on the kernel tree. I'll try to provide some steps below. > I'd like to make sure the way. > > - Background > > we need to try this tree > http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora > Because #1's tree is not work on xen-ia64. > we need to try compile and build the tree > with the latest patche of BZ#199684. That's essentially correct. The tree above is used to generate the linux-2.6-xen.patch which is used in the Fedora rpm. If we make that tree work with the Fedora ia64 config, and the Fedora xen-ia64 config, then everything should work well. Here is another approach, though, which moves us closer to the final product. The Fedora kernel cvs tree is available via instructions from http://people.redhat.com/davej/ I took that tree and imported it to mercurial. The result is http://free.linux.hp.com/~agriffis/kernel-cvs/ Next I cloned that tree, added the bugzilla 199684 patch (which includes your work), plus the minor kernel-2.6.spec modifications and created another mercurial tree which is http://free.linux.hp.com/~agriffis/kernel-cvs-ia64/ So the final result is that you can: hg clone http://free.linux.hp.com/~agriffis/kernel-cvs-ia64/ cd kernel-cvs-ia64/devel make ia64 This will build an ia64 kernel and attempt to build a xen kernel. Watch it break, figure it out, contribute to the patch, send back a diff! I hope that helps. Thanks for your assistance. Regards, Aron From prarit at redhat.com Wed Jul 26 13:18:01 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Wed, 26 Jul 2006 09:18:01 -0400 Subject: [Fedora-xen] Re: [Xen-ia64-devel] Re: [Fedora-ia64-list] Re: Four ways RH could helpwith xen-ia64 In-Reply-To: <20060726130019.GA16091@mustard.flatmonk> References: <01913ADC4FF97E40AE0E2B001574AEE12DBBDD@pdsmsx412.ccr.corp.intel.com> <2CC6B09D1F7E33takebe_akio@jp.fujitsu.com> <44C74CB9.3010209@redhat.com> <30C6B0ACC956EDtakebe_akio@jp.fujitsu.com> <20060726130019.GA16091@mustard.flatmonk> Message-ID: <44C76B89.70803@redhat.com> > So the final result is that you can: > > hg clone http://free.linux.hp.com/~agriffis/kernel-cvs-ia64/ > cd kernel-cvs-ia64/devel > make ia64 > > This will build an ia64 kernel and attempt to build a xen kernel. > Watch it break, figure it out, contribute to the patch, send back > a diff! > > > Everyone once-in-a-while we will also be updating the BZ with an updated "known good" patch. P. From takebe_akio at jp.fujitsu.com Wed Jul 26 15:28:08 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Thu, 27 Jul 2006 00:28:08 +0900 Subject: [Fedora-xen] Re: [Xen-ia64-devel] Re: [Fedora-ia64-list] Re: Four ways RH could helpwith xen-ia64 In-Reply-To: <20060726130019.GA16091@mustard.flatmonk> References: <2CC6B09D1F7E33takebe_akio@jp.fujitsu.com> <44C74CB9.3010209@redhat.com> <30C6B0ACC956EDtakebe_akio@jp.fujitsu.com> <20060726130019.GA16091@mustard.flatmonk> Message-ID: <31C6B0C8191AA6takebe_akio@jp.fujitsu.com> Hi, Aron and Prarit Thank you for your explanation. I confused bacause there are some tree. But I'm clear now. Thanks again. I'll work on http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora by using BZ 199684 patch. I have two other question. Where from is the above tree? xen-unstable? xen-ia64-unstble? And which cset is the above tree base on? I don't know which xen I should use. Best Regards, Akio Takebe >Akio Takebe wrote: [Wed Jul 26 2006, 08:12:38AM EDT] >> Thank you for your reply. >> I'm still a little confused about the way of FC6-xen/IPF contribution. > >I'm sorry, I know that it's confusing. There are multiple ways to >work on the kernel tree. I'll try to provide some steps below. > >> I'd like to make sure the way. >> >> - Background >> >> we need to try this tree >> http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora >> Because #1's tree is not work on xen-ia64. >> we need to try compile and build the tree >> with the latest patche of BZ#199684. > >That's essentially correct. The tree above is used to generate the >linux-2.6-xen.patch which is used in the Fedora rpm. If we make that >tree work with the Fedora ia64 config, and the Fedora xen-ia64 config, >then everything should work well. > >Here is another approach, though, which moves us closer to the final >product. The Fedora kernel cvs tree is available via instructions >from http://people.redhat.com/davej/ > >I took that tree and imported it to mercurial. The result is >http://free.linux.hp.com/~agriffis/kernel-cvs/ > >Next I cloned that tree, added the bugzilla 199684 patch (which >includes your work), plus the minor kernel-2.6.spec modifications and >created another mercurial tree which is >http://free.linux.hp.com/~agriffis/kernel-cvs-ia64/ > >So the final result is that you can: > > hg clone http://free.linux.hp.com/~agriffis/kernel-cvs-ia64/ > cd kernel-cvs-ia64/devel > make ia64 > >This will build an ia64 kernel and attempt to build a xen kernel. >Watch it break, figure it out, contribute to the patch, send back >a diff! > >I hope that helps. Thanks for your assistance. > >Regards, >Aron From quintela at redhat.com Wed Jul 26 16:27:17 2006 From: quintela at redhat.com (Juan Quintela) Date: Wed, 26 Jul 2006 18:27:17 +0200 Subject: [Fedora-xen] Re: [Xen-ia64-devel] Re: [Fedora-ia64-list] Re: Four ways RH could helpwith xen-ia64 In-Reply-To: <31C6B0C8191AA6takebe_akio@jp.fujitsu.com> References: <2CC6B09D1F7E33takebe_akio@jp.fujitsu.com> <44C74CB9.3010209@redhat.com> <30C6B0ACC956EDtakebe_akio@jp.fujitsu.com> <20060726130019.GA16091@mustard.flatmonk> <31C6B0C8191AA6takebe_akio@jp.fujitsu.com> Message-ID: <1153931237.2508.28.camel@anano.mitica> On Thu, 2006-07-27 at 00:28 +0900, Akio Takebe wrote: > Hi, Aron and Prarit > > Thank you for your explanation. > I confused bacause there are some tree. > > But I'm clear now. Thanks again. > I'll work on http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora > by using BZ 199684 patch. > > I have two other question. > Where from is the above tree? xen-unstable? xen-ia64-unstble? It comes from linux-2.6-xen (this follows xen-unstable with 1-2 days lag), and linux-2.6 (plain linus 2.6 tree). It gets updated daily. Actual changesets are: [quintela at anano linux-2.6]$ hg tip changeset: 33089:93feac10afde [quintela at anano linux-2.6-xen]$ hg tip -v changeset: 22749:d195197a6bed14f372d4526917d4476a30f299d6 xen-unstable changeset: 10731:77ec02027c17714124935612f1b3cb52fec3f436 > And which cset is the above tree base on? It don't have any ia64 specific bits still. I received a mail from you (i.e. Aiko) with two patches and anther from Prarit telling me to wait before I apply the patches. I am having a _big_ execshield problem on x86, once that is finished (I hope Thrusday/Friday) I will take a look at compiling the tree on ia64 box (already got access to one box, thanks Prarit). Later, Juan. From aron at hp.com Thu Jul 27 04:10:58 2006 From: aron at hp.com (Aron Griffis) Date: Thu, 27 Jul 2006 00:10:58 -0400 Subject: [Fedora-xen] [PATCH 4 of 5] Export some additional symbols needed for forward port to 2.6.18 In-Reply-To: Message-ID: <5602e37817d5712662b8.1153973458@vino.zko.hp.com> 1 file changed, 4 insertions(+) arch/ia64/xen/hypervisor.c | 4 ++++ # HG changeset patch # User agriffis at cheo.zko.hp.com # Node ID 5602e37817d5712662b8240b5efa16a9c847c032 # Parent 8de5c39ac1ef23a8c257fd02186d9810f9c358c5 Export some additional symbols needed for forward port to 2.6.18 Signed-off-by: Aron Griffis diff -r 8de5c39ac1ef -r 5602e37817d5 arch/ia64/xen/hypervisor.c --- a/arch/ia64/xen/hypervisor.c Thu Jul 27 00:09:59 2006 -0400 +++ b/arch/ia64/xen/hypervisor.c Thu Jul 27 00:10:03 2006 -0400 @@ -35,6 +35,7 @@ EXPORT_SYMBOL(HYPERVISOR_shared_info); EXPORT_SYMBOL(HYPERVISOR_shared_info); start_info_t *xen_start_info; +EXPORT_SYMBOL(xen_start_info); int running_on_xen; EXPORT_SYMBOL(running_on_xen); @@ -91,6 +92,7 @@ ia64_xenmem_reservation_op(unsigned long } return ret; } +EXPORT_SYMBOL(ia64_xenmem_reservation_op); //XXX same as i386, x86_64 contiguous_bitmap_set(), contiguous_bitmap_clear() // move those to lib/contiguous_bitmap? @@ -379,12 +381,14 @@ HYPERVISOR_grant_table_op(unsigned int c return ____HYPERVISOR_grant_table_op(cmd, uop, count); } +EXPORT_SYMBOL(HYPERVISOR_grant_table_op); /////////////////////////////////////////////////////////////////////////// // PageForeign(), SetPageForeign(), ClearPageForeign() struct address_space xen_ia64_foreign_dummy_mapping; +EXPORT_SYMBOL(xen_ia64_foreign_dummy_mapping); /////////////////////////////////////////////////////////////////////////// // foreign mapping From aron at hp.com Thu Jul 27 04:10:55 2006 From: aron at hp.com (Aron Griffis) Date: Thu, 27 Jul 2006 00:10:55 -0400 Subject: [Fedora-xen] [PATCH 1 of 5] Add files which went lost in a merge goof In-Reply-To: Message-ID: <489de0be169cc96a4110.1153973455@vino.zko.hp.com> 3 files changed, 669 insertions(+) arch/ia64/kernel/gate.S | 376 +++++++++++++++++++++++++++++++++++++++++++ arch/ia64/kernel/gate.lds.S | 96 ++++++++++ arch/ia64/kernel/patch.c | 197 ++++++++++++++++++++++ # HG changeset patch # User agriffis at cheo.zko.hp.com # Node ID 489de0be169cc96a41105f8cb9046be740a9a706 # Parent 61b9455653982d901cac92052c30099eeffddd39 Add files which went lost in a merge goof Signed-off-by: Aron Griffis diff -r 61b945565398 -r 489de0be169c arch/ia64/kernel/gate.S --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/arch/ia64/kernel/gate.S Thu Jul 27 00:09:52 2006 -0400 @@ -0,0 +1,376 @@ +/* + * This file contains the code that gets mapped at the upper end of each task's text + * region. For now, it contains the signal trampoline code only. + * + * Copyright (C) 1999-2003 Hewlett-Packard Co + * David Mosberger-Tang + */ + +#include + +#include +#include +#include +#include +#include +#include + +/* + * We can't easily refer to symbols inside the kernel. To avoid full runtime relocation, + * complications with the linker (which likes to create PLT stubs for branches + * to targets outside the shared object) and to avoid multi-phase kernel builds, we + * simply create minimalistic "patch lists" in special ELF sections. + */ + .section ".data.patch.fsyscall_table", "a" + .previous +#define LOAD_FSYSCALL_TABLE(reg) \ +[1:] movl reg=0; \ + .xdata4 ".data.patch.fsyscall_table", 1b-. + + .section ".data.patch.brl_fsys_bubble_down", "a" + .previous +#define BRL_COND_FSYS_BUBBLE_DOWN(pr) \ +[1:](pr)brl.cond.sptk 0; \ + .xdata4 ".data.patch.brl_fsys_bubble_down", 1b-. + +GLOBAL_ENTRY(__kernel_syscall_via_break) + .prologue + .altrp b6 + .body + /* + * Note: for (fast) syscall restart to work, the break instruction must be + * the first one in the bundle addressed by syscall_via_break. + */ +{ .mib + break 0x100000 + nop.i 0 + br.ret.sptk.many b6 +} +END(__kernel_syscall_via_break) + +/* + * On entry: + * r11 = saved ar.pfs + * r15 = system call # + * b0 = saved return address + * b6 = return address + * On exit: + * r11 = saved ar.pfs + * r15 = system call # + * b0 = saved return address + * all other "scratch" registers: undefined + * all "preserved" registers: same as on entry + */ + +GLOBAL_ENTRY(__kernel_syscall_via_epc) + .prologue + .altrp b6 + .body +{ + /* + * Note: the kernel cannot assume that the first two instructions in this + * bundle get executed. The remaining code must be safe even if + * they do not get executed. + */ + adds r17=-1024,r15 // A + mov r10=0 // A default to successful syscall execution + epc // B causes split-issue +} + ;; + rsm psr.be | psr.i // M2 (5 cyc to srlz.d) + LOAD_FSYSCALL_TABLE(r14) // X + ;; + mov r16=IA64_KR(CURRENT) // M2 (12 cyc) + shladd r18=r17,3,r14 // A + mov r19=NR_syscalls-1 // A + ;; + lfetch [r18] // M0|1 + mov r29=psr // M2 (12 cyc) + // If r17 is a NaT, p6 will be zero + cmp.geu p6,p7=r19,r17 // A (sysnr > 0 && sysnr < 1024+NR_syscalls)? + ;; + mov r21=ar.fpsr // M2 (12 cyc) + tnat.nz p10,p9=r15 // I0 + mov.i r26=ar.pfs // I0 (would stall anyhow due to srlz.d...) + ;; + srlz.d // M0 (forces split-issue) ensure PSR.BE==0 +(p6) ld8 r18=[r18] // M0|1 + nop.i 0 + ;; + nop.m 0 +(p6) tbit.z.unc p8,p0=r18,0 // I0 (dual-issues with "mov b7=r18"!) + nop.i 0 + ;; +(p8) ssm psr.i +(p6) mov b7=r18 // I0 +(p8) br.dptk.many b7 // B + + mov r27=ar.rsc // M2 (12 cyc) +/* + * brl.cond doesn't work as intended because the linker would convert this branch + * into a branch to a PLT. Perhaps there will be a way to avoid this with some + * future version of the linker. In the meantime, we just use an indirect branch + * instead. + */ +#ifdef CONFIG_ITANIUM +(p6) add r14=-8,r14 // r14 <- addr of fsys_bubble_down entry + ;; +(p6) ld8 r14=[r14] // r14 <- fsys_bubble_down + ;; +(p6) mov b7=r14 +(p6) br.sptk.many b7 +#else + BRL_COND_FSYS_BUBBLE_DOWN(p6) +#endif + ssm psr.i + mov r10=-1 +(p10) mov r8=EINVAL +(p9) mov r8=ENOSYS + FSYS_RETURN +END(__kernel_syscall_via_epc) + +# define ARG0_OFF (16 + IA64_SIGFRAME_ARG0_OFFSET) +# define ARG1_OFF (16 + IA64_SIGFRAME_ARG1_OFFSET) +# define ARG2_OFF (16 + IA64_SIGFRAME_ARG2_OFFSET) +# define SIGHANDLER_OFF (16 + IA64_SIGFRAME_HANDLER_OFFSET) +# define SIGCONTEXT_OFF (16 + IA64_SIGFRAME_SIGCONTEXT_OFFSET) + +# define FLAGS_OFF IA64_SIGCONTEXT_FLAGS_OFFSET +# define CFM_OFF IA64_SIGCONTEXT_CFM_OFFSET +# define FR6_OFF IA64_SIGCONTEXT_FR6_OFFSET +# define BSP_OFF IA64_SIGCONTEXT_AR_BSP_OFFSET +# define RNAT_OFF IA64_SIGCONTEXT_AR_RNAT_OFFSET +# define UNAT_OFF IA64_SIGCONTEXT_AR_UNAT_OFFSET +# define FPSR_OFF IA64_SIGCONTEXT_AR_FPSR_OFFSET +# define PR_OFF IA64_SIGCONTEXT_PR_OFFSET +# define RP_OFF IA64_SIGCONTEXT_IP_OFFSET +# define SP_OFF IA64_SIGCONTEXT_R12_OFFSET +# define RBS_BASE_OFF IA64_SIGCONTEXT_RBS_BASE_OFFSET +# define LOADRS_OFF IA64_SIGCONTEXT_LOADRS_OFFSET +# define base0 r2 +# define base1 r3 + /* + * When we get here, the memory stack looks like this: + * + * +===============================+ + * | | + * // struct sigframe // + * | | + * +-------------------------------+ <-- sp+16 + * | 16 byte of scratch | + * | space | + * +-------------------------------+ <-- sp + * + * The register stack looks _exactly_ the way it looked at the time the signal + * occurred. In other words, we're treading on a potential mine-field: each + * incoming general register may be a NaT value (including sp, in which case the + * process ends up dying with a SIGSEGV). + * + * The first thing need to do is a cover to get the registers onto the backing + * store. Once that is done, we invoke the signal handler which may modify some + * of the machine state. After returning from the signal handler, we return + * control to the previous context by executing a sigreturn system call. A signal + * handler may call the rt_sigreturn() function to directly return to a given + * sigcontext. However, the user-level sigreturn() needs to do much more than + * calling the rt_sigreturn() system call as it needs to unwind the stack to + * restore preserved registers that may have been saved on the signal handler's + * call stack. + */ + +#define SIGTRAMP_SAVES \ + .unwabi 3, 's'; /* mark this as a sigtramp handler (saves scratch regs) */ \ + .unwabi @svr4, 's'; /* backwards compatibility with old unwinders (remove in v2.7) */ \ + .savesp ar.unat, UNAT_OFF+SIGCONTEXT_OFF; \ + .savesp ar.fpsr, FPSR_OFF+SIGCONTEXT_OFF; \ + .savesp pr, PR_OFF+SIGCONTEXT_OFF; \ + .savesp rp, RP_OFF+SIGCONTEXT_OFF; \ + .savesp ar.pfs, CFM_OFF+SIGCONTEXT_OFF; \ + .vframesp SP_OFF+SIGCONTEXT_OFF + +GLOBAL_ENTRY(__kernel_sigtramp) + // describe the state that is active when we get here: + .prologue + SIGTRAMP_SAVES + .body + + .label_state 1 + + adds base0=SIGHANDLER_OFF,sp + adds base1=RBS_BASE_OFF+SIGCONTEXT_OFF,sp + br.call.sptk.many rp=1f +1: + ld8 r17=[base0],(ARG0_OFF-SIGHANDLER_OFF) // get pointer to signal handler's plabel + ld8 r15=[base1] // get address of new RBS base (or NULL) + cover // push args in interrupted frame onto backing store + ;; + cmp.ne p1,p0=r15,r0 // do we need to switch rbs? (note: pr is saved by kernel) + mov.m r9=ar.bsp // fetch ar.bsp + .spillsp.p p1, ar.rnat, RNAT_OFF+SIGCONTEXT_OFF +(p1) br.cond.spnt setup_rbs // yup -> (clobbers p8, r14-r16, and r18-r20) +back_from_setup_rbs: + alloc r8=ar.pfs,0,0,3,0 + ld8 out0=[base0],16 // load arg0 (signum) + adds base1=(ARG1_OFF-(RBS_BASE_OFF+SIGCONTEXT_OFF)),base1 + ;; + ld8 out1=[base1] // load arg1 (siginfop) + ld8 r10=[r17],8 // get signal handler entry point + ;; + ld8 out2=[base0] // load arg2 (sigcontextp) + ld8 gp=[r17] // get signal handler's global pointer + adds base0=(BSP_OFF+SIGCONTEXT_OFF),sp + ;; + .spillsp ar.bsp, BSP_OFF+SIGCONTEXT_OFF + st8 [base0]=r9 // save sc_ar_bsp + adds base0=(FR6_OFF+SIGCONTEXT_OFF),sp + adds base1=(FR6_OFF+16+SIGCONTEXT_OFF),sp + ;; + stf.spill [base0]=f6,32 + stf.spill [base1]=f7,32 + ;; + stf.spill [base0]=f8,32 + stf.spill [base1]=f9,32 + mov b6=r10 + ;; + stf.spill [base0]=f10,32 + stf.spill [base1]=f11,32 + ;; + stf.spill [base0]=f12,32 + stf.spill [base1]=f13,32 + ;; + stf.spill [base0]=f14,32 + stf.spill [base1]=f15,32 + br.call.sptk.many rp=b6 // call the signal handler +.ret0: adds base0=(BSP_OFF+SIGCONTEXT_OFF),sp + ;; + ld8 r15=[base0] // fetch sc_ar_bsp + mov r14=ar.bsp + ;; + cmp.ne p1,p0=r14,r15 // do we need to restore the rbs? +(p1) br.cond.spnt restore_rbs // yup -> (clobbers r14-r18, f6 & f7) + ;; +back_from_restore_rbs: + adds base0=(FR6_OFF+SIGCONTEXT_OFF),sp + adds base1=(FR6_OFF+16+SIGCONTEXT_OFF),sp + ;; + ldf.fill f6=[base0],32 + ldf.fill f7=[base1],32 + ;; + ldf.fill f8=[base0],32 + ldf.fill f9=[base1],32 + ;; + ldf.fill f10=[base0],32 + ldf.fill f11=[base1],32 + ;; + ldf.fill f12=[base0],32 + ldf.fill f13=[base1],32 + ;; + ldf.fill f14=[base0],32 + ldf.fill f15=[base1],32 + mov r15=__NR_rt_sigreturn + .restore sp // pop .prologue + break __BREAK_SYSCALL + + .prologue + SIGTRAMP_SAVES +setup_rbs: + mov ar.rsc=0 // put RSE into enforced lazy mode + ;; + .save ar.rnat, r19 + mov r19=ar.rnat // save RNaT before switching backing store area + adds r14=(RNAT_OFF+SIGCONTEXT_OFF),sp + + mov r18=ar.bspstore + mov ar.bspstore=r15 // switch over to new register backing store area + ;; + + .spillsp ar.rnat, RNAT_OFF+SIGCONTEXT_OFF + st8 [r14]=r19 // save sc_ar_rnat + .body + mov.m r16=ar.bsp // sc_loadrs <- (new bsp - new bspstore) << 16 + adds r14=(LOADRS_OFF+SIGCONTEXT_OFF),sp + ;; + invala + sub r15=r16,r15 + extr.u r20=r18,3,6 + ;; + mov ar.rsc=0xf // set RSE into eager mode, pl 3 + cmp.eq p8,p0=63,r20 + shl r15=r15,16 + ;; + st8 [r14]=r15 // save sc_loadrs +(p8) st8 [r18]=r19 // if bspstore points at RNaT slot, store RNaT there now + .restore sp // pop .prologue + br.cond.sptk back_from_setup_rbs + + .prologue + SIGTRAMP_SAVES + .spillsp ar.rnat, RNAT_OFF+SIGCONTEXT_OFF + .body +restore_rbs: + // On input: + // r14 = bsp1 (bsp at the time of return from signal handler) + // r15 = bsp0 (bsp at the time the signal occurred) + // + // Here, we need to calculate bspstore0, the value that ar.bspstore needs + // to be set to, based on bsp0 and the size of the dirty partition on + // the alternate stack (sc_loadrs >> 16). This can be done with the + // following algorithm: + // + // bspstore0 = rse_skip_regs(bsp0, -rse_num_regs(bsp1 - (loadrs >> 19), bsp1)); + // + // This is what the code below does. + // + alloc r2=ar.pfs,0,0,0,0 // alloc null frame + adds r16=(LOADRS_OFF+SIGCONTEXT_OFF),sp + adds r18=(RNAT_OFF+SIGCONTEXT_OFF),sp + ;; + ld8 r17=[r16] + ld8 r16=[r18] // get new rnat + extr.u r18=r15,3,6 // r18 <- rse_slot_num(bsp0) + ;; + mov ar.rsc=r17 // put RSE into enforced lazy mode + shr.u r17=r17,16 + ;; + sub r14=r14,r17 // r14 (bspstore1) <- bsp1 - (sc_loadrs >> 16) + shr.u r17=r17,3 // r17 <- (sc_loadrs >> 19) + ;; + loadrs // restore dirty partition + extr.u r14=r14,3,6 // r14 <- rse_slot_num(bspstore1) + ;; + add r14=r14,r17 // r14 <- rse_slot_num(bspstore1) + (sc_loadrs >> 19) + ;; + shr.u r14=r14,6 // r14 <- (rse_slot_num(bspstore1) + (sc_loadrs >> 19))/0x40 + ;; + sub r14=r14,r17 // r14 <- -rse_num_regs(bspstore1, bsp1) + movl r17=0x8208208208208209 + ;; + add r18=r18,r14 // r18 (delta) <- rse_slot_num(bsp0) - rse_num_regs(bspstore1,bsp1) + setf.sig f7=r17 + cmp.lt p7,p0=r14,r0 // p7 <- (r14 < 0)? + ;; +(p7) adds r18=-62,r18 // delta -= 62 + ;; + setf.sig f6=r18 + ;; + xmpy.h f6=f6,f7 + ;; + getf.sig r17=f6 + ;; + add r17=r17,r18 + shr r18=r18,63 + ;; + shr r17=r17,5 + ;; + sub r17=r17,r18 // r17 = delta/63 + ;; + add r17=r14,r17 // r17 <- delta/63 - rse_num_regs(bspstore1, bsp1) + ;; + shladd r15=r17,3,r15 // r15 <- bsp0 + 8*(delta/63 - rse_num_regs(bspstore1, bsp1)) + ;; + mov ar.bspstore=r15 // switch back to old register backing store area + ;; + mov ar.rnat=r16 // restore RNaT + mov ar.rsc=0xf // (will be restored later on from sc_ar_rsc) + // invala not necessary as that will happen when returning to user-mode + br.cond.sptk back_from_restore_rbs +END(__kernel_sigtramp) diff -r 61b945565398 -r 489de0be169c arch/ia64/kernel/gate.lds.S --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/arch/ia64/kernel/gate.lds.S Thu Jul 27 00:09:52 2006 -0400 @@ -0,0 +1,96 @@ +/* + * Linker script for gate DSO. The gate pages are an ELF shared object prelinked to its + * virtual address, with only one read-only segment and one execute-only segment (both fit + * in one page). This script controls its layout. + */ + +#include + +#include + +SECTIONS +{ + . = GATE_ADDR + SIZEOF_HEADERS; + + .hash : { *(.hash) } :readable + .dynsym : { *(.dynsym) } + .dynstr : { *(.dynstr) } + .gnu.version : { *(.gnu.version) } + .gnu.version_d : { *(.gnu.version_d) } + .gnu.version_r : { *(.gnu.version_r) } + .dynamic : { *(.dynamic) } :readable :dynamic + + /* + * This linker script is used both with -r and with -shared. For the layouts to match, + * we need to skip more than enough space for the dynamic symbol table et al. If this + * amount is insufficient, ld -shared will barf. Just increase it here. + */ + . = GATE_ADDR + 0x500; + + .data.patch : { + __start_gate_mckinley_e9_patchlist = .; + *(.data.patch.mckinley_e9) + __end_gate_mckinley_e9_patchlist = .; + + __start_gate_vtop_patchlist = .; + *(.data.patch.vtop) + __end_gate_vtop_patchlist = .; + + __start_gate_fsyscall_patchlist = .; + *(.data.patch.fsyscall_table) + __end_gate_fsyscall_patchlist = .; + + __start_gate_brl_fsys_bubble_down_patchlist = .; + *(.data.patch.brl_fsys_bubble_down) + __end_gate_brl_fsys_bubble_down_patchlist = .; + } :readable + .IA_64.unwind_info : { *(.IA_64.unwind_info*) } + .IA_64.unwind : { *(.IA_64.unwind*) } :readable :unwind +#ifdef HAVE_BUGGY_SEGREL + .text (GATE_ADDR + PAGE_SIZE) : { *(.text) *(.text.*) } :readable +#else + . = ALIGN (PERCPU_PAGE_SIZE) + (. & (PERCPU_PAGE_SIZE - 1)); + .text : { *(.text) *(.text.*) } :epc +#endif + + /DISCARD/ : { + *(.got.plt) *(.got) + *(.data .data.* .gnu.linkonce.d.*) + *(.dynbss) + *(.bss .bss.* .gnu.linkonce.b.*) + *(__ex_table) + *(__mca_table) + } +} + +/* + * We must supply the ELF program headers explicitly to get just one + * PT_LOAD segment, and set the flags explicitly to make segments read-only. + */ +PHDRS +{ + readable PT_LOAD FILEHDR PHDRS FLAGS(4); /* PF_R */ +#ifndef HAVE_BUGGY_SEGREL + epc PT_LOAD FILEHDR PHDRS FLAGS(1); /* PF_X */ +#endif + dynamic PT_DYNAMIC FLAGS(4); /* PF_R */ + unwind 0x70000001; /* PT_IA_64_UNWIND, but ld doesn't match the name */ +} + +/* + * This controls what symbols we export from the DSO. + */ +VERSION +{ + LINUX_2.5 { + global: + __kernel_syscall_via_break; + __kernel_syscall_via_epc; + __kernel_sigtramp; + + local: *; + }; +} + +/* The ELF entry point can be used to set the AT_SYSINFO value. */ +ENTRY(__kernel_syscall_via_epc) diff -r 61b945565398 -r 489de0be169c arch/ia64/kernel/patch.c --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/arch/ia64/kernel/patch.c Thu Jul 27 00:09:52 2006 -0400 @@ -0,0 +1,197 @@ +/* + * Instruction-patching support. + * + * Copyright (C) 2003 Hewlett-Packard Co + * David Mosberger-Tang + */ +#include +#include + +#include +#include +#include +#include +#include + +/* + * This was adapted from code written by Tony Luck: + * + * The 64-bit value in a "movl reg=value" is scattered between the two words of the bundle + * like this: + * + * 6 6 5 4 3 2 1 + * 3210987654321098765432109876543210987654321098765432109876543210 + * ABBBBBBBBBBBBBBBBBBBBBBBCCCCCCCCCCCCCCCCCCDEEEEEFFFFFFFFFGGGGGGG + * + * CCCCCCCCCCCCCCCCCCxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx + * xxxxAFFFFFFFFFEEEEEDxGGGGGGGxxxxxxxxxxxxxBBBBBBBBBBBBBBBBBBBBBBB + */ +static u64 +get_imm64 (u64 insn_addr) +{ + u64 *p = (u64 *) (insn_addr & -16); /* mask out slot number */ + + return ( (p[1] & 0x0800000000000000UL) << 4) | /*A*/ + ((p[1] & 0x00000000007fffffUL) << 40) | /*B*/ + ((p[0] & 0xffffc00000000000UL) >> 24) | /*C*/ + ((p[1] & 0x0000100000000000UL) >> 23) | /*D*/ + ((p[1] & 0x0003e00000000000UL) >> 29) | /*E*/ + ((p[1] & 0x07fc000000000000UL) >> 43) | /*F*/ + ((p[1] & 0x000007f000000000UL) >> 36); /*G*/ +} + +/* Patch instruction with "val" where "mask" has 1 bits. */ +void +ia64_patch (u64 insn_addr, u64 mask, u64 val) +{ + u64 m0, m1, v0, v1, b0, b1, *b = (u64 *) (insn_addr & -16); +# define insn_mask ((1UL << 41) - 1) + unsigned long shift; + + b0 = b[0]; b1 = b[1]; + shift = 5 + 41 * (insn_addr % 16); /* 5 bits of template, then 3 x 41-bit instructions */ + if (shift >= 64) { + m1 = mask << (shift - 64); + v1 = val << (shift - 64); + } else { + m0 = mask << shift; m1 = mask >> (64 - shift); + v0 = val << shift; v1 = val >> (64 - shift); + b[0] = (b0 & ~m0) | (v0 & m0); + } + b[1] = (b1 & ~m1) | (v1 & m1); +} + +void +ia64_patch_imm64 (u64 insn_addr, u64 val) +{ + /* The assembler may generate offset pointing to either slot 1 + or slot 2 for a long (2-slot) instruction, occupying slots 1 + and 2. */ + insn_addr &= -16UL; + ia64_patch(insn_addr + 2, + 0x01fffefe000UL, ( ((val & 0x8000000000000000UL) >> 27) /* bit 63 -> 36 */ + | ((val & 0x0000000000200000UL) << 0) /* bit 21 -> 21 */ + | ((val & 0x00000000001f0000UL) << 6) /* bit 16 -> 22 */ + | ((val & 0x000000000000ff80UL) << 20) /* bit 7 -> 27 */ + | ((val & 0x000000000000007fUL) << 13) /* bit 0 -> 13 */)); + ia64_patch(insn_addr + 1, 0x1ffffffffffUL, val >> 22); +} + +void +ia64_patch_imm60 (u64 insn_addr, u64 val) +{ + /* The assembler may generate offset pointing to either slot 1 + or slot 2 for a long (2-slot) instruction, occupying slots 1 + and 2. */ + insn_addr &= -16UL; + ia64_patch(insn_addr + 2, + 0x011ffffe000UL, ( ((val & 0x0800000000000000UL) >> 23) /* bit 59 -> 36 */ + | ((val & 0x00000000000fffffUL) << 13) /* bit 0 -> 13 */)); + ia64_patch(insn_addr + 1, 0x1fffffffffcUL, val >> 18); +} + +/* + * We need sometimes to load the physical address of a kernel + * object. Often we can convert the virtual address to physical + * at execution time, but sometimes (either for performance reasons + * or during error recovery) we cannot to this. Patch the marked + * bundles to load the physical address. + */ +void __init +ia64_patch_vtop (unsigned long start, unsigned long end) +{ + s32 *offp = (s32 *) start; + u64 ip; + + while (offp < (s32 *) end) { + ip = (u64) offp + *offp; + + /* replace virtual address with corresponding physical address: */ + ia64_patch_imm64(ip, ia64_tpa(get_imm64(ip))); + ia64_fc((void *) ip); + ++offp; + } + ia64_sync_i(); + ia64_srlz_i(); +} + +void __init +ia64_patch_mckinley_e9 (unsigned long start, unsigned long end) +{ + static int first_time = 1; + int need_workaround; + s32 *offp = (s32 *) start; + u64 *wp; + + need_workaround = (local_cpu_data->family == 0x1f && local_cpu_data->model == 0); + + if (first_time) { + first_time = 0; + if (need_workaround) + printk(KERN_INFO "Leaving McKinley Errata 9 workaround enabled\n"); + else + printk(KERN_INFO "McKinley Errata 9 workaround not needed; " + "disabling it\n"); + } + if (need_workaround) + return; + + while (offp < (s32 *) end) { + wp = (u64 *) ia64_imva((char *) offp + *offp); + wp[0] = 0x0000000100000000UL; /* nop.m 0; nop.i 0; nop.i 0 */ + wp[1] = 0x0004000000000200UL; + wp[2] = 0x0000000100000011UL; /* nop.m 0; nop.i 0; br.ret.sptk.many b6 */ + wp[3] = 0x0084006880000200UL; + ia64_fc(wp); ia64_fc(wp + 2); + ++offp; + } + ia64_sync_i(); + ia64_srlz_i(); +} + +static void __init +patch_fsyscall_table (unsigned long start, unsigned long end) +{ + extern unsigned long fsyscall_table[NR_syscalls]; + s32 *offp = (s32 *) start; + u64 ip; + + while (offp < (s32 *) end) { + ip = (u64) ia64_imva((char *) offp + *offp); + ia64_patch_imm64(ip, (u64) fsyscall_table); + ia64_fc((void *) ip); + ++offp; + } + ia64_sync_i(); + ia64_srlz_i(); +} + +static void __init +patch_brl_fsys_bubble_down (unsigned long start, unsigned long end) +{ + extern char fsys_bubble_down[]; + s32 *offp = (s32 *) start; + u64 ip; + + while (offp < (s32 *) end) { + ip = (u64) offp + *offp; + ia64_patch_imm60((u64) ia64_imva((void *) ip), + (u64) (fsys_bubble_down - (ip & -16)) / 16); + ia64_fc((void *) ip); + ++offp; + } + ia64_sync_i(); + ia64_srlz_i(); +} + +void __init +ia64_patch_gate (void) +{ +# define START(name) ((unsigned long) __start_gate_##name##_patchlist) +# define END(name) ((unsigned long)__end_gate_##name##_patchlist) + + patch_fsyscall_table(START(fsyscall), END(fsyscall)); + patch_brl_fsys_bubble_down(START(brl_fsys_bubble_down), END(brl_fsys_bubble_down)); + ia64_patch_vtop(START(vtop), END(vtop)); + ia64_patch_mckinley_e9(START(mckinley_e9), END(mckinley_e9)); +} From aron at hp.com Thu Jul 27 04:10:56 2006 From: aron at hp.com (Aron Griffis) Date: Thu, 27 Jul 2006 00:10:56 -0400 Subject: [Fedora-xen] [PATCH 2 of 5] Port xen ioremap mods forward to 2.6.18-rc2 In-Reply-To: Message-ID: <575b49ce64a2098515c4.1153973456@vino.zko.hp.com> 2 files changed, 4 insertions(+), 14 deletions(-) arch/ia64/mm/ioremap.c | 2 ++ include/asm-ia64/io.h | 16 ++-------------- # HG changeset patch # User agriffis at cheo.zko.hp.com # Node ID 575b49ce64a2098515c48a3f29a214f853025fcf # Parent 489de0be169cc96a41105f8cb9046be740a9a706 Port xen ioremap mods forward to 2.6.18-rc2 Signed-off-by: Aron Griffis diff -r 489de0be169c -r 575b49ce64a2 arch/ia64/mm/ioremap.c --- a/arch/ia64/mm/ioremap.c Thu Jul 27 00:09:52 2006 -0400 +++ b/arch/ia64/mm/ioremap.c Thu Jul 27 00:09:55 2006 -0400 @@ -16,7 +16,9 @@ static inline void __iomem * static inline void __iomem * __ioremap (unsigned long offset, unsigned long size) { +#ifdef CONFIG_XEN offset = HYPERVISOR_ioremap(offset, size); +#endif return (void __iomem *) (__IA64_UNCACHED_OFFSET | offset); } diff -r 489de0be169c -r 575b49ce64a2 include/asm-ia64/io.h --- a/include/asm-ia64/io.h Thu Jul 27 00:09:52 2006 -0400 +++ b/include/asm-ia64/io.h Thu Jul 27 00:09:55 2006 -0400 @@ -451,25 +451,13 @@ __writeq (unsigned long val, volatile vo # define outl_p outl #endif -/* - * An "address" in IO memory space is not clearly either an integer or a pointer. We will - * accept both, thus the casts. - * - * On ia-64, we access the physical I/O memory space through the uncached kernel region. - */ -static inline void __iomem * -ioremap (unsigned long offset, unsigned long size) -{ - offset = HYPERVISOR_ioremap(offset, size); - return (void __iomem *) (__IA64_UNCACHED_OFFSET | (offset)); -} +extern void __iomem * ioremap(unsigned long offset, unsigned long size); +extern void __iomem * ioremap_nocache (unsigned long offset, unsigned long size); static inline void iounmap (volatile void __iomem *addr) { } - -#define ioremap_nocache(o,s) ioremap(o,s) /* Use normal IO mappings for DMI */ #define dmi_ioremap ioremap From aron at hp.com Thu Jul 27 04:10:54 2006 From: aron at hp.com (Aron Griffis) Date: Thu, 27 Jul 2006 00:10:54 -0400 Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 Message-ID: Hi Juan, These patches are the result of Akio, Prarit, Alex and me working on fixing the ia64 build of your tree. At this point the bare-metal Linux kernel builds and boots. The xen kernel builds but doesn't complete booting. Nonetheless, since these patches seem to take us most of the way there, we'd like to request them to be applied to your tree. Thanks, Aron -------------- next part -------------- 12 files changed, 684 insertions(+), 18 deletions(-) arch/ia64/kernel/gate.S | 376 +++++++++++++++++++++++++++++++++++++++ arch/ia64/kernel/gate.lds.S | 96 +++++++++ arch/ia64/kernel/patch.c | 197 ++++++++++++++++++++ arch/ia64/mm/ioremap.c | 2 arch/ia64/xen/hypervisor.c | 4 drivers/xen/blkback/blkback.c | 1 drivers/xen/core/evtchn.c | 2 drivers/xen/netback/common.h | 1 drivers/xen/netback/netback.c | 1 drivers/xen/netfront/netfront.c | 1 include/asm-ia64/hw_irq.h | 5 include/asm-ia64/io.h | 16 - From aron at hp.com Thu Jul 27 04:10:57 2006 From: aron at hp.com (Aron Griffis) Date: Thu, 27 Jul 2006 00:10:57 -0400 Subject: [Fedora-xen] [PATCH 3 of 5] hw_resend_irq() isn't passed struct hw_interrupt_type in 2.6.18 In-Reply-To: Message-ID: <8de5c39ac1ef23a8c257.1153973457@vino.zko.hp.com> 2 files changed, 3 insertions(+), 4 deletions(-) drivers/xen/core/evtchn.c | 2 +- include/asm-ia64/hw_irq.h | 5 ++--- # HG changeset patch # User agriffis at cheo.zko.hp.com # Node ID 8de5c39ac1ef23a8c257fd02186d9810f9c358c5 # Parent 575b49ce64a2098515c48a3f29a214f853025fcf hw_resend_irq() isn't passed struct hw_interrupt_type in 2.6.18 Signed-off-by: Aron Griffis diff -r 575b49ce64a2 -r 8de5c39ac1ef drivers/xen/core/evtchn.c --- a/drivers/xen/core/evtchn.c Thu Jul 27 00:09:55 2006 -0400 +++ b/drivers/xen/core/evtchn.c Thu Jul 27 00:09:59 2006 -0400 @@ -694,7 +694,7 @@ int irq_ignore_unhandled(unsigned int ir return !!(irq_status.flags & XENIRQSTAT_shared); } -void resend_irq_on_evtchn(struct hw_interrupt_type *h, unsigned int i) +void resend_irq_on_evtchn(unsigned int i) { int evtchn = evtchn_from_irq(i); shared_info_t *s = HYPERVISOR_shared_info; diff -r 575b49ce64a2 -r 8de5c39ac1ef include/asm-ia64/hw_irq.h --- a/include/asm-ia64/hw_irq.h Thu Jul 27 00:09:55 2006 -0400 +++ b/include/asm-ia64/hw_irq.h Thu Jul 27 00:09:59 2006 -0400 @@ -104,10 +104,9 @@ static inline void ia64_resend_irq(unsig static inline void ia64_resend_irq(unsigned int vector) { #ifdef CONFIG_XEN - extern void resend_irq_on_evtchn(struct hw_interrupt_type *h, - unsigned int i); + extern void resend_irq_on_evtchn(unsigned int i); if (is_running_on_xen()) - resend_irq_on_evtchn(h, vector); + resend_irq_on_evtchn(vector); else #endif /* CONFIG_XEN */ platform_send_ipi(smp_processor_id(), vector, IA64_IPI_DM_INT, 0); From aron at hp.com Thu Jul 27 04:10:59 2006 From: aron at hp.com (Aron Griffis) Date: Thu, 27 Jul 2006 00:10:59 -0400 Subject: [Fedora-xen] [PATCH 5 of 5] Fix compilation in 2.6.18 by adding #includes In-Reply-To: Message-ID: 4 files changed, 4 insertions(+) drivers/xen/blkback/blkback.c | 1 + drivers/xen/netback/common.h | 1 + drivers/xen/netback/netback.c | 1 + drivers/xen/netfront/netfront.c | 1 + # HG changeset patch # User agriffis at cheo.zko.hp.com # Node ID aabd6c30336524b8bc0cc21291870170e6e2ea97 # Parent 5602e37817d5712662b8240b5efa16a9c847c032 Fix compilation in 2.6.18 by adding #includes Signed-off-by: Aron Griffis diff -r 5602e37817d5 -r aabd6c303365 drivers/xen/blkback/blkback.c --- a/drivers/xen/blkback/blkback.c Thu Jul 27 00:10:03 2006 -0400 +++ b/drivers/xen/blkback/blkback.c Thu Jul 27 00:10:06 2006 -0400 @@ -40,6 +40,7 @@ #include #include #include +#include #include "common.h" /* diff -r 5602e37817d5 -r aabd6c303365 drivers/xen/netback/common.h --- a/drivers/xen/netback/common.h Thu Jul 27 00:10:03 2006 -0400 +++ b/drivers/xen/netback/common.h Thu Jul 27 00:10:06 2006 -0400 @@ -46,6 +46,7 @@ #include #include #include +#include #define DPRINTK(_f, _a...) \ pr_debug("(file=%s, line=%d) " _f, \ diff -r 5602e37817d5 -r aabd6c303365 drivers/xen/netback/netback.c --- a/drivers/xen/netback/netback.c Thu Jul 27 00:10:03 2006 -0400 +++ b/drivers/xen/netback/netback.c Thu Jul 27 00:10:06 2006 -0400 @@ -37,6 +37,7 @@ #include "common.h" #include #include +#include /*#define NETBE_DEBUG_INTERRUPT*/ diff -r 5602e37817d5 -r aabd6c303365 drivers/xen/netfront/netfront.c --- a/drivers/xen/netfront/netfront.c Thu Jul 27 00:10:03 2006 -0400 +++ b/drivers/xen/netfront/netfront.c Thu Jul 27 00:10:06 2006 -0400 @@ -50,6 +50,7 @@ #include #include #include +#include #include #include #include From xiantao.zhang at intel.com Thu Jul 27 08:04:49 2006 From: xiantao.zhang at intel.com (Zhang, Xiantao) Date: Thu, 27 Jul 2006 16:04:49 +0800 Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 Message-ID: Hi Aron, Could you share me the current status for fedora-xen-ia64? Through your mails, I see we should focus our efforts on linux-2.6-xen-fedora. But when I applied the patch 199684 on it, conflicts occurs. Do you have any suggestion for contributing to Fedora ? Thanks & Best Regards -Xiantao OTC,Intel Corporation > -----Original Message----- > From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] > On Behalf Of Aron Griffis > Sent: 2006?7?27? 12:11 > To: Juan Quintela > Cc: Prarit Bhargava; fedora-xen at redhat.com; Chris Wright; > fedora-ia64-list at redhat.com; Alex Williamson; > xen-ia64-devel at lists.xensource.com > Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 > > Hi Juan, > > These patches are the result of Akio, Prarit, Alex and me working on fixing > the > ia64 build of your tree. At this point the bare-metal Linux kernel builds and > boots. The xen kernel builds but doesn't complete booting. Nonetheless, > since > these patches seem to take us most of the way there, we'd like to request them > to be applied to your tree. > > Thanks, > Aron From takebe_akio at jp.fujitsu.com Thu Jul 27 08:46:45 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Thu, 27 Jul 2006 17:46:45 +0900 Subject: [Xen-ia64-devel] RE: [Fedora-xen] [PATCH 0 of 5] fixlinux-2.6-xen-fedora on ia64 In-Reply-To: References: Message-ID: <3AC6B15930FA26takebe_akio@jp.fujitsu.com> Hi, Xiantao BZ's patch is old. Today 139 cset is added to linux-2.6-xen-fedora tree. So I think we should use Aron's patches. Best Regards, Akio Takebe >Hi Aron, > Could you share me the current status for fedora-xen-ia64? Through your >mails, I see we should focus our efforts on linux-2.6-xen-fedora. But when >I applied the patch 199684 on it, conflicts occurs. Do you have any >suggestion for contributing to Fedora ? >Thanks & Best Regards >-Xiantao > >OTC,Intel Corporation > >> -----Original Message----- >> From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] >> On Behalf Of Aron Griffis >> Sent: 2006$B%Hs%d%D(B27$B%M%f(B 12:11 >> To: Juan Quintela >> Cc: Prarit Bhargava; fedora-xen at redhat.com; Chris Wright; >> fedora-ia64-list at redhat.com; Alex Williamson; >> xen-ia64-devel at lists.xensource.com >> Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 >> >> Hi Juan, >> >> These patches are the result of Akio, Prarit, Alex and me working on fixing >> the >> ia64 build of your tree. At this point the bare-metal Linux kernel >> builds and >> boots. The xen kernel builds but doesn't complete booting. Nonetheless, >> since >> these patches seem to take us most of the way there, we'd like to request >> them >> to be applied to your tree. >> >> Thanks, >> Aron > >_______________________________________________ >Xen-ia64-devel mailing list >Xen-ia64-devel at lists.xensource.com >http://lists.xensource.com/xen-ia64-devel From xiantao.zhang at intel.com Thu Jul 27 09:15:11 2006 From: xiantao.zhang at intel.com (Zhang, Xiantao) Date: Thu, 27 Jul 2006 17:15:11 +0800 Subject: [Xen-ia64-devel] RE: [Fedora-xen] [PATCH 0 of 5] fixlinux-2.6-xen-fedora on ia64 Message-ID: Hi Akio, Thank you for your information. I am using the CSet34705 which should be latest, and do you mean I should apply Aron's patches on it. right? In addition, what's status about it? BTW, Thanks & Best Regards -Xiantao OTC,Intel Corporation > -----Original Message----- > From: Akio Takebe [mailto:takebe_akio at jp.fujitsu.com] > Sent: 2006?7?27? 16:47 > To: Zhang, Xiantao; Aron Griffis; Juan Quintela > Cc: Prarit Bhargava; fedora-xen at redhat.com; Chris Wright; > fedora-ia64-list at redhat.com; xen-ia64-devel at lists.xensource.com > Subject: Re: [Xen-ia64-devel] RE: [Fedora-xen] [PATCH 0 of 5] > fixlinux-2.6-xen-fedora on ia64 > > Hi, Xiantao > > BZ's patch is old. > Today 139 cset is added to linux-2.6-xen-fedora tree. > So I think we should use Aron's patches. > > Best Regards, > > Akio Takebe > > >Hi Aron, > > Could you share me the current status for fedora-xen-ia64? Through your > > >mails, I see we should focus our efforts on linux-2.6-xen-fedora. But when > >I applied the patch 199684 on it, conflicts occurs. Do you have any > >suggestion for contributing to Fedora ? > >Thanks & Best Regards > >-Xiantao > > > >OTC,Intel Corporation > > > >> -----Original Message----- > >> From: fedora-xen-bounces at redhat.com > [mailto:fedora-xen-bounces at redhat.com] > >> On Behalf Of Aron Griffis > >> Sent: 2006????27?? 12:11 > >> To: Juan Quintela > >> Cc: Prarit Bhargava; fedora-xen at redhat.com; Chris Wright; > >> fedora-ia64-list at redhat.com; Alex Williamson; > >> xen-ia64-devel at lists.xensource.com > >> Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 > >> > >> Hi Juan, > >> > >> These patches are the result of Akio, Prarit, Alex and me working on fixing > >> the > >> ia64 build of your tree. At this point the bare-metal Linux kernel > >> builds and > >> boots. The xen kernel builds but doesn't complete booting. Nonetheless, > >> since > >> these patches seem to take us most of the way there, we'd like to request > >> them > >> to be applied to your tree. > >> > >> Thanks, > >> Aron > > > >_______________________________________________ > >Xen-ia64-devel mailing list > >Xen-ia64-devel at lists.xensource.com > >http://lists.xensource.com/xen-ia64-devel From takebe_akio at jp.fujitsu.com Thu Jul 27 09:35:34 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Thu, 27 Jul 2006 18:35:34 +0900 Subject: [Xen-ia64-devel] RE: [Fedora-xen] [PATCH 0 of 5] fixlinux-2.6-xen-fedora on ia64 In-Reply-To: References: Message-ID: <3DC6B160028E17takebe_akio@jp.fujitsu.com> Hi, Xiantao Yes, you are right. And I think you must use the following patch. Now I cannot boot by using xen-ia64-unstable (not linux-2.6-xen-fedora) on FC6. I'm debuging it. Then I'll try to boot by using xen-ia64-unstable/xen and linux-2.6-xen- fedora. diff -r 61b945565398 drivers/char/tpm/tpm.h --- a/drivers/char/tpm/tpm.h Wed Jul 26 17:22:38 2006 +0200 +++ b/drivers/char/tpm/tpm.h Wed Aug 02 00:30:00 2006 +0900 @@ -125,7 +125,7 @@ static inline void tpm_write_index(int b static inline u32 get_chip_buffersize(struct tpm_chip *chip) { - return chip->vendor->buffersize; + return chip->vendor.buffersize; } extern void tpm_get_timeouts(struct tpm_chip *); Best Regards, Akio Takebe >Hi Akio, > Thank you for your information. I am using the CSet34705 which should be >latest, and do you mean I should apply Aron's patches on it. right? In >addition, what's status about it? >BTW, > >Thanks & Best Regards >-Xiantao > >OTC,Intel Corporation > >> -----Original Message----- >> From: Akio Takebe [mailto:takebe_akio at jp.fujitsu.com] >> Sent: 2006?7?27? 16:47 >> To: Zhang, Xiantao; Aron Griffis; Juan Quintela >> Cc: Prarit Bhargava; fedora-xen at redhat.com; Chris Wright; >> fedora-ia64-list at redhat.com; xen-ia64-devel at lists.xensource.com >> Subject: Re: [Xen-ia64-devel] RE: [Fedora-xen] [PATCH 0 of 5] >> fixlinux-2.6-xen-fedora on ia64 >> >> Hi, Xiantao >> >> BZ's patch is old. >> Today 139 cset is added to linux-2.6-xen-fedora tree. >> So I think we should use Aron's patches. >> >> Best Regards, >> >> Akio Takebe >> >> >Hi Aron, >> > Could you share me the current status for fedora-xen-ia64? Through your >> >> >mails, I see we should focus our efforts on linux-2.6-xen-fedora. But when >> >I applied the patch 199684 on it, conflicts occurs. Do you have any >> >suggestion for contributing to Fedora ? >> >Thanks & Best Regards >> >-Xiantao >> > >> >OTC,Intel Corporation >> > >> >> -----Original Message----- >> >> From: fedora-xen-bounces at redhat.com >> [mailto:fedora-xen-bounces at redhat.com] >> >> On Behalf Of Aron Griffis >> >> Sent: 2006????27?? 12:11 >> >> To: Juan Quintela >> >> Cc: Prarit Bhargava; fedora-xen at redhat.com; Chris Wright; >> >> fedora-ia64-list at redhat.com; Alex Williamson; >> >> xen-ia64-devel at lists.xensource.com >> >> Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 >> >> >> >> Hi Juan, >> >> >> >> These patches are the result of Akio, Prarit, Alex and me working on >> >> fixing >> >> the >> >> ia64 build of your tree. At this point the bare-metal Linux kernel >> >> builds and >> >> boots. The xen kernel builds but doesn't complete booting. >> >> Nonetheless, >> >> since >> >> these patches seem to take us most of the way there, we'd like to >> >> request >> >> them >> >> to be applied to your tree. >> >> >> >> Thanks, >> >> Aron >> > >> >_______________________________________________ >> >Xen-ia64-devel mailing list >> >Xen-ia64-devel at lists.xensource.com >> >http://lists.xensource.com/xen-ia64-devel -------------- next part -------------- A non-text attachment was scrubbed... Name: tpm.patch Type: application/octet-stream Size: 416 bytes Desc: not available URL: From xiantao.zhang at intel.com Thu Jul 27 09:37:44 2006 From: xiantao.zhang at intel.com (Zhang, Xiantao) Date: Thu, 27 Jul 2006 17:37:44 +0800 Subject: [Xen-ia64-devel] RE: [Fedora-xen] [PATCH 0 of 5] fixlinux-2.6-xen-fedora on ia64 Message-ID: Very clear now! Thank you very much. -Xiantao OTC,Intel Corporation > -----Original Message----- > From: Akio Takebe [mailto:takebe_akio at jp.fujitsu.com] > Sent: 2006?7?27? 17:36 > To: Zhang, Xiantao; Aron Griffis; Juan Quintela > Cc: Prarit Bhargava; fedora-xen at redhat.com; Chris Wright; > fedora-ia64-list at redhat.com; xen-ia64-devel at lists.xensource.com; Akio > Takebe > Subject: RE: [Xen-ia64-devel] RE: [Fedora-xen] [PATCH 0 of 5] > fixlinux-2.6-xen-fedora on ia64 > > Hi, Xiantao > > Yes, you are right. > And I think you must use the following patch. > > Now I cannot boot by using xen-ia64-unstable > (not linux-2.6-xen-fedora) on FC6. > I'm debuging it. > Then I'll try to boot by using xen-ia64-unstable/xen and linux-2.6-xen- > fedora. > > diff -r 61b945565398 drivers/char/tpm/tpm.h > --- a/drivers/char/tpm/tpm.h Wed Jul 26 17:22:38 2006 +0200 > +++ b/drivers/char/tpm/tpm.h Wed Aug 02 00:30:00 2006 +0900 > @@ -125,7 +125,7 @@ static inline void tpm_write_index(int b > > static inline u32 get_chip_buffersize(struct tpm_chip *chip) > { > - return chip->vendor->buffersize; > + return chip->vendor.buffersize; > } > > extern void tpm_get_timeouts(struct tpm_chip *); > > Best Regards, > > Akio Takebe > > >Hi Akio, > > Thank you for your information. I am using the CSet34705 which should > be > >latest, and do you mean I should apply Aron's patches on it. right? In > >addition, what's status about it? > >BTW, > > > >Thanks & Best Regards > >-Xiantao > > > >OTC,Intel Corporation > > > >> -----Original Message----- > >> From: Akio Takebe [mailto:takebe_akio at jp.fujitsu.com] > >> Sent: 2006?7?27? 16:47 > >> To: Zhang, Xiantao; Aron Griffis; Juan Quintela > >> Cc: Prarit Bhargava; fedora-xen at redhat.com; Chris Wright; > >> fedora-ia64-list at redhat.com; xen-ia64-devel at lists.xensource.com > >> Subject: Re: [Xen-ia64-devel] RE: [Fedora-xen] [PATCH 0 of 5] > >> fixlinux-2.6-xen-fedora on ia64 > >> > >> Hi, Xiantao > >> > >> BZ's patch is old. > >> Today 139 cset is added to linux-2.6-xen-fedora tree. > >> So I think we should use Aron's patches. > >> > >> Best Regards, > >> > >> Akio Takebe > >> > >> >Hi Aron, > >> > Could you share me the current status for fedora-xen-ia64? Through your > > >> > >> >mails, I see we should focus our efforts on linux-2.6-xen-fedora. But when > >> >I applied the patch 199684 on it, conflicts occurs. Do you have any > >> >suggestion for contributing to Fedora ? > >> >Thanks & Best Regards > >> >-Xiantao > >> > > >> >OTC,Intel Corporation > >> > > >> >> -----Original Message----- > >> >> From: fedora-xen-bounces at redhat.com > >> [mailto:fedora-xen-bounces at redhat.com] > >> >> On Behalf Of Aron Griffis > >> >> Sent: 2006????27?? 12:11 > >> >> To: Juan Quintela > >> >> Cc: Prarit Bhargava; fedora-xen at redhat.com; Chris Wright; > >> >> fedora-ia64-list at redhat.com; Alex Williamson; > >> >> xen-ia64-devel at lists.xensource.com > >> >> Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 > >> >> > >> >> Hi Juan, > >> >> > >> >> These patches are the result of Akio, Prarit, Alex and me working on > >> >> fixing > >> >> the > >> >> ia64 build of your tree. At this point the bare-metal Linux kernel > >> >> builds and > >> >> boots. The xen kernel builds but doesn't complete booting. > >> >> Nonetheless, > >> >> since > >> >> these patches seem to take us most of the way there, we'd like to > >> >> request > >> >> them > >> >> to be applied to your tree. > >> >> > >> >> Thanks, > >> >> Aron > >> > > >> >_______________________________________________ > >> >Xen-ia64-devel mailing list > >> >Xen-ia64-devel at lists.xensource.com > >> >http://lists.xensource.com/xen-ia64-devel From swcodfather at gmail.com Thu Jul 27 11:03:24 2006 From: swcodfather at gmail.com (Nick) Date: Thu, 27 Jul 2006 12:03:24 +0100 Subject: [Fedora-xen] Problem installing a Domu instance with latest FC5 kernel Message-ID: Is anybody prepared to offer any advice? Even a link to a useful resource. I have worked through the projects wiki on this subject, and there is nothing I haven't tried. TIA Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From prarit at redhat.com Thu Jul 27 11:16:54 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Thu, 27 Jul 2006 07:16:54 -0400 Subject: [Fedora-xen] Re: [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 In-Reply-To: References: Message-ID: <44C8A0A6.7060700@redhat.com> Aron Griffis wrote: > Hi Juan, > > These patches are the result of Akio, Prarit, Alex and me working on fixing the > ia64 build of your tree. At this point the bare-metal Linux kernel builds and > boots. The xen kernel builds but doesn't complete booting. Nonetheless, since > these patches seem to take us most of the way there, we'd like to request them > to be applied to your tree. > > Ack'ing this patchset. Thanks, P. From aron at hp.com Thu Jul 27 15:14:14 2006 From: aron at hp.com (Aron Griffis) Date: Thu, 27 Jul 2006 11:14:14 -0400 Subject: [Fedora-xen] [PATCH] Enable building xen on ia64 Message-ID: <20060727151414.GG10460@vino.americas.hpqcorp.net> Hi Juan, After you apply the patch bomb I sent last night, here is the kernel-2.6.spec patch to enable building xen on ia64. If possible, we (Prarit and I) would like these patches applied ASAP so that xen-ia64 can land in today's rpms. Additionally this patch removes a redundant buildkdump setting for ppc64. Since buildkdump defaults to 1 at the top of the spec, there's no reason for ppc64 to have the special case. Regards, Aron # HG changeset patch # User agriffis at cheo.zko.hp.com # Node ID 0d2d750a9002f1ecc354a352b1b88602485ba8f6 # Parent 4cf516051efbc66f7fa32fd289780328785a6ba9 Enable building xen on ia64. Also remove redundant buildkdump setting for ppc64. Signed-off-by: Aron Griffis diff -r 4cf516051efb -r 0d2d750a9002 devel/kernel-2.6.spec --- a/devel/kernel-2.6.spec Thu Jul 27 07:19:58 2006 -0400 +++ b/devel/kernel-2.6.spec Thu Jul 27 10:39:44 2006 -0400 @@ -65,14 +65,8 @@ Summary: The Linux kernel (the core of t %endif # Xen only builds on i686, x86_64 and ia64 ... -#%ifnarch i686 x86_64 ia64 -%ifnarch i686 x86_64 +%ifnarch i686 x86_64 ia64 %define buildxen 0 -%endif - - -%ifarch ppc64 -%define buildkdump 1 %endif # Second, per-architecture exclusions (ifarch) @@ -812,11 +806,10 @@ cd linux-%{kversion}.%{_target_cpu} #%patch951 -p1 %patch950 -p1 -b .p.xen # -# ... and back out all the ia64-specific sections, as they currently prevent +# ... and back out all the tpm-specific sections, as they currently prevent # non-xen builds from working. -# Now also with tpm -# -for f in `find drivers/char/tpm arch/ia64/ include/asm-ia64/ include/xen/interface/arch-ia64.h* -type f -name "*.p.xen"` ; do \ +# +for f in `find drivers/char/tpm -type f -name "*.p.xen"` ; do \ g=`dirname $f`/`basename $f .p.xen`; \ mv "$f" "$g"; \ if [ ! -s "$g" ] ; then rm -f "$g" ; fi; \ From quintela at redhat.com Thu Jul 27 15:35:41 2006 From: quintela at redhat.com (Juan Quintela) Date: Thu, 27 Jul 2006 17:35:41 +0200 Subject: [Fedora-xen] Re: [PATCH] Enable building xen on ia64 In-Reply-To: <20060727151414.GG10460@vino.americas.hpqcorp.net> References: <20060727151414.GG10460@vino.americas.hpqcorp.net> Message-ID: <1154014542.2439.1.camel@anano.mitica> On Thu, 2006-07-27 at 11:14 -0400, Aron Griffis wrote: > Hi Juan, > > After you apply the patch bomb I sent last night, here is the > kernel-2.6.spec patch to enable building xen on ia64. If possible, > we (Prarit and I) would like these patches applied ASAP so that > xen-ia64 can land in today's rpms. > > Additionally this patch removes a redundant buildkdump setting for > ppc64. Since buildkdump defaults to 1 at the top of the spec, there's > no reason for ppc64 to have the special case. Get the two rawhide xen bugs fixed 1h ago. Next kernel should work well on i386 & x86_64. I have to go now, bu next on the queue is integration of your patches, I hope they will appear tonight, tomorrow morning the later. Later, Juan. From aron at hp.com Thu Jul 27 16:40:50 2006 From: aron at hp.com (Aron Griffis) Date: Thu, 27 Jul 2006 12:40:50 -0400 Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 In-Reply-To: <3DC6B160028E17takebe_akio@jp.fujitsu.com> <3AC6B15930FA26takebe_akio@jp.fujitsu.com> References: <3DC6B160028E17takebe_akio@jp.fujitsu.com> <3AC6B15930FA26takebe_akio@jp.fujitsu.com> Message-ID: <20060727164049.GH10460@vino.americas.hpqcorp.net> Xiantao and Akio, Sorry that I'm not very good sharing status. Here is an update to hopefully put us on the same page again. First, a review of the repos available, since this is always a point of confusion: http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora - This is Juan's tree from which he generates linux-2.6-xen.patch for the Fedora kernel rpm. Juan creates this tree as a combination of pulls from: http://kernel.org/hg/linux-2.6 - automatic mirror of Linus' git tree http://xenbits.xensource.com/linux-2.6-xen.hg - sparse tree patches applied to 2.6.16 kernel, maintained mostly-daily by Christian http://xenbits.xensource.com/ext/linux-2.6.tip-xen.hg - sparse tree patches merged to 2.6.18 kernel, maintained sporadically by Chris Wright PLUS Juan's own patches to make it all work together. http://free.linux.hp.com/~agriffis/linux-2.6-xen-fedora-ia64 - This pulls from linux-2.6-xen-fedora, but also includes our patches to fix building on ia64. http://free.linux.hp.com/~agriffis/kernel-cvs - This is a mercurial mirror of the Fedora kernel cvs (see http://people.redhat.com/davej), updated numerous times per day by me. http://free.linux.hp.com/~agriffis/kernel-cvs-ia64 - This pulls from kernel-cvs, but also includes spec-file changes necessary to build and test on ia64. In particular, this includes linux-2.6-xen-ia64.patch which is our current collection of updates to Juan's tree to support ia64. Second, what works, what doesn't: kernel-cvs-ia64 builds on ia64, both with and without CONFIG_XEN. The normal kernel boots, the xen kernel doesn't yet. Considering that everything builds at this point, I've requested for Juan to update his repo *and* update the spec to enable building on ia64. This is driven by wanting to land in FC6 T2. We still need to make the xen kernel boot though :-) Third, how to contribute: If you prefer to work with raw xen and kernel sources instead of the rpm, do this first to get the kernel configs: hg clone http://free.linux.hp.com/~agriffis/kernel-cvs-ia64 cd kernel-cvs-ia64/devel make configs That generates these files, which you can use in a kernel tree with oldconfig: kernel-2.6.17-ia64.config kernel-2.6.17-ia64-xen.config Next get the kernel to work on: hg clone http://free.linux.hp.com/~agriffis/linux-2.6-xen-fedora-ia64 Send your patches to me and cc fedora-xen and xen-ia64-devel. To know what hypervisor changeset to use, check the spec file: cd kernel-cvs-ia64/devel grep -m1 xen_hv_cset kernel-2.6.spec Thanks, Aron From aron at hp.com Thu Jul 27 17:05:27 2006 From: aron at hp.com (Aron Griffis) Date: Thu, 27 Jul 2006 13:05:27 -0400 Subject: [Xen-ia64-devel] RE: [Fedora-xen] [PATCH 0 of 5] fixlinux-2.6-xen-fedora on ia64 In-Reply-To: <3AC6B15930FA26takebe_akio@jp.fujitsu.com> References: <3AC6B15930FA26takebe_akio@jp.fujitsu.com> Message-ID: <20060727170526.GI10460@vino.americas.hpqcorp.net> Akio Takebe wrote: [Thu Jul 27 2006, 04:46:45AM EDT] > BZ's patch is old. > Today 139 cset is added to linux-2.6-xen-fedora tree. > So I think we should use Aron's patches. Thanks, I just put an updated patch in BZ 199684, but best approach is to work from the mercurial trees I described in my previous email. Aron From aron at hp.com Thu Jul 27 17:08:11 2006 From: aron at hp.com (Aron Griffis) Date: Thu, 27 Jul 2006 13:08:11 -0400 Subject: [Xen-ia64-devel] RE: [Fedora-xen] [PATCH 0 of 5] fixlinux-2.6-xen-fedora on ia64 In-Reply-To: <3DC6B160028E17takebe_akio@jp.fujitsu.com> References: <3DC6B160028E17takebe_akio@jp.fujitsu.com> Message-ID: <20060727170811.GJ10460@vino.americas.hpqcorp.net> Akio, I intentionally omitted this from what I submitted to Juan because the rpm currently backs out ALL the xen modifications to the tpm code. But you're right... to build from linux-2.6-xen-fedora-ia64, you need to either (1) apply this patch, or (2) disable tpm in the config. Aron Akio Takebe wrote: [Thu Jul 27 2006, 05:35:34AM EDT] > diff -r 61b945565398 drivers/char/tpm/tpm.h > --- a/drivers/char/tpm/tpm.h Wed Jul 26 17:22:38 2006 +0200 > +++ b/drivers/char/tpm/tpm.h Wed Aug 02 00:30:00 2006 +0900 > @@ -125,7 +125,7 @@ static inline void tpm_write_index(int b > > static inline u32 get_chip_buffersize(struct tpm_chip *chip) > { > - return chip->vendor->buffersize; > + return chip->vendor.buffersize; > } > > extern void tpm_get_timeouts(struct tpm_chip *); From quintela at redhat.com Fri Jul 28 00:43:05 2006 From: quintela at redhat.com (Juan Quintela) Date: Fri, 28 Jul 2006 02:43:05 +0200 Subject: [Fedora-xen] Re: [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 In-Reply-To: References: Message-ID: <1154047385.2439.11.camel@anano.mitica> On Thu, 2006-07-27 at 00:10 -0400, Aron Griffis wrote: > Hi Juan, > > These patches are the result of Akio, Prarit, Alex and me working on fixing the > ia64 build of your tree. At this point the bare-metal Linux kernel builds and > boots. The xen kernel builds but doesn't complete booting. Nonetheless, since > these patches seem to take us most of the way there, we'd like to request them > to be applied to your tree. Hi Aron All of 5 of them are integrated on linux-2.6-xen-fedora (as you can guess, none of them is controversial). Later, Juan. From quintela at redhat.com Fri Jul 28 00:51:08 2006 From: quintela at redhat.com (Juan Quintela) Date: Fri, 28 Jul 2006 02:51:08 +0200 Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 In-Reply-To: <20060727164049.GH10460@vino.americas.hpqcorp.net> References: <3DC6B160028E17takebe_akio@jp.fujitsu.com> <3AC6B15930FA26takebe_akio@jp.fujitsu.com> <20060727164049.GH10460@vino.americas.hpqcorp.net> Message-ID: <1154047868.2439.15.camel@anano.mitica> On Thu, 2006-07-27 at 12:40 -0400, Aron Griffis wrote: Hi > http://xenbits.xensource.com/linux-2.6-xen.hg > - sparse tree patches applied to 2.6.16 kernel, > maintained mostly-daily by Christian > http://xenbits.xensource.com/ext/linux-2.6.tip-xen.hg > - sparse tree patches merged to 2.6.18 kernel, > maintained sporadically by Chris Wright > PLUS Juan's own patches to make it all work together. Actually this last two are also full trees, not sparse trees. It is way, way easier to work against a full tree that against a sparse tree. > Send your patches to me and cc fedora-xen and xen-ia64-devel. > To know what hypervisor changeset to use, check the spec file: > cd kernel-cvs-ia64/devel > grep -m1 xen_hv_cset kernel-2.6.spec Wow, you are fast catching my changes :) That variable was called xen_cset until yesterday :) Later, Juan. From takebe_akio at jp.fujitsu.com Fri Jul 28 01:00:41 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Fri, 28 Jul 2006 10:00:41 +0900 Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 In-Reply-To: <20060727164049.GH10460@vino.americas.hpqcorp.net> References: <3AC6B15930FA26takebe_akio@jp.fujitsu.com> <20060727164049.GH10460@vino.americas.hpqcorp.net> Message-ID: <44C6B1E13F20D6takebe_akio@jp.fujitsu.com> Hi, Aron Thank you for your good explanation. I have one question. > Send your patches to me and cc fedora-xen and xen-ia64-devel. > To know what hypervisor changeset to use, check the spec file: > cd kernel-cvs-ia64/devel > grep -m1 xen_hv_cset kernel-2.6.spec Which is this cset xen-ustable's cset or xen-ia64-unstable's cset? Best Regards, Akio Takebe From quintela at redhat.com Fri Jul 28 01:08:10 2006 From: quintela at redhat.com (Juan Quintela) Date: Fri, 28 Jul 2006 03:08:10 +0200 Subject: [Fedora-xen] Re: Four ways RH could help with xen-ia64 In-Reply-To: <20060725160746.GA3851@vino.zko.hp.com> References: <20060722133124.GB12649@mustard> <1153578830.2461.13.camel@anano.mitica> <20060725160746.GA3851@vino.zko.hp.com> Message-ID: <1154048890.2439.28.camel@anano.mitica> Hi Aron > I posted a message a while back containing a method for absolutely > matching the hypervisor to the kernel patch: > > https://www.redhat.com/archives/fedora-xen/2006-July/msg00024.html > > Is that approximately what you're doing now? No :) My experience is that HV <-> dom0 is too unstable. Then basically I update the hypervisor when I found that i386/x86_64 domU kernel don't work. Or somebody complains that HVM has become too unstable and that using unstable HV fixes it. With the state of flush that is xen at this moment, I preffer that approach. But feel free to ask me to update the HV each time that gets broken for you :) > > > - old domU should run on new hypervisor > > > > Agreed. I normally test plain fc5 domU on all my new kernels. > > > > > - new domU NOT guaranteed to run on old hypervisor > > > > We have found that lately this "normally" works, versus bugs. > > I'm sorry, your response confuses me here. :-( In the past, no guarantees that not matching dom0 <->HV will work. And it failed quite a bit. Lately (for 3.0.2 more or less), HV and dom0 try to agree on a minimum set of capabilities. And it has worked "reasonablely well". I have seen a couple of bugs in the compatibility, but they were fixed quite fast. > Just to be clear: These three bullet points I posted are the stated > goals of Xen upstream. Fedora should assume that a new domU will NOT > run on an old hypervisor, regardless of empirical evidence... For FC6, this is not a problem. But for the future, this is a _big_ problem. When FC7 is about to be out, it is reasonable for fedora users to expect that installing a new domU will lets them to test fc7 domU on its existing fc6 dom0. My understanding is that XenSource expect that dom0 <-> domU interface to stay stable. HV <-> domU interface to be a "we will not broke on purpose", but no guarntees. Later, Juan. From xiantao.zhang at intel.com Fri Jul 28 01:13:23 2006 From: xiantao.zhang at intel.com (Zhang, Xiantao) Date: Fri, 28 Jul 2006 09:13:23 +0800 Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 Message-ID: Aron, Thanks you for detail. Seems very clear now. I have the same question with Akio. Which Cset for xen and xenLinux is using for debug? Are they compatible? Thanks & Best Regards -Xiantao OTC,Intel Corporation > -----Original Message----- > From: Aron Griffis [mailto:aron at hp.com] > Sent: 2006?7?28? 0:41 > To: Zhang, Xiantao; Akio Takebe > Cc: fedora-xen at redhat.com; fedora-ia64-list at redhat.com; > xen-ia64-devel at lists.xensource.com > Subject: RE: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 > > Xiantao and Akio, > > Sorry that I'm not very good sharing status. Here is an update to > hopefully put us on the same page again. > > First, a review of the repos available, since this is always a point > of confusion: > > http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora > - This is Juan's tree from which he generates linux-2.6-xen.patch > for the Fedora kernel rpm. Juan creates this tree as > a combination of pulls from: > http://kernel.org/hg/linux-2.6 > - automatic mirror of Linus' git tree > http://xenbits.xensource.com/linux-2.6-xen.hg > - sparse tree patches applied to 2.6.16 kernel, > maintained mostly-daily by Christian > http://xenbits.xensource.com/ext/linux-2.6.tip-xen.hg > - sparse tree patches merged to 2.6.18 kernel, > maintained sporadically by Chris Wright > PLUS Juan's own patches to make it all work together. > > http://free.linux.hp.com/~agriffis/linux-2.6-xen-fedora-ia64 > - This pulls from linux-2.6-xen-fedora, but also includes our > patches to fix building on ia64. > > http://free.linux.hp.com/~agriffis/kernel-cvs > - This is a mercurial mirror of the Fedora kernel cvs (see > http://people.redhat.com/davej), updated numerous times per > day by me. > > http://free.linux.hp.com/~agriffis/kernel-cvs-ia64 > - This pulls from kernel-cvs, but also includes spec-file changes > necessary to build and test on ia64. In particular, this > includes linux-2.6-xen-ia64.patch which is our current > collection of updates to Juan's tree to support ia64. > > Second, what works, what doesn't: > > kernel-cvs-ia64 builds on ia64, both with and without CONFIG_XEN. > The normal kernel boots, the xen kernel doesn't yet. > > Considering that everything builds at this point, I've requested > for Juan to update his repo *and* update the spec to enable > building on ia64. This is driven by wanting to land in FC6 T2. > We still need to make the xen kernel boot though :-) > > Third, how to contribute: > > If you prefer to work with raw xen and kernel sources instead of > the rpm, do this first to get the kernel configs: > hg clone http://free.linux.hp.com/~agriffis/kernel-cvs-ia64 > cd kernel-cvs-ia64/devel > make configs > > That generates these files, which you can use in a kernel tree > with oldconfig: > kernel-2.6.17-ia64.config > kernel-2.6.17-ia64-xen.config > > Next get the kernel to work on: > hg clone http://free.linux.hp.com/~agriffis/linux-2.6-xen-fedora-ia64 > > Send your patches to me and cc fedora-xen and xen-ia64-devel. > To know what hypervisor changeset to use, check the spec file: > cd kernel-cvs-ia64/devel > grep -m1 xen_hv_cset kernel-2.6.spec > > Thanks, > Aron From quintela at redhat.com Fri Jul 28 01:21:31 2006 From: quintela at redhat.com (Juan Quintela) Date: Fri, 28 Jul 2006 03:21:31 +0200 Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 In-Reply-To: <44C6B1E13F20D6takebe_akio@jp.fujitsu.com> References: <3AC6B15930FA26takebe_akio@jp.fujitsu.com> <20060727164049.GH10460@vino.americas.hpqcorp.net> <44C6B1E13F20D6takebe_akio@jp.fujitsu.com> Message-ID: <1154049691.2439.33.camel@anano.mitica> On Fri, 2006-07-28 at 10:00 +0900, Akio Takebe wrote: > Hi, Aron > > Thank you for your good explanation. > I have one question. > > > Send your patches to me and cc fedora-xen and xen-ia64-devel. > > To know what hypervisor changeset to use, check the spec file: > > cd kernel-cvs-ia64/devel > > grep -m1 xen_hv_cset kernel-2.6.spec > Which is this cset xen-ustable's cset or xen-ia64-unstable's cset? xen-unstable (only for the HV). As far as I am concerned xen-ia64-unstable don't exist :) Patchs arrive to me though xen-unstable -> linux-2.6-xen (prefered method for core things) Somebody send me a mail or ask me to hg pull for some tree especially for things that don't make sense to be on xen-unstable because they are based in a quite old kernel. Later, Juan. From aron at hp.com Fri Jul 28 04:41:28 2006 From: aron at hp.com (Aron Griffis) Date: Fri, 28 Jul 2006 00:41:28 -0400 Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 In-Reply-To: <1154047868.2439.15.camel@anano.mitica> References: <3DC6B160028E17takebe_akio@jp.fujitsu.com> <3AC6B15930FA26takebe_akio@jp.fujitsu.com> <20060727164049.GH10460@vino.americas.hpqcorp.net> <1154047868.2439.15.camel@anano.mitica> Message-ID: <20060728044128.GA19498@olive.flatmonk> Juan Quintela wrote: [Thu Jul 27 2006, 08:51:08PM EDT] > > http://xenbits.xensource.com/linux-2.6-xen.hg > > - sparse tree patches applied to 2.6.16 kernel, > > maintained mostly-daily by Christian > > http://xenbits.xensource.com/ext/linux-2.6.tip-xen.hg > > - sparse tree patches merged to 2.6.18 kernel, > > maintained sporadically by Chris Wright > > PLUS Juan's own patches to make it all work together. > > Actually this last two are also full trees, not sparse trees. It is > way, way easier to work against a full tree that against a sparse tree. That's what I meant, I just said it unclearly :-) Thanks, Aron From aron at hp.com Fri Jul 28 04:42:55 2006 From: aron at hp.com (Aron Griffis) Date: Fri, 28 Jul 2006 00:42:55 -0400 Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 In-Reply-To: <44C6B1E13F20D6takebe_akio@jp.fujitsu.com> References: <3AC6B15930FA26takebe_akio@jp.fujitsu.com> <20060727164049.GH10460@vino.americas.hpqcorp.net> <44C6B1E13F20D6takebe_akio@jp.fujitsu.com> Message-ID: <20060728044254.GB19498@olive.flatmonk> Akio Takebe wrote: [Thu Jul 27 2006, 09:00:41PM EDT] > > To know what hypervisor changeset to use, check the spec file: > > cd kernel-cvs-ia64/devel > > grep -m1 xen_hv_cset kernel-2.6.spec > Which is this cset xen-ustable's cset or xen-ia64-unstable's cset? xen-unstable Aron From aron at hp.com Fri Jul 28 04:45:31 2006 From: aron at hp.com (Aron Griffis) Date: Fri, 28 Jul 2006 00:45:31 -0400 Subject: [Fedora-xen] [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 In-Reply-To: References: Message-ID: <20060728044531.GC19498@olive.flatmonk> Zhang, Xiantao wrote: [Thu Jul 27 2006, 09:13:23PM EDT] > Thanks you for detail. Seems very clear now. I have the same > question with Akio. Which Cset for xen and xenLinux is using for > debug? Are they compatible? I have a tracker on my web page that might help answer this question. It updates automatically. See the top of http://free.linux.hp.com/~agriffis/ Aron From aron at hp.com Fri Jul 28 12:06:54 2006 From: aron at hp.com (Aron Griffis) Date: Fri, 28 Jul 2006 08:06:54 -0400 Subject: [Fedora-xen] [PATCH-UPDATE] Enable building xen on ia64 In-Reply-To: <20060727151414.GG10460@vino.americas.hpqcorp.net> References: <20060727151414.GG10460@vino.americas.hpqcorp.net> Message-ID: <20060728120654.GA31195@olive.flatmonk> Hi Juan, Please don't forget to apply these spec changes once you've updated linux-2.6-xen.patch. - First, enable building xen on ia64. - Second, get rid of the redundant buildkdump setting for ppc64 and ppc64iseries, since buildkdump=1 is already the default (for that reason, cc'd Don Zickus who seems to have added it) - Third, update config-xen-ia64. It was originally written assuming inheritance of config-xen-xen which has now gone away. Thanks, Aron configs/config-xen-ia64 | 21 ++++++++++----------- kernel-2.6.spec | 15 ++++----------- 2 files changed, 14 insertions(+), 22 deletions(-) Signed-off-by: Aron Griffis diff -r bfc3d0da96c9 devel/kernel-2.6.spec --- a/devel/kernel-2.6.spec Fri Jul 28 07:26:52 2006 -0400 +++ b/devel/kernel-2.6.spec Fri Jul 28 07:58:50 2006 -0400 @@ -65,14 +65,8 @@ Summary: The Linux kernel (the core of t %endif # Xen only builds on i686, x86_64 and ia64 ... -#%ifnarch i686 x86_64 ia64 -%ifnarch i686 x86_64 +%ifnarch i686 x86_64 ia64 %define buildxen 0 -%endif - - -%ifarch ppc64 ppc64iseries -%define buildkdump 1 %endif # Second, per-architecture exclusions (ifarch) @@ -818,11 +812,10 @@ cd linux-%{kversion}.%{_target_cpu} #%patch951 -p1 %patch950 -p1 -b .p.xen # -# ... and back out all the ia64-specific sections, as they currently prevent +# ... and back out all the tpm-specific sections, as they currently prevent # non-xen builds from working. -# Now also with tpm -# -for f in `find drivers/char/tpm arch/ia64/ include/asm-ia64/ include/xen/interface/arch-ia64.h* -type f -name "*.p.xen"` ; do \ +# +for f in `find drivers/char/tpm -type f -name "*.p.xen"` ; do \ g=`dirname $f`/`basename $f .p.xen`; \ mv "$f" "$g"; \ if [ ! -s "$g" ] ; then rm -f "$g" ; fi; \ diff -r bfc3d0da96c9 devel/configs/config-xen-ia64 --- a/devel/configs/config-xen-ia64 Fri Jul 28 07:26:52 2006 -0400 +++ b/devel/configs/config-xen-ia64 Fri Jul 28 07:58:50 2006 -0400 @@ -1,14 +1,3 @@ -# override i686 xen - -# CONFIG_X86 is not set -# CONFIG_X86_XEN is not set -CONFIG_IA64=y -CONFIG_XEN=y -CONFIG_XEN_IA64_DOM0_VP=y -CONFIG_XEN_DISABLE_SERIAL=y - -# override ia64 generic - # CONFIG_IA64_GENERIC is not set CONFIG_IA64_DIG=y # CONFIG_DISCONTIGMEM_MANUAL is not set @@ -16,5 +5,15 @@ CONFIG_FLATMEM_MANUAL=y CONFIG_FLATMEM_MANUAL=y CONFIG_FORCE_MAX_ZONEORDER=11 +CONFIG_XEN=y +CONFIG_XEN_IA64_DOM0_VP=y +CONFIG_XEN_DISABLE_SERIAL=y +# CONFIG_XEN_BLKDEV_TAP is not set +# CONFIG_XEN_PCIDEV_BACKEND is not set +# CONFIG_XEN_PCIDEV_BACKEND_VPCI is not set +# CONFIG_XEN_PCIDEV_BACKEND_PASS is not set +# CONFIG_XEN_PCIDEV_BE_DEBUG is not set +# CONFIG_XEN_TPMDEV_BACKEND is not set + # internal #defines conflict with xen-ia64 # CONFIG_FB_NEOMAGIC is not set From aron at hp.com Fri Jul 28 12:31:58 2006 From: aron at hp.com (Aron Griffis) Date: Fri, 28 Jul 2006 08:31:58 -0400 Subject: [Fedora-xen] Re: [PATCH 0 of 5] fix linux-2.6-xen-fedora on ia64 In-Reply-To: <1154047385.2439.11.camel@anano.mitica> References: <1154047385.2439.11.camel@anano.mitica> Message-ID: <20060728123158.GC31195@olive.flatmonk> Juan Quintela wrote: [Thu Jul 27 2006, 08:43:05PM EDT] > All of 5 of them are integrated on linux-2.6-xen-fedora (as you can > guess, none of them is controversial). Thank you, Juan :-) From dzickus at redhat.com Fri Jul 28 14:40:06 2006 From: dzickus at redhat.com (Don Zickus) Date: Fri, 28 Jul 2006 10:40:06 -0400 Subject: [Fedora-xen] [PATCH-UPDATE] Enable building xen on ia64 In-Reply-To: <20060728120654.GA31195@olive.flatmonk> References: <20060727151414.GG10460@vino.americas.hpqcorp.net> <20060728120654.GA31195@olive.flatmonk> Message-ID: <20060728144006.GK31574@redhat.com> On Fri, Jul 28, 2006 at 08:06:54AM -0400, Aron Griffis wrote: > Hi Juan, > > Please don't forget to apply these spec changes once you've updated > linux-2.6-xen.patch. > > - First, enable building xen on ia64. > > - Second, get rid of the redundant buildkdump setting for ppc64 and > ppc64iseries, since buildkdump=1 is already the default (for that > reason, cc'd Don Zickus who seems to have added it) > > diff -r bfc3d0da96c9 devel/kernel-2.6.spec > --- a/devel/kernel-2.6.spec Fri Jul 28 07:26:52 2006 -0400 > +++ b/devel/kernel-2.6.spec Fri Jul 28 07:58:50 2006 -0400 > @@ -65,14 +65,8 @@ Summary: The Linux kernel (the core of t > %endif > > # Xen only builds on i686, x86_64 and ia64 ... > -#%ifnarch i686 x86_64 ia64 > -%ifnarch i686 x86_64 > +%ifnarch i686 x86_64 ia64 > %define buildxen 0 > -%endif > - > - > -%ifarch ppc64 ppc64iseries > -%define buildkdump 1 > %endif > NAK. You missed the couple of lines above the #Xen only.. where buildkudmp is disabled. With Juan's recent change of moving the 'buildxen' definition, I can consolidate the ppc64.. stuff and the x86.. stuff together. That is the better fix. But PLEASE do not remove the buildkdump line. Cheers, Don From aron at hp.com Fri Jul 28 14:48:26 2006 From: aron at hp.com (Aron Griffis) Date: Fri, 28 Jul 2006 10:48:26 -0400 Subject: [Fedora-xen] [PATCH-UPDATE] Enable building xen on ia64 In-Reply-To: <20060728144006.GK31574@redhat.com> References: <20060727151414.GG10460@vino.americas.hpqcorp.net> <20060728120654.GA31195@olive.flatmonk> <20060728144006.GK31574@redhat.com> Message-ID: <20060728144826.GA16297@vino.americas.hpqcorp.net> Don Zickus wrote: [Fri Jul 28 2006, 10:40:06AM EDT] > NAK. You missed the couple of lines above the #Xen only.. where > buildkudmp is disabled. With Juan's recent change of moving the > 'buildxen' definition, I can consolidate the ppc64.. stuff and the x86.. > stuff together. That is the better fix. But PLEASE do not remove the > buildkdump line. Gah, sorry I misread that! I should have paid attention to that bad feeling about "fixing" something outside of the ia64 sections... :-| Aron From russell at flora.ca Fri Jul 28 14:52:45 2006 From: russell at flora.ca (Russell McOrmond) Date: Fri, 28 Jul 2006 10:52:45 -0400 Subject: [Fedora-xen] Tracking some problems: XenU's crashing, sockets not listening Message-ID: <44CA24BD.803@flora.ca> Sorry for just subscribing and jumping in, but I've got some problems that I'm wanting to try to find a workaround or fix for fairly quickly. XenU has Kernel panic (xennet?) https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199944 Thoughts? These problems may not be related: a) A XenU crashed, when fortunately I had an 'xm console' open so I could see the kernel panic. Other XenU's have crashed since (I had to reboot some this morning), but I haven't captured anything interesting as output since. b) Programs listening on a port for connections have started to refuse connections until I restart the application. This is also recent, and may just be a coincidence that it is only happening on Xen servers or around the same time that the XenU's started to turn into Zombie-*'s Looking around the various archives/docs the only thing I could find of any problems with applications related to TLS. While I thought that the FC5 updates would set things up 'right', I've done the following this morning in each of my XenU's. # mv /lib/tls /lib/tls.disabled # echo "hwcap 0 nosegneg" >/etc/ld.so.conf.d/nosegneg.conf I then went looking for libraries with a 'tls/' and found: openldap-servers-2.3.19-4 [root at bankura tls]# rpm -ql openldap-servers | grep tls/ /usr/lib/tls/i486 /usr/lib/tls/i486/libslapd_db-4.4.so /usr/lib/tls/i586 /usr/lib/tls/i586/libslapd_db-4.4.so /usr/lib/tls/i686 /usr/lib/tls/i686/libslapd_db-4.4.so -- Russell McOrmond, Internet Consultant: Please help us tell the Canadian Parliament to protect our property rights as owners of Information Technology. Sign the petition! http://www.digital-copyright.ca/petition/ict/ "The government, lobbied by legacy copyright holders and hardware manufacturers, can pry my camcorder, computer, home theater, or portable media player from my cold dead hands!" From Patrick.Petit at Sun.COM Fri Jul 28 17:38:45 2006 From: Patrick.Petit at Sun.COM (Patrick Petit) Date: Fri, 28 Jul 2006 19:38:45 +0200 Subject: [Fedora-xen] Re: trouble starting xend In-Reply-To: <44C64CAF.1070309@sun.com> References: <44C64CAF.1070309@sun.com> Message-ID: <44CA4BA5.6060006@sun.com> Nobody knows or would care to help out? Thanks - Patrick > Hi There, > > After upgrading from 'kernel-xen0-2.6.17-1.2139_FC5' to > 'kernel-xen0-2.6.17-1.2157_FC5' I am seeing the following error when I > start xend > > # uname -a > Linux jesma55 2.6.17-1.2157_FC5xen0 #1 SMP Wed Jul 12 00:28:36 EDT > 2006 i686 athlon i386 GNU/Linux > > # cat /var/log/xend.log > > [2006-07-25 16:29:50 xend] INFO (SrvDaemon:185) Xend exited with > status 1. > > [2006-07-25 16:49:49 xend] INFO (SrvDaemon:285) Xend Daemon started > > [2006-07-25 16:49:49 xend] ERROR (SrvDaemon:299) Exception starting > xend ((22, 'Invalid argument')) > > Traceback (most recent call last): > > File > "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line > 288, in run > > xinfo = xc.xeninfo() > > error: (22, 'Invalid argument') > > [2006-07-25 16:49:49 xend] INFO (SrvDaemon:185) Xend exited with > status 1. > > > I use Python 2.4.2 > > Any help appreciated. > > Thanks > - Patrick > > > > From garysiao at gmail.com Mon Jul 31 20:25:42 2006 From: garysiao at gmail.com (Gary Siao) Date: Mon, 31 Jul 2006 16:25:42 -0400 Subject: [Fedora-xen] XEN image Message-ID: hi gurus is there a way we can clone or backup the XEN server to a DVD and use it to restoring the server unto another server... thanks ! gary -------------- next part -------------- An HTML attachment was scrubbed... URL: From lamont at gurulabs.com Mon Jul 31 21:25:40 2006 From: lamont at gurulabs.com (Lamont R. Peterson) Date: Mon, 31 Jul 2006 15:25:40 -0600 Subject: [Fedora-xen] XEN image In-Reply-To: References: Message-ID: <200607311525.45255.lamont@gurulabs.com> On Monday 31 July 2006 02:25pm, Gary Siao wrote: > hi gurus > > is there a way we can clone or backup the XEN server to a DVD and use it to > restoring the server unto another server... I would recommend creating a Kickstart installation that will build your Xen setup and Dom0 the way you want. In it's %post section, you can run a script that will copy your configs onto the newly installed box from some file server. -- Lamont R. Peterson Senior Instructor Guru Labs, L.C. [ http://www.GuruLabs.com/ ] GPG Key fingerprint: F98C E31A 5C4C 834A BCAB 8CB3 F980 6C97 DC0D D409 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From fedora at adslpipe.co.uk Mon Jul 31 07:53:29 2006 From: fedora at adslpipe.co.uk (Andy Burns) Date: Mon, 31 Jul 2006 08:53:29 +0100 Subject: [Fedora-xen] PAE *is* now required for Xen [was re: Heads-up: ... ] In-Reply-To: <20060518014851.GA17408@redhat.com> References: <1147889279.13113.22.camel@aglarond.local><69304d110605171349o65d40cadn7d63fd869b341e83@mail.gmail.com> <20060518014851.GA17408@redhat.com> Message-ID: <44CDB6F9.9020005@adslpipe.co.uk> Dave Jones wrote: > On Wed, May 17, 2006 at 10:49:03PM +0200, Antonio Vargas wrote: > > > >2) Switch the 32-bit xen kernels to require PAE. For most "current" > > >non-laptop hardware, this is a non-issue. It does mean that xen won't > > >work a lot of earlier PentiumM laptops > > > > xen always needed p6 hardware (didnt run on k6-II for example), > > and AFAIK p6 supports PAE always, so not any lose here i think > > Sadly, not the case.. > Celerons, and some Pentium-M's (as Jeremy noted above) are > P6 class, yet lack PAE. Ouch, this just bit my Dell D800 Pentium M 1.3GHz :-( Obviously there haven't been Xen kernels available for a while, the previous one I had was 2.6.17-1.2307_FC6xen which worked for me, now I've updated to 2.6.17-1.2462.fc6xen and can't boot due to lack of PAE, presumably this does at least mean fc6t2 is "real close now" ... I was already considering upgrading to a D820 to get HVM capability once the merom CPUs hit the shelves, I guess this will provide additional impetus ...