xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Bei Guan <gbtju85@gmail.com>
To: Todd Deshane <todd.deshane@xen.org>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
	Xen Devel <xen-devel@lists.xensource.com>,
	Andrei Warkentin <andreiw@motorola.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: pvops Domain 0 Creased when boot Xen-unstable on Ubuntu10.04
Date: Wed, 18 May 2011 15:13:55 +0800	[thread overview]
Message-ID: <BANLkTi=rqU71i026vMWnLy+c-CU6FyX_2g@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=4tWusEnOWChDbm-i0y4tMmeO6hw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 5978 bytes --]

2011/5/18 Todd Deshane <todd.deshane@xen.org>

> On Tue, May 17, 2011 at 12:43 PM, Bei Guan <gbtju85@gmail.com> wrote:
> >
> >> >         You appear to be getting dumped into a debug shell within the
> >> >         initramfs
> >> >         so you can quite easily have a poke around and see what's
> >> >         going on I
> >> >         think.
> >> >
> >> >
> >> > Sorry, can you give me more detail about how to do this? What command
> >> > or what others? Many thanks.
> >>
> >> It's a minimal Linux environment, you should have e.g. "ls" and "cat".
> >> Try and find the mount command which is failing.
> >
> > I did the following command to find the failed mount command. But, it
> seems
> > can't find that. So, is there any problem with my steps and what other
> work
> > can I do?
>
> When you get dropped into the minimal (initramfs) prompt it gives you
> some good suggestions.
>
> For example. You can do  "ls /dev" and "cat /proc/modules" and you can
> probably even try to run a mount command maybe. You can also
> double-check things like "cat /proc/cmdline", etc.
>
> See if you can determine what devices in /dev are actually available,
> such as your sda, hda, or xvda devices.
>

Some boot information got from initramfs is list below. It seems that the
/dev/sda9 is available, but there no drivers module in /proc/modules. I also
can't mount /dev/sda9 to other directory. So, what's the problem with it?
And if a device that need to be mount can't be found in the /dev, what
should I do to make it available?


(initramfs) cat /proc/cmdline
nopat root=/dev/sda9 ro console=tty0 console=ttyS0,115200n8 console=hvc0
earlyprintk=xen nomodeset initcall_debug debug loglevel=10

(initramfs) ls /dev
console              ttyS1               hvc6                tty41
null                    ttyS2               hvc7                tty44
pts                    ttyS3               ptmx                tty43
loop0                 rtc0                 tty                 bsg
block                 rtc                   tty0                sg1
loop1                 hidraw0           tty1                tty46
loop3                 ttyS0               tty10               tty45
loop4                 cpu                 tty11               tty47
loop5                 sda                 tty12               tty48
loop2                 disk                tty13               tty49
loop7                 full                  tty14               tty5
ram10                kmem             tty15               tty50
ram7                  kmsg              tty16               tty51
loop6                  mem              tty17               tty52
ram1                  oldmem           tty18               tty53
ram0                   port                tty19               tty54
ram13                 random           tty2                tty55
ram11                 urandom         tty20               tty56
ram3                   zero               tty21               tty57
ram12                 autofs             tty22               tty58
ram15                 blktap-control  tty23               tty59
ram14                 cpu_dma_latency     tty24       tty6
ram9                  mapper            tty26               tty60
ram2                  mcelog             tty27               tty62
ram5                  hpet                 tty28               tty61
ram4                  network_latency        tty29       tty7
ram8                  network_throughput   tty3         tty63
ram6                  rfkill                  tty30               tty9
input                  snapshot           tty32               tty8
char                   net                    tty31               vcs
usbmon3            vga_arbiter         tty25               usbmon0
bus                    watchdog           sr0                 vcsa
adsp                  nvram                scd0                vcs1
audio                  xen                   tty35               vcsa1
dsp                    sequencer          tty36               sda8
snd                     sequencer2       tty34               sda2
mixer                  hvc0                  tty37               sda7
usbmon1             hvc1                  tty33               sda5
usbmon4             hvc2                  tty39               sda6
usbmon5             hidraw1              tty38               sda9
usbmon6             hvc3                  tty4                 sda1
usbmon7             hvc4                  tty42
usbmon2             hvc5                  tty40
(initramfs) cat /proc/modules
(initramfs)

(initramfs) mount -o /dev/sda9 /root
mount: cannot read /etc/fstab: No such file or directory
(initramfs) ls /etc
modprobe.d     default        lvm            console-setup  udev
(initramfs) fstype /dev/sda\b9
FSTYPE=ext4dev
FSSIZE=33738981376

(initramfs) ls /
dev      lib64    var      init     conf     scripts  proc
root     lib      bin      etc      sbin     sys      tmp


Thanks
Bei Guan


>
> Hope that helps.
>
> Thanks,
> Todd
>
> > (initramfs) dmeg | grep mount
> > (initramfs)
> > (initramfs) cat /proc/mounts
> > rootfs / rootfs rw 0 0
> > none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
> > none /proc proc rw,nosuid,nodev,noexec,relatime 0 0
> > none /dev tmpfs rw,relatime,mode=755 0 0
> > none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620 0 0
> > (initramfs)
> >
> > Thanks,
> > Bei Guan
> >
> >>
> >> Ian.
> >> >
> >> >
> >> >
> >> >
> >> >         Ian.
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> >
> >
>
>
>
> --
> Todd Deshane
> http://www.linkedin.com/in/deshantm
> http://www.xen.org/products/cloudxen.html
> http://runningxen.com/
>

[-- Attachment #1.2: Type: text/html, Size: 7977 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-05-18  7:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 17:42 pvops Domain 0 Creased when boot Xen-unstable on Ubuntu10.04 Bei Guan
2011-05-16 17:53 ` Konrad Rzeszutek Wilk
2011-05-17 14:39   ` Bei Guan
2011-05-17 14:44     ` Konrad Rzeszutek Wilk
2011-05-17 15:27       ` Bei Guan
2011-05-17 15:34         ` Ian Campbell
2011-05-17 15:48           ` Bei Guan
2011-05-17 15:49             ` Ian Campbell
2011-05-17 16:43               ` Bei Guan
2011-05-17 21:40                 ` Todd Deshane
2011-05-18  7:13                   ` Bei Guan [this message]
2011-05-18  7:25                     ` Ian Campbell
2011-05-18  7:43                       ` Bei Guan
2011-05-18  8:11                         ` Ian Campbell

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='BANLkTi=rqU71i026vMWnLy+c-CU6FyX_2g@mail.gmail.com' \
    --to=gbtju85@gmail.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=andreiw@motorola.com \
    --cc=konrad.wilk@oracle.com \
    --cc=todd.deshane@xen.org \
    --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 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).