search for: mbargs

...Automate running it if xen (the package) and the xen kernel are installed. But only if the user WANTS to run it. 2. Allow users to automatically modify the variables passed into the xen.gz line (that is, more or less memory, add console settings, etc.) If you look at the current script, "--mbargs=dom0_mem=1024M,max:1024M loglvl=all guest_loglvl=all" is hard coded in as the only option for the xen.gz line. While doing that we also still want to preserve the ability to run that kernel in other places than just for xen dom0 setups. Here is how I propose we do that. Currently the /usr/b...

...file /etc/sysconfig/xen-kernel ... if there is any other items you want on the 'kernel /xen.gz' line, you would edit the file. For example, I like to add 'com1=115200,8n1 console=com1' to the end of that line so I can use consoles in virsh. So I would change the line: XEN_KERNEL_MBARGS="--mbargs=dom0_mem=1024M,max:1024M loglvl=all guest_loglvl=all" to XEN_KERNEL_MBARGS="--mbargs=dom0_mem=1024M,max:1024M loglvl=all guest_loglvl=all com1=115200,8n1 console=com1" (both of those should be one line if they wrap) This is also where you can assign more or less me...

Hey M A, I was quite excited to see that with Fedora Core 16 I can just do: ''yum install xen'' and the hypervisor is installed. Sadly the grub is not updated so nothing gets loaded. Should I report bugs against this on bugzilla.redhat.com or just send them to your personally? libvirt seems to have forgotten about Xen too.. but that is a different issue. I played with running