From mboxrd@z Thu Jan 1 00:00:00 1970 From: "=?utf-8?q?S=2E=C3=87a=C4=9Flar?= Onur" Subject: strange domU problem Date: Wed, 10 Jan 2007 16:35:59 +0200 Message-ID: <200701101636.02759.caglar@pardus.org.tr> Reply-To: caglar@pardus.org.tr Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0913423406==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0913423406== Content-Type: multipart/signed; boundary="nextPart8470419.5GBJzpd7OG"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart8470419.5GBJzpd7OG Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi; After upgrading to current xen-3.0.4-testing.hg domU's starts to not workin= g=20 as expected, here are the some findings; * dom0 boot without a problem * xend starts without a problem * As soon as "xm create domain", domain enters a blocked state and never=20 returns (nothing changes if i use old 3.0.3-domU kernel or new one) * dmesg, xen dmesg, xen logs shows nothing strange * Starting another domU while first domU in blocked state unfreezes first o= ne=20 for a while and first domU starts to boot but after a while (~5seconds)=20 enters blocked state again * Second domU also enters blocked state as soon as it started * In order to boot/use first domU ,i have to continuosly destroy/create sec= ond=20 domU but they always ended in blocked state Here are the some output # xm create pardus -c Name ID Mem VCPUs State Time(= s) Domain-0 0 1755 1 r----- 251.3 pardus 1 256 1 -b---- 4.3 # xm create cacti -c Name ID Mem VCPUs State Time(= s) Domain-0 0 1499 1 r----- 319.1 cacti 4 256 1 -b---- 1.6 pardus 2 256 1 ------ 28.5 #xm info host : zangetsu release : 2.6.16.37-6-dom0 version : #1 Wed Jan 10 05:18:02 EET 2007 machine : i686 nr_cpus : 1 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 1 threads_per_core : 1 cpu_mhz : 1729 hw_caps : afe9fbff:00100000:00000000:00000040:00000180 total_memory : 2038 free_memory : 0 xen_major : 3 xen_minor : 0 xen_extra : .4-1 xen_caps : xen-3.0-x86_32 xen_pagesize : 4096 platform_params : virt_start=3D0xfc000000 xen_changeset : unavailable cc_compiler : Configured=20 with: /var/pisi/gcc-4.2.0-14/work/gcc-4.2-20070102/c cc_compile_by : root cc_compile_domain : cc_compile_date : Wed Jan 10 03:22:58 EET 2007 xend_config_format : 3 # cat /etc/xen/pardus name =3D "pardus"; memory =3D 256; kernel =3D "/boot/kernel-2.6.16.29-5-domU"; disk =3D [ "file:/var/xen/domU-pardus,xvda,w" ]; root =3D "/dev/xvda ro"; vif =3D [ "" ]; Log can be found @ http://cekirdek.pardus.org.tr/~caglar/xend.log Any hints will be appreciated... Cheers =2D-=20 S.=C3=87a=C4=9Flar Onur http://cekirdek.pardus.org.tr/~caglar/ Linux is like living in a teepee. No Windows, no Gates and an Apache in hou= se! --nextPart8470419.5GBJzpd7OG Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.1 (GNU/Linux) iD8DBQBFpPnSy7E6i0LKo6YRAmhFAKC5UnMHNM2Ee/IdvIUOSx3g0fNprACgiE0H tQo9U5MOfAtHwjD142ZX1W8= =Sx/n -----END PGP SIGNATURE----- --nextPart8470419.5GBJzpd7OG-- --===============0913423406== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0913423406==--