xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: ranjith krishnan <ranjithkrishnan1@gmail.com>
To: "Gizmo Chicken" <gizmochicken@gmail.com>,
	"Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Dario Faggioli <dario.faggioli@citrix.com>, xen-devel@lists.xen.org
Subject: Re: Xen 4.1 compile from source and install on Fedora 17
Date: Wed, 12 Jun 2013 10:06:07 -0600	[thread overview]
Message-ID: <CAEybL6yrj56AtJ2QhJeo_RXvN6zExz9XkHinceeAtkXBvs2DKg@mail.gmail.com> (raw)
In-Reply-To: <CAHdVSpmOVyUtAXgrzpDRPEgxJKVEzJswPk_fHRQDM9ewQwym1A@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1636 bytes --]

Thanks for your replies!

Pasi, Are you suggesting me to install Fedora 18 and check grub2
configuration and try to build my new grub from that ? Since I have Fedora
17 installed now as Dom0 and have Xen working, can't I use this grub2 as a
working example.

Dario and Gizmo,

>> Dario,
> >>
> >> When you say that using virt-manager is entirely possible with Xen 4.2
> >> on Fedora 18, with which toolstack, XL or XM, do you mean?
> >>
> > Both, actually. libxl driver is definitely less mature, and might still
> > miss some features, but the basic create-pause-resume-shutdown-destroy
> > workload works really well for me.
>
>
>  It is just that the machine I am working on is a university machine, and
it has
 fedora 17, hence I am trying to get things working on Fedora 17 first.
Installing
 a new OS means I have to give the machine to the system admins, which
takes
 more time and me trying out things.

 I also remember reading in some forums where libvirt/virt-manager having
 issues running on Xen 4.2 and F18, which was why I started with Fedora 17
 in the first place.

 Dario,
 Did you compile Xen from source and install on F18 ? If yes can you give
me
 some tips on how you got it working, especially the grub entries. When I
first
 tried compiling/installing Xen from source, I was unable to boot Xen.

 Now that I have the grub.cfg file from the F17 (Xen installed using yum),
can I
 use this as an example and edit my grub.cfg after I compile/install Xen?
 Also, grub2 tells us not to manually edit grub.cfg since it is
autogenerated from
/etc/default/grub. So what is the right way to do it ?


-- 
Ranjith krishnan

[-- Attachment #1.2: Type: text/html, Size: 2243 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-06-12 16:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 21:44 Xen 4.1 compile from source and install on Fedora 17 ranjith krishnan
2013-06-12  6:07 ` Pasi Kärkkäinen
2013-06-12  8:33 ` Dario Faggioli
2013-06-12  9:02   ` Gizmo Chicken
2013-06-12  9:35     ` Dario Faggioli
2013-06-12 13:22       ` Gizmo Chicken
2013-06-12 16:06         ` ranjith krishnan [this message]
2013-06-12 17:48           ` M A Young
2013-06-12 23:44         ` Dario Faggioli
2013-06-18  6:31           ` ranjith krishnan

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=CAEybL6yrj56AtJ2QhJeo_RXvN6zExz9XkHinceeAtkXBvs2DKg@mail.gmail.com \
    --to=ranjithkrishnan1@gmail.com \
    --cc=dario.faggioli@citrix.com \
    --cc=gizmochicken@gmail.com \
    --cc=pasik@iki.fi \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).