From: "Teo En Ming" <enming.teo@asiasoftsea.net>
To: "Teo En Ming" <enming.teo@asiasoftsea.net>,
"Boris Derzhavets" <bderzhavets@yahoo.com>,
"Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Sander Eikelenboom <linux@eikelenboom.it>, xen-devel@lists.xensource.com
Subject: Re: Re[8]: Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel
Date: Sat, 25 Jul 2009 02:31:16 +0800 [thread overview]
Message-ID: <WC20090724183116.5700DE@asiasoftsea.net> (raw)
In-Reply-To: <WC20090724182702.8900DD@asiasoftsea.net>
[-- Attachment #1.1: Type: text/plain, Size: 17723 bytes --]
As a matter of fact, our servers are either Dell PowerEdge 1950/2950 and IBM
xSeries.
I am just testing it out on our lab PC first.
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)
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 Message-----
From: "Teo En Ming" <enming.teo@asiasoftsea.net>
To: "Boris Derzhavets" <bderzhavets@yahoo.com>, "Pasi Kärkkäinen"
<pasik@iki.fi>
Cc: Sander Eikelenboom <linux@eikelenboom.it>, xen-devel@lists.xensource.com
Date: Sat, 25 Jul 2009 02:27:02 +0800
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in Jeremy's
PVOPS Kernel
Dear Boris,
My next step will be a 64-bit Xen Dom 0 host.
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)
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
Message-----
From: Boris Derzhavets <bderzhavets@yahoo.com>
To: Pasi Kärkkäinen <pasik@iki.fi>,
enming.teo@asiasoftsea.net
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
xen-devel@lists.xensource.com
Date: Fri, 24 Jul 2009 10:57:49 -0700 (PDT)
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0 in
Jeremy's PVOPS Kernel
Teo, it is up to you how to manage, if you just having fun.
Otherwise, downloading 64-bit OpenSuse 11.1 ISO image
takes just 12-14 hr even at slow ADSL speed ( like 100 KB/sec).
Install takes 30 minutes and brings you to the trusted results,
instead
of wasting a lot of time in case of business environment
assignment.
Pasi has 32-bit experience due to hardware limitations, which
you don't
have.
Boris.
--- On Fri, 7/24/09, Teo En Ming <enming.teo@asiasoftsea.net> wrote:
From: Teo En Ming <enming.teo@asiasoftsea.net>
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen Dom 0
in Jeremy's PVOPS Kernel
To: "Boris Derzhavets" <bderzhavets@yahoo.com>, "Pasi
Kärkkäinen" <pasik@iki.fi>
Cc: "Sander Eikelenboom" <linux@eikelenboom.it>,
xen-devel@lists.xensource.com
Date: Friday, July 24, 2009, 12:56 PM
Dear Boris,
My colleague installed OpenSUSE 11.1 32-bit on the Core 2 Duo
machine in our labs. Please see my earlier replies in the same topic.
I was too lazy to reformat and install 64-bit OpenSUSE, so I
proceeded with Xen Dom 0 pvops kernel compilation on 32-bit Linux host.
I admit I am getting a lot of headache. Haha.
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering)
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 Message-----
From: Boris Derzhavets <bderzhavets@yahoo.com>
To: enming.teo@asiasoftsea.net, Pasi Kärkkäinen
<pasik@iki.fi>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
xen-devel@lists.xensource.com
Date: Fri, 24 Jul 2009 09:57:18 -0700 (PDT)
Subject: Re: Re[8]: [Xen-devel] Unable to Configure Xen
Dom 0 in Jeremy's PVOPS Kernel
Once again, i don't see any reason to to run 32-bit OS on
Core2Duo,
unless you like Xen head ache. Core development
(PVOPS) is obviously
running in 64-bit environment.
Boris.
--- On Fri, 7/24/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: Re[8]: [Xen-devel] Unable to Configure
Xen Dom 0 in Jeremy's PVOPS Kernel
To: enming.teo@asiasoftsea.net, "Pasi Kärkkäinen"
<pasik@iki.fi>
Cc: "Sander Eikelenboom"
<linux@eikelenboom.it>, xen-devel@lists.xensource.com
Date: Friday, July 24, 2009, 12:47 PM
>After doing the above,
I re-installed back the Xen hypervisor, libraries and tools, and also
>the kernel, initrd, and modules. Then I proceeded to reboot my machine.
After rebooting, > my CentOS 4.7 32-bit PV guest is still able to start
and run!
Why it wouldn't ? If your image stays
the same.
> I am still very puzzled! What causes the
PV guest initially cannot start? Then what >subsequently causes the PV
guest to suddenly be able to start and run???
That is not supposed to happen. I would
suggest clean OS (without any built in xen presence) install , followed
by Xen 3.4.1+pvops kernel clean install.
Boris.
--- On Fri, 7/24/09, Teo En Ming <enming.teo@asiasoftsea.net> wrote:
From: Teo En Ming
<enming.teo@asiasoftsea.net>
Subject: Re: Re[8]: [Xen-devel] Unable to
Configure Xen Dom 0 in Jeremy's PVOPS Kernel
To: "Teo En Ming"
<enming.teo@asiasoftsea.net>, "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "Sander Eikelenboom"
<linux@eikelenboom.it>, xen-devel@lists.xensource.com
Date: Friday, July 24, 2009, 12:19 PM
Dear All,
I am very puzzled. In investigating the
cause of the sudden success of the CentOS 4.7 32-bit PV guest being able to
run, I have uninstalled 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, which also removed my self compiled Xen Dom 0
pvops enabled kernel, initrd and kernel modules.
After doing the above, I re-installed back
the Xen hypervisor, libraries and tools, and also the kernel, initrd, and
modules. Then I proceeded to reboot my machine. After rebooting, my CentOS
4.7 32-bit PV guest is still able to start and run!
I am still very puzzled! What causes the PV
guest initially cannot start? Then what subsequently causes the PV guest to
suddenly be able to start and run???
***scratches head***
Anyway my CentOS 4.7 guest domain is now
running. I shall now proceed to virtualize OpenSolaris 2009.06.
Thank you.
Also see screenshots of my CentOS 4.7 PV
guest here:
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) 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 Message-----
From: "Teo En Ming"
<enming.teo@asiasoftsea.net>
To: "Teo En Ming"
<enming.teo@asiasoftsea.net>, "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Sander Eikelenboom
<linux@eikelenboom.it>, 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 PVOPS Kernel
Hi Pasi,
It's very strange. Suddenly my CentOS 4.7
32-bit PV guest is able to start!!! Previously it refuses to start at all.
I think I must have changed something in
Dom 0 when I attempted "yast --install virt-manager". This action might have
solved the problem. When I tried to install virt-manager, it also tries to
install xen-libs-3.3.1 and xen-tools-3.3.1 as dependencies. However, I
started off my Xen Dom 0 pvops kernel install with Xen 3.4.1 rc8 branch.
I need to investigate more why suddenly
my CentOS 4.7 32-bit PV guest is able to start.
Mr. Teo En Ming (Zhang Enming)
Dip(Mechatronics Engineering) 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 Message-----
From: "Teo En Ming"
<enming.teo@asiasoftsea.net>
To: "Pasi Kärkkäinen"
<pasik@iki.fi>
Cc: Sander Eikelenboom
<linux@eikelenboom.it>, 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 Jeremy's PVOPS Kernel
Hi Pasi,
I realized that Fedora 10 32-bit
anaconda installer does not install PAE kernel after mounting the guest disk
image file. I mounted the guest disk image file using losetup and kpartx
which adds device nodes to /dev/mapper. I examined the /boot directory after
mounting the guest disk image file and found no PAE vmlinuz and initrd.
Still using the mounted Fedora 10
32-bit guest disk image file, I changed root to the guest disk filesystems
and attempted to install the PAE kernel. Then I modified menu.lst to boot
the PAE kernel. After modifying the 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 kernel. It is able to boot now (since the PAE
kernel is xen-aware) but then it complains cannot mount /dev/root. Probably
something to do with the PAE initrd file.
Mr. Teo En Ming (Zhang Enming)
Dip(Mechatronics Engineering) 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 Message-----
From: Pasi Kärkkäinen
<pasik@iki.fi>
To: Teo En Ming
<enming.teo@asiasoftsea.net>
Cc: Sander Eikelenboom
<linux@eikelenboom.it>, 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 in Jeremy's PVOPS Kernel
On Fri, Jul 24, 2009 at 08:37:09PM +0800, Teo En Ming wrote:
> Hi
>
> I attempted to install
Fedora 10 32-bit PV guest using
> images/pxeboot/vmlinuz-PAE
and images/pxeboot/initrd-PAE.img from the F10
> media. The non-PAE kernel
could not load the installer. I finished my Fedora
> 10 32-bit PV guest
installation but it also cannot boot up after
> installation, same as the
CentOS 4.7 PV guest installation.
>
Fedora 10 installer has a bug, as
a default it installs non-PAE kernel for
xen domU. You need to use a
kickstart script (like this) to fix it:
http://pasik.reaktio.net/fedora/f10-xen-domu-ks.cfg
[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 pv_ops Xen domU
support enabled, so there's no
need for separate kernel-xen with these distros).
Fedora 11 doesn't have that
installer bug, so it installs right
out-of-the-box as Xen domU.
What's the error you get when you
start the guest after installation?
Please paste the "xm log" as
text.
I don't have any problems with
CentOS 5.3 dom0.
-- Pasi
-----Inline Attachment Follows-----
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel [http://lists.xensource.com/xen-devel]
-----Inline Attachment Follows-----
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel [http://lists.xensource.com/xen-devel]
-----Inline Attachment Follows-----
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
[https://mail.asiasoftsea.net/mc/compose?to=Xen-devel@lists.xensource.com]
http://lists.xensource.com/xen-devel [http://lists.xensource.com/xen-devel]
[-- Attachment #1.2: Type: text/html, Size: 26676 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2009-07-24 18:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 17:57 Re[8]: Unable to Configure Xen Dom 0 in Jeremy's PVOPS Kernel Boris Derzhavets
2009-07-24 18:27 ` Teo En Ming
2009-07-24 18:31 ` Teo En Ming [this message]
2009-07-25 11:14 ` Mr. Teo En Ming (Zhang Enming)
-- strict thread matches above, loose matches on Subject: below --
2009-07-24 16:57 Re[8]: " Boris Derzhavets
2009-07-24 16:56 ` Teo En Ming
2009-07-27 9:51 ` Stefano Stabellini
2009-07-24 16:47 Boris Derzhavets
2009-07-23 16:40 Re[2]: " Sander Eikelenboom
2009-07-23 16:44 ` Teo En Ming
2009-07-23 17:03 ` Teo En Ming
2009-07-23 17:06 ` Teo En Ming
2009-07-23 17:23 ` Re[4]: " Sander Eikelenboom
2009-07-23 17:17 ` Teo En Ming
2009-07-23 17:45 ` Re[6]: " Sander Eikelenboom
2009-07-23 17:46 ` Teo En Ming
2009-07-23 18:09 ` [SPAM] Re[8]: " Sander Eikelenboom
2009-07-23 18:08 ` Teo En Ming
2009-07-23 18:24 ` Teo En Ming
2009-07-23 18:43 ` Teo En Ming
2009-07-23 19:11 ` Teo En Ming
2009-07-23 19:48 ` Pasi Kärkkäinen
2009-07-23 19:51 ` Teo En Ming
2009-07-23 20:24 ` Pasi Kärkkäinen
2009-07-23 20:25 ` Teo En Ming
2009-07-23 20:32 ` Teo En Ming
2009-07-24 8:19 ` Teo En Ming
2009-07-24 12:37 ` Teo En Ming
2009-07-24 13:31 ` Pasi Kärkkäinen
2009-07-24 13:54 ` Teo En Ming
2009-07-24 14:54 ` Teo En Ming
2009-07-24 16:19 ` Teo En Ming
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=WC20090724183116.5700DE@asiasoftsea.net \
--to=enming.teo@asiasoftsea.net \
--cc=bderzhavets@yahoo.com \
--cc=linux@eikelenboom.it \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.