On 10/25/07, Liberio Cunha Neto <[EMAIL PROTECTED]> wrote: > some comments inline > > > On 10/25/07, Chuck Short <[EMAIL PROTECTED]> wrote: > > Hello, > > > > In order to get Xen working really well for servers in the hardy > > release. I wish to solicit opinions, in an effort to improve the spec > > that I'm in the middle of writing: > > > > 1. Kernel side > > > > Since 2.6.23 will have xen paravirt-ops (domU) we should use that > > right? However, it does not have the full features that users will > > want. No HVM console and no Windows XP guests. Its just basic basic > > domU support. So thats not really an option in my opinion. In gutsy, > > we decided to switch to opensuse dom0 kernel, however this caused more > > problems than what it was worth. So Im using fedora as a base this > > time. I have already started to port their kernel from 2.6.22->2.6.2x. > > paravirt-ops is only supported for domUs (so doesn't work for the host > kernel) and only X86 (no X86_64 available yet), what you are > suggesting here ?
Im suggesting not to use paravirt-ops > > > > > 2. Xen hypervisor side > > > > Recently, Xen-3.1.1 was released that contains various fixes for the > > Xen-3.1. However the next version of (Xen-3.2) will be release in > > November. This will (hopefully) include things like cpufreq support. > > (This will also have to be ported from 2.6.18 to 2.6.24). In my > > opinnon, we should be using Xen-3.2 for hardy. I would also like the > > resync debian's patches with our own. So the tools will be in a better > > shape. > > cpufreq is way out of shape , if you check the unstable tree and > complains about it you will know, right now people using unstable is > having all kinds of clock issues because this. > > > > > 3. Windows support > > > > Users would like to use Xen to use windows with it (god only knows why ;) > > why they can't run windows right now ?, the main problem right now is > windows drivers opensource or free available , they don't exists , but > if you don't mind that load dom0 with networking and HD controllers > (via qemu) I don't see any problems , other than need to create all by > hand , no nice tool > > > > > 4. Xen-tools > > > > I would like to expand our simple base of tools that we use now > > (xen-tools, xenman). I would like to use things like virt-man > > (especially for the desktop, however its redhat only no debian images) > > however I might not have time for that. > > virt-manager have good things and bad ones , one that I really don't > like is the way virt-manager store the domU configuration , instead of > the default /etc/xen/domain.conf they use internaly stuff to manage > this so example , if you have a windows or any HVM host and wants to > enable qemu monitor (so you can change de CD image with the HVM > running) instead of just adding monitor = 1 , to your config you will > need to hack virt-manager to do it (this is only one example I have a > lot more if you want) > > > > > > > > Comments and help during the hardy release cycle is greatly appreciated. > > > > Thanks > > chuck > > > > -- > > ubuntu-server mailing list > > [email protected] > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > > More info: https://wiki.ubuntu.com/ServerTeam > > > -- ubuntu-server mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
