Hi! When I tried to start a domU where the root-device (/dev/md/5) was still mounted in the dom0, I got an error about the dev being mounted. A "xm destroy domain" resulted in a Zombie and a Kernel-Ooops (following below). When I tried to start the domain after unmounting the device, it shows up in "xm list", but doesn''t start (but can be destroyed) Is there anything I can do about the zombies exept for KILLING the xend process? shutting down doesn''t work, since it tries to shutdown/destroy the zombies ... Kernel: 2.6.16-rc3-xen xen: 3.0.0 (xm info), build-nr(?) 8885 (number of gentoo ebuild) Syslog: Feb 23 15:08:08 piggy kernel: general protection fault: 0000 [#1] Feb 23 15:08:08 piggy kernel: SMP Feb 23 15:08:08 piggy kernel: Modules linked in: xt_physdev iptable_filter ip_tables x_tables Feb 23 15:08:08 piggy kernel: CPU: 0 Feb 23 15:08:08 piggy kernel: EIP: 0061:[<c0168159>] Not tainted VLI Feb 23 15:08:08 piggy kernel: EFLAGS: 00010286 (2.6.16-rc3-xen #1) Feb 23 15:08:08 piggy kernel: EIP is at blkdev_put+0xd/0x13c Feb 23 15:08:08 piggy kernel: eax: fffffffa ebx: fffffffa ecx: 00000000 edx: 00000019 Feb 23 15:08:08 piggy kernel: esi: c471db88 edi: c0572340 ebp: 00000000 esp: c11abef0 Feb 23 15:08:08 piggy kernel: ds: 007b es: 007b ss: 0069 Feb 23 15:08:08 piggy kernel: Process events/0 (pid: 8, threadinfo=c11aa000 task=c11a1030) Feb 23 15:08:08 piggy kernel: Stack: <0>00000000 00000000 c471db40 c471db88 c0572340 c471db1c c02b75a8 fffffffa Feb 23 15:08:08 piggy kernel: c471db1c c02b7415 c471db40 c471db1c c471db84 c012f94f c471db1c c012c3cf Feb 23 15:08:08 piggy kernel: c11abf3c c0572360 c057234c c02b73f8 00000000 c0572354 c11abf8c c057234c Feb 23 15:08:08 piggy kernel: Call Trace: Feb 23 15:08:08 piggy kernel: [<c02b75a8>] vbd_free+0x29/0x2b Feb 23 15:08:08 piggy kernel: [<c02b7415>] free_blkif+0x1d/0x6e Feb 23 15:08:08 piggy kernel: [<c012f94f>] run_workqueue+0x76/0xea Feb 23 15:08:08 piggy kernel: [<c012c3cf>] do_sigaction+0x1a3/0x275 Feb 23 15:08:08 piggy kernel: [<c02b73f8>] free_blkif+0x0/0x6e Feb 23 15:08:08 piggy kernel: [<c012fb05>] worker_thread+0x142/0x164 Feb 23 15:08:08 piggy kernel: [<c0119f5f>] default_wake_function+0x0/0x12 Feb 23 15:08:08 piggy kernel: [<c0119f5f>] default_wake_function+0x0/0x12 Feb 23 15:08:08 piggy kernel: [<c012f9c3>] worker_thread+0x0/0x164 Feb 23 15:08:08 piggy kernel: [<c0132fd5>] kthread+0xb7/0xbd Feb 23 15:08:08 piggy kernel: [<c0132f1e>] kthread+0x0/0xbd Feb 23 15:08:08 piggy kernel: [<c0105e75>] kernel_thread_helper+0x5/0xb Feb 23 15:08:08 piggy kernel: Code: 24 04 89 3c 24 e8 f2 f9 ff ff 89 c3 31 c0 85 db 74 dc 89 3c 24 e8 04 00 00 00 89 d8 eb d0 55 31 ed 57 56 53 83 ec 08 8b 5c 24 1c <8b> 73 04 8b 7b 58 f0 ff 4b 0c 0f 88 2f 04 00 00 e8 01 6c 23 00 Feb 23 15:08:08 piggy logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/2/2050 -- ********************************************************************* * * * Martin Schipany email: elcondor@warum.net * * mobil: +43 660 770 880 0 * * fax : +43 660 33 770 880 0 * * IRC : ElCondor on channel #diddl * * * *******************************************************************'' _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Martin Schipany wrote:> Hi! > > When I tried to start a domU where the root-device (/dev/md/5) was still > mounted in the dom0, I got an error about the dev being mounted. A "xm > destroy domain" resulted in a Zombie and a Kernel-Ooops (following below). > When I tried to start the domain after unmounting the device, it shows up > in "xm list", but doesn''t start (but can be destroyed) > > Is there anything I can do about the zombies exept for KILLING the xend > process? shutting down doesn''t work, since it tries to shutdown/destroy the > zombies ...Hi Martin, I don''t have an answer to this, and from everything I''ve read these zombies are not easily killed. But, I want to draw more attention to this, because I''m having similar problems, and yes, my test server will hang when shutting down as well. Another thing that bothered me is that the command: xm shutdown --all --wait --halt was destroying my domains, but they hadn''t even finished shutting down yet. In fact, they were destroyed before the file systems were even unmounted. So much for data integrity. Then I found that a timeout was killing them prematurely. Naturally I searched through all configuration files, but didn''t find the timeout. It was hard-coded in python/xen/xend/XendDomainInfo.py. I''ve changed it, but hard-coding something like this gives me an uneasy feeling. These situations have prevented me from releasing Xen 3 in a stable environment. Okay, I''ve done my due diligence with Xen 3 and I won''t put it on my stable servers. However, I take issue with the front page of the www.xensource.com web page. There''s a big icon that says "Xen 3.0 Now in Community Release!" Then, you go to the download page to download 3.0.1: "The downloads on this page have been built from the Xen 3.0.1 open source community code base. They have undergone very limited testing, are not supported in any way whatsoever, and will be fixed on a best-effort basis only." I''m sorry Xen project managers, but if Xen 3 isn''t ready for production, then please draw more attention to the Xen 2.0 on the Xensource web page. Or at least, on the Xen 3 downloads page, include a link for Xen 2 and state that *that''s* what should be used in a stable environment. I worry about people who haven''t done testing on Xen 3 and have decided to run Xen 3 in a production setting. -James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 James Henderson wrote:> I''m sorry Xen project managers, but if Xen 3 isn''t ready for production, > then please draw more attention to the Xen 2.0 on the Xensource web > page. Or at least, on the Xen 3 downloads page, include a link for Xen > 2 and state that *that''s* what should be used in a stable environment. >I''m somewhat new to Xen, so I''m curious. Xen 2.0.7 is significantly more stable than the 3.0 version? I''ve only run into one problem with my VM''s: They don''t shutdown cleanly when I run xm shutdown domain1 . The domain simply powers off. I may downgrade to xen 2.0.7 in the hopes that stuff works better... Another question, whats the most recent kernel that xen uses? Is it just 2.6.12.6 (Xen 3.0)? Thanks, - -- David Kowis ISO Team Lead - www.sourcemage.org Source Mage GNU/Linux Progress isn''t made by early risers. It''s made by lazy men trying to find easier ways to do something. - Robert Heinlein Any sufficiently advanced technology is indistinguishable from magic. - Arthur C. Clarke -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) iQGVAwUBQ/9C0cnf+vRw63ObAQoDnQv9HkY5Lp4hyIhNSWj3sCR0CqpssWVWeSMJ A+AlHJE+JkzbVHklNsF0B24vFpUGjem/8dzIPvGJRG3PIgbbdzMvteHjKZYjirkx hHwxHSzpUcotTennaLvawAlPL1PsWCZzZ9dCLSYc8bw7zECnj8ilcEAbQoWaeKdG LwEknqlgdmJC+y2cfhDVTPtatiZUhsyR7pmoO9pGR5TohWH1WWs+wHjG8QGGsfNe QZpRaEiGAy8G0NAKrZeW2aYaag96MsZ3z4afiqJx39seSevdEpnZvmGlHWiP1akw wT7p5vkI7VsO9wrsl7ZLZBkRdi1v92I2vORthVVRjnWo1gYC6cFf4cCjmG/SQW3X NE9E7qBMbBLL5c6z3LCnwu9oSMtD31S3A8+5ypyjDejYFrTLwEf3wiqIq9qr3/m6 YN4lRAd5+/6/tAcjJJVmuxfMjK6aQeO5u7O8hmocW/lcCwx1D+iymSjCssVeYR8+ 2G3lkpEVsqI/iFOBxxEUGQbzWE0QQKrk =k3Nx -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Feb 24, 2006 at 11:30:57AM -0600, David Kowis wrote:> James Henderson wrote: > > I''m sorry Xen project managers, but if Xen 3 isn''t ready for production, > > then please draw more attention to the Xen 2.0 on the Xensource web > > page. Or at least, on the Xen 3 downloads page, include a link for Xen > > 2 and state that *that''s* what should be used in a stable environment. > > > > I''m somewhat new to Xen, so I''m curious. Xen 2.0.7 is significantly more > stable than the 3.0 version? I''ve only run into one problem with my > VM''s: They don''t shutdown cleanly when I run xm shutdown domain1 . The > domain simply powers off. I may downgrade to xen 2.0.7 in the hopes that > stuff works better...In my experience xen 3.x has lots of bugs that the developers have not yet found time to address, whereas xen 2.x has lots of bugs that are either known about and won''t be fixed or are unknown and won''t be investigated, since 2.x is effectively obsolete now. So personally I wouldn''t downgrade to 2.x except as a last resort. Unfortunately for me the hardware I''m having most trouble with will not boot at all under 2.x and just memory leaks itself to death under 3.x, so... :) At least using 3.x your bug reports can do some good. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Andy Smith wrote:> In my experience xen 3.x has lots of bugs that the developers have not > yet found time to address, whereas xen 2.x has lots of bugs that are > either known about and won''t be fixed or are unknown and won''t be > investigated, since 2.x is effectively obsolete now. > > So personally I wouldn''t downgrade to 2.x except as a last resort. > > Unfortunately for me the hardware I''m having most trouble with will > not boot at all under 2.x and just memory leaks itself to death > under 3.x, so... :)D''oh! :(> > At least using 3.x your bug reports can do some good.Works for me :) I''m planning on putting my vms through some pretty hefty thrashing. Should definitely test their stability. And I''ve no big problems with using xen 3.0 so I''ll stick with it then. Thanks :) - -- David Kowis ISO Team Lead - www.sourcemage.org Source Mage GNU/Linux Progress isn''t made by early risers. It''s made by lazy men trying to find easier ways to do something. - Robert Heinlein Any sufficiently advanced technology is indistinguishable from magic. - Arthur C. Clarke -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) iQGVAwUBQ/9HRcnf+vRw63ObAQp03gv/WYjtD3Xdxn9WUt9nBIa/RYxvG/Qq2WoO J2qroBXpRletq/MzkGK4uw1YXJJQ5vXmlqB2T6I7A4u0Lv/7aSCXzPCk45tjRKvH Qs8pbsbtVXylRls4bA36W85ip3CoC27nZBASs2eU1zBUDlexttA9Y69HlkEv3R0z L6wmYTazf5RdluMJ25XZsKlO/noWHsHkRkJzw+NyJOSsPfsTsntXwMQQ0jmleJWu 1Hs2FHKd2NsYXFw9b3RDvxO64FBJQX8bUBk0ooNsICjUeL+2MuZzePT6ACE0yjlQ aJWicXlBop+66zywY3nNxg0fjmC4q6rBtglPwoMYC9Wy5r30AOPWiP7RUpGC8BUD NE+m12yxmQjE9oMHk0VVTHGM7cpE1Onhp6yR54oA0mdeM5h4FLpkOHoYy2y6lANz OhIAnxG+LkkxvQj1Uqo2O0tFPook2Li7XX8r4Po7BNiHJ4cpae4+fykwDn+O6ZkU MQsYXC7iqOTteHmISG15TpombBKOB2m9 =JQ1e -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users