k8n-ultra9:/etc/xen# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 245 1 r----- 444.1 Zombie-Apache 4 256 1 -----d 182.0 k8n-ultra9:/etc/xen# xm destroy 4 k8n-ultra9:/etc/xen# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 245 1 r----- 444.3 Zombie-Apache 4 256 1 -----d 182.0 What can I do? -- Gabor HALASZ <halasz.g@freemail.hu> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Le Jeudi 15 Décembre 2005 14:16, Gabor HALASZ a écrit :> What can I do?reset or reboot :) -- David CHANIAL - Euro Web SARL - http://www.euro-web.fr Location de serveurs dédiés infogérés Infogérance et consulting Hébergement mutualisé sur mesure Serveurs de jeux _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> k8n-ultra9:/etc/xen# xm list > Name ID Mem(MiB) VCPUs State Time(s) > Domain-0 0 245 1 r----- 444.1 > Zombie-Apache 4 256 1 -----d 182.0 > k8n-ultra9:/etc/xen# xm destroy 4 > k8n-ultra9:/etc/xen# xm list > Name ID Mem(MiB) VCPUs State Time(s) > Domain-0 0 245 1 r----- 444.3 > Zombie-Apache 4 256 1 -----d 182.0 > > What can I do?What version of Xen is this? Do you know what you did to kill the domain? In general, zombie domains aren''t too much to worry about from a user point of view. They typically don''t really consume more than a few KB of memory (despite being listed as holding their full size on ''xm list''). However, they''re an indication that something has gone wrong (usually in the tools) and Xen isn''t prepared to destory them completely as it thinks some resources are still in use. It''s good to report such issues wo we can fix them. Thanks, Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ian Pratt schrieb: - snip -> What version of Xen is this? Do you know what you did to kill the >domain? > >In general, zombie domains aren''t too much to worry about from a user >point of view. They typically don''t really consume more than a few KB of >memory (despite being listed as holding their full size on ''xm list''). > >However, they''re an indication that something has gone wrong (usually in >the tools) and Xen isn''t prepared to destory them completely as it >thinks some resources are still in use. It''s good to report such issues >wo we can fix them. > >I would like to look somewhat deeper into that, too. I have several similar machines (IBM x330) with identical setup (xen 2.0.7), just different number of domUs. They all run fine, but one of them every few days does not. One of the domUs is not reachable any more then (though shown by xm list), cannot be destroyed (still shown by xm list with 0 used memory), and if I try to reboot the physical machine the shutdown process hangs after shutdown of the network (that usually means driving to the colocation center, urgh). The only way I can make reboot work then is a) destroy the domU that is not working b) run "/etc/init.d/xend restart" which claims not to work c) then reboot the machine. There is one difference to the other machines: they all run HIGHMEM4G=y kernels, but the one having problems has only 1 GB of physical memory. Can that be the source of the problems? Thanks, Dirk _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users