From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Lu=EDs?= Silva Subject: Re: domU can not start in Xen 4.0.1-rc3-pre using tapdisk Date: Tue, 22 Jun 2010 23:57:02 +0100 Message-ID: <1277247422.2566.2.camel@luis-port> References: Reply-To: luis.silva@axiomasoft.pt Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1229747245==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: Jia Rao Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============1229747245== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-hcMxY9vANgEKxtrYHVo2" --=-hcMxY9vANgEKxtrYHVo2 Content-Type: multipart/alternative; boundary="=-/6OWBFEHzcSyXRZ3visM" --=-/6OWBFEHzcSyXRZ3visM Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, I think that in order to use tap devices with pvops kernel you have to use "tap2:aio:path_to_file". At least it works for me... Even for 4.0.1 rc2 I had to use "tap2:tapdisk:aio:...". Lu=C3=ADs On Tue, 2010-06-22 at 11:01 -0400, Jia Rao wrote: > 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. >=20 >=20 >=20 > 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. >=20 >=20 > 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. >=20 >=20 > 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' >=20 >=20 > When using file:PATH/disk.img, domU can boot successfully. >=20 >=20 > Thus I am afraid it is somethin wrong with tapdisk driver in dom0 >=20 >=20 > FYI > dom0: 2.6.32.15 centos 5.4 > dom0 config:=20 > CONFIG_XEN_BALLOON=3Dy > CONFIG_XEN_SCRUB_PAGES=3Dy > CONFIG_XEN_DEV_EVTCHN=3Dy > CONFIG_XEN_BACKEND=3Dy > CONFIG_XEN_NETDEV_BACKEND=3Dy > CONFIG_XEN_BLKDEV_BACKEND=3Dy > CONFIG_XEN_BLKDEV_TAP=3Dm > CONFIG_XEN_BLKBACK_PAGEMAP=3Dy > CONFIG_XEN_PCIDEV_BACKEND=3Dy > CONFIG_XEN_PCIDEV_BACKEND_VPCI=3Dy > CONFIG_XEN_BLKDEV_FRONTEND=3Dm > CONFIG_XEN_NETDEV_FRONTEND=3Dm >=20 >=20 > I did load the modules: blktap xen_blkfront xen_netfront before > starting xend. >=20 >=20 > xen: 4.0.1-rc3-pre >=20 >=20 > any ideas? >=20 >=20 > Thanks. >=20 >=20 >=20 >=20 >=20 > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users --=-/6OWBFEHzcSyXRZ3visM Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello,

I think that in order to use tap devices with pvops kernel you have to use = "tap2:aio:path_to_file". At least it works for me... Even = for 4.0.1 rc2 I had to use "tap2:tapdisk:aio:...".

Luís
On Tue, 2010-06-22 at 11:01 -0400, Jia Rao wrote:

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 bl= ktap driver.

When using tap:aio: PATH/disk.img in domU disk configuration, th= e 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 te= rminated 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=3Dy

CONFIG_XEN_SCRUB_PAGES=3Dy

CONFIG_XEN_DEV_EVTCHN=3Dy

CONFIG_XEN_BACKEND=3Dy

CONFIG_XEN_NETDEV_BACKEND=3Dy

CONFIG_XEN_BLKDEV_BACKEND=3Dy

CONFIG_XEN_BLKDEV_TAP=3Dm

CONFIG_XEN_BLKBACK_PAGEMAP=3Dy

CONFIG_XEN_PCIDEV_BACKEND=3Dy

CONFIG_XEN_PCIDEV_BACKEND_VPCI=3Dy

CONFIG_XEN_BLKDEV_FRONTEND=3Dm

CONFIG_XEN_NETDEV_FRONTEND=3Dm

I did load the modules: blktap xen_blkfront xen_netfront before startin= g xend.

xen: 4.0.1-rc3-pre

any ideas?

Thanks.

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

--=-/6OWBFEHzcSyXRZ3visM-- --=-hcMxY9vANgEKxtrYHVo2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAkwhP7oACgkQXSU0BM8MHj8FdQCfTVZlKu+2eMler6p4XhKu2ola 9S8AnijV3N27AdIn9kBrdnqjv5vSFLPi =mQvB -----END PGP SIGNATURE----- --=-hcMxY9vANgEKxtrYHVo2-- --===============1229747245== 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 --===============1229747245==--