Hi My xensource configuration: - server dell poweredge 710 with 4c intel xeon processors and 8GB memory - dom0 - debian lenny x86 with xen 3.2.1 - domU - 3 x debian lenny About 2 years ago i''ve created 3 instances of debian (~60GB img, 512 ram, 1 core per each virtual server ). 2 of them are normal working server, 3th is testing, many times was starting and shutdown. One week ago i''ve created 4th instance via xen-create-image (just like 3 previous) but with 200GB img. Create was successful, but when i try `xm create /etc/xen/virt4.cfg'' and that machine just started, dom0 was completly frozen and on tty console was some strange messages which unfortunately i dont remember. After restart dom0 only 2 producting server started (they started by scripts /etc/init.d/virt1.sh and virt2.sh with contains `xm create /etc/xen/virtX.cfg'') but when i was trying to start testing machine virt3 (xm create -c /etc/xen/virt3.cfg) dom0 suspensed again. There is no suspicious info in /var/log/messages or syslog or dmesg in dom0 or virt3 (which image i mounted in temporary folder). The two machines virt1 and virt2 are very important, so i can''t start virt3 or virt4 to see what messages was printed to console (and generate suspension dom0 again). For me it was something like memory dump. Thanks for eny help and sorry for my english. Regards _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, On 04/01/2011 02:53 PM, tower wrote:> One week ago i''ve created 4th instance via xen-create-image (just like > 3 previous) but with 200GB img. Create was successful, but when i try > `xm create /etc/xen/virt4.cfg'' and that machine just started, dom0 was > completly frozen and on tty console was some strange messages which > unfortunately i dont remember.First thing to try is to give dom0 a fixed amount of memory. Edit /boot/grub/menu.lst. It should have a line that says # xenhopt Change that line to # xenhopt=dom0_mem=768M Keep the # at the beginning of the line. The value of 768M works for me, maybe you can get away with less. This depends on how many domUs you have and whether you have HVM domUs or not. The next step will apply this value to the various grub entries for xen. Run: update-grub Check menu.lst. The xen boot entry should look like: title Xen 3.2-1-amd64 / Debian GNU/Linux, kernel 2.6.26-2-xen-amd64 root (hd0,0) kernel /xen-3.2-1-amd64.gz dom0_mem=768M module /vmlinuz-2.6.26-2-xen-amd64 root=/dev/md1 ro console=tty0 module /initrd.img-2.6.26-2-xen-amd64 Now edit /etc/xen/xend-config.sxp. Find a (probably commented out) line that says (dom0-min-mem x) where x is some value. Uncomment this line and make x=0, so it reads: (dom0-min-mem 0) Now reboot your dom0. Does this fix your problem? Regards, Thomas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users