From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jia Rao Subject: domU can not start in Xen 4.0.1-rc3-pre using tapdisk Date: Tue, 22 Jun 2010 11:01:18 -0400 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1881646924==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: xen-users@lists.xensource.com, xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============1881646924== Content-Type: multipart/alternative; boundary=00151747363e89596b04899fb132 --00151747363e89596b04899fb132 Content-Type: text/plain; charset=ISO-8859-1 The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1. However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS: Waiting for devices to initialise: 295s...290s... Then after reboot, the domU can not mount the filesystem /dev/root and kernel panic. *When using tap:tapdisk:aio* PATH/disk.img. the booting process terminated at a error: Error: [Errno 2] No such file or directory: 'aio:/PATH/disk.img' *When using file*:PATH/disk.img, domU can boot successfully. Thus I am afraid it is somethin wrong with tapdisk driver in dom0 FYI dom0: 2.6.32.15 centos 5.4 dom0 config: CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XEN_NETDEV_BACKEND=y CONFIG_XEN_BLKDEV_BACKEND=y CONFIG_XEN_BLKDEV_TAP=m CONFIG_XEN_BLKBACK_PAGEMAP=y CONFIG_XEN_PCIDEV_BACKEND=y CONFIG_XEN_PCIDEV_BACKEND_VPCI=y CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_XEN_NETDEV_FRONTEND=m I did load the modules: blktap xen_blkfront xen_netfront before starting xend. xen: 4.0.1-rc3-pre any ideas? Thanks. --00151747363e89596b04899fb132 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be boo= ted successfully under 2.6.18.8-xen dom0 and xen 3.3.1.

= However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can = not boot with tapdisk. I am wondering it is something related to the blktap= driver.

When using tap:aio: PATH/disk.img in domU disk c= onfiguration, the boot process hanged at a prompt:
XENBUS: Waitin= g for devices to initialise: 295s...290s...
Then after reboot, th= e domU can not mount the filesystem /dev/root and kernel panic.

When using tap:tapdisk:aio PATH/disk.img. the bo= oting process terminated at a error:
Error: [Errno 2] No such fil= e or directory: 'aio:/PATH/disk.img'

Wh= en using file:PATH/disk.img, domU can boot successfully.

Thus I am afraid it is somethin wrong with tapdisk driv= er in dom0

FYI
dom0: 2.6.32.15 centos 5.= 4
dom0 config:=A0
CONFIG_XEN_BALLOON=3Dy
CONFIG_XEN_SCRUB_PAGES=3Dy
CONFIG_XEN_DEV_EVTCHN=3Dy
CO= NFIG_XEN_BACKEND=3Dy
CONFIG_XEN_NETDEV_BACKEND=3Dy
CONF= IG_XEN_BLKDEV_BACKEND=3Dy
CONFIG_XEN_BLKDEV_TAP=3Dm
CON= FIG_XEN_BLKBACK_PAGEMAP=3Dy
CONFIG_XEN_PCIDEV_BACKEND=3Dy
CONFIG_XEN_PCIDEV_BACKEND_VPCI= =3Dy
CONFIG_XEN_BLKDEV_FRONTEND=3Dm
CONFIG_XEN_NE= TDEV_FRONTEND=3Dm

I did load the modules: blktap x= en_blkfront xen_netfront before starting xend.

xen: 4.0.1-rc3-pre

any ideas?<= /div>

Thanks.


--00151747363e89596b04899fb132-- --===============1881646924== 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 --===============1881646924==--