From: Anthony Liguori <aliguori@us.ibm.com>
To: Gabor HALASZ <halasz.g@freemail.hu>
Cc: Xen-devel@lists.xensource.com
Subject: Re: No block devices in domU
Date: Fri, 28 Oct 2005 13:11:33 -0500 [thread overview]
Message-ID: <436269D5.9050906@us.ibm.com> (raw)
In-Reply-To: <43620D87.5050106@freemail.hu>
Gabor HALASZ wrote:
> Hi!
>
> I tried to build a devel xen on x86_64 (xeon) on debian sarge; updated
> with mercurial, and built with default kernel config. When booting
> domU I can't see xen_blk: initialize... line on the console and I
> havn't block devices in domU.
Ryan Harper and I are looking into this right now.
There's a race condition somewhere in the block front driver. Xend is
doing everything it's supposed to and the frontend appears to be being
probed.
Regards,
Anthony Liguori
> The messages of domU
>
> ...
> RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize
> Xen virtual console successfully installed as tty1
> Event-channel device installed.
> xen_net: Initialising virtual ethernet driver.
> md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
> NET: Registered protocol family 2
> ...
> # mount /proc/
> # cat /proc/devices
> Character devices:
> 1 mem
> 4 tty
> 5 /dev/tty
> 5 /dev/console
> 5 /dev/ptmx
> 10 misc
> 128 ptm
> 136 pts
> 203 cpu/cpuid
>
> Block devices:
> 1 ramdisk
> 9 md
> 254 mdp
>
> The view from dom0:
>
> xen:~# xm list
> Name ID Mem(MiB) VCPUs State Time(s)
> Domain-0 0 245 1 r----- 2100.4
> test 10 256 1 -b---- 0.5
> xen:~# xm block-list 10
> (2049 ((virtual-device 2049) (backend-id 0) (backend
> /local/domain/0/backend/vbd/10/2049) (ring-ref 8) (event-channel 6)))
> (2050 ((virtual-device 2050) (backend-id 0) (backend
> /local/domain/0/backend/vbd/10/2050) (ring-ref 9) (event-channel 7)))
> (2051 ((virtual-device 2051) (backend-id 0) (backend
> /local/domain/0/backend/vbd/10/2051) (ring-ref 10) (event-channel 8)))
>
> The configuration:
>
> xen:~# cat /etc/xen/test
> builder = 'linux'
> kernel = "/boot/vmlinuz-2.6.12.6-xenU"
> ramdisk = "/boot/ramdisk.ext2"
> memory = 256
> name = "test"
> nics = 0
> on_poweroff = 'destroy'
> on_reboot = 'restart'
> on_crash = 'restart'
> root = "/dev/ram0 rw"
> vcpus = 1
> extra = "ramdisk=32768"
> disk = [ 'phy:evms/ZorpRoot,sda1,w',
> 'phy:evms/ZorpLog,sda2,w', 'phy:evms/ZorpSwap,sda3,w' ]
>
> What can I do?
>
prev parent reply other threads:[~2005-10-28 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 11:37 No block devices in domU Gabor HALASZ
2005-10-28 18:11 ` Anthony Liguori [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=436269D5.9050906@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=Xen-devel@lists.xensource.com \
--cc=halasz.g@freemail.hu \
/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.