search for: xenhopt

Hi, you have to limit dom0 memory on two places, xen hypervisor option and xend config. In this example below I limit memory to 256MB: /boot/grub/menu.lst 87c87 < # xenhopt= --- > # xenhopt=dom0_mem=256M /etc/xen/xend-config.sxp 120c120 < (dom0-min-mem 196) --- > (dom0-min-mem 256) After changing /boot/grub/menu.lst you have to run update-grub and reboot the machine. After changing /etc/xen/xend-config.sxp you have to restart xend with /etc/init.d/xend re...

...g/ make world make install apt-get install yaird mkinitrd.yaird -o /boot/initrd.img-2.6.18-xen 2.6.18-xen update-rc.d xend defaults 20 21 update-rc.d xendomains defaults 21 20 nano -w /boot/grub/menu.lst # edited the following: ## Xen hypervisor options to use with the default Xen boot option # xenhopt=dom0_mem=512M com1=9600,8n1 vcpus=1 ## Xen Linux kernel options to use with the default Xen boot option # xenkopt=console=tty0 maxcpus=1 console=ttyS0,9600n8 update-grub ----- after a reboot everything looks just fine, except: ifconfig shows only a xenbr0, no peth or veth.. The network works, c...

...ily running the > Lenny version of Xen and GRUB seems to be working fine. > > What is the best way of tracking down Xen fail to boot bugs? A serial console log would be very useful if you have the hardware capability. Otherwise adding "noreboot" to the hypervisor command line (xenhopt in /boot/grub/menu.lst or by hand) will allow you to catch the error displayed on system A which may help in that case. It's possible there will be something on system B which is too quick to see as well or at least see how far you get before the crash. 2.6.32-11 was uploaded yesterday which a...

...nitrd.img-2.6.18-xen 2.6.18-xen >> update-rc.d xend defaults 20 21 >> update-rc.d xendomains defaults 21 20 >> >> nano -w /boot/grub/menu.lst >> # edited the following: >> >> ## Xen hypervisor options to use with the default Xen boot option >> # xenhopt=dom0_mem=512M com1=9600,8n1 vcpus=1 >> ## Xen Linux kernel options to use with the default Xen boot option >> # xenkopt=console=tty0 maxcpus=1 console=ttyS0,9600n8 >> >> update-grub >> ----- >> >> after a reboot everything looks just fine, except: >...

flight 22184 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/22184/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail REGR. vs. 22106 test-amd64-i386-xl-win7-amd64 9 guest-localmigrate fail REGR. vs. 22106 Regressions which are regarded as

...t;> >> which seems to be backed up by, >> >> >> http://slackware.osuosl.org/slackware-3.3/docs/linux-2.0.30/svga.txt >> >> i edit "/boot/grub/menu.lst" to >> >> ### BEGIN AUTOMAGIC KERNELS LIST >> ... >> # xenhopt=dom0_mem=512M noirqdebug vga=775 >> # xenkopt=max_loop=64 console=tty0 console=ttyS0,115200n8 >> ... >> >> then, a subsequent >> >> update-grub >> >> re-generates "/boot/grub/menu.lst" to contain, >> >>...