From listas at openlogic.com.br Mon Jan 2 10:42:03 2006 From: listas at openlogic.com.br (Leonardo Pinto) Date: Mon, 2 Jan 2006 10:42:03 -0000 Subject: [Fedora-xen] Re: [Xen-users] Xen-Fedora4 or 5, dead-end... Message-ID: <20060102124203.8417E102FCD@openlogic.com.br> > Did changing the MTU size help? Yes, its help was of much value. However it is as I said before: The Xen of the Fedora Core 5 is much more steady, however the virtual machine does not obtain to see the interface eth0, being without network... > Also is there a package for fedora core 5 already? I didnt even know > fedora core 5 was released? Thanks in advance! Yes! It reads this: http://fedoranews.org/wiki/Fedora_Weekly_News_Issue_27 Greetings, -- Leonardo Pinto listas#openlogic dot com br ________________________________________________ Mensagem enviada usando OpenLogic WebMail 2.7.2 From listas at openlogic.com.br Thu Jan 5 10:25:44 2006 From: listas at openlogic.com.br (Leonardo Pinto) Date: Thu, 5 Jan 2006 10:25:44 -0000 Subject: [Fedora-xen] Personalizing names of "vifX.X" Message-ID: <20060105122544.2B305102FCE@openlogic.com.br> Somebody could answer me if is possible to modify the standard of the name of the virtual interfaces vifX.X? And where I can make these alterations for my proper personalizations? Thankful, -- Leonardo Pinto listas#openlogic dot com br ________________________________________________ Mensagem enviada usando OpenLogic WebMail 2.7.2 From listas at openlogic.com.br Thu Jan 5 13:59:58 2006 From: listas at openlogic.com.br (Leonardo Pinto) Date: Thu, 5 Jan 2006 13:59:58 -0000 Subject: [Fedora-xen] Re: [Xen-users] Personalizing names of "vifX.X" Message-ID: <20060105155958.97918102FCE@openlogic.com.br> Here everything functioned well. I applied the patches in the hand in following the files of the FC4: "/etc/xen/scripts/vif-common.sh" and "/usr/lib/python/xen/xend/server/netif.py" Remaining only obviously the last adjustment in the configuration file of the virtual machine: "vif = [ ' mac=aa:00:00:00:00:11, bridge=isp0, vifname=isp0.0 ' ]" Special thanks for "PAINCHAUD Christophe". -- Leonardo Pinto listas#openlogic dot com br > I tried to apply it to the 2 files vif-common.sh and netif.py however the vifnames specified inside the config don't work. Any ideas ?On 1/5/06, PAINCHAUD Christophe > > > <cpainchaud at ecritel.net> wrote: > A dev just pointed me this link : > http://xenbits.xensource.com/xen-unstable.hg?cmd=changeset;node=95f84e37c90d573dd01cc29db5b81ffb5f86f84a > > Regards... > > Christophe PAINCHAUD > > > Somebody could answer me if is possible to modify the standard of the name > of the virtual interfaces vifX.X? And where I can make these alterations for > my proper personalizations? > > Thankful, > -- > Leonardo Pinto ________________________________________________ Mensagem enviada usando OpenLogic WebMail 2.7.2 From xen.mails at gmail.com Thu Jan 5 19:18:46 2006 From: xen.mails at gmail.com (Anand) Date: Fri, 6 Jan 2006 00:48:46 +0530 Subject: [Fedora-xen] Re: [Xen-users] Personalizing names of "vifX.X" In-Reply-To: <20060105155958.97918102FCE@openlogic.com.br> References: <20060105155958.97918102FCE@openlogic.com.br> Message-ID: My mistake i was still trying to use vifname= setting as a seperate directive instead of using it with the vif= setting. Works like a charm. Thanks everyone. On 1/5/06, Leonardo Pinto wrote: > > Here everything functioned well. I applied the patches in the hand in > following the files of the FC4: > > "/etc/xen/scripts/vif-common.sh" and > "/usr/lib/python/xen/xend/server/netif.py" > > Remaining only obviously the last adjustment in the configuration file of > the virtual machine: > > "vif = [ ' mac=aa:00:00:00:00:11, bridge=isp0, vifname=isp0.0 ' ]" > > Special thanks for "PAINCHAUD Christophe". > > -- > Leonardo Pinto > listas#openlogic dot com br > > > I tried to apply it to the 2 files vif-common.sh and netif.py however > the > vifnames specified inside the config don't work. Any ideas ?On 1/5/06, > PAINCHAUD Christophe > > > > > > <cpainchaud at ecritel.net> wrote: > > A dev just pointed me this link : > > > > http://xenbits.xensource.com/xen-unstable.hg?cmd=changeset;node=95f84e37c90d573dd01cc29db5b81ffb5f86f84a > > > > Regards... > > > > Christophe PAINCHAUD > > > > > > Somebody could answer me if is possible to modify the standard of the > name > > of the virtual interfaces vifX.X? And where I can make these alterations > for > > my proper personalizations? > > > > Thankful, > > -- > > Leonardo Pinto > > > ________________________________________________ > Mensagem enviada usando OpenLogic WebMail 2.7.2 > > -- regards, Anand -------------- next part -------------- An HTML attachment was scrubbed... URL: From xen.mails at gmail.com Fri Jan 6 13:28:14 2006 From: xen.mails at gmail.com (Anand) Date: Fri, 6 Jan 2006 18:58:14 +0530 Subject: [Fedora-xen] Re: [Xen-users] Personalizing names of "vifX.X" In-Reply-To: <20060105155958.97918102FCE@openlogic.com.br> References: <20060105155958.97918102FCE@openlogic.com.br> Message-ID: I am using the custom vif names now inside domU config. However while booting up and shutting down domU, i see this inside /var/log/messages in dom0 Jan 6 18:54:20 xen net.agent[8922]: remove event not handled Jan 6 18:54:36 xen hald[4869]: Timed out waiting for hotplug event 1148. Rebasing to 1149 Jan 6 18:54:37 xen hal.hotplug[9720]: timout(10000 ms) waiting for /class/net/vif3.0 This is the third time a domU has been booted on this machine so i can understand the vif3.0, however i have put a custom name for the vifname as vm01. ifconfig from dom0 eth0 Link encap:Ethernet HWaddr 00:08:A1:50:FA:19 inet addr:192.168.1.250 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::208:a1ff:fe50:fa19/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7828 errors:0 dropped:0 overruns:0 frame:0 TX packets:6329 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3537327 (3.3 MiB) TX bytes:835757 (816.1 KiB) 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:1 errors:0 dropped:0 overruns:0 frame:0 TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:76 (76.0 b) TX bytes:76 (76.0 b) 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:7811 errors:0 dropped:0 overruns:0 frame:0 TX packets:6449 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3548430 (3.3 MiB) TX bytes:859382 (839.2 KiB) Interrupt:16 Base address:0xa000 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:6332 errors:0 dropped:0 overruns:0 frame:0 TX packets:7830 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:837371 (817.7 KiB) TX bytes:3537471 (3.3 MiB) vm01 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:7 errors:0 dropped:0 overruns:0 frame:0 TX packets:55 errors:0 dropped:14 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:762 (762.0 b) TX bytes:11140 (10.8 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:341 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:31190 (30.4 KiB) TX bytes:378 (378.0 b) ifconfig from inside domU eth0 Link encap:Ethernet HWaddr AA:00:00:18:98:FB inet addr:192.168.1.105 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::a800:ff:fe18:98fb/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:56 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11226 (10.9 KiB) TX bytes:762 (762.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:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Any help would be appreciated. On 1/5/06, Leonardo Pinto wrote: > > Here everything functioned well. I applied the patches in the hand in > following the files of the FC4: > > "/etc/xen/scripts/vif-common.sh" and > "/usr/lib/python/xen/xend/server/netif.py" > > Remaining only obviously the last adjustment in the configuration file of > the virtual machine: > > "vif = [ ' mac=aa:00:00:00:00:11, bridge=isp0, vifname=isp0.0 ' ]" > > Special thanks for "PAINCHAUD Christophe". > > -- > Leonardo Pinto > listas#openlogic dot com br > > > I tried to apply it to the 2 files vif-common.sh and netif.py however > the > vifnames specified inside the config don't work. Any ideas ?On 1/5/06, > PAINCHAUD Christophe > > > > > > <cpainchaud at ecritel.net> wrote: > > A dev just pointed me this link : > > > > http://xenbits.xensource.com/xen-unstable.hg?cmd=changeset;node=95f84e37c90d573dd01cc29db5b81ffb5f86f84a > > > > Regards... > > > > Christophe PAINCHAUD > > > > > > Somebody could answer me if is possible to modify the standard of the > name > > of the virtual interfaces vifX.X? And where I can make these alterations > for > > my proper personalizations? > > > > Thankful, > > -- > > Leonardo Pinto > > > ________________________________________________ > Mensagem enviada usando OpenLogic WebMail 2.7.2 > > -- regards, Anand -------------- next part -------------- An HTML attachment was scrubbed... URL: From listas at openlogic.com.br Sun Jan 8 11:26:43 2006 From: listas at openlogic.com.br (Leonardo Pinto) Date: Sun, 8 Jan 2006 11:26:43 -0000 Subject: [Fedora-xen] Warnings in the boot Message-ID: <20060108132643.24271102FCC@openlogic.com.br> After to have brought up to date xen for the version 2.6.12.6-xen3_7.1_fc4, I started to receive these errors in boot from the guest: 1. Error: Montando sistemas de arquivos sys: [ OK ] modprobe: FATAL: Error inserting rtc (/lib/modules/2.6.12.6-xen3_7.1_fc4/kernel/drivers/char/rtc.ko): Input/output error 2. Error: INIT: Entering runlevel: 4 Inicializando em modo n\uffffo-interativo Iniciando hotplug: cat: */class: No such file or directory cat: */vendor: No such file or directory cat: */device: No such file or directory cat: */subsystem_vendor: No such file or directory cat: */subsystem_device: No such file or directory Bad PCI agent invocation [ OK ] 3. Error: Iniciando Kernel Logger (klogd): [ OK ] Warning, no capability kernel module found, is it builtin? Service will not start without capabilities. Although everything to function duly, what I could disable to finish with these warnings? -- Leonardo Pinto listas#openlogic dot com br ________________________________________________ Mensagem enviada usando OpenLogic WebMail 2.7.2 From fedora at adslpipe.co.uk Sun Jan 8 14:25:23 2006 From: fedora at adslpipe.co.uk (Andy Burns) Date: Sun, 08 Jan 2006 14:25:23 +0000 Subject: [Fedora-xen] Xen3 stability, x86_64 status? Message-ID: <43C120D3.70002@adslpipe.co.uk> Daniel Veillard wrote: > Paul Wouters wrote: > >> Does it run on fedora x86_64 yet? > > I didn't tried myself, running on a i686 ATM. The xen package is available > on x86_64, but I don't see the kernel-xen packages Any news on x86_64 kernels in FC5/rawhide? Alternatively can anyone confirm whether or not the xensource kernels work on top of the 64bit hypervisor in FC5/rawhide? From veillard at redhat.com Mon Jan 9 09:08:43 2006 From: veillard at redhat.com (Daniel Veillard) Date: Mon, 9 Jan 2006 04:08:43 -0500 Subject: [Fedora-xen] Xen3 stability, x86_64 status? In-Reply-To: <43C120D3.70002@adslpipe.co.uk> References: <43C120D3.70002@adslpipe.co.uk> Message-ID: <20060109090843.GA10036@redhat.com> On Sun, Jan 08, 2006 at 02:25:23PM +0000, Andy Burns wrote: > Daniel Veillard wrote: > > >Paul Wouters wrote: > > > >>Does it run on fedora x86_64 yet? > > > >I didn't tried myself, running on a i686 ATM. The xen package is available > >on x86_64, but I don't see the kernel-xen packages > > Any news on x86_64 kernels in FC5/rawhide? Alternatively can anyone > confirm whether or not the xensource kernels work on top of the 64bit > hypervisor in FC5/rawhide? Apparently Philip Van Hoof was able to make images for FC4 working, I don't see why FC5 would generate a hard incompatibility, but well if something can break it usually will ... http://pvanhoof.be/blog/index.php/2005/12/31/82-xen-ready-to-go-images-for-x86_64 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 cpainchaud at ecritel.net Thu Jan 5 13:59:32 2006 From: cpainchaud at ecritel.net (PAINCHAUD Christophe) Date: Thu, 5 Jan 2006 14:59:32 +0100 Subject: [Fedora-xen] RE: [Xen-users] Personalizing names of "vifX.X" Message-ID: A dev just pointed me this link : http://xenbits.xensource.com/xen-unstable.hg?cmd=changeset;node=95f84e37c90d 573dd01cc29db5b81ffb5f86f84a Regards... Christophe PAINCHAUD -----Message d'origine----- De?: xen-users-bounces at lists.xensource.com [mailto:xen-users-bounces at lists.xensource.com] De la part de Leonardo Pinto Envoy??: Thursday, January 05, 2006 11:26 AM ??: Xen Users Cc?: Fedora Xen Objet?: [Xen-users] Personalizing names of "vifX.X" Somebody could answer me if is possible to modify the standard of the name of the virtual interfaces vifX.X? And where I can make these alterations for my proper personalizations? Thankful, -- Leonardo Pinto listas#openlogic dot com br -------------- next part -------------- An HTML attachment was scrubbed... URL: From xen.mails at gmail.com Thu Jan 5 14:33:28 2006 From: xen.mails at gmail.com (Anand) Date: Thu, 5 Jan 2006 20:03:28 +0530 Subject: [Fedora-xen] Re: [Xen-users] Personalizing names of "vifX.X" In-Reply-To: References: Message-ID: I tried to apply it to the 2 files vif-common.sh and netif.py however the vifnames specified inside the config don't work. Any ideas ? On 1/5/06, PAINCHAUD Christophe wrote: > > > A dev just pointed me this link : > > http://xenbits.xensource.com/xen-unstable.hg?cmd=changeset;node=95f84e37c90d573dd01cc29db5b81ffb5f86f84a > > Regards... > > Christophe PAINCHAUD > > -----Message d'origine----- > De : xen-users-bounces at lists.xensource.com [ > mailto:xen-users-bounces at lists.xensource.com] > De la part de Leonardo Pinto > Envoy? : Thursday, January 05, 2006 11:26 AM > ? : Xen Users > Cc : Fedora Xen > Objet : [Xen-users] Personalizing names of "vifX.X" > > Somebody could answer me if is possible to modify the standard of the name > of the virtual interfaces vifX.X? And where I can make these alterations > for > my proper personalizations? > > Thankful, > > -- > Leonardo Pinto > listas#openlogic dot com br > > _______________________________________________ > Xen-users mailing list > Xen-users at lists.xensource.com > http://lists.xensource.com/xen-users > > -- regards, Anand -------------- next part -------------- An HTML attachment was scrubbed... URL: From listas at openlogic.com.br Sat Jan 14 23:17:03 2006 From: listas at openlogic.com.br (Leonardo Pinto) Date: Sat, 14 Jan 2006 23:17:03 -0000 Subject: [Fedora-xen] =?iso-8859-1?q?Re=3A_=28linux-br=29_Par=E2metros_em?= =?iso-8859-1?q?_shell_script?= Message-ID: <20060115011703.266CD102FCD@openlogic.com.br> Falou e disse camarada... # ./tes a b c d e f g h i j k l a, b, c, d, e, f, g, h, i, j, k, l Essa foi a solu??o mais natural certamente: echo ... ${10}, ${11}, ${12} Tinha visto essas chaves em alguns scripts mais profissionais, e fiquei sem entender. Agora ?tudo? faz sentido. Mas s? n?o entendi o por que dos programadores utilizarem "indiscriminadamente" elas em todas as vari?veis. Sds, -- Leonardo Pinto listas#openlogic dot com br > On Saturday 14 January 2006 19:24, Leonardo Pinto wrote: > #!/bin/bash > echo $1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12 > > Ol?, > > $ ./tes a b c d e f g h i j k l > a, b, c, d, e, f, g, h, i, a0, a1, a2 > a, b, c, d, e, f, g, h, i, j, k, l > > $ cat tes > #!/bin/sh > echo $1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12 > echo ${1}, ${2}, ${3}, ${4}, ${5}, ${6}, ${7}, ${8}, ${9}, ${10}, ${11}, ${12} > > Procure na net em algum tutorial de Shell Script por "parameter substitution". > > Herbert. ________________________________________________ Mensagem enviada usando OpenLogic WebMail 2.7.2 From fraser at georgetown.wehave.net Wed Jan 18 15:07:31 2006 From: fraser at georgetown.wehave.net (Fraser Campbell) Date: Wed, 18 Jan 2006 10:07:31 -0500 Subject: [Fedora-xen] PAE enabled Xen? Message-ID: <43CE59B3.9090609@georgetown.wehave.net> Hi, I'm wondering if there are any plans to provide a PAE enabled version of xen, kernel-xen-hypervisor and kernel-xen-guest? We are doing extensive testing with FC5 and large memory machines (8GB so far). For now I will track down the source RPMs and look at rebuilding them. Thanks! From bstein at redhat.com Wed Jan 18 23:49:00 2006 From: bstein at redhat.com (Brian Stein) Date: Wed, 18 Jan 2006 18:49:00 -0500 Subject: [Fedora-xen] PAE enabled Xen? In-Reply-To: <43CE59B3.9090609@georgetown.wehave.net> References: <43CE59B3.9090609@georgetown.wehave.net> Message-ID: <1137628141.3250.16.camel@localhost.localdomain> On Wed, 2006-01-18 at 10:07 -0500, Fraser Campbell wrote: > Hi, > > I'm wondering if there are any plans to provide a PAE enabled version of > xen, kernel-xen-hypervisor and kernel-xen-guest? PAE is in the current plan and will be included once a few outstanding issues are resolved. > We are doing extensive testing with FC5 and large memory machines (8GB > so far). What tests are you running to evaluate FC5t2? -- Brian Stein Red Hat, Inc. From sfolkwil at redhat.com Thu Jan 19 14:32:02 2006 From: sfolkwil at redhat.com (Sam Folk-Williams) Date: Thu, 19 Jan 2006 09:32:02 -0500 Subject: [Fedora-xen] documentation/packages for xen on FC 5? Message-ID: <43CFA2E2.2010603@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm trying to get up to speed on xen from a user/support perspective. I've found the howto for FC 4 (and the link to the packages on Riel's people page) very helpful. Is there something similar for FC 5? Generally I'm wondering if the packages installed via yum from the main devel repos will work, or if someone has a link to packages for FC5. Also, would be more than happy to help contribute to documentation for the project. Thanks, Sam - - -- Sam Folk-Williams, RHCE Red Hat Global Support Services GPG ID: 1024D/1B0D46BA Public Key: http://people.redhat.com/sfolkwil/sfw.asc - -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFDz6JBzOw+vBsNRroRAnlPAJ0T0M6TZKgBiWXiirtTl46UY+QvTQCfQvDE K/Ebepw8RkPuzc7zrd41WwE= =YeKA - -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFDz6LhzOw+vBsNRroRAnySAJ0X9NdwiBIetmhkCXcXSgDRhu9nSwCePrXz bsNjRSVGhsQBo9lWAK+feQY= =qXnQ -----END PGP SIGNATURE----- From waipeng_yip at portalphenom.com Thu Jan 19 15:52:30 2006 From: waipeng_yip at portalphenom.com (Yip Wai Peng) Date: Thu, 19 Jan 2006 23:52:30 +0800 Subject: [Fedora-xen] Hang when starting xenU using riel's packages Message-ID: <200601192352.30745.waipeng_yip@portalphenom.com> Hi all, I am using kernel-xenU, kernel-xen0, and xen-3 from http://people.redhat.com/~riel/xen_for_fc4/. xen0 boots up fine, but when I start xenU, it hangs at the below screen. I have already moved /lib/tls out of the way. --------- *************************************************************** *************************************************************** ** WARNING: Currently emulating unsupported memory accesses ** ** in /lib/tls libraries. The emulation is very ** ** slow. To ensure full performance you should ** ** execute the following as root: ** ** mv /lib/tls /lib/tls.disabled ** ** Offending process: init (pid=1) ** *************************************************************** *************************************************************** Continuing... ---------- My xen config file is as follows: kernel ="/boot/vmlinuz-2.6.12-1.1454_FC4xenU" memory = 128 name = "waipeng" nics = 1 disk = ['phy:/servers/waipeng,hda1,w'] root = "/dev/hda1" extra = "ro selinux=0 3 The log shows this: [2006-01-19 23:43:17 xend] DEBUG (image:156) initDomain: cpu=-1 mem_kb=131072 ssidref=-1 dom=3 [2006-01-19 23:43:17 xend] DEBUG (XendDomainInfo:843) init_domain> Created domain=3 name=waipeng memory=128 [2006-01-19 23:43:17 xend] INFO (XendRoot:141) EVENT> xend.domain.create ['waipeng', 3] [2006-01-19 23:43:17 xend] INFO (image:217) buildDomain os=linux dom=3 vcpus=1 [2006-01-19 23:43:17 xend] DEBUG (image:255) dom = 3 [2006-01-19 23:43:17 xend] DEBUG (image:256) image = /boot/vmlinuz-2.6.12-1.1454_FC4xenU [2006-01-19 23:43:17 xend] DEBUG (image:257) store_evtchn = 1 [2006-01-19 23:43:17 xend] DEBUG (image:258) console_evtchn = 2 [2006-01-19 23:43:17 xend] DEBUG (image:259) cmdline = root=/dev/hda1 ro selinux=0 3 [2006-01-19 23:43:17 xend] DEBUG (image:260) ramdisk = [2006-01-19 23:43:17 xend] DEBUG (image:261) flags = 0 [2006-01-19 23:43:17 xend] DEBUG (image:262) vcpus = 1 [2006-01-19 23:43:17 xend] INFO (xsobj:326) DBMap>introduceDomain> 3 59700 /domain/499d6865-9920-4f87-bc34-6fd4b1933bb3 [2006-01-19 23:43:17 xend] DEBUG (XendDomainInfo:698) writing key availability=online to path /cpu/0 in store [2006-01-19 23:43:17 xend] WARNING (XendDomainInfo:1100) Unknown config field boot [2006-01-19 23:43:17 xend] ERROR (XendDomainInfo:443) ['vif', ['mac', 'aa:00:00:7d:9a:01']] [2006-01-19 23:43:17 xend] INFO (XendRoot:141) EVENT> xend.domain.unpause ['waipeng', 3] Questions: 1) Anybody have encountered this before? How did you managed to solve this? 2) Does the mac error matters? Why is it there in the first place? I would appreciate any help given. Thanks! Wai Peng From fraser at georgetown.wehave.net Thu Jan 19 20:32:32 2006 From: fraser at georgetown.wehave.net (Fraser Campbell) Date: Thu, 19 Jan 2006 15:32:32 -0500 Subject: [Fedora-xen] PAE enabled Xen? In-Reply-To: <1137628141.3250.16.camel@localhost.localdomain> References: <43CE59B3.9090609@georgetown.wehave.net> <1137628141.3250.16.camel@localhost.localdomain> Message-ID: <43CFF760.1070409@georgetown.wehave.net> Brian Stein wrote: >>We are doing extensive testing with FC5 and large memory machines (8GB >>so far). > > > What tests are you running to evaluate FC5t2? Early stages so far, we are testing exclusively around Xen: - simple performance and stress tests - live migration tests Guest filesystems had been using loopback on NFS but we are switching our tests over to NFS root and SAN next week, since loopback on NFS was not promising. We are running both SLES and FC5 in guests. Performance and stability have been about where we expected. Fraser From stuart at elsn.org Thu Jan 19 22:56:57 2006 From: stuart at elsn.org (Stuart Ellis) Date: Thu, 19 Jan 2006 22:56:57 +0000 Subject: [Fedora-xen] documentation/packages for xen on FC 5? In-Reply-To: <43CFA2E2.2010603@redhat.com> References: <43CFA2E2.2010603@redhat.com> Message-ID: <1137711417.3008.25.camel@localhost.localdomain> On Thu, 2006-01-19 at 09:32 -0500, Sam Folk-Williams wrote: > Hi, > > I'm trying to get up to speed on xen from a user/support perspective. > I've found the howto for FC 4 (and the link to the packages on Riel's > people page) very helpful. Is there something similar for FC 5? > Generally I'm wondering if the packages installed via yum from the main > devel repos will work, or if someone has a link to packages for FC5. > > Also, would be more than happy to help contribute to documentation for > the project. As far as I'm aware, the wiki page is pretty much it at the moment, so more would be great. The page here explains how to sign up: http://www.fedoraproject.org/wiki/DocsProject/NewWriters -- Stuart Ellis stuart at elsn.org Fedora Documentation Project: http://fedora.redhat.com/projects/docs/ GPG key ID: 7098ABEA GPG key fingerprint: 68B0 E291 FB19 C845 E60E 9569 292E E365 7098 ABEA -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From sct at redhat.com Fri Jan 20 19:43:20 2006 From: sct at redhat.com (Stephen Tweedie) Date: Fri, 20 Jan 2006 14:43:20 -0500 Subject: [Fedora-xen] Hang when starting xenU using riel's packages In-Reply-To: <200601192352.30745.waipeng_yip@portalphenom.com> References: <200601192352.30745.waipeng_yip@portalphenom.com> Message-ID: <20060120194320.GB24812@devserv.devel.redhat.com> Hi, On Thu, Jan 19, 2006 at 11:52:30PM +0800, Yip Wai Peng wrote: > I am using kernel-xenU, kernel-xen0, and xen-3 from > http://people.redhat.com/~riel/xen_for_fc4/. xen0 boots up fine, but when I > start xenU, it hangs at the below screen. I have already moved /lib/tls out > of the way. > --------- > *************************************************************** > *************************************************************** > ** WARNING: Currently emulating unsupported memory accesses ** > ** in /lib/tls libraries. The emulation is very ** > ** slow. To ensure full performance you should ** > ** execute the following as root: ** > ** mv /lib/tls /lib/tls.disabled ** > ** Offending process: init (pid=1) ** > *************************************************************** > *************************************************************** That message is OK --- this just turns up when the Xen kernel comes across a statically linked binary. The distro now has magic to disable tls dynamically at run time for Xen kernels, but that depends on running shared libraries, so static binaries still trigger the tls warning. We have disabled the tls warning in the fc5t2 xen kernels for this reason. The hang is more worrying --- things are supposed to continue after a 5-second timeout after that message, so a hang implies that timers aren't working properly. Can you reproduce this on fc5t2, which has a MUCH newer xen HV/tools/kernel combination? Thanks, Stephen From fraser at georgetown.wehave.net Mon Jan 23 17:16:44 2006 From: fraser at georgetown.wehave.net (Fraser Campbell) Date: Mon, 23 Jan 2006 12:16:44 -0500 Subject: [Fedora-xen] Enabling NFS root for Xen guests in FC5 Message-ID: <43D50F7C.2090402@georgetown.wehave.net> Hi, CONFIG_IP_PNP and suboptions as well as CONFIG_ROOT_NFS should be enabled in Xen guest kernels in order for NFS root to be used in Xen guests. At least kernel-xen-guest-2.6.15-1.29_FC5 and kernel-xen-guest-2.6.14-1.21_FC5 do not have these options enabled. I'm hoping these options can be enabled in future builds or were they intentionally turned off for a reason? Thanks, Fraser From sct at redhat.com Thu Jan 26 21:31:36 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Thu, 26 Jan 2006 16:31:36 -0500 Subject: [Fedora-xen] Enabling NFS root for Xen guests in FC5 In-Reply-To: <43D50F7C.2090402@georgetown.wehave.net> References: <43D50F7C.2090402@georgetown.wehave.net> Message-ID: <1138311096.4013.1.camel@orbit.scot.redhat.com> Hi, On Mon, 2006-01-23 at 12:16 -0500, Fraser Campbell wrote: > CONFIG_IP_PNP and suboptions as well as CONFIG_ROOT_NFS should be > enabled in Xen guest kernels in order for NFS root to be used in Xen guests. Yes, the NFS root option is attractive. But in-kernel NFS root has all sorts of problems. We'd far prefer to have eventual support in the initrd for NFS mounting, and avoid the kernel issue altogether. --Stephen From gawain.lynch at bigpond.com Thu Jan 26 22:26:58 2006 From: gawain.lynch at bigpond.com (Gawain Lynch) Date: Fri, 27 Jan 2006 11:26:58 +1300 Subject: [Fedora-xen] Draft Xen Quick Start for FC5 Message-ID: <1138314419.29913.99.camel@legolas.felicity.net.au> Hi All, I have put up a Quick Start page on the wiki [1] for FC5. This document is based on the original one for FC4 but is updated to take into account changes in FC5/Xen 3. I currently consider it draft but it Works For Me (tm). I would be very grateful if some of you could take it for a spin and let me know any issues/errors/omissions you find. It is not currently linked to the main Xen Wiki page, I'll do that once I am happy that I have it right. Take care, Gawain [1] http://fedoraproject.org/wiki/FedoraFC5XenQuickstart From gawain.lynch at bigpond.com Thu Jan 26 22:34:30 2006 From: gawain.lynch at bigpond.com (Gawain Lynch) Date: Fri, 27 Jan 2006 11:34:30 +1300 Subject: [Fedora-xen] Draft Xen Quick Start for FC5 In-Reply-To: <1138314419.29913.99.camel@legolas.felicity.net.au> References: <1138314419.29913.99.camel@legolas.felicity.net.au> Message-ID: <1138314870.29913.104.camel@legolas.felicity.net.au> Sorry that URL should have been: http://fedoraproject.org/wiki/FedoraCore5XenQuickstart From katzj at redhat.com Thu Jan 26 22:57:00 2006 From: katzj at redhat.com (Jeremy Katz) Date: Thu, 26 Jan 2006 17:57:00 -0500 Subject: [Fedora-xen] Draft Xen Quick Start for FC5 Message-ID: <1138316220.30569.7.camel@bree.local.net> On Fri, 2006-01-27 at 11:26 +1300, Gawain Lynch wrote: > I have put up a Quick Start page on the wiki [1] for FC5. This document > is based on the original one for FC4 but is updated to take into account > changes in FC5/Xen 3. Ack, apparently, we were both working on similar things. I've actually updated the FC4 one to include a much better description of how to do things in FC5 taking advantage of the installer functionality rather than using yum and chroots. This is far better as it allows things like SELinux to work and gives you a much more manageable system. See http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 for the write-up including this information. It probably makes sense to canonicalize on this as it is going to be the more supported method of installing guests with FC5 and later. Jeremy From sfolkwil at redhat.com Thu Jan 26 23:00:19 2006 From: sfolkwil at redhat.com (Sam Folk-Williams) Date: Thu, 26 Jan 2006 18:00:19 -0500 Subject: [Fedora-xen] Draft Xen Quick Start for FC5 In-Reply-To: <1138314870.29913.104.camel@legolas.felicity.net.au> References: <1138314419.29913.99.camel@legolas.felicity.net.au> <1138314870.29913.104.camel@legolas.felicity.net.au> Message-ID: <43D95483.1030104@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gawain Lynch wrote: > Sorry that URL should have been: > > http://fedoraproject.org/wiki/FedoraCore5XenQuickstart > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen Gawain, As Jeremy mentioned the install process is going to be a lot easier thanks to the work he and the other developers are doing currently. Your work is definitely appreciated, though. I'm going to be organizing all the Xen docs for the wiki, so let's definitely touch base. I want to get a more comprehensive set of docs for FC5 than just the install guide. Thanks, Sam - -- Sam Folk-Williams, RHCE Red Hat Global Support Services GPG ID: 1024D/1B0D46BA Public Key: http://people.redhat.com/sfolkwil/sfw.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFD2VSCzOw+vBsNRroRAtWgAJ44KipH2RBnXZ2sZAJM5ejSLSUoHACeIIh0 cTFavt8xDVti2JpcEVPSTH4= =MDnh -----END PGP SIGNATURE----- From lamont at gurulabs.com Thu Jan 26 23:00:55 2006 From: lamont at gurulabs.com (Lamont R. Peterson) Date: Thu, 26 Jan 2006 16:00:55 -0700 Subject: [Fedora-xen] Draft Xen Quick Start for FC5 In-Reply-To: <1138314419.29913.99.camel@legolas.felicity.net.au> References: <1138314419.29913.99.camel@legolas.felicity.net.au> Message-ID: <200601261601.00091.lamont@gurulabs.com> On Thursday 26 January 2006 03:26pm, Gawain Lynch wrote: > Hi All, > > I have put up a Quick Start page on the wiki [1] for FC5. This document > is based on the original one for FC4 but is updated to take into account > changes in FC5/Xen 3. Cool. Thanks! :) > I currently consider it draft but it Works For Me (tm). I would be very > grateful if some of you could take it for a spin and let me know any > issues/errors/omissions you find. I would love to. Probably Saturday. I have dual-Opteron at home that I'll do that on, so it could be interesting to see how that goes. > It is not currently linked to the main Xen Wiki page, I'll do that once > I am happy that I have it right. > > Take care, > > Gawain > > [1] http://fedoraproject.org/wiki/FedoraFC5XenQuickstart -- Lamont R. Peterson Senior Instructor Guru Labs, L.C. [ http://www.GuruLabs.com/ ] -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From gawain.lynch at bigpond.com Fri Jan 27 00:05:17 2006 From: gawain.lynch at bigpond.com (Gawain Lynch) Date: Fri, 27 Jan 2006 13:05:17 +1300 Subject: [Fedora-xen] Draft Xen Quick Start for FC5 In-Reply-To: <1138316220.30569.7.camel@bree.local.net> References: <1138316220.30569.7.camel@bree.local.net> Message-ID: <1138320317.2713.2.camel@legolas.felicity.net.au> On Thu, 2006-01-26 at 17:57 -0500, Jeremy Katz wrote: > Ack, apparently, we were both working on similar things. I had an inkling that this might be the case, you know what they say about great minds... :-P Do you object to me cleaning up yours a bit and incorporating some other bits from mine? I see you have added some already, but I am just anal about presentation (just ask my long suffering wife) :-) Take care, Gawain From yongkang.you at intel.com Fri Jan 27 03:03:33 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Fri, 27 Jan 2006 11:03:33 +0800 Subject: [Fedora-xen] Simple testing results for Xen and VMX on FC5-test2. Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575031C9413@pdsmsx402.ccr.corp.intel.com> Hi all, I have done a simple checking for Xen and VMX on FC5-test2. Basically, I can create VMX on FC5-test2 IA32. But FC5-test2 IA32e (x86-64) doesn't provide Xen and Xen0 kernel, so didn't do Xen and VMX testing for it. Beside of testing Xen and VMX, I also found some issues about installation, which I have updated the bug #179078 as a NB. The following is the testing results only for Xen and VMX. ========================= 1. *** IA32E hasn't RPMS about Xen hypervisor and Xen0/XenU kernels. __FAIL__ 2. *** In order to boot up IA32 Xen0, I have to add pci=noacpi as the boot parameters of Xen0 kernel, or system will hang when initial PCI. I don't know if it is only related to my Machine. __FAIL__ 3. After install IA32 Xen RPMs, I can see /boot/grub/grub.conf has been changed with Xen kernels. __PASS__ 4. *** /usr/lib/xen/boot/vmxloader isn't in the RPM package, so VMX Guest couldn't be created. I suspected build system hasn't bcc, it is from DEV86 package. __FAIL__ 5. After copy a useable vmxloader to the destination, IA32 VMX Guest can be created successfully! __PASS__ 6. VMX has good network connection and Xwindows started. __PASS__ 7. XenU can be created and works well. __PASS__ 8. Couldn't get Xen Changeset by "xm info" or "xm dmesg". 9. The new kernel names of Xen/Xen0/XenU seemed a little confused. E.g. the Xen0 name is like vmlinuz-2.6.15-1.29_FC5hypervisor. I thought hypervisor is for Xen.gz. Xen0 is the Service OS. ========================== Any comments please let me know. But I will have 8 days holiday from tomorrow, so emails reply might be slow and occasional. [FYI] We are planning to do more testing for FC5-test3. Best Regards, Yongkang (Kangkang) ?? From katzj at redhat.com Fri Jan 27 16:03:28 2006 From: katzj at redhat.com (Jeremy Katz) Date: Fri, 27 Jan 2006 11:03:28 -0500 Subject: [Fedora-xen] Simple testing results for Xen and VMX on FC5-test2. In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD30575031C9413@pdsmsx402.ccr.corp.intel.com> References: <16A54BF5D6E14E4D916CE26C9AD30575031C9413@pdsmsx402.ccr.corp.intel.com> Message-ID: <1138377808.6643.10.camel@bree.local.net> On Fri, 2006-01-27 at 11:03 +0800, You, Yongkang wrote: > 1. *** IA32E hasn't RPMS about Xen hypervisor and Xen0/XenU > kernels. __FAIL__ Getting x86_64 building involved a couple of chicken sacrifices I think. Stephen was making good progress yesterday, though, so x86_64 will hopefully show up for test3. > 2. *** In order to boot up IA32 Xen0, I have to add pci=noacpi as > the boot parameters of Xen0 kernel, or system will hang when > initial PCI. I don't know if it is only related to > my Machine. __FAIL__ Please file a bug including some actual details about your hardware instead of just vague statements like this. > 4. *** /usr/lib/xen/boot/vmxloader isn't in the RPM package, > so VMX Guest couldn't be created. I suspected build system hasn't > bcc, it is from DEV86 package. __FAIL__ Although it would be great if someone would actually port this stuff to not use ancient, barely maintained toolchains and/or the approach of actually distributing the firmware in the repository (as done by Bochs, which is the upstream for this stuff), I went ahead and got dev86 to build on x86_64 so that vmxloader is in later xen packages. > 9. The new kernel names of Xen/Xen0/XenU seemed a little confused. > E.g. the Xen0 name is like vmlinuz-2.6.15-1.29_FC5hypervisor. I > thought hypervisor is for Xen.gz. Xen0 is the Service OS. The kernel-xen-hypervisor package includes both the Xen hypervisor and the dom0 kernel as these two are tightly intertwined. Jeremy From fraser at wehave.net Sat Jan 28 13:46:32 2006 From: fraser at wehave.net (Fraser Campbell) Date: Sat, 28 Jan 2006 08:46:32 -0500 Subject: [Fedora-xen] Enabling NFS root for Xen guests in FC5 In-Reply-To: <1138311096.4013.1.camel@orbit.scot.redhat.com> References: <43D50F7C.2090402@georgetown.wehave.net> <1138311096.4013.1.camel@orbit.scot.redhat.com> Message-ID: <43DB75B8.5050609@wehave.net> Stephen C. Tweedie wrote: >>CONFIG_IP_PNP and suboptions as well as CONFIG_ROOT_NFS should be >>enabled in Xen guest kernels in order for NFS root to be used in Xen guests. > > > Yes, the NFS root option is attractive. But in-kernel NFS root has all > sorts of problems. We'd far prefer to have eventual support in the > initrd for NFS mounting, and avoid the kernel issue altogether. Interesting, I guess I'll give explicit mounts inside the initrd a try then. Thanks! From rdh at samuisystems.com Mon Jan 30 05:21:58 2006 From: rdh at samuisystems.com (Randolph Hill) Date: Sun, 29 Jan 2006 21:21:58 -0800 (PST) Subject: [Fedora-xen] Simple Instructions on networking Message-ID: <20060130052158.618.qmail@web33707.mail.mud.yahoo.com> I am new to Fedora and Xen. I have everything up and running with the exception of being able to access the network from my guest domain. I am looking for some simple instructions to get me going. My system is connected to a Linksys Wireless router. I would like to have internet access from the guest domain. Pointers are appreciated. Thanks Randy Samui Systems, Inc. 5954B Bartonsville Road Frederick, MD 21701 PHONE: +1(301) 631-5799 vMail/FAX: +1(301) 542-0042 rdh at samuisystems.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From sfolkwil at redhat.com Mon Jan 30 05:37:35 2006 From: sfolkwil at redhat.com (Sam Folk-Williams) Date: Mon, 30 Jan 2006 00:37:35 -0500 Subject: [Fedora-xen] Simple Instructions on networking In-Reply-To: <20060130052158.618.qmail@web33707.mail.mud.yahoo.com> References: <20060130052158.618.qmail@web33707.mail.mud.yahoo.com> Message-ID: <43DDA61F.70601@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Randolph Hill wrote: > I am new to Fedora and Xen. I have everything up and running with the exception of being able > to access the network from my guest domain. I am looking for some simple instructions to get me going. > My system is connected to a Linksys Wireless router. I would like to have internet access from the guest domain. > > Pointers are appreciated. > > Thanks > > Randy > Randy -- most likely the eth0 interface is not configured. If you are in a text-only environment try running "netconfig" to set up networking. Or, you can run system-config-network. In either case, usually you just need to create a /etc/sysconfig/network-scripts/ifcfg-eth0 file then bring that device up with "ifup eth0". Either tool mentioned above will do this for you. Sam > Samui Systems, Inc. 5954B Bartonsville Road Frederick, MD 21701 PHONE: +1(301) 631-5799 vMail/FAX: +1(301) 542-0042 rdh at samuisystems.com > > > > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFD3aYfzOw+vBsNRroRAjkBAJ41DvzO02VcobEw+OUV1mW+vK9eDwCdHQsJ vik9MitInHxtFvQd5zafJ9Q= =QzzK -----END PGP SIGNATURE----- From sct at redhat.com Mon Jan 30 15:15:50 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Mon, 30 Jan 2006 10:15:50 -0500 Subject: [Fedora-xen] Simple testing results for Xen and VMX on FC5-test2. In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD30575031C9413@pdsmsx402.ccr.corp.intel.com> References: <16A54BF5D6E14E4D916CE26C9AD30575031C9413@pdsmsx402.ccr.corp.intel.com> Message-ID: <1138634150.3682.4.camel@orbit.scot.redhat.com> Hi, On Fri, 2006-01-27 at 11:03 +0800, You, Yongkang wrote: > I have done a simple checking for Xen and VMX on FC5-test2. Basically, I can create VMX on FC5-test2 IA32. But FC5-test2 IA32e (x86-64) doesn't provide Xen and Xen0 kernel, so didn't do Xen and VMX testing for it. > > Beside of testing Xen and VMX, I also found some issues about installation, which I have updated the bug #179078 as a NB. The following is the testing results only for Xen and VMX. > ========================= > 1. *** IA32E hasn't RPMS about Xen hypervisor and Xen0/XenU kernels. __FAIL__ It's coming. I hope. The upstream x86_64 stuff from linux-2.6-merge doesn't actually compile at the moment (though that's easy to fix), and once compiled it fails in different, compiler-dependent ways on some of my hardware. I've got a minimally stable boot now on a different box, but the upstream base in this case is proving hard to work with. > 2. *** In order to boot up IA32 Xen0, I have to add pci=noacpi as the boot > parameters of Xen0 kernel, or system will hang when initial PCI. I don't know if it is only related to my Machine. It's certainly hardware-dependent, but you're not the only person reporting the need for such options. Please open a bugzilla so that we can track this one properly, as we'd really like to automate such options as much as possible for the main release. One thing that would be worth knowing is whether the main, non-xen rawhide SMP kernel boots on this box. The UP kernel disables a bunch of advanced hardware enablement for compatibility purposes, but the SMP one should match Xen as closely as possible. > 8. Couldn't get Xen Changeset by "xm info" or "xm dmesg". Not sure how easy that would be to add, since we don't build it out of Mercurial directly but rather out of a tarballed copy from the CVS build system. I'm being careful to add the changeset info to the changelog in the rpm, though. Thanks, Stephen From sct at redhat.com Mon Jan 30 15:18:33 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Mon, 30 Jan 2006 10:18:33 -0500 Subject: [Fedora-xen] Simple Instructions on networking In-Reply-To: <20060130052158.618.qmail@web33707.mail.mud.yahoo.com> References: <20060130052158.618.qmail@web33707.mail.mud.yahoo.com> Message-ID: <1138634314.3682.7.camel@orbit.scot.redhat.com> Hi, On Sun, 2006-01-29 at 21:21 -0800, Randolph Hill wrote: > I am new to Fedora and Xen. I have everything up and running with the > exception of being able > to access the network from my guest domain. I am looking for some > simple instructions to get me going. Is this a current Rawhide install, or something different? Network scripts are sensitive to change in Xen, so it's important to know exactly what sort of config you're starting with. Thanks, Stephen From yongkang.you at intel.com Tue Jan 31 15:57:32 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Tue, 31 Jan 2006 23:57:32 +0800 Subject: [Fedora-xen] Simple testing results for Xen and VMXon FC5-test2. Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575031C9417@pdsmsx402.ccr.corp.intel.com> >-----Original Message----- >> 1. *** IA32E hasn't RPMS about Xen hypervisor and Xen0/XenU kernels. >__FAIL__ > >It's coming. I hope. The upstream x86_64 stuff from linux-2.6-merge >doesn't actually compile at the moment (though that's easy to fix), and >once compiled it fails in different, compiler-dependent ways on some of >my hardware. I've got a minimally stable boot now on a different box, >but the upstream base in this case is proving hard to work with. I am very glad to hear it is coming. :) Hope we can see it in the FC5-test3 x86_64 packages. > >> 2. *** In order to boot up IA32 Xen0, I have to add pci=noacpi as the boot >> parameters of Xen0 kernel, or system will hang when initial PCI. I don't know if >it is only related to my Machine. > >It's certainly hardware-dependent, but you're not the only person >reporting the need for such options. Please open a bugzilla so that we >can track this one properly, as we'd really like to automate such >options as much as possible for the main release. > >One thing that would be worth knowing is whether the main, non-xen >rawhide SMP kernel boots on this box. The UP kernel disables a bunch of >advanced hardware enablement for compatibility purposes, but the SMP one >should match Xen as closely as possible. I am not sure how common used my machine is. :( But it can work with latest Xen + 2.6.12 kernel in the RHEL4u2 or FC4. So the new problem may be related with new kernel 2.6.15? I can fire a new bug about it. My testing machine is SMP enabled. > >> 8. Couldn't get Xen Changeset by "xm info" or "xm dmesg". > >Not sure how easy that would be to add, since we don't build it out of >Mercurial directly but rather out of a tarballed copy from the CVS build >system. I'm being careful to add the changeset info to the changelog in >the rpm, though. Em. If we can found some changeset info in changelog or other way, it may bring some help to customers and developers. :-) > >Thanks, > Stephen Best Regards, Yongkang (Kangkang) ?? From yongkang.you at intel.com Tue Jan 31 16:05:11 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Wed, 1 Feb 2006 00:05:11 +0800 Subject: [Fedora-xen] Simple testing results for Xen and VMXon FC5-test2. Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575031C9418@pdsmsx402.ccr.corp.intel.com> Hi Jeremy, Thanks for you quickly reply. >-----Original Message----- >> 9. The new kernel names of Xen/Xen0/XenU seemed a little confused. >> E.g. the Xen0 name is like vmlinuz-2.6.15-1.29_FC5hypervisor. I >> thought hypervisor is for Xen.gz. Xen0 is the Service OS. > >The kernel-xen-hypervisor package includes both the Xen hypervisor and >the dom0 kernel as these two are tightly intertwined. > Yes, I recognized the Xen hypervisor and dom0 kernel are coming from 1 package. But you see, the dom0 kernel is named vmlinuz-2.6.15-1.29_FC5hypervisor. I mixed it with Xen.gz at the beginning. Why not named it like vmlinuz-2.6.15-1.29_FC5Xen0 for easily distinguishing. :) >Jeremy > > Best Regards, Yongkang (Kangkang) ?? From sct at redhat.com Tue Jan 31 19:33:38 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Tue, 31 Jan 2006 14:33:38 -0500 Subject: [Fedora-xen] Simple testing results for Xen and VMXon FC5-test2. In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD30575031C9417@pdsmsx402.ccr.corp.intel.com> References: <16A54BF5D6E14E4D916CE26C9AD30575031C9417@pdsmsx402.ccr.corp.intel.com> Message-ID: <1138736018.4512.63.camel@orbit.scot.redhat.com> Hi, On Tue, 2006-01-31 at 23:57 +0800, You, Yongkang wrote: > I am not sure how common used my machine is. :( But it can work with > latest Xen + 2.6.12 kernel in the RHEL4u2 or FC4. So the new problem > may be related with new kernel 2.6.15? I can fire a new bug about it. Thanks, please do. > >Not sure how easy that would be to add, since we don't build it out of > >Mercurial directly but rather out of a tarballed copy from the CVS build > >system. I'm being careful to add the changeset info to the changelog in > >the rpm, though. > > Em. If we can found some changeset info in changelog or other way, it > may bring some help to customers and developers. :-) Yes, it's already in the changelogs: "rpm -q --changelog xen" shows me ... * Mon Jan 30 2006 - 3.0-0.20060130.fc5 - Update to xen-unstable from 20060130 (cset 8705) --Stephen