Hi,
One more query. When i had build the source code of the xen
hypervisor (make world) it had build the linux kernel also(downloaded
the bits using mercurial).
Would it be possible to just build the hypervisor ?
Isn't the hypervisor and linux kernel linked ? Pardon my ignorance.
Like is the linux kernel which is used is specially build to work
with the hyper visor or i can i can build any version of the kernel
and it should work with the hypervisor.
thanks
On Tue, Sep 8, 2009 at 5:46 AM, shankha<shankhabanerjee@xxxxxxxxx> wrote:
> Hi Fajar,
> Thanks for your continued help. I checked through yast the following
> are installed on my system
>
> 1. Kernel-Xen
> The linux kernel for xen paravirtualization.
> This kernel can be used both as the domain0 ("xen0") and as an
> unprivileged ("xenU") kernel.
>
> Version : 2.6.27.7-9.1 (x86_64)
>
> 2. kernel-xen-base
> The Linux kernel for Xen paravirtualization.
> This kernel can be used both as the domain0 ("xen0") and as an
> unprivileged ("xenU") kernel.
>
> 2.6.27.7-9.1 (x86_64)
>
> 3. kernel-xen-extra
> The Linux kernel for Xen paravirtualization.
> This kernel can be used both as the domain0 ("xen0") and as an
> unprivileged ("xenU") kernel.
>
>
> 2.6.27.7-9.1 (x86_64)
>
> 4. xen
> This is the xen hypervisor
>
> 3.3.1_18494_03-1.8 (x86_64)
>
> 4. xen-devel
> 3.3.1_18494_03-1.8 (x86_64)
>
> This package contains libraries and header files.
>
> When i try to to uninstall this package it says it has a dependency on libvrt.
>
> 5.xen - libs
> xen virtualization libraries
>
> 6. xen - tools
> Packages for starting stopping packages.
>
>
> I guess i can let the first 3 packages as it is. I will
> uninstall the xen hypervisor and other packages related to it.
>
> I can then put the the new hypervisor(3.4) and related libraries
> under /boot and boot with the kernel already installed.
>
> Does it look good or have i made mistakes ?
>
> thanks
>
>
> On Mon, Sep 7, 2009 at 11:21 PM, Fajar A. Nugraha<fajar@xxxxxxxxx> wrote:
>> On Tue, Sep 8, 2009 at 4:53 AM, shankha<shankhabanerjee@xxxxxxxxx> wrote:
>>> Hi,
>>> I am trying to use a new version of the hypervisor. I am not trying to
>>> install a new version of the kernel.
>>
>> In that case you don't need to install kernel 2.6.18-8 if you don't
>> want to. You can use your existing kernel.
>> However installing hypervisor and userland tools will overwrite some
>> files installed by your OS if your OS already has its own Xen version.
>>
>> --
>> Fajar
>>
>>>
>>> thanks
>>>
>>> On Mon, Sep 7, 2009 at 5:37 PM, Fajar A. Nugraha<fajar@xxxxxxxxx> wrote:
>>>> On Tue, Sep 8, 2009 at 3:57 AM, shankha<shankhabanerjee@xxxxxxxxx> wrote:
>>>>> Hi,
>>>>> Thanks for your reply. Could you please let me know what is the
>>>>> problem with my mkinitrd command. Is it because i may have forgot to
>>>>> copy some part of the installation.
>>>>
>>>> Installing a new KERNEL (including xen kernel) should be "safe" (as in
>>>> it shouldn't overwrite anything you already have) assuming it's
>>>> version is different from what you have. It's easier to simply run
>>>> "make modules_install" and "make install" on kernel build directory.
>>>>
>>>> Installxing Xen however, is more then just the kernel. It also
>>>> installs hypervisor userland tools (e.g. xm, xend, etc.), which most
>>>> likely will overwrite what you already have. Which is why I said you
>>>> can only have one version of Xen.
>>>>
>>>> What are you trying to do here? Use a new kernel or use a new Xen
>>>> version? Those two does not necessarily be done at the same time. If
>>>> you only want a new Xen version, usually you can just use kernel-xen
>>>> provided by your distro and simply install the hypervisor (xen.gz) and
>>>> userland tools.
>>>>
>>>> Here's a hint : trying out different versions of Xen is actually
>>>> easiest on RHEL5, thanks to Gitco's repository
>>>> http://www.gitco.de/repo/.
>>>>
>>>>> IF yes can we make a wild guess.
>>>>> Also what are the correct options that should be used while creating
>>>>> the image.
>>>>
>>>> man mkinitrd? I'm not familiar enough with Suse, but as I recall its
>>>> option is slightly different from Redhat's.
>>>>
>>>> --
>>>> Fajar
>>>>
>>>
>>
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|