xen May 2006

xen@lists.fedoraproject.org

69 participants
92 discussions

xen version 2 under Fedora Core 1 or 2
by Eric Marty 26 May '06

26 May '06

Hello, Anbody has already installed xen version 2 under Fedora Core 1 or 2 ? I have a lot of probleme with this version. And if someone has the process. Thanks by avance Eric -------------- ALICE HAUT DEBIT : TRIPLE PLAY A 29,95 EUR/MOIS -------------- Découvrez vite ALICEBOX : avec le modem WIFI, profitez de l'ADSL, de la TELEPHONIE et en exclusivité de la TELEVISION ! Bénéficiez aussi de la hotline gratuite 24h/24 ! Soumis à conditions. Pour en profiter cliquez ici http://abonnement.aliceadsl.fr

2 2

RE: [Fedora-xen] DomU/Dom0/Hypervisor boot on FC6 Tiger4/Montecito/Xen
by Zhang, Xiantao 26 May '06

26 May '06

Hi Fenghua, Did you create XenU successfully ? From your mail, seems xenU is OK now, but I met a issue when creates xenU, it will die at booting time . Have you met the issue? If yes, and how to fix it? Thanks:-) -Xiantao ________________________________ From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com] On Behalf Of Yu, Fenghua Sent: 2006年5月26日 9:42 To: fedora-xen(a)redhat.com Subject: [Fedora-xen] DomU/Dom0/Hypervisor boot on FC6 Tiger4/Montecito/Xen XenU, Xen0, and Xen from latest rpms (2.6.16-1.2211_FC6) can boot on FC6 Tiger4/Montecito/Xen now. To make this work: 1. For Xen0 boot kernel panic, need to use newer cpio to generate correct initrd. If you see kernel panic on /dev/root mount failure during Xen0 boot, it is because of this issue. 2. Xend causes Xen0 hang at the last boot phase. Seems xend doesn’t work well with python2.4. I use python2.3 as temporary w/a. Need to look into this issue later. 3. Other configurations changes. Intel QA starts testing on FC6 IPF Xen now. In the mean time, I’m looking into VTi now. Thanks. -Fenghua

1 0

RE: [Fedora-xen] Re: [Fedora-ia64-list] Xen and Xen0 boot on FC6IPF/Xen
by Zhang, Xiantao 25 May '06

25 May '06

Agree:) Thanks -Xiantao > -----Original Message----- > From: Tian, Kevin > Sent: 2006年5月26日 9:30 > To: 'Aron Griffis'; Zhang, Xiantao > Cc: fedora-xen(a)redhat.com > Subject: RE: [Fedora-xen] Re: [Fedora-ia64-list] Xen and Xen0 boot on > FC6IPF/Xen > > >From: Aron Griffis > >Sent: 2006年5月26日 9:22 > > > >Zhang, Xiantao wrote: [Thu May 25 2006, 08:52:25PM EDT] > >> Because FC5's mkinitrd is 5.0.32-1 and cpio is 2.6.11.2.1, we > >> installed RPMs to FC5 directly, it should create initrd > >> dynamically, we can boot to xen0 and start xend now, but when > >> creating domains, we got the block status. When install to > >> rhel4, we should upgrade mkinitrd and cpio first, am I right? > > > >I don't know about RHEL4. If possible, I would recommend using FC5 > >or > >Rawhide systems instead of trying to retrofit RHEL4. Do you have > >a reason to use it instead of Fedora for testing? > > > >Aron > > I think Xiantao is talking about a temporary solution on RHEL4 before > we got FC installed in our box. Now we have FC installed and then RPM > installation on FC5 creates write initrd automatically as Xiantao said. > > Thanks, > Kevin

1 0

RE: [Fedora-xen] DomU/Dom0/Hypervisor boot on FC6 Tiger4/Montecito/Xen
by Tian, Kevin 25 May '06

25 May '06

Great news. Thanks, Kevin ________________________________ From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com] On Behalf Of Yu, Fenghua Sent: 2006年5月26日 9:42 To: fedora-xen(a)redhat.com Subject: [Fedora-xen] DomU/Dom0/Hypervisor boot on FC6 Tiger4/Montecito/Xen XenU, Xen0, and Xen from latest rpms (2.6.16-1.2211_FC6) can boot on FC6 Tiger4/Montecito/Xen now. To make this work: 1. For Xen0 boot kernel panic, need to use newer cpio to generate correct initrd. If you see kernel panic on /dev/root mount failure during Xen0 boot, it is because of this issue. 2. Xend causes Xen0 hang at the last boot phase. Seems xend doesn’t work well with python2.4. I use python2.3 as temporary w/a. Need to look into this issue later. 3. Other configurations changes. Intel QA starts testing on FC6 IPF Xen now. In the mean time, I’m looking into VTi now. Thanks. -Fenghua

1 0

DomU/Dom0/Hypervisor boot on FC6 Tiger4/Montecito/Xen
by Yu, Fenghua 25 May '06

25 May '06

XenU, Xen0, and Xen from latest rpms (2.6.16-1.2211_FC6) can boot on FC6 Tiger4/Montecito/Xen now. To make this work: 1. For Xen0 boot kernel panic, need to use newer cpio to generate correct initrd. If you see kernel panic on /dev/root mount failure during Xen0 boot, it is because of this issue. 2. Xend causes Xen0 hang at the last boot phase. Seems xend doesn't work well with python2.4. I use python2.3 as temporary w/a. Need to look into this issue later. 3. Other configurations changes. Intel QA starts testing on FC6 IPF Xen now. In the mean time, I'm looking into VTi now. Thanks. -Fenghua

1 0

RE: [Fedora-xen] Re: [Fedora-ia64-list] Xen and Xen0 boot on FC6IPF/Xen
by Tian, Kevin 25 May '06

25 May '06

>From: Aron Griffis >Sent: 2006年5月26日 9:22 > >Zhang, Xiantao wrote: [Thu May 25 2006, 08:52:25PM EDT] >> Because FC5's mkinitrd is 5.0.32-1 and cpio is 2.6.11.2.1, we >> installed RPMs to FC5 directly, it should create initrd >> dynamically, we can boot to xen0 and start xend now, but when >> creating domains, we got the block status. When install to >> rhel4, we should upgrade mkinitrd and cpio first, am I right? > >I don't know about RHEL4. If possible, I would recommend using FC5 >or >Rawhide systems instead of trying to retrofit RHEL4. Do you have >a reason to use it instead of Fedora for testing? > >Aron I think Xiantao is talking about a temporary solution on RHEL4 before we got FC installed in our box. Now we have FC installed and then RPM installation on FC5 creates write initrd automatically as Xiantao said. Thanks, Kevin

1 0

[Patch] fix rpmbuild for xen-ia64
by Akio Takebe 25 May '06

25 May '06

Hi, Aron This patch fix rpmbuilding kernel-xenU on ia64. If you want to install kerne-xenU into /boot, I'll fix with another way. (e.g. make %{xenUimage_install_path}) I think we can install it into /boot/efi/EFI/redhat on ia64. What do you think about this? Signed-off-by: Akio Takebe <takebe_akio(a)jp.fujitsu.com> diff -r f8ab3683a4fb SPECS/kernel-2.6.spec --- a/SPECS/kernel-2.6.spec Wed May 24 22:19:50 2006 -0400 +++ b/SPECS/kernel-2.6.spec Sun May 28 16:48:09 2006 +0900 @@ -1621,7 +1621,7 @@ fi %files xenU %defattr(-,root,root) -/boot/vmlinuz-%{KVERREL}xenU +/%{image_install_path}/vmlinuz-%{KVERREL}xenU /boot/System.map-%{KVERREL}xenU /boot/config-%{KVERREL}xenU %dir /lib/modules/%{KVERREL}xenU Best Regards, Akio Takebe

2 5

RE: [Fedora-xen] Re: [Fedora-ia64-list] Xen and Xen0 boot on FC6 IPF/Xen
by Zhang, Xiantao 25 May '06

25 May '06

Hi Aron/Fenghua, Because FC5's mkinitrd is 5.0.32-1 and cpio is 2.6.11.2.1, we installed RPMs to FC5 directly, it should create initrd dynamically, we can boot to xen0 and start xend now, but when creating domains, we got the block status. When install to rhel4, we should upgrade mkinitrd and cpio first, am I right? Thanks -Xiantao > -----Original Message----- > From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com] > On Behalf Of Yu, Fenghua > Sent: 2006年5月26日 0:04 > To: Aron Griffis > Cc: fedora-xen(a)redhat.com > Subject: [Fedora-xen] Re: [Fedora-ia64-list] Xen and Xen0 boot on FC6 IPF/Xen > > On Thu, May 25, 2006 at 09:27:11AM -0400, Aron Griffis wrote: > > Hi Fenghua, > > > > Yu, Fenghua wrote: [Wed May 24 2006, 11:10:13PM EDT] > > > Hypervisor and Xen0 from latest IPF/Xen rpms can boot on FC6/Montecito now. > > > Minor changes needed in configuration and initrd to pass kernel panic. And > xend > > > will cause system hang. I disable it for the time being. So we can focus > more > > > on XenU. > > > > This is great news! :-) > > > > Could you share those minor changes? > > > > Regards, > > Aron > > > > P.S. I moved this conversation to fedora-xen since we're trying to > > consolidate discussion around fedora-xen-ia64 on that list. > > The configuration change is just copying xen.gz from /boot to > /boot/efi/efi/redhat. > > The kernel panic happens in initrd when mounting root devices. There is no real > initrd change. My build is working. I'm using mkinitrd-5.0.32-1 and > cpio-2.6-11.2.1. Could you check yours? I think actually cpio causes the issue > since kernel panic goes away after I re-archieve your initrd with my cpio. > > Thanks. > > -Fenghua > > -- > Fedora-xen mailing list > Fedora-xen(a)redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen

2 1

Re: [Fedora-ia64-list] Xen and Xen0 boot on FC6 IPF/Xen
by Aron Griffis 25 May '06

25 May '06

Hi Fenghua, Yu, Fenghua wrote: [Wed May 24 2006, 11:10:13PM EDT] > Hypervisor and Xen0 from latest IPF/Xen rpms can boot on FC6/Montecito now. > Minor changes needed in configuration and initrd to pass kernel panic. And xend > will cause system hang. I disable it for the time being. So we can focus more > on XenU. This is great news! :-) Could you share those minor changes? Regards, Aron P.S. I moved this conversation to fedora-xen since we're trying to consolidate discussion around fedora-xen-ia64 on that list.

2 2

Lost peth0, not sure how to get it back...
by Tom Bishop 25 May '06

25 May '06

I have been playing with xen and domU and things were working fine, I've added a second nic to my setup and somehow when configuring it I have lost peth0, so none of my domains are working. When I run the xen network-bridge script I get the following: [root@localhost scripts]# ./network-bridge start net.bridge.bridge-nf-call-arptables = 0 net.bridge.bridge-nf-call-ip6tables = 0 net.bridge.bridge-nf-call-iptables = 0 SIOCSIFNAME: Device or resource busy Here is the output of my ifconfig -a (note no peth0): eth0 Link encap:Ethernet HWaddr 00:06:5B:15:C5:0B inet addr:10.99.99.5 Bcast:10.99.99.7 Mask:255.255.255.248 inet6 addr: fe80::206:5bff:fe15:c50b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2463 errors:0 dropped:0 overruns:0 frame:0 TX packets:2554 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1537351 (1.4 MiB) TX bytes:376789 (367.9 KiB) Interrupt:5 Base address:0xa400 eth1 Link encap:Ethernet HWaddr 00:05:5D:D0:C0:DB UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:7 errors:0 dropped:0 overruns:0 frame:0 TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1540 (1.5 KiB) TX bytes:6448 (6.2 KiB) Interrupt:11 Base address:0x4800 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:2518 errors:0 dropped:0 overruns:0 frame:0 TX packets:2518 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2933900 (2.7 MiB) TX bytes:2933900 (2.7 MiB) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 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) veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:10.99.99.4 Bcast:10.99.99.7 Mask:255.255.255.248 BROADCAST MULTICAST MTU:1500 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) veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 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) veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 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) veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 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) veth4 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 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) veth5 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 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) veth6 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 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) veth7 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 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) vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 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) vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 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) vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 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) vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 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) vif0.4 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 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) vif0.5 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 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) vif0.6 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 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) vif0.7 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 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) xenbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 b) TX bytes:468 (468.0 b) Any suggestions/help would be appreciated. Thanks.

2 1

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen May 2006