Hi; After upgrading to current xen-3.0.4-testing.hg domU''s starts to not working 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 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 one for a while and first domU starts to boot but after a while (~5seconds) 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 second 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=0xfc000000 xen_changeset : unavailable cc_compiler : Configured 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 = "pardus"; memory = 256; kernel = "/boot/kernel-2.6.16.29-5-domU"; disk = [ "file:/var/xen/domU-pardus,xvda,w" ]; root = "/dev/xvda ro"; vif = [ "" ]; Log can be found @ http://cekirdek.pardus.org.tr/~caglar/xend.log Any hints will be appreciated... Cheers -- S.Çağlar Onur <caglar@pardus.org.tr> http://cekirdek.pardus.org.tr/~caglar/ Linux is like living in a teepee. No Windows, no Gates and an Apache in house! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi; 10 Oca 2007 Çar 16:35 tarihinde, S.Çağlar Onur şunları yazmıştı:> After upgrading to current xen-3.0.4-testing.hg domU''s starts to not > working 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 > 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 > one for a while and first domU starts to boot but after a while (~5seconds) > 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 > second domU but they always ended in blocked stateAfter trying lots of different setups i found the problem, somehow if xen/ is compiled with gcc-4.2 domU hangs forever as i described but dom0 boots/works fine without a problem. So here are the some more findings; * gcc-3.4.6 compiled xen/ and gcc-4.2 compiled dom0/domU kernels (3.0.4_1) works well, * gcc-4.2 compiled xen/ and gcc-3.4.6 compiled dom0/domU kernels (3.0.3) hangs as described, So neither gcc-4.2 generates wrong code for hypervisor or xen/ has some bugs triggered by gcc-4.2. Is there a way to debug/investigate so i can try to find the problem? Cheers -- S.Çağlar Onur <caglar@pardus.org.tr> http://cekirdek.pardus.org.tr/~caglar/ Linux is like living in a teepee. No Windows, no Gates and an Apache in house! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel