Return-path: Envelope-to: www-data@lists.xensource.com Delivery-date: Sat, 24 Jan 2009 13:35:20 -0800 Received: from localhost ([127.0.0.1] helo=lists.colo.xensource.com) by lists.xensource.com with esmtp (Exim 4.43) id 1LQq9v-0008Js-MT; Sat, 24 Jan 2009 13:35:19 -0800 Received: from spam.xensource.com ([70.42.241.90]) by lists.xensource.com with esmtp (Exim 4.43) id 1LQq97-0007xx-E4 for xen-users@lists.xensource.com; Sat, 24 Jan 2009 13:34:29 -0800 X-ASG-Debug-ID: 1232832868-016200240000-xM1yvO X-Barracuda-URL: http://spam.xensource.com:8000/cgi-bin/mark.cgi Received: from wf-out-1314.google.com (localhost [127.0.0.1]) by spam.xensource.com (Spam Firewall) with ESMTP id A1FE41189B4 for ; Sat, 24 Jan 2009 13:34:28 -0800 (PST) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.171]) by spam.xensource.com with ESMTP id 13Pj2D5TLzz6qoPh for ; Sat, 24 Jan 2009 13:34:28 -0800 (PST) Received: by wf-out-1314.google.com with SMTP id 28so5830189wff.9 for ; Sat, 24 Jan 2009 13:34:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=bp2G+po36FZ6DRAcR5XiQ3ctD361xVxAGcZ/zSEzKZY=; b=QGdF5Kft2d8cyBJyQ2A/gxWgNOGjsf9G05Xqk9YDCNPHJ4IDZR5dRzKMPsI1hsqJ0p 8PfLIzT2IklQh8Yo2XW+YeRRFtGU8NKSPznPcRfQhCmNTApg1nCnkP1lQ8BMVtixbdm3 4IE0CKHXD6h72oJ4oLVDGnYAPpr3fDy8Qdu8M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Qv5Dd5CG9nqkl8Zwhs2G+8Uqm500S0OsqareaSRfvpC75gfEc6NX2atnRc7wznSy40 Q53rR98kDmh5TmTz0z9kFnE5C3LOBAkuWeXvXrG7BZTrzdf01bkHU8lXZKuDbHQHZyza EaKQhODInfeOw703Njez3VEscP97IKrBpcsFw= MIME-Version: 1.0 Received: by 10.142.48.14 with SMTP id v14mr572576wfv.122.1232832868214; Sat, 24 Jan 2009 13:34:28 -0800 (PST) In-Reply-To: <772cf79b0901241248g3c4ec774v35069bf4ce6a8036@mail.gmail.com> References: <772cf79b0901241019m270e5b5bpe987a514a4798861@mail.gmail.com> <7207d96f0901241151o5fa61bd1kbb4ca13b60bf9842@mail.gmail.com> <772cf79b0901241219m35a8eacwfcf87bf0270150ff@mail.gmail.com> <7207d96f0901241229q7dd26838w17cd8f5a5c63256a@mail.gmail.com> <772cf79b0901241235y725a9e92j4f4b622f8f802854@mail.gmail.com> <772cf79b0901241248g3c4ec774v35069bf4ce6a8036@mail.gmail.com> Date: Sat, 24 Jan 2009 16:34:28 -0500 Message-ID: <772cf79b0901241334p3b9db628ic6e908960cc3e004@mail.gmail.com> X-ASG-Orig-Subj: Re: [Xen-users] DomU in it's own LVM partition fails to boot CentOS 5.2 Dom0/U Subject: Re: [Xen-users] DomU in it's own LVM partition fails to boot CentOS 5.2 Dom0/U From: Peter Hoose To: "Fajar A. Nugraha" X-Barracuda-Connect: wf-out-1314.google.com[209.85.200.171] X-Barracuda-Start-Time: 1232832868 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at xensource.com X-Barracuda-Spam-Score: 0.41 X-Barracuda-Spam-Status: No, SCORE=0.41 using per-user scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=6.0 KILL_LEVEL=1000.0 tests=HTML_MESSAGE, SUBJECT_FUZZY_TION X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.16042 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.41 SUBJECT_FUZZY_TION Attempt to obfuscate words in Subject: 0.00 HTML_MESSAGE BODY: HTML included in message Cc: xen-users@lists.xensource.com X-BeenThere: xen-users@lists.xensource.com X-Mailman-Version: 2.1.5 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0816545094==" Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com --===============0816545094== Content-Type: multipart/alternative; boundary=000e0cd3116a2d67b704614145fd --000e0cd3116a2d67b704614145fd Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit All good now, and I definitely see a big performance improvement with partitions vs. tap: /dev/xvda: Timing cached reads: 7856 MB in 2.00 seconds = 3936.95 MB/sec Timing buffered disk reads: 306 MB in 3.00 seconds = 101.95 MB/sec Previously I was getting ~10MB/s with tap. On Sat, Jan 24, 2009 at 3:48 PM, Peter Hoose wrote: > Never mind, it may have been the mirror, just tried a different one and the > install is chugging along smoothly thus far. > > Thanks for all of your help! > > > On Sat, Jan 24, 2009 at 3:35 PM, Peter Hoose wrote: > >> > Yes. For this purpose, you create one LV on dom0, map it to domU as >> > xvda, and install domU like what you'd do with file-based disk image. >> >> Sweet! >> >> Got much closer this time around my new config: >> >> kernel = "/var/lib/xen/boot/CentOS/CentOS_5_x64_vmlinuz" >> ramdisk = "/var/lib/xen/boot/CentOS/CentOS_5_x64_initrd.img" >> extra = "text" >> name = "guest01" >> memory = "1024" >> disk = [ 'phy:/dev/VolGroup00/guest01,xvda,w', ] >> vif = [ 'bridge=xenbr0', ] >> vcpus=1 >> on_reboot = 'destroy' >> on_crash = 'destroy' >> >> The disk shows up properly now, and in theory, it lets me create >> partitions on it, format them, etc... But it bombs out as soon as it starts >> to install with: >> >> Error >> The file system-config-securitylevel-tui-1.6.29.1-2.1.el5.x86_64.rpm >> cannot be opened. This is due to a missing file, a corrupt package >> or corrupt media. Please verify your installation source. >> >> If you exit, your system will be left in an inconsistent state that >> will likely require reinstallation. >> >> This happens regardless of packages selected, it seems to be the first >> file each time, this is install from the same mirror that I used with no >> problems with file based, so it seems to still be something wrong with my >> disk setup? >> >> Anyways, it's much closer now and past the first big question/issue I had. >> >> If you have any ideas what caused the above error, I'd appreciate it, if >> not I'll just hack away at it until it works. >> >> Thanks, >> Peter >> >> >> On Sat, Jan 24, 2009 at 3:29 PM, Fajar A. Nugraha wrote: >> >>> On Sun, Jan 25, 2009 at 3:19 AM, Peter Hoose wrote: >>> > I just created a LVM based vbd in my dom0, I want to use >>> > this as my 'disk' for my domU, which I would create my partitions on. >>> Is >>> > this possible, >>> >>> Yes. For this purpose, you create one LV on dom0, map it to domU as >>> xvda, and install domU like what you'd do with file-based disk image. >>> >>> > or do I need to create a /boot, / and /swap on my domU and >>> > share those with dom0 for it to access natively? IE: Does the dom0 see >>> this >>> > partition as a disk that it can create partitions on, or does it see it >>> just >>> > like a normal partition? >>> >>> I'm not quite sure what you mean, but you can do this : >>> - create two LVs on dom0, map it to domU as xvda1 (for / ) and xvda2 >>> (for swap). You don't need a separate /boot. >>> - do mkfs.ext3 and mkswap on dom0 directly on that LV (not creating >>> partition on top of it) >>> - populate domU's filesystem (for example, by extracting "templates" >>> like the one from jailtime.org, or by copying from a working domU.) >>> - create a suitable initrd >>> >>> Regards, >>> >>> Fajar >>> >> >> > --000e0cd3116a2d67b704614145fd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable All good now, and I definitely see a big performance improvement with parti= tions vs. tap:

/dev/xvda:
 Timing cached reads:   = 7856 MB in  2.00 seconds =3D 3936.95 MB/sec
 Timing buffered d= isk reads:  306 MB in  3.00 seconds =3D 101.95 MB/sec


Previously I was getting ~10MB/s with tap.

On Sat, Jan 24, 2009 at 3:48 PM, Peter Hoose &l= t;phoose@gmail.com> wrote= :
Never mind, it ma= y have been the mirror, just tried a different one and the install is chugg= ing along smoothly thus far.

Thanks for all of your help!

<= br>
On Sat, Jan 24, 2009 at 3:35 PM, Peter Hoose = <phoose@gmail.com> wrote:
> Yes. Fo= r this purpose, you create one LV on dom0, map it to domU as
> xvda, and install domU like what you'd do with file-based disk ima= ge.

Sweet!

Got much closer this time around my new con= fig:


kernel =3D "/var/lib/xen/boot/CentOS/CentOS_5_x64_vmlinuz"
ramdisk =3D "/var/lib/xen/boot/CentOS/CentOS_5_x64_initrd.img" extra =3D "text"
name =3D "guest01"
memory =3D "1024"

disk =3D [ 'phy:/dev/VolGroup00/guest01,xvda,w', ]
vif =3D [ 'bridge=3Dxenbr0', ]
vcpus=3D1
on_reboot =3D 'destroy'
on_crash =3D 'destroy'

The disk shows up properly now, and in theory, it lets me create partitions on it, format them, etc... But it bombs out as soon as it starts to install with:

Error
The file system-config-securityleve= l-tui-1.6.29.1-2.1.el5.x86_64.rpm
cannot be opened.  This is due t= o a missing file, a corrupt package
or corrupt media.  Please verif= y your installation source.

If you exit, your system will be left in an inconsistent state that
= will likely require reinstallation.

This happens regardless of packa= ges selected, it seems to be the first file each time, this is install from= the same mirror that I used with no problems with file based, so it seems = to still be something wrong with my disk setup?

Anyways, it's much closer now and past the first big question/issue= I had.

If you have any ideas what caused the above error, I'd a= ppreciate it, if not I'll just hack away at it until it works.

Thanks,
  Peter
=

On Sat, Jan 24, 2009 at 3:29 PM, Fajar A= . Nugraha <fajar@fajar.net> wrote:
On Sun, Jan 25, 2009 at 3:19 AM, Peter Hoose <phoose@gmail.com> wrote:
> I just created a LVM based vbd in my dom0, I want to use > this as my 'disk' for my domU, which I would create my partiti= ons on. Is
> this possible,

Yes. For this purpose, you create one LV on dom0, map it to domU as xvda, and install domU like what you'd do with file-based disk image.

> or do I need to create a /boot, / and /swap on my domU and
> share those with dom0 for it to access natively? IE: Does the dom0 see= this
> partition as a disk that it can create partitions on, or does it see i= t just
> like a normal partition?

I'm not quite sure what you mean, but you can do this :
- create two LVs on dom0, map it to domU as xvda1 (for / ) and xvda2
(for swap). You don't need a separate /boot.
- do mkfs.ext3 and mkswap on dom0 directly on that LV (not creating
partition on top of it)
- populate domU's filesystem (for example, by extracting "template= s"
like the one from jailtim= e.org, or by copying from a working domU.)
- create a suitable initrd

Regards,

Fajar



--000e0cd3116a2d67b704614145fd-- --===============0816545094== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users --===============0816545094==--