Hi All, The dom0 suddenly stops responding. The time interval is not regular. I am not able to access it even via network. It just freezes and do not respond. No message appears on console. Any suggestion will be of great help. booty _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Jun 21, 2007, at 10:21 AM, ashok bhardwaj wrote:> Hi All, > > The dom0 suddenly stops responding. The time interval is not > regular. I am not able to access it even via network. It just > freezes and do not respond. No message appears on console. > Any suggestion will be of great help. >It would be hugely useful if you gave a bit more information. 1. What version of Xen? 2. What kernel version are you running and what distribution? 3. What domUs are you running and what kernel versions? 4. What did you change or update before the dom0 started crashing? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
cremes.devlist@mac.com <cremes.devlist@mac.com> wrote:>> The dom0 suddenly stops responding. The time interval is not >> regular. I am not able to access it even via network. It just >> freezes and do not respond. No message appears on console. >> Any suggestion will be of great help. >> > > It would be hugely useful if you gave a bit more information. > > 1. What version of Xen? > 2. What kernel version are you running and what distribution? > 3. What domUs are you running and what kernel versions? > > 4. What did you change or update before the dom0 started crashing?I have the same problem, Xen 3.1.0 with a custom kernelconfig on Athlon 64 x86_64 mode. Freezes are irregular (anywhere between 30 minutes and two days so far), machine does not respond to anything after that. Unfortunately it is 200km away and while I do have console view (Peppercon LARA) it does not allow me to send Ctrl-a to Xen Hypervisor or SysRq to the kernel. Distributions are Debian etch both in dom0 and domU. The machine is running rock-solid with the etch-shipped non-xen Debian kernel, memtest is fine. So far it only has one single domU that servers a few DNS requests per minute with a perl script, so almost no load. I think it lives substantially longer when no domU is running at all, but I''m not exactly sure and I don''t know how long I will have that Peppercon thing, so I''d rather not sit a week waiting for a crash without domU. Unfortunately this is a new box, so there isn''t really a period "before crashing". I will downgrade to Xen 3.0.4 tomorrow which I have running in a similar environment (almost the same hardware (except NIC and SATA driver), the same setup) for ages now. Anything I can to do help debugging? Regards, Bernhard _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Bernhard Schmidt <berni@birkenwald.de> wrote:> I think it lives substantially longer when no domU is running at all, > but I''m not exactly sure and I don''t know how long I will have that > Peppercon thing, so I''d rather not sit a week waiting for a crash > without domU.Crashed again without domU, I''m going to downgrade now. Regards, Bernhard _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Bernhard Schmidt <berni@birkenwald.de> wrote:>> I think it lives substantially longer when no domU is running at all, >> but I''m not exactly sure and I don''t know how long I will have that >> Peppercon thing, so I''d rather not sit a week waiting for a crash >> without domU. > Crashed again without domU, I''m going to downgrade now.Downgrading to 3.0.4 did not work (the 2.6.16.33 kernel does not find/use my VIA SATA controller), upgrading to 3.0-unstable (from hg) exposes the very same problem, freeze of dom0 within minutes to hours. Informations with xen 3.1.0: xm dmesg: http://users.birkenwald.de/~berni/volatile/xm_dmesg.txt xm info: http://users.birkenwald.de/~berni/volatile/xm_info.txt dmesg: http://users.birkenwald.de/~berni/volatile/dmesg.txt dom0 conf: http://users.birkenwald.de/~berni/volatile/xen.config The machine is perfectly stable with Kernel 2.6.18-4-amd, I''ve been doing bzip2/bunzip2/diff in a loop for half a day now, no issues. Memtest86+ is currently running, but does not show any issues as well. Any more information needed? Should I open a bugreport? Regards, Bernhard _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Bernhard Schmidt <berni@birkenwald.de> wrote: > >>> I think it lives substantially longer when no domU is running at all, >>> but I''m not exactly sure and I don''t know how long I will have that >>> Peppercon thing, so I''d rather not sit a week waiting for a crash >>> without domU. >> Crashed again without domU, I''m going to downgrade now. > > Downgrading to 3.0.4 did not work (the 2.6.16.33 kernel does not > find/use my VIA SATA controller), upgrading to 3.0-unstable (from hg) > exposes the very same problem, freeze of dom0 within minutes to hours. > > Informations with xen 3.1.0: > xm dmesg: http://users.birkenwald.de/~berni/volatile/xm_dmesg.txt > xm info: http://users.birkenwald.de/~berni/volatile/xm_info.txt > dmesg: http://users.birkenwald.de/~berni/volatile/dmesg.txt > dom0 conf: http://users.birkenwald.de/~berni/volatile/xen.config > > The machine is perfectly stable with Kernel 2.6.18-4-amd, I''ve been > doing bzip2/bunzip2/diff in a loop for half a day now, no issues. > Memtest86+ is currently running, but does not show any issues as well. > > Any more information needed? Should I open a bugreport? > > Regards, > Bernhard >Yes you need to submit a bug report. It looks like you''ve done a good amount of testing on your own, its time to at least open an issue with the developers. I personally don''t know what else could be going on. Ryan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ryan Burke wrote:>> Bernhard Schmidt <berni@birkenwald.de> wrote: >>You might have to delete all files in /var/lib/xenstored/ This solved it for me on CentOs 5 ++>> >>>> I think it lives substantially longer when no domU is running at all, >>>> but I''m not exactly sure and I don''t know how long I will have that >>>> Peppercon thing, so I''d rather not sit a week waiting for a crash >>>> without domU. >>>> >>> Crashed again without domU, I''m going to downgrade now. >>> >> Downgrading to 3.0.4 did not work (the 2.6.16.33 kernel does not >> find/use my VIA SATA controller), upgrading to 3.0-unstable (from hg) >> exposes the very same problem, freeze of dom0 within minutes to hours. >> >> Informations with xen 3.1.0: >> xm dmesg: http://users.birkenwald.de/~berni/volatile/xm_dmesg.txt >> xm info: http://users.birkenwald.de/~berni/volatile/xm_info.txt >> dmesg: http://users.birkenwald.de/~berni/volatile/dmesg.txt >> dom0 conf: http://users.birkenwald.de/~berni/volatile/xen.config >> >> The machine is perfectly stable with Kernel 2.6.18-4-amd, I''ve been >> doing bzip2/bunzip2/diff in a loop for half a day now, no issues. >> Memtest86+ is currently running, but does not show any issues as well. >> >> Any more information needed? Should I open a bugreport? >> >> Regards, >> Bernhard >> >> > > Yes you need to submit a bug report. It looks like you''ve done a good > amount of testing on your own, its time to at least open an issue with the > developers. I personally don''t know what else could be going on. > > Ryan > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >-- Virtual Space International Inc. Steven Dugway USA 206-734-HOST Canada 514-939-HOST (4678) ext 5 Skype:stevenvsi; savetimehosting.net 911hosting.net goodprivacy.net Spam is not allowed: AUP http://www.virtualspaceintl.net/acceptable_use.html -------------------------------------------------------------- Internet Is Here To Stay, Make Sure Your Business Is! -------------------------------------------------------------- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Steven wrote: Hi,> You might have to delete all files in /var/lib/xenstored/ > This solved it for me on CentOs 5Didn''t help. It appears to have been a hardware issue after all, I had my hoster replace the mainboard for one with an AMD chipset and it was still crashing. After replacing RAM, CPU and Power Supply the machine has been stable for over a week now. Again note that all possible test tools (memtest86+, cpuburn, compression/decompression/md5 in a loop) worked fine. Still a little bit too early to be sure (I once had an uptime of >1 week before, although without load), but it looks like a solution. I''ll keep looking for one more week and close the bugzilla report I opened.>>>>> I think it lives substantially longer when no domU is running at all, >>>>> but I''m not exactly sure and I don''t know how long I will have that >>>>> Peppercon thing, so I''d rather not sit a week waiting for a crash >>>>> without domU. >>>>> >>>> Crashed again without domU, I''m going to downgrade now. >>>> >>> Downgrading to 3.0.4 did not work (the 2.6.16.33 kernel does not >>> find/use my VIA SATA controller), upgrading to 3.0-unstable (from hg) >>> exposes the very same problem, freeze of dom0 within minutes to hours. >>> >>> Informations with xen 3.1.0: >>> xm dmesg: http://users.birkenwald.de/~berni/volatile/xm_dmesg.txt >>> xm info: http://users.birkenwald.de/~berni/volatile/xm_info.txt >>> dmesg: http://users.birkenwald.de/~berni/volatile/dmesg.txt >>> dom0 conf: http://users.birkenwald.de/~berni/volatile/xen.config >>> >>> The machine is perfectly stable with Kernel 2.6.18-4-amd, I''ve been >>> doing bzip2/bunzip2/diff in a loop for half a day now, no issues. >>> Memtest86+ is currently running, but does not show any issues as well. >>> >>> Any more information needed? Should I open a bugreport? >>> >>> Regards, >>> Bernhard >>> >>> >> >> Yes you need to submit a bug report. It looks like you''ve done a good >> amount of testing on your own, its time to at least open an issue with >> the >> developers. I personally don''t know what else could be going on.Regards, Bernhard _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users