Hello, I''m observing a situation where domU crashes and xend continuously tries to restart it. For example, I have to write commands like this to actually get it to stop: for i in `seq 80 90`; do xm destroy $i; done I''ve tried adding restart = "never" and restart = ''never'' to the domain config file (the file that gets passed to `xm create`). Is this a known issue? Am I doing something wrong? Thanks, -Jon _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Mon, Oct 10, 2005 at 02:53:53PM -0400, Jonathan M. McCune wrote:> Hello, > > I''m observing a situation where domU crashes and xend continuously tries > to restart it. For example, I have to write commands like this to > actually get it to stop: > > for i in `seq 80 90`; do xm destroy $i; done > > I''ve tried adding restart = "never" and restart = ''never'' to the domain > config file (the file that gets passed to `xm create`). Is this a known > issue? Am I doing something wrong?It''s a bug. Please use the new config options on_poweroff, on_reboot, and on_crash (documented in the example configuration files in tools/examples/xmexample{1,2,3}). We are supposed to be backwards compatible with the old restart option, but that is clearly broken. Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Mon, Oct 10, 2005 at 08:41:05PM +0100, Ewan Mellor wrote:> On Mon, Oct 10, 2005 at 02:53:53PM -0400, Jonathan M. McCune wrote: > > > Hello, > > > > I''m observing a situation where domU crashes and xend continuously tries > > to restart it. For example, I have to write commands like this to > > actually get it to stop: > > > > for i in `seq 80 90`; do xm destroy $i; done > > > > I''ve tried adding restart = "never" and restart = ''never'' to the domain > > config file (the file that gets passed to `xm create`). Is this a known > > issue? Am I doing something wrong? > > It''s a bug. Please use the new config options on_poweroff, on_reboot, and > on_crash (documented in the example configuration files in > tools/examples/xmexample{1,2,3}). We are supposed to be backwards compatible > with the old restart option, but that is clearly broken.Also, xm shutdown --halt should override any restarting configuration, and definitively halt the domain. Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Mon, Oct 10, 2005 at 02:53:53PM -0400, Jonathan M. McCune wrote:> Hello, > > I''m observing a situation where domU crashes and xend continuously tries > to restart it. For example, I have to write commands like this to > actually get it to stop: > > for i in `seq 80 90`; do xm destroy $i; done > > I''ve tried adding restart = "never" and restart = ''never'' to the domain > config file (the file that gets passed to `xm create`). Is this a known > issue? Am I doing something wrong?I''ve assigned this bug #309. Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, 2005-10-11 at 00:58 +0100, Ewan Mellor wrote:> On Mon, Oct 10, 2005 at 02:53:53PM -0400, Jonathan M. McCune wrote: > > > Hello, > > > > I''m observing a situation where domU crashes and xend continuously tries > > to restart it. For example, I have to write commands like this to > > actually get it to stop: > > > > for i in `seq 80 90`; do xm destroy $i; done > > > > I''ve tried adding restart = "never" and restart = ''never'' to the domain > > config file (the file that gets passed to `xm create`). Is this a known > > issue? Am I doing something wrong?I don''t know if this is the same thing, but I noticed that my guest domain (vm1) seems to have died twice and resurrected, leaving zombies behind. x235:~ # xm list Name ID Mem(MiB) CPU VCPUs State Time(s) Domain-0 0 121 0 1 r----- 3333.5 Zombie-vm1 4 0 1 1 ----cd 0.3 Zombie-1-vm1 5 0 1 1 ----cd 0.3 vm1 6 126 1 1 -b---- 745.7 vm2 7 126 1 1 -b---- 866.3 I am also seeing this messages on ''xm dmesg'': (XEN) (file=/tmp/xen-unstable.hg/xen/include/asm/mm.h, line=203) Error pfn 0: rd=ff1ab080, od=ffbfb080, caf=80000002, taf=f0000002 (XEN) DOM2: (file=mm.c, line=350) Could not get page ref for pfn 0 (XEN) DOM2: (file=mm.c, line=2220) Could not get page for mach->phys update (XEN) (file=grant_table.c, line=1016) Bad flags (0) or dom (0). (NB. expected dom 0) (XEN) (file=grant_table.c, line=791) gnttab_transfer: Transferee has no reservation headroom (32567,32768) or provided a bad grant ref (00000000) or is dying (11) (XEN) (file=grant_table.c, line=1016) Bad flags (0) or dom (0). (NB. expected dom 0) (XEN) (file=grant_table.c, line=791) gnttab_transfer: Transferee has no reservation headroom (32567,32768) or provided a bad grant ref (00000000) or is dying (11) (XEN) (file=grant_table.c, line=1016) Bad flags (0) or dom (0). (NB. expected dom 0) (XEN) (file=grant_table.c, line=791) gnttab_transfer: Transferee has no reservation headroom (32567,32768) or provided a bad grant ref (00000000) or is dying (11)> > I''ve assigned this bug #309. > > Ewan. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ewan Mellor <ewan@xensource.com> wrote on 10/10/2005 06:58:35 PM:> On Mon, Oct 10, 2005 at 02:53:53PM -0400, Jonathan M. McCune wrote: > > > Hello, > > > > I''m observing a situation where domU crashes and xend continuouslytries> > to restart it. For example, I have to write commands like this to > > actually get it to stop: > > > > for i in `seq 80 90`; do xm destroy $i; done > > > > I''ve tried adding restart = "never" and restart = ''never'' to the domain> > config file (the file that gets passed to `xm create`). Is this aknown> > issue? Am I doing something wrong? > > I''ve assigned this bug #309. > > Ewan.I think this has been changed recently. If you look at the recent "example" domain config files in /etc/xen, you''ll see that now we have 3 things to control the behavior when a domain exits: on_poweroff = ''destroy'' (default value) on_reboot = ''restart'' (default value) on_crash = ''restart'' (default value) As a result, if a domain is crashing, it would be automatically be restarted (with a different domain ID) by default. To prevent a domain from being endlessly restarted after it crashes, you can set: on_crash = ''preserve'' The comments in the "example" domain config files given in /etc/xen provide more info on these parameters and how the original "restart" parameter is handled under the new scheme. Regards, Khoa H. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel