From: "Crazy" <kelberts@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: Xen and Kernel 2.6.25
Date: Fri, 13 Jun 2008 11:41:26 -0300 [thread overview]
Message-ID: <g2u0un$4kg$1@ger.gmane.org> (raw)
In-Reply-To: <18514.31853.524156.930331@mariner.uk.xensource.com>
Really nice.
I try to use 2.6.5 with the domU support, and it´s working!
The only thing that isnt working its the vnc. I think because 2.6.25-xen,
doenst have frambuffer for xen support yet
Its a task for 2.6.26 perhaps
see in http://wiki.xensource.com/xenwiki/XenParavirtOps
-----------------------------
# eatures in 2.6.25:
* x86-32 support
* SMP
* Console (hvc0)
* Blockfront (xvdX)
* Netfront
# Queued for 2.6.26:
* Balloon (contraction only)
* paravirtual framebuffer + mouse (pvfb)
* 2.6.26 onwards will be PAE-only
-------------------------------------------------
"Ian Jackson" <Ian.Jackson@eu.citrix.com> escreveu na mensagem
news:18514.31853.524156.930331@mariner.uk.xensource.com...
> Grzegorz Mi³o¶ writes ("Re: [Xen-devel] Xen and Kernel 2.6.25"):
>> > Some question.
>> > Can I install Xen-3.2.1 with 2.6.18-xen kernel... to my Dom0
>> > and without HVM, starting a debian(DomU) with kernel 2.6.25 from kernel
>> > src
>> > and compiled with all XEN port / features ?
>>
>> I don't think you'll be able to compile 2.6.25 DomU kernel from
>> vanilla sources (= kernel.org + xenbits.xensource.com).
>
> Recent mainline kernels (including 2.6.25) have domU support. It's
> not feature complete but it should be useable. (Last I checked
> save/restore and ballooning weren't supported, but work in this area
> is continuing apace.)
>
> Ian.
next prev parent reply other threads:[~2008-06-13 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 22:41 Xen and Kernel 2.6.25 Crazy
2008-06-13 11:29 ` Grzegorz Miłoś
2008-06-13 13:55 ` Ian Jackson
2008-06-13 14:41 ` Crazy [this message]
2008-06-18 17:41 ` Mark Williamson
2008-06-13 16:06 ` Grzegorz Miłoś
2008-06-18 17:39 ` Mark Williamson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='g2u0un$4kg$1@ger.gmane.org' \
--to=kelberts@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.