Hi all, i have a CentoOS based Xen Dom0 running gitco xen3.3.1. I''m experiencing problems with debian Lenny FV domU. After some days of perfect working the VM start to consume all cpu and than i can only connect via ssh to VM and nothing work, neither the "top" command! Any idea? Thanks a lot and regards, Francesco _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jul 14, 2009 at 12:12:28PM +0200, Francesco Gallo wrote:> Hi all, > > > > i have a CentoOS based Xen Dom0 running gitco xen3.3.1. I''m experiencing > problems with debian Lenny FV domU. After some days of perfect working the > VM start to consume all cpu and than i can only connect via ssh to VM and > nothing work, neither the "top" command! > > > > Any idea? >Why are you running it as HVM (Fully Virtualized) ? PV would be faster and most probably work better.. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi all, i have a CentoOS based Xen Dom0 running gitco xen3.3.1. I''m experiencing problems with debian Lenny FV domU. After some days of perfect working the VM start to consume all cpu and than i can only connect via ssh to VM and nothing work, neither the "top" command! Any idea? Thanks a lot and regards, Francesco _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi all, i have a CentoOS based Xen Dom0 running gitco xen3.3.1. I''m experiencing problems with debian Lenny FV domU. After some days of perfect working the VM start to consume all cpu and than i can only connect via ssh to VM and nothing work, neither the "top" command! Any idea? Thanks a lot and regards, Francesco _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Jul 16, 2009 at 2:37 PM, Francesco Gallo<cluster@xinet.it> wrote:> Hi all, > > > > i have a CentoOS based Xen Dom0 running gitco xen3.3.1. I’m experiencing > problems with debian Lenny FV domU. After some days of perfect working the > VM start to consume all cpu and than i can only connect via ssh to VM and > nothing work, neither the “top” command!It works fine on my setup, with kernel 2.6.26-2-xen-amd64. Which domU kernel did you use? What is your domU config like? Are you sure it''s not because something trivial, like out of memory? Was there any error message on console or syslog? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I''m getting the same thing - DomU runs fine for weeks or months, but then our monitoring system tells us it''s down. From the outside, it''s ''dead'' - doesn''t respond to pings or anything. From Dom0 we can connect to the console (xm console <guestname>) and get the last few pages of output - but there''s nothing unusual logged (just a load of Shorewall log lines which is normal). The guest is absolutely dead to the console as well. xentop reports that teh guest is taking 100% cpu. All I can do is kill it and restart it. Almost all my guests are Debian Lenny, installed with debbootstrap and then cloned. Some have never done it (yet !), others have done it two or three times over the last few months. Dom0 runs 2.6.18-6-xen-686 Guests run 2.6.18-5-xen-vserver-686 or 2.6.18-6-xen-686 - both have guests that have never crashed, both have guests that have. -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>On Thu, Jul 16, 2009 at 2:37 PM, Francesco Gallo<cluster@xinet.it> wrote: >> Hi all, >> >> >> >> i have a CentoOS based Xen Dom0 running gitco xen3.3.1. I''m experiencing >> problems with debian Lenny FV domU. After some days of perfect workingthe>> VM start to consume all cpu and than i can only connect via ssh to VM and >> nothing work, neither the "top" command! > > It works fine on my setup, with kernel 2.6.26-2-xen-amd64. Which domU > kernel did you use? What is your domU config like? Are you sure it''s > not because something trivial, like out of memory? Was there any error > message on console or syslog?I use Kernel 2.6.26-2-686 and my config is: kernel = ''/usr/lib/xen/boot/hvmloader'' device_model = ''/usr/lib/xen/bin/qemu-dm'' builder = ''hvm'' name = "XXXX-xxxx" memory = "4096" vcpus = 4 arc_libdir = ''lib'' # Disks disk [''phy:/dev/XenVG/SquidGatewaLV,xvda,w'',''file:/root/ISO/lenny-net.iso,hdc:cdr om,r''] vif = [ ''mac=00:10:3c:87:32:12, bridge=xenbr1, type=ioemu''] on_reboot = ''restart'' on_crash = ''destroy'' # Behaviour boot=''c'' vfb = [''type=vnc,vncunused=1''] sdl=0 and no message in console! I hope in your help! Regards, Francesco _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Simon Hobson <linux@thehobsons.co.uk> writes:> I''m getting the same thing - DomU runs fine for weeks or months, but > then our monitoring system tells us it''s down. From the outside, it''s > ''dead'' - doesn''t respond to pings or anything. From Dom0 we can > connect to the console (xm console <guestname>) and get the last few > pages of output - but there''s nothing unusual logged (just a load of > Shorewall log lines which is normal). The guest is absolutely dead to > the console as well. > > xentop reports that teh guest is taking 100% cpu. > > All I can do is kill it and restart it. > > Almost all my guests are Debian Lenny, installed with debbootstrap and > then cloned. Some have never done it (yet !), others have done it two > or three times over the last few months. > > > Dom0 runs 2.6.18-6-xen-686 > Guests run 2.6.18-5-xen-vserver-686 or 2.6.18-6-xen-686 - both have > guests that have never crashed, both have guests that have.See http://thread.gmane.org/gmane.comp.emulators.xen.devel/55056/ for a workaround. I also encountered this problem (http://lists.xensource.com/archives/html/xen-devel/2009-07/msg00659.html) however, my guest are running the stock Lenny kernel (2.6.26). -- Feri. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ferenc Wagner wrote:> > I''m getting the same thing - DomU runs fine for weeks or months, but >> then our monitoring system tells us it''s down. From the outside, it''s >> ''dead'' - doesn''t respond to pings or anything. From Dom0 we can >> connect to the console (xm console <guestname>) and get the last few >> pages of output - but there''s nothing unusual logged (just a load of >> Shorewall log lines which is normal). The guest is absolutely dead to >> the console as well. >> >> xentop reports that teh guest is taking 100% cpu. >> >> All I can do is kill it and restart it. >> >> Almost all my guests are Debian Lenny, installed with debbootstrap and >> then cloned. Some have never done it (yet !), others have done it two >> or three times over the last few months. >> >> >> Dom0 runs 2.6.18-6-xen-686 >> Guests run 2.6.18-5-xen-vserver-686 or 2.6.18-6-xen-686 - both have >> guests that have never crashed, both have guests that have. > >See http://thread.gmane.org/gmane.comp.emulators.xen.devel/55056/ for >a workaround. I also encountered this problem >(http://lists.xensource.com/archives/html/xen-devel/2009-07/msg00659.html) >however, my guest are running the stock Lenny kernel (2.6.26).Hmm, I don''t think it''s that - my symptoms are different. From the first link, I see that this event is characterised by an inability to start PV guests and existing guests showing state blocked. In my case, I can start a PV guest, and the stuck guest shows state running and consumes 100% cpu. Also, if it were that, wouldn''t I expect to see other guests on the same host lock up ? -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Simon Hobson <linux@thehobsons.co.uk> writes:> From the first link, I see that this event is characterised by an > inability to start PV guests and existing guests showing state > blocked.When a guest is stuck this way, it''s constantly in running state. There is some confusion in the report, yes.> In my case, I can start a PV guest, and the stuck guest shows state > running and consumes 100% cpu.Yes, that agrees with my experience.> Also, if it were that, wouldn''t I expect to see other guests on the > same host lock up ?It isn''t that simple. Other guests lock up when they fill their console buffers, apparently. But new guests seem to work fine for me. Just try it, when you next experience this: stop xend, kill xenconsoled, start xends. Don''t touch xenstored! If everything returns to normal, then this was it. If not, then something else. :) -- Regards, Feri. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ferenc Wagner wrote:> > From the first link, I see that this event is characterised by an >> inability to start PV guests and existing guests showing state >> blocked. > >When a guest is stuck this way, it''s constantly in running state. >There is some confusion in the report, yes. > >> In my case, I can start a PV guest, and the stuck guest shows state >> running and consumes 100% cpu. > >Yes, that agrees with my experience. > >> Also, if it were that, wouldn''t I expect to see other guests on the >> same host lock up ? > >It isn''t that simple. Other guests lock up when they fill their >console buffers, apparently. But new guests seem to work fine for >me. Just try it, when you next experience this: stop xend, kill >xenconsoled, start xends. Don''t touch xenstored! If everything >returns to normal, then this was it. If not, then something else. :)OK, I almost wrote that I''ll wait for it to happen again - but that isn''t exactly what I mean, I''m not exactly wanting it to happen ! I''ll try that next time it does happen - but it does seem to be very irregular. -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ferenc Wagner wrote:>It isn''t that simple. Other guests lock up when they fill their >console buffers, apparently. But new guests seem to work fine for >me. Just try it, when you next experience this: stop xend, kill >xenconsoled, start xends. Don''t touch xenstored! If everything >returns to normal, then this was it. If not, then something else. :)Yup, that was it exactly - just had a guest lock up on us this morning and that freed it up without a restart. :) -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users