From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Teo En Ming" Subject: Re: Re[8]: Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel Date: Sat, 25 Jul 2009 00:19:09 +0800 Message-ID: References: <20090723202455.GH24960@edu.joroinen.fi> <20090724133119.GL24960@edu.joroinen.fi> Reply-To: enming.teo@asiasoftsea.net Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0241007583==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Teo En Ming , Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Cc: Sander Eikelenboom , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0241007583== Content-Type: multipart/alternative; boundary="0724_1619_09_PART-BREAK" --0724_1619_09_PART-BREAK Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear All, I am very puzzled. In investigating the cause of the sudden success of th= e=20 CentOS 4.7 32-bit PV guest being able to run, I have uninstalled=20 virt-manager and all of its dependencies: docbook python-gtk-vnc xen-libs 3.3.1 scrollkeeper xen-tools 3.3.1 libvirt 0.4.6 libvirt-python vm-install 0.3.24 Then I proceeded to "make uninstall" in xen-3.4-testing source tree, whic= h=20 also removed my self compiled Xen Dom 0 pvops enabled kernel, initrd and=20 kernel modules. After doing the above, I re-installed back the Xen hypervisor, libraries = and=20 tools, and also the kernel, initrd, and modules. Then I proceeded to rebo= ot=20 my machine. After rebooting, my CentOS 4.7 32-bit PV guest is still able = to=20 start and run! I am still very puzzled! What causes the PV guest initially cannot start?= =20 Then what subsequently causes the PV guest to suddenly be able to start a= nd=20 run??? ***scratches head*** Anyway my CentOS 4.7 guest domain is now running. I shall now proceed to=20 virtualize OpenSolaris 2009.06. Thank you. Also see screenshots of my CentOS 4.7 PV guest here:=20 http://teo-en-ming-aka-zhang-enming.blogspot.com/2009/07/creating-centos-= 47-32-bit.html Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)=20 BEng(Hons)(Mechanical Engineering) Technical Support Engineer Information Technology Department =20 Asiasoft Online Pte Ltd =20 Tampines Central 1 #04-01 Tampines Plaza =20 Singapore 529541 Republic of Singapore =20 Mobile Phone: +65-9648-9798 =20 MSN: teoenming@hotmail.com -----Original Message----- From: "Teo En Ming" To: "Teo En Ming" , "Pasi K=E4rkk=E4inen"=20 Cc: Sander Eikelenboom , xen-devel@lists.xensource.= com Date: Fri, 24 Jul 2009 22:54:26 +0800 Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's= =20 PVOPS Kernel Hi Pasi, It's very strange. Suddenly my CentOS 4.7 32-bit PV guest is able to=20 start!!! Previously it refuses to start at all. I think I must have changed something in Dom 0 when I attempted "yast=20 --install virt-manager". This action might have solved the problem. When = I=20 tried to install virt-manager, it also tries to install xen-libs-3.3.1 an= d=20 xen-tools-3.3.1 as dependencies. However, I started off my Xen Dom 0 pvop= s=20 kernel install with Xen 3.4.1 rc8 branch. I need to investigate more why suddenly my CentOS 4.7 32-bit PV guest=20 is able to start. Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)=20 BEng(Hons)(Mechanical Engineering) Technical Support Engineer Information Technology Department =20 Asiasoft Online Pte Ltd =20 Tampines Central 1 #04-01 Tampines Plaza =20 Singapore 529541 Republic of Singapore =20 Mobile Phone: +65-9648-9798 =20 MSN: teoenming@hotmail.com -----Original=20 Message----- =20 From: "Teo En Ming" =20 To: "Pasi K=E4rkk=E4inen" =20 Cc: Sander Eikelenboom ,=20 xen-devel@lists.xensource.com =20 Date: Fri, 24 Jul 2009 21:54:00 +0800 =20 Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in=20 Jeremy's PVOPS Kernel =20 =20 Hi Pasi, =20 =20 I realized that Fedora 10 32-bit anaconda installer does not install=20 PAE kernel after mounting the guest disk image file. I mounted the guest=20 disk image file using losetup and kpartx which adds device nodes to=20 /dev/mapper. I examined the /boot directory after mounting the guest disk= =20 image file and found no PAE vmlinuz and initrd. =20 =20 Still using the mounted Fedora 10 32-bit guest disk image file, I=20 changed root to the guest disk filesystems and attempted to install the P= AE=20 kernel. Then I modified menu.lst to boot the PAE kernel. After modifying = the=20 grub configuration of the guest domain, I un-mounted the guest filesystem= . =20 =20 I proceeded to boot the F10 32-bit guest, since I changed to PAE=20 kernel. It is able to boot now (since the PAE kernel is xen-aware) but th= en=20 it complains cannot mount /dev/root. Probably something to do with the PA= E=20 initrd file. =20 Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)=20 BEng(Hons)(Mechanical Engineering) =20 Technical Support Engineer =20 Information Technology Department =20 Asiasoft Online Pte Ltd =20 Tampines Central 1 #04-01 Tampines Plaza =20 Singapore 529541 =20 Republic of Singapore =20 Mobile Phone: +65-9648-9798 =20 MSN: teoenming@hotmail.com =20 =20 -----Original=20 Message----- =20 From: Pasi K=E4rkk=E4inen =20 To: Teo En Ming =20 Cc: Sander Eikelenboom ,=20 xen-devel@lists.xensource.com =20 Date: Fri, 24 Jul 2009 16:31:19 +0300 =20 Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in=20 Jeremy's PVOPS Kernel =20 =20 =20 On Fri, Jul=20 24, 2009 at 08:37:09PM +0800, Teo En Ming wrote: =20 > Hi =20 > =20 > I attempted to install Fedora 10 32-bit PV guest using =20 > images/pxeboot/vmlinuz-PAE and=20 images/pxeboot/initrd-PAE.img from the F10 =20 > media. The non-PAE kernel could not load the installer. I=20 finished my Fedora =20 > 10 32-bit PV guest installation but it also cannot boot up=20 after =20 > installation, same as the CentOS 4.7 PV guest=20 installation. =20 > =20 =20 Fedora 10 installer has a bug, as a default it installs non-PAE=20 kernel for =20 xen domU. You need to use a kickstart script (like this) to fix=20 it: =20 http://pasik.reaktio.net/fedora/f10-xen-domu-ks.cfg=20 [http://pasik.reaktio.net/fedora/f10-xen-domu-ks.cfg] =20 =20 The important lines being: =20 =20 -kernel =20 kernel-PAE =20 =20 (Fedora 10 and Fedora 11 default kernels are compiled with=20 pv_ops Xen domU =20 support enabled, so there's no need for separate kernel-xen=20 with these distros). =20 =20 Fedora 11 doesn't have that installer bug, so it installs right =20 out-of-the-box as Xen domU. =20 =20 What's the error you get when you start the guest after=20 installation? =20 Please paste the "xm log" as text. =20 =20 I don't have any problems with CentOS 5.3 dom0. =20 =20 -- Pasi --0724_1619_09_PART-BREAK Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Dear All,
 
I am very puzzled. In investigating the cause of the sudden success = of=20 the CentOS 4.7 32-bit PV guest being able to run, I have uninstalled=20 virt-manager and all of its dependencies:
 
docbook
python-gtk-vnc
xen-libs 3.3.1
scrollkeeper
xen-tools 3.3.1
libvirt 0.4.6
libvirt-python
vm-install 0.3.24
 
Then I proceeded to "make uninstall" in xen-3.4-testing source tree,= =20 which also removed my self compiled Xen Dom 0 pvops enabled kernel, initr= d=20 and kernel modules.
 
After doing the above, I re-installed back the Xen hypervisor,=20 libraries and tools, and also the kernel, initrd, and modules. Then I=20 proceeded to reboot my machine. After rebooting, my CentOS 4.7 32-bit PV=20 guest is still able to start and run!
 
I am still very puzzled! What causes the PV guest initially cannot=20 start? Then what subsequently causes the PV guest to suddenly be able to=20 start and run???
 
***scratches head***
 
Anyway my CentOS 4.7 guest domain is now running. I shall now procee= d=20 to virtualize OpenSolaris 2009.06.
 
Thank you.
 
Also see screenshots of my CentOS 4.7 PV guest here:=20 http://teo-en-ming-aka-zhang-enming.blogspot.com/2009/07/creating-centos-= 47-32-bit.html
 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)=20 BEng(Hons)(Mechanical Engineering)
Technical Support Engineer
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541
Republic of Singapore
Mobile Phone: +65-9648-9798
MSN: teoenming@hotmail.com


-----Original=20 Message-----
From: "Teo En Ming" <enming.teo@asiasoftsea.net>
To: "Teo En Ming" <enming.teo@asiasoftsea.net>, "Pasi=20 K=E4rkk=E4inen" <pasik@iki.fi>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,=20 xen-devel@lists.xensource.com
Date: Fri, 24 Jul 2009 22:54:26 +0800
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in= =20 Jeremy's PVOPS Kernel

Hi Pasi,
 
It's very strange. Suddenly my CentOS 4.7 32-bit PV guest is able = to=20 start!!! Previously it refuses to start at all.
 
I think I must have changed something in Dom 0 when I attempted "y= ast=20 --install virt-manager". This action might have solved the problem. When = I=20 tried to install virt-manager, it also tries to install xen-libs-3.3.1 an= d=20 xen-tools-3.3.1 as dependencies. However, I started off my Xen Dom 0 pvop= s=20 kernel install with Xen 3.4.1 rc8 branch.
 
I need to investigate more why suddenly my CentOS 4.7 32-bit PV gu= est=20 is able to start.
 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)=20 BEng(Hons)(Mechanical Engineering)
Technical Support Engineer
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541
Republic of Singapore
Mobile Phone: +65-9648-9798
MSN: teoenming@hotmail.com


-----Origi= nal=20 Message-----
From: "Teo En Ming" <enming.teo@asiasoftsea.net>
To: "Pasi K=E4rkk=E4inen" <pasik@iki.fi>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,=20 xen-devel@lists.xensource.com
Date: Fri, 24 Jul 2009 21:54:00 +0800
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 = in=20 Jeremy's PVOPS Kernel

Hi Pasi,
 
I realized that Fedora 10 32-bit anaconda installer does not=20 install PAE kernel after mounting the guest disk image file. I mounted th= e=20 guest disk image file using losetup and kpartx which adds device nodes to= =20 /dev/mapper. I examined the /boot directory after mounting the guest disk= =20 image file and found no PAE vmlinuz and initrd.
 
Still using the mounted Fedora 10 32-bit guest disk image file, = I=20 changed root to the guest disk filesystems and attempted to install the P= AE=20 kernel. Then I modified menu.lst to boot the PAE kernel. After modifying = the=20 grub configuration of the guest domain, I un-mounted the guest filesystem= .
 
I proceeded to boot the F10 32-bit guest, since I changed to PAE= =20 kernel. It is able to boot now (since the PAE kernel is xen-aware) but th= en=20 it complains cannot mount /dev/root. Probably something to do with the PA= E=20 initrd file.

 
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)=20 BEng(Hons)(Mechanical Engineering)
Technical Support Engineer
Information Technology Department
Asiasoft Online Pte Ltd
Tampines Central 1 #04-01 Tampines Plaza
Singapore 529541
Republic of Singapore
Mobile Phone: +65-9648-9798
MSN: teoenming@hotmail.com


-----Origi= nal=20 Message-----
From: Pasi K=E4rkk=E4inen <pasik@iki.fi>
To: Teo En Ming <enming.teo@asiasoftsea.net>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,=20 xen-devel@lists.xensource.com
Date: Fri, 24 Jul 2009 16:31:19 +0300
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom = 0=20 in Jeremy's PVOPS Kernel

On Fri,= Jul=20 24, 2009 at 08:37:09PM +0800, Teo En Ming wrote:
> Hi
>
> I attempted to install Fedora 10 32-bit PV guest usin= g
> images/pxeboot/vmlinuz-PAE and=20 images/pxeboot/initrd-PAE.img from the F10
> media. The non-PAE kernel could not load the installe= r.=20 I finished my Fedora
> 10 32-bit PV guest installation but it also cannot bo= ot=20 up after
> installation, same as the CentOS 4.7 PV guest=20 installation.
>

Fedora 10 installer has a bug, as a default it installs=20 non-PAE kernel for
xen domU. You need to use a kickstart script (like this) t= o=20 fix it:
http://pasik.reaktio.net/fedora/f10-xen-domu-ks.cfg

The important lines being:

-kernel
kernel-PAE

(Fedora 10 and Fedora 11 default kernels are compiled with= =20 pv_ops Xen domU
support enabled, so there's no need for separate kernel-xe= n=20 with these distros).

Fedora 11 doesn't have that installer bug, so it installs=20 right
out-of-the-box as Xen domU.

What's the error you get when you start the guest after=20 installation?
Please paste the "xm log" as text.

I don't have any problems with CentOS 5.3 dom0.

-- Pasi
--0724_1619_09_PART-BREAK-- --===============0241007583== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0241007583==--