From: kishore kumar <bodkekumar@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: Xen Dom U kernel
Date: Fri, 23 Apr 2010 13:48:27 -0700 [thread overview]
Message-ID: <v2s9f975f341004231348mba21f0a8qe1d21dcb7622789f@mail.gmail.com> (raw)
In-Reply-To: <20100423203732.GB20961@phenom.dumpdata.com>
[-- Attachment #1.1: Type: text/plain, Size: 784 bytes --]
I only commented out extra = "4" option.
and tried to see my fdisk -l /dev/sda2.
Then ran xm creatr -c with my guest config file.
THank YOu.
On Fri, Apr 23, 2010 at 1:37 PM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:
> On Fri, Apr 23, 2010 at 01:27:40PM -0700, kishore kumar wrote:
> > Now I see something different in the console.
>
> You got the kernel to boot, the initrd was able to see the disk
> and mount the partition.
>
> For posterity, what did you do from my last e-mail to get to this stage?
>
>
> > Please find the attached console output and the guest configuration file.
>
> That is normal /etc/fstab problem. You need to fix it (/etc/fstab) to have
> the right
> partitions in it. If you don't understand this, look up on Google that
> exact error.
>
[-- Attachment #1.2: Type: text/html, Size: 1193 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2010-04-23 20:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 23:13 Xen Dom U kernel kishore kumar
2010-04-14 16:14 ` [Xen-devel] " Pasi Kärkkäinen
2010-04-14 16:58 ` kishore kumar
2010-04-14 17:14 ` Pasi Kärkkäinen
2010-04-14 17:58 ` Jeremy Fitzhardinge
2010-04-16 22:24 ` [Xen-devel] " kishore kumar
2010-04-17 12:22 ` Pasi Kärkkäinen
2010-04-19 19:08 ` kishore kumar
2010-04-19 19:27 ` Pasi Kärkkäinen
2010-04-19 21:29 ` listmail
2010-04-19 23:28 ` kishore kumar
2010-04-20 3:25 ` listmail
2010-04-20 22:27 ` kishore kumar
2010-04-20 22:38 ` Konrad Rzeszutek Wilk
2010-04-20 22:53 ` [Xen-devel] " kishore kumar
2010-04-20 23:39 ` Konrad Rzeszutek Wilk
2010-04-21 0:09 ` [Xen-devel] " kishore kumar
2010-04-21 1:45 ` Konrad Rzeszutek Wilk
2010-04-22 18:31 ` kishore kumar
2010-04-22 19:53 ` Pasi Kärkkäinen
2010-04-22 20:08 ` [Xen-devel] " kishore kumar
2010-04-22 20:25 ` Pasi Kärkkäinen
2010-04-22 20:39 ` kishore kumar
2010-04-22 20:48 ` Pasi Kärkkäinen
2010-04-22 21:35 ` kishore kumar
2010-04-22 21:47 ` Konrad Rzeszutek Wilk
2010-04-23 0:15 ` kishore kumar
2010-04-23 1:36 ` Konrad Rzeszutek Wilk
2010-04-23 17:51 ` kishore kumar
2010-04-23 18:04 ` Konrad Rzeszutek Wilk
2010-04-23 18:09 ` kishore kumar
2010-04-23 18:34 ` Sander Eikelenboom
2010-04-23 18:39 ` kishore kumar
2010-04-23 20:08 ` Konrad Rzeszutek Wilk
2010-04-23 20:27 ` [Xen-devel] " kishore kumar
2010-04-23 20:37 ` Konrad Rzeszutek Wilk
2010-04-23 20:48 ` kishore kumar [this message]
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=v2s9f975f341004231348mba21f0a8qe1d21dcb7622789f@mail.gmail.com \
--to=bodkekumar@gmail.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).