Hi, Is it possible to use HVM (full virtualization) for Linux guests but use PV drivers instead inside the DomU for extra performance? What shall I do to be able to do it? Where can I download these drivers for several standard kernels? (HVM domU = standard distribution kernel, not-xen-aware) Or, does the recent introduction of VMI into the linux kernel make this automatic for us? i.e. if I use any recent kernel, such as Ubuntu''s 2.6.22-14-generic, will paravirtualized disk/network drivers be automatically activated? Thanks for any insight, Best regards, Emre Erenoglu erenoglu@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Nov 22, 2007 at 01:47:06PM +0100, Emre Erenoglu wrote:> Hi, > > Is it possible to use HVM (full virtualization) for Linux guests but use PV > drivers instead inside the DomU for extra performance? >Yes.> What shall I do to be able to do it? Where can I download these drivers for > several standard kernels? (HVM domU = standard distribution kernel, > not-xen-aware) >You can download xen source tree and compile "unmodified drivers" from there, or you can use the ones distributed with your distribution, if available.> Or, does the recent introduction of VMI into the linux kernel make this > automatic for us? i.e. if I use any recent kernel, such as Ubuntu''s > 2.6.22-14-generic, will paravirtualized disk/network drivers be > automatically activated? >VMI is VMware''s interface to run paravirtual Linux on VMware. It doesn''t work or help at all with Xen. If you''re running paravirtual linux on xen, you already have paravirtualized ("full speed") drivers in use. If you''re using HVM domU on Xen, then you need to install Xen PV drivers on domU. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Pasi, comments below: On Nov 22, 2007 3:35 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Thu, Nov 22, 2007 at 01:47:06PM +0100, Emre Erenoglu wrote: > > Hi, > > > > Is it possible to use HVM (full virtualization) for Linux guests but use > PV > > drivers instead inside the DomU for extra performance? > > > > Yes.OK> > > > What shall I do to be able to do it? Where can I download these drivers > for > > several standard kernels? (HVM domU = standard distribution kernel, > > not-xen-aware) > > >> You can download xen source tree and compile "unmodified drivers" from > there, or you can use the ones distributed with your distribution, if > available.OK, I will do that. I don''t think my distribution has these drivers as a package.> > > > Or, does the recent introduction of VMI into the linux kernel make this > > automatic for us? i.e. if I use any recent kernel, such as Ubuntu''s > > 2.6.22-14-generic, will paravirtualized disk/network drivers be > > automatically activated? > > > > VMI is VMware''s interface to run paravirtual Linux on VMware. It doesn''t > work or help at all with Xen.Well maybe I stated wrong, i was mentioning VMI (or whatever function it is) as a common way to enable standard kernels to work as Paravirtual when they detect the presence of a hypervisor. I think this is now standard for all, including VMWare and XEN. FYI, it is possible to boot a 2.6.23 vanilla kernel as paravirtual DomU, but my question was if the paravirtual drivers were already there if I use HVM instead of Paravirtualization. I hope I mentioned it right...> > If you''re running paravirtual linux on xen, you already have > paravirtualized > ("full speed") drivers in use.Yes, however, my DomU crashes on boot with the PV kernel. I couldn''t find why.> > > If you''re using HVM domU on Xen, then you need to install Xen PV drivers > on > domU. > > -- Pasi >Thanks, just one last question, when I compile and modprobe these PV modules, how can I understand that they are actually working? Do they print some message in dmesg? Regards, Emre _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Nov 22, 2007 at 03:57:23PM +0100, Emre Erenoglu wrote:> > > > > Or, does the recent introduction of VMI into the linux kernel make this > > > automatic for us? i.e. if I use any recent kernel, such as Ubuntu''s > > > 2.6.22-14-generic, will paravirtualized disk/network drivers be > > > automatically activated? > > > > > > > VMI is VMware''s interface to run paravirtual Linux on VMware. It doesn''t > > work or help at all with Xen. > > > Well maybe I stated wrong, i was mentioning VMI (or whatever function it is) > as a common way to enable standard kernels to work as Paravirtual when they > detect the presence of a hypervisor. I think this is now standard for all, > including VMWare and XEN.This standard paravirtualization layer/support is called "paravirt ops" in kernel. "paravirt ops" is then implemented for Xen, VMI, KVM, Lguest etc..> FYI, it is possible to boot a 2.6.23 vanilla kernel as paravirtual DomU, but > my question was if the paravirtual drivers were already there if I use HVM > instead of Paravirtualization. I hope I mentioned it right... >No, HVM PV drivers are not included with the vanilla kernel, you need to obtain and load them separately.> > > > > If you''re running paravirtual linux on xen, you already have > > paravirtualized > > ("full speed") drivers in use. > > > Yes, however, my DomU crashes on boot with the PV kernel. I couldn''t find > why. >What dom0 distribution are you using? Are xen/kernel packages provided by the distribution or self compiled? What is your domU distribution? Is the domU PV kernel from the distribution, or self compiled? PV domU is the most common type of virtual machine on Xen, and it definitely works fine as long as you''re running matching/compatible versions of Xen and kernels.> > > > > > If you''re using HVM domU on Xen, then you need to install Xen PV drivers > > on > > domU. > > > > -- Pasi > > > > Thanks, just one last question, when I compile and modprobe these PV > modules, how can I understand that they are actually working? Do they > print some message in dmesg? >Yes. Usually you need to edit/recreate your initrd to load these modules during the domU bootup. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Pasi, thanks again for your response. Answers below: On Nov 22, 2007 5:36 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Thu, Nov 22, 2007 at 03:57:23PM +0100, Emre Erenoglu wrote: > > > > > > > Or, does the recent introduction of VMI into the linux kernel make > this > > > > automatic for us? i.e. if I use any recent kernel, such as Ubuntu''s > > > > 2.6.22-14-generic, will paravirtualized disk/network drivers be > > > > automatically activated? > > > > > > > > > > VMI is VMware''s interface to run paravirtual Linux on VMware. It > doesn''t > > > work or help at all with Xen. > > > > > > Well maybe I stated wrong, i was mentioning VMI (or whatever function it > is) > > as a common way to enable standard kernels to work as Paravirtual when > they > > detect the presence of a hypervisor. I think this is now standard for > all, > > including VMWare and XEN. > > This standard paravirtualization layer/support is called "paravirt ops" in > kernel. > > "paravirt ops" is then implemented for Xen, VMI, KVM, Lguest etc.. > > > FYI, it is possible to boot a 2.6.23 vanilla kernel as paravirtual DomU, > but > > my question was if the paravirtual drivers were already there if I use > HVM > > instead of Paravirtualization. I hope I mentioned it right... > > > > No, HVM PV drivers are not included with the vanilla kernel, you need to > obtain and load them separately. >OK> > > > > > > > > If you''re running paravirtual linux on xen, you already have > > > paravirtualized > > > ("full speed") drivers in use. > > > > > > Yes, however, my DomU crashes on boot with the PV kernel. I couldn''t > find > > why. > > > > What dom0 distribution are you using? > > Are xen/kernel packages provided by the distribution or self compiled? >I''m using Ubuntu 7.10 with 2.6.22-14-xen as Dom0. Packages are provided by the distribution.> > What is your domU distribution? Is the domU PV kernel from the > distribution, or self compiled?DomU is Pardus 2007.2. It has default kernel 2.6.18-8, but as I wanted paravirtualization, I was using Ubuntu''s 2.6.22-14-xen. The crash started with this release kernel. when Ubuntu was beta, I was able to use 2.6.22-12-xen without problems. Pardus 2007.2 is able to work with Ubuntu 2.6.22-14-generic kernel (on bare metal) without problems. It used to be working as DomU with 2.6.22-12-xenbut not anymore with 2.6.22-14-xen. I filed a bug report 1 month ago, no answer yet. I switched to VMWare for the moment until I resolve this issue, VMWare disk performance is not good even if I enabled PV support (VMI). Therefore, my aim now is to use standard Pardus kernel 2.6.18-8, but compile PV drivers for use with Dom0 (Ubuntu 7.10 2.6.22-14-xen, Xen 3.1)> > PV domU is the most common type of virtual machine on Xen, and it > definitely > works fine as long as you''re running matching/compatible versions of Xen > and > kernels. > > > > > > > > > > If you''re using HVM domU on Xen, then you need to install Xen PV > drivers > > > on > > > domU. > > > > > > -- Pasi > > > > > > > Thanks, just one last question, when I compile and modprobe these PV > > modules, how can I understand that they are actually working? Do they > > print some message in dmesg? > > > > Yes. > > Usually you need to edit/recreate your initrd to load these modules during > the domU bootup. > > -- Pasi >OK, I''ll do that. thanks a lot again. -- Emre Erenoglu erenoglu@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Nov 22, 2007 at 06:48:26PM +0100, Emre Erenoglu wrote:> > > > > > Yes, however, my DomU crashes on boot with the PV kernel. I couldn''t > > find > > > why. > > > > > > > What dom0 distribution are you using? > > > > Are xen/kernel packages provided by the distribution or self compiled? > > > > I''m using Ubuntu 7.10 with 2.6.22-14-xen as Dom0. Packages are provided by > the distribution. >OK. Afaik Xen in Ubuntu (and in Debian) is not very well tested..> > > > What is your domU distribution? Is the domU PV kernel from the > > distribution, or self compiled? > > > DomU is Pardus 2007.2. It has default kernel 2.6.18-8, but as I wanted > paravirtualization, I was using Ubuntu''s 2.6.22-14-xen. The crash started > with this release kernel. when Ubuntu was beta, I was able to use > 2.6.22-12-xen without problems. > Pardus 2007.2 is able to work with Ubuntu 2.6.22-14-generic kernel (on bare > metal) without problems. It used to be working as DomU with > 2.6.22-12-xenbut not anymore with > 2.6.22-14-xen. I filed a bug report 1 month ago, no answer yet. > > I switched to VMWare for the moment until I resolve this issue, VMWare disk > performance is not good even if I enabled PV support (VMI). > > Therefore, my aim now is to use standard Pardus kernel 2.6.18-8, but compile > PV drivers for use with Dom0 (Ubuntu 7.10 2.6.22-14-xen, Xen 3.1) >I have never heard of Pardus before :) So I can''t comment about it or it''s support for Xen.. I would recommend you to use RHEL, CentOS, SLES, Opensuse or Fedora.. those distributions are known to ship Xen and work to make it stable/usable.. Get for example Fedora 8, use it on both dom0 and on domU, and you should get things working well.. RHEL 5.1 or CentOS 5.1 should be good choises too.. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Pasi, my comments below: On Nov 22, 2007 7:24 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Thu, Nov 22, 2007 at 06:48:26PM +0100, Emre Erenoglu wrote: > > > > > > > > Yes, however, my DomU crashes on boot with the PV kernel. I > couldn''t > > > find > > > > why. > > > > > > > > > > What dom0 distribution are you using? > > > > > > Are xen/kernel packages provided by the distribution or self compiled? > > > > > > > I''m using Ubuntu 7.10 with 2.6.22-14-xen as Dom0. Packages are provided > by > > the distribution. > > > > OK. > > Afaik Xen in Ubuntu (and in Debian) is not very well tested.. >Possibly.> > > > > > > What is your domU distribution? Is the domU PV kernel from the > > > distribution, or self compiled? > > > > > > DomU is Pardus 2007.2. It has default kernel 2.6.18-8, but as I wanted > > paravirtualization, I was using Ubuntu''s 2.6.22-14-xen. The crash > started > > with this release kernel. when Ubuntu was beta, I was able to use > > 2.6.22-12-xen without problems. > > Pardus 2007.2 is able to work with Ubuntu 2.6.22-14-generic kernel (on > bare > > metal) without problems. It used to be working as DomU with > > 2.6.22-12-xenbut not anymore with > > 2.6.22-14-xen. I filed a bug report 1 month ago, no answer yet. > > > > I switched to VMWare for the moment until I resolve this issue, VMWare > disk > > performance is not good even if I enabled PV support (VMI). > > > > Therefore, my aim now is to use standard Pardus kernel 2.6.18-8, but > compile > > PV drivers for use with Dom0 (Ubuntu 7.10 2.6.22-14-xen, Xen 3.1) > > > > I have never heard of Pardus before :) So I can''t comment about it or it''s > support for Xen.. >It''s OK with Xen (http://www.pardus.org.tr/eng/index.html) . Normally it has XEN 3.1 with its 2.6.18 kernel but I would like to use a newer kernel.> > I would recommend you to use RHEL, CentOS, SLES, Opensuse or Fedora.. > those > distributions are known to ship Xen and work to make it stable/usable..> Get for example Fedora 8, use it on both dom0 and on domU, and you should > get > things working well..I also have Fedora 8 as Dom0, but I think Ubuntu 7.10 runs less problematic Xen than Fedora. I have numerous problems with Fedora 8, especially with it''s Virt-Manager and networking (doesn''t support bridging out of the box, have to do some tricks, virt-manager can''t make a PV domain, doesn''t have xenbr0 but virbr0 etc. etc.). I just couldn''t get used to it. Nevertheless, my Pardus can''t boot with its 2.6.21 xen kernel as I guess Fedora guys likes to make some non-standard way to making INIT. (Ubuntu kernels just boot fine on bare-metal). I don''t understand why I can''t just replace the kernel and still boot fine (good old linux days?).> > RHEL 5.1 or CentOS 5.1 should be good choises too.. > > -- Pasi > >Thanks a lot for your patience, Br, Emre Erenoglu erenoglu@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Nov 23, 2007 at 11:39:35AM +0100, Emre Erenoglu wrote:> > > DomU is Pardus 2007.2. It has default kernel 2.6.18-8, but as I wanted > > > paravirtualization, I was using Ubuntu''s 2.6.22-14-xen. The crash > > started > > > with this release kernel. when Ubuntu was beta, I was able to use > > > 2.6.22-12-xen without problems. > > > Pardus 2007.2 is able to work with Ubuntu 2.6.22-14-generic kernel (on > > bare > > > metal) without problems. It used to be working as DomU with > > > 2.6.22-12-xenbut not anymore with > > > 2.6.22-14-xen. I filed a bug report 1 month ago, no answer yet. > > > > > > I switched to VMWare for the moment until I resolve this issue, VMWare > > disk > > > performance is not good even if I enabled PV support (VMI). > > > > > > Therefore, my aim now is to use standard Pardus kernel 2.6.18-8, but > > compile > > > PV drivers for use with Dom0 (Ubuntu 7.10 2.6.22-14-xen, Xen 3.1) > > > > > > > I have never heard of Pardus before :) So I can''t comment about it or it''s > > support for Xen.. > > > > It''s OK with Xen (http://www.pardus.org.tr/eng/index.html) . Normally it has > XEN 3.1 with its 2.6.18 kernel but I would like to use a newer kernel. >OK. Just remember that newer Xen versions support older kernels.. backwards compatibility. But not the other way around.. If your kernel is compiled for Xen 3.0.3, it will work under Xen 3.1.0. But if your kernel is compiled for Xen 3.1.0, it wont work with Xen 3.0.3.> > > > > I would recommend you to use RHEL, CentOS, SLES, Opensuse or Fedora.. > > those > > distributions are known to ship Xen and work to make it stable/usable.. > > > > Get for example Fedora 8, use it on both dom0 and on domU, and you should > > get > > things working well.. > > > I also have Fedora 8 as Dom0, but I think Ubuntu 7.10 runs less problematic > Xen than Fedora. I have numerous problems with Fedora 8, especially with > it''s Virt-Manager and networking (doesn''t support bridging out of the box, > have to do some tricks, virt-manager can''t make a PV domain, doesn''t have > xenbr0 but virbr0 etc. etc.). I just couldn''t get used to it. >You know you don''t have to use virt-manager.. :) Just use the cmdline tools and create your own configuration file for domU.. that way you know for sure what you get and how.> Nevertheless, my Pardus can''t boot with its 2.6.21 xen kernel as I guess > Fedora guys likes to make some non-standard way to making INIT. (Ubuntu > kernels just boot fine on bare-metal). > > I don''t understand why I can''t just replace the kernel and still boot fine > (good old linux days?). >You should ask from Pardus guys/lists.. I don''t what they support/require. What happens when you boot your domU with Pardus kernel? Is it PV domU? Are you using pygrub? -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Nov 23, 2007 3:43 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Fri, Nov 23, 2007 at 11:39:35AM +0100, Emre Erenoglu wrote: > > > > DomU is Pardus 2007.2. It has default kernel 2.6.18-8, but as I > wanted > > > > paravirtualization, I was using Ubuntu''s 2.6.22-14-xen. The crash > > > started > > > > with this release kernel. when Ubuntu was beta, I was able to use > > > > 2.6.22-12-xen without problems. > > > > Pardus 2007.2 is able to work with Ubuntu 2.6.22-14-generic kernel > (on > > > bare > > > > metal) without problems. It used to be working as DomU with > > > > 2.6.22-12-xenbut not anymore with > > > > 2.6.22-14-xen. I filed a bug report 1 month ago, no answer yet. > > > > > > > > I switched to VMWare for the moment until I resolve this issue, > VMWare > > > disk > > > > performance is not good even if I enabled PV support (VMI). > > > > > > > > Therefore, my aim now is to use standard Pardus kernel 2.6.18-8, but > > > compile > > > > PV drivers for use with Dom0 (Ubuntu 7.10 2.6.22-14-xen, Xen 3.1) > > > > > > > > > > I have never heard of Pardus before :) So I can''t comment about it or > it''s > > > support for Xen.. > > > > > > > It''s OK with Xen (http://www.pardus.org.tr/eng/index.html) . Normally it > has > > XEN 3.1 with its 2.6.18 kernel but I would like to use a newer kernel. > > > > OK. > > Just remember that newer Xen versions support older kernels.. backwards > compatibility. But not the other way around.. > > If your kernel is compiled for Xen 3.0.3, it will work under Xen 3.1.0. > But if your kernel is compiled for Xen 3.1.0, it wont work with Xen 3.0.3. >In fact, I didn''t try this. So I will install distribution''s own DomU kernel and see if it will work with Ubuntu''s 2.6.22-14-xen Dom0 kernel and Xen version.> > > > > > > > I would recommend you to use RHEL, CentOS, SLES, Opensuse or Fedora.. > > > those > > > distributions are known to ship Xen and work to make it > stable/usable.. > > > > > > > Get for example Fedora 8, use it on both dom0 and on domU, and you > should > > > get > > > things working well.. > > > > > > I also have Fedora 8 as Dom0, but I think Ubuntu 7.10 runs less > problematic > > Xen than Fedora. I have numerous problems with Fedora 8, especially with > > it''s Virt-Manager and networking (doesn''t support bridging out of the > box, > > have to do some tricks, virt-manager can''t make a PV domain, doesn''t > have > > xenbr0 but virbr0 etc. etc.). I just couldn''t get used to it. > > > > You know you don''t have to use virt-manager.. :) > > Just use the cmdline tools and create your own configuration file for > domU.. > that way you know for sure what you get and how. >Yes, I didn''t use virt-manager at the end :) but even with my config files, domain crashed. Don''t know what has changed inside the domain to make these crashes.> > Nevertheless, my Pardus can''t boot with its 2.6.21 xen kernel as I guess > > Fedora guys likes to make some non-standard way to making INIT. (Ubuntu > > kernels just boot fine on bare-metal). > > > > I don''t understand why I can''t just replace the kernel and still boot > fine > > (good old linux days?). > > > > You should ask from Pardus guys/lists.. I don''t what they support/require. > > What happens when you boot your domU with Pardus kernel? Is it PV domU? > Are > you using pygrub?I never tried booting into Pardus with its own DomU kernel. I always tried, - Ubuntu 7.10 dom0 kernel as domU, 2.6.22-14-xen, or - Fedora 8, dom0 kernel as domU, 2.6.21, or - Fedora 8, standard 2.6.23 kernel (with paravirt-ops) all crashed. I''m attaching the crash report, maybe there is someone that has an idea why it happens> > > -- Pasi >Thanks a lot again and again, Br, Emre _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
report attached... On Nov 23, 2007 3:57 PM, Emre Erenoglu <erenoglu@gmail.com> wrote:> > > On Nov 23, 2007 3:43 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > > On Fri, Nov 23, 2007 at 11:39:35AM +0100, Emre Erenoglu wrote: > > > > > DomU is Pardus 2007.2. It has default kernel 2.6.18-8, but as I > > wanted > > > > > paravirtualization, I was using Ubuntu''s 2.6.22-14-xen. The crash > > > > started > > > > > with this release kernel. when Ubuntu was beta, I was able to use > > > > > 2.6.22-12-xen without problems. > > > > > Pardus 2007.2 is able to work with Ubuntu 2.6.22-14-generic kernel > > (on > > > > bare > > > > > metal) without problems. It used to be working as DomU with > > > > > 2.6.22-12-xenbut not anymore with > > > > > 2.6.22-14-xen. I filed a bug report 1 month ago, no answer yet. > > > > > > > > > > I switched to VMWare for the moment until I resolve this issue, > > VMWare > > > > disk > > > > > performance is not good even if I enabled PV support (VMI). > > > > > > > > > > Therefore, my aim now is to use standard Pardus kernel 2.6.18-8, > > but > > > > compile > > > > > PV drivers for use with Dom0 (Ubuntu 7.10 2.6.22-14-xen, Xen 3.1) > > > > > > > > > > > > > I have never heard of Pardus before :) So I can''t comment about it > > or it''s > > > > support for Xen.. > > > > > > > > > > It''s OK with Xen ( http://www.pardus.org.tr/eng/index.html) . Normally > > it has > > > XEN 3.1 with its 2.6.18 kernel but I would like to use a newer kernel. > > > > > > > OK. > > > > Just remember that newer Xen versions support older kernels.. backwards > > compatibility. But not the other way around.. > > > > If your kernel is compiled for Xen 3.0.3, it will work under Xen 3.1.0. > > But if your kernel is compiled for Xen 3.1.0, it wont work with Xen > > 3.0.3. > > > > In fact, I didn''t try this. So I will install distribution''s own DomU > kernel and see if it will work with Ubuntu''s 2.6.22-14-xen Dom0 kernel and > Xen version. > > > > > > > > > > > > > I would recommend you to use RHEL, CentOS, SLES, Opensuse or > > Fedora.. > > > > those > > > > distributions are known to ship Xen and work to make it > > stable/usable.. > > > > > > > > > > Get for example Fedora 8, use it on both dom0 and on domU, and you > > should > > > > get > > > > things working well.. > > > > > > > > > I also have Fedora 8 as Dom0, but I think Ubuntu 7.10 runs less > > problematic > > > Xen than Fedora. I have numerous problems with Fedora 8, especially > > with > > > it''s Virt-Manager and networking (doesn''t support bridging out of the > > box, > > > have to do some tricks, virt-manager can''t make a PV domain, doesn''t > > have > > > xenbr0 but virbr0 etc. etc.). I just couldn''t get used to it. > > > > > > > You know you don''t have to use virt-manager.. :) > > > > Just use the cmdline tools and create your own configuration file for > > domU.. > > that way you know for sure what you get and how. > > > > Yes, I didn''t use virt-manager at the end :) but even with my config > files, domain crashed. Don''t know what has changed inside the domain to make > these crashes. > > > > > Nevertheless, my Pardus can''t boot with its 2.6.21 xen kernel as I > > guess > > > Fedora guys likes to make some non-standard way to making INIT. > > (Ubuntu > > > kernels just boot fine on bare-metal). > > > > > > I don''t understand why I can''t just replace the kernel and still boot > > fine > > > (good old linux days?). > > > > > > > You should ask from Pardus guys/lists.. I don''t what they > > support/require. > > > > What happens when you boot your domU with Pardus kernel? Is it PV domU? > > Are > > you using pygrub? > > > I never tried booting into Pardus with its own DomU kernel. I always > tried, > > - Ubuntu 7.10 dom0 kernel as domU, 2.6.22-14-xen, or > - Fedora 8, dom0 kernel as domU, 2.6.21, or > - Fedora 8, standard 2.6.23 kernel (with paravirt-ops) > > all crashed. I''m attaching the crash report, maybe there is someone that > has an idea why it happens > > > > > > > > -- Pasi > > > > Thanks a lot again and again, > > Br, Emre-- Emre Erenoglu erenoglu@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Nov 23, 2007 at 03:57:55PM +0100, Emre Erenoglu wrote:> > > > Nevertheless, my Pardus can''t boot with its 2.6.21 xen kernel as I guess > > > Fedora guys likes to make some non-standard way to making INIT. (Ubuntu > > > kernels just boot fine on bare-metal). > > > > > > I don''t understand why I can''t just replace the kernel and still boot > > fine > > > (good old linux days?). > > > > > > > You should ask from Pardus guys/lists.. I don''t what they support/require. > > > > What happens when you boot your domU with Pardus kernel? Is it PV domU? > > Are > > you using pygrub? > > > I never tried booting into Pardus with its own DomU kernel. I always tried, > > - Ubuntu 7.10 dom0 kernel as domU, 2.6.22-14-xen, or > - Fedora 8, dom0 kernel as domU, 2.6.21, or > - Fedora 8, standard 2.6.23 kernel (with paravirt-ops) > > all crashed. I''m attaching the crash report, maybe there is someone that has > an idea why it happens >Hmm.. Pardus has domU kernel available? You should definitely use that.. Always use the kernel provided by the domU distribution.. and use pygrub to load the domU kernel from domU''s filesystem (/boot). -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Again,
I''m now running my domU as a HVM domU. I also downloaded the source of
"unmodified drivers" from the xensource 3.1 repository.
However, I can''t compile it, do you have an idea why? I''m
attaching the
output below (note that kernel itself compiles just fine). Some of t
voyager linux-2.6 # pwd
/d/xen/xen-3.1-testing.hg/unmodified_drivers/linux-2.6
voyager linux-2.6 # cat README
To build:
1. ./mkbuildtree
NB. You can override paths to Xen sources and XenLinux sources via
the XEN and XL environment variable.
2. make -C /path/to/kernel/source M=$PWD modules
NB. The kernel sources here are your native kernel build tree, not
the XenLinux sources referred to in step 1.
You get four modules, xen-platform-pci.ko, xenbus.ko, xen-vbd.ko, and
xen-vnif.ko. Load xen-platform-pci first, then xenbus, and then
whichever of xen-vbd and xen-vnif you happen to need.
voyager linux-2.6 # make -C /usr/src/linux-2.6.18.8-86/ M=$PWD modules
make: `/usr/src/linux-2.6.18.8-86'' entering directory
make[2]: *** Hedef
`/d/xen/xen-3.1-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.o''
no rule to compile balloon.o, `/d/xen/xen-3.1-testing.hg
/unmodified_drivers/linux-2.6/balloon/xen-balloon.o'' is needed. stop.
make[1]: *** [/d/xen/xen-3.1-testing.hg/unmodified_drivers/linux-2.6/balloon]
Error 2
make: *** [_module_/d/xen/xen-3.1-testing.hg/unmodified_drivers/linux-2.6]
Error 2
make: `/usr/src/linux-2.6.18.8-86'' leaving directory
voyager linux-2.6 #
I translated some of the error messages from Turkish to English but I guess
you''ll get the point. What am I doing wrong? Should I first run the 1st
step
or not? As I''m in a HVM DomU, I don''t see a reason to run the
first step. If
so, which sources shall I use for Xen, the sources in my dom0?
Didn''t get it fully I guess...
Thanks a lot,
Emre
On Nov 22, 2007 3:35 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> On Thu, Nov 22, 2007 at 01:47:06PM +0100, Emre Erenoglu wrote:
> > Hi,
> >
> > Is it possible to use HVM (full virtualization) for Linux guests but
use
> PV
> > drivers instead inside the DomU for extra performance?
> >
>
> Yes.
>
> > What shall I do to be able to do it? Where can I download these
drivers
> for
> > several standard kernels? (HVM domU = standard distribution kernel,
> > not-xen-aware)
> >
>
> You can download xen source tree and compile "unmodified drivers"
from
> there, or you can use the ones distributed with your distribution, if
> available.
>
> > Or, does the recent introduction of VMI into the linux kernel make
this
> > automatic for us? i.e. if I use any recent kernel, such as
Ubuntu''s
> > 2.6.22-14-generic, will paravirtualized disk/network drivers be
> > automatically activated?
> >
>
> VMI is VMware''s interface to run paravirtual Linux on VMware. It
doesn''t
> work or help at all with Xen.
>
> If you''re running paravirtual linux on xen, you already have
> paravirtualized
> ("full speed") drivers in use.
>
> If you''re using HVM domU on Xen, then you need to install Xen PV
drivers
> on
> domU.
>
> -- Pasi
>
--
Emre Erenoglu
erenoglu@gmail.com
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
I think I''m starting to get it. I have to do both steps. Now I''m trying to download the sources for Xen and XenLinux from my Ubuntu repositories. However, I can''t understand the difference between "Xen Sources" and "XenLinux Sources" mentioned in the README. What are they? Xen Sources = Hypervisor source code? XenLinux sources = xen dom0 kernel? Can anybody comment? Emre On Nov 26, 2007 6:48 PM, Emre Erenoglu <erenoglu@gmail.com> wrote:> Hi Again, > > I''m now running my domU as a HVM domU. I also downloaded the source of > "unmodified drivers" from the xensource 3.1 repository. > > However, I can''t compile it, do you have an idea why? I''m attaching the > output below (note that kernel itself compiles just fine). Some of t > > voyager linux-2.6 # pwd > /d/xen/xen-3.1-testing.hg/unmodified_drivers/linux-2.6 > > voyager linux-2.6 # cat README > To build: > > 1. ./mkbuildtree > NB. You can override paths to Xen sources and XenLinux sources via > the XEN and XL environment variable. > > 2. make -C /path/to/kernel/source M=$PWD modules > NB. The kernel sources here are your native kernel build tree, not > the XenLinux sources referred to in step 1. > > You get four modules, xen-platform-pci.ko, xenbus.ko, xen-vbd.ko, and > xen-vnif.ko. Load xen-platform-pci first, then xenbus, and then > whichever of xen-vbd and xen-vnif you happen to need. > > voyager linux-2.6 # make -C /usr/src/linux-2.6.18.8-86/ M=$PWD modules > make: `/usr/src/linux-2.6.18.8-86'' entering directory > make[2]: *** Hedef `/d/xen/xen-3.1-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.o'' > no rule to compile balloon.o, `/d/xen/xen-3.1-testing.hg > /unmodified_drivers/linux-2.6/balloon/xen-balloon.o'' is needed. stop. > make[1]: *** [/d/xen/xen-3.1-testing.hg/unmodified_drivers/linux-2.6/balloon] > Error 2 > make: *** [_module_/d/xen/xen- 3.1-testing.hg/unmodified_drivers/linux-2.6] > Error 2 > make: `/usr/src/linux-2.6.18.8-86'' leaving directory > voyager linux-2.6 # > > I translated some of the error messages from Turkish to English but I > guess you''ll get the point. What am I doing wrong? Should I first run the > 1st step or not? As I''m in a HVM DomU, I don''t see a reason to run the first > step. If so, which sources shall I use for Xen, the sources in my dom0? > > Didn''t get it fully I guess... > > Thanks a lot, > > Emre > > > > On Nov 22, 2007 3:35 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > > On Thu, Nov 22, 2007 at 01:47:06PM +0100, Emre Erenoglu wrote: > > > Hi, > > > > > > Is it possible to use HVM (full virtualization) for Linux guests but > > use PV > > > drivers instead inside the DomU for extra performance? > > > > > > > Yes. > > > > > What shall I do to be able to do it? Where can I download these > > drivers for > > > several standard kernels? (HVM domU = standard distribution kernel, > > > not-xen-aware) > > > > > > > You can download xen source tree and compile "unmodified drivers" from > > there, or you can use the ones distributed with your distribution, if > > available. > > > > > Or, does the recent introduction of VMI into the linux kernel make > > this > > > automatic for us? i.e. if I use any recent kernel, such as Ubuntu''s > > > 2.6.22-14-generic, will paravirtualized disk/network drivers be > > > automatically activated? > > > > > > > VMI is VMware''s interface to run paravirtual Linux on VMware. It doesn''t > > > > work or help at all with Xen. > > > > If you''re running paravirtual linux on xen, you already have > > paravirtualized > > ("full speed") drivers in use. > > > > If you''re using HVM domU on Xen, then you need to install Xen PV drivers > > on > > domU. > > > > -- Pasi > > > > > > -- > > Emre Erenoglu > erenoglu@gmail.com >-- Emre Erenoglu erenoglu@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Again, OK, I managed to find the sources of my xen-hypervisor-3.1 package, downloaded and extracted it into my DomU. I also had the DomU HVM kernel sources. I ran 1.st step then 2nd. Things compiled seemingly well. However, the "xenbus.ko" does not compile. It has no place in the Makefile. Why? I modprobed the modules produced, i.e. xen-platform-pci, xen-balloon, xen-vbd, xen-vnif, and got the following responses in dmesg output: Xen version 3.1. Hypercall area is 1 pages. register_blkdev: cannot get major 3 for ide vbd vbd-768: 19 xlvbd_add at /local/domain/0/backend/vbd/1/768 register_blkdev: cannot get major 3 for ide vbd vbd-832: 19 xlvbd_add at /local/domain/0/backend/vbd/1/832 register_blkdev: cannot get major 22 for ide vbd vbd-5632: 19 xlvbd_add at /local/domain/0/backend/vbd/1/5632 xen_mem: Initialising balloon driver. netfront: Initialising virtual ethernet driver. vif vif-0: 2 parsing device/vif/0/mac So except this vbd error, it seems OK. I don''t know if this vbd error is a warning or really an error though... Is there a known way to test the performance? Thanks, Emre _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users