Hello, I have a problem with the memory of one xen server (debian sarge). After booting I can see something like this (with xm list): Domain-0 0 195 0 r---- 21.4 server1 70 79 0 -b--- 62.8 9670 server2 11 79 0 -b--- 83.5 9611 server3 13 79 0 -b--- 33.7 9613 server4 14 79 0 -b--- 83.1 9614 server5 57 79 0 -b--- 5.5 9657 .... I have configured 200 MB for the xen server itself (Domain-0) and 80 MB for every server. There are 20 servers with 80 MB + 1x200 MB, about 1800 MB, the server has 2000 MB. After some days/weeks and some xm shutdown/destroy/creates later "xm list" shows: Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 195 0 r---- 9822.9 Domain-4 4 80 0 --p-- 0.0 server1 70 79 0 -b--- 62.9 9670 server2 11 79 0 -b--- 3684.5 9611 server3 13 79 0 -b--- 7434.6 9613 There are suddenly names like "Domain-4", "Domain-5" and so on. At first I had no problem with them, all servers have been running. But as soon as there are 4 "unknown" Domain-x-servers, the memory of the server is full and I cannot restart any server anymore. I cannot remove the unknown "Domain-x"-servers with xm shutdown/destroy. I have to reboot the whole server. Is this an error in Xen? Did I made any error? Regards, Ralf Dreibrodt -- Mesos Telefon 49 221 4855798-1 Eupener Str. 150 Fax 49 221 4855798-9 50933 Koeln Mail rd@mesos.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, I just had this exact problem, had about 8, Domain-24 - Domain-32 all unkillable. Had to shut down all running domU''s, xend restart, and then there were still some left, so without any domU''s running do xm destroy <domain> til they are all gone, I was able to clear it all up w/o rebooting the dom0 and restore full functionality. If anybody has Idea''s on why this might happen I''d love to know as well. Regards, John Fairbairn> Hello, > > I have a problem with the memory of one xen server (debian sarge). > > After booting I can see something like this (with xm list): > Domain-0 0 195 0 r---- 21.4 > server1 70 79 0 -b--- 62.8 9670 > server2 11 79 0 -b--- 83.5 9611 > server3 13 79 0 -b--- 33.7 9613 > server4 14 79 0 -b--- 83.1 9614 > server5 57 79 0 -b--- 5.5 9657 > .... > > I have configured 200 MB for the xen server itself (Domain-0) and 80 MB > for every server. > > There are 20 servers with 80 MB + 1x200 MB, about 1800 MB, the server > has 2000 MB. > > After some days/weeks and some xm shutdown/destroy/creates later "xm > list" shows: > Name Id Mem(MB) CPU State Time(s) Console > Domain-0 0 195 0 r---- 9822.9 > Domain-4 4 80 0 --p-- 0.0 > server1 70 79 0 -b--- 62.9 9670 > server2 11 79 0 -b--- 3684.5 9611 > server3 13 79 0 -b--- 7434.6 9613 > > There are suddenly names like "Domain-4", "Domain-5" and so on. > > At first I had no problem with them, all servers have been running. > But as soon as there are 4 "unknown" Domain-x-servers, the memory of the > server is full and I cannot restart any server anymore. > > I cannot remove the unknown "Domain-x"-servers with xm shutdown/destroy. > I have to reboot the whole server. > > Is this an error in Xen? > Did I made any error? > > Regards, > Ralf Dreibrodt > > -- > Mesos Telefon 49 221 4855798-1 > Eupener Str. 150 Fax 49 221 4855798-9 > 50933 Koeln Mail rd@mesos.de > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- In the game of life it takes a root prompt to really foul up. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> There are 20 servers with 80 MB + 1x200 MB, about 1800 MB, > the server has 2000 MB. > > After some days/weeks and some xm shutdown/destroy/creates > later "xm list" shows: > Name Id Mem(MB) CPU State Time(s) Console > Domain-0 0 195 0 r---- 9822.9 > Domain-4 4 80 0 --p-- 0.0 > server1 70 79 0 -b--- 62.9 9670 > server2 11 79 0 -b--- 3684.5 9611 > server3 13 79 0 -b--- 7434.6 9613 > > There are suddenly names like "Domain-4", "Domain-5" and so on.Looks like you have some zombie domains that have got into a bad state. This can be due to a tools bug, or to a real hypervisor bug, though we haven''t seen any of the latter in a while. If you can find a way to reproduce this reliably it would help track it down. The other approach is to use a DEBUG=y build of Xen, and then hit ''o'' on the serial console when its in this state. Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users