I have installed "Xen" on Fedora16 host using "yum install xen" command and
it has been installed properly. I can see the changes in /etc/grub2.cfg
file too. But when I reboot then the entry for Xen is not listed in the
boot menu. On further analyzing I found that in /etc/grub.conf there is no
entry related to Xen. Do we need to modify grub.conf manually ? If yes then
how to do that. ?
Please help me with this.
Here is another 4.1.3 release candidate for testing which is temporarily
My plan is to update F17 and F16 to 4.1.3 when it is released, probably
also rawhide (unless 4.2 is out by then which is unlikely). F15 will
almost certainly have reached EOL by the time 4.1.3 appears, so won't be
First of all, apologizes if the issue has been discussed already (I
joined only a couple of months ago), but I was wondering whether there
already are plans on how to support that UEFI Secure Boot crazy (and
I've been gentle :-P) thing from the point of view of the xen packages
I mean, is some sort of binary signing involved? If so, are we already
able to do it, or at least will we be able to take advantage of whatever
Fedora will do with kernel images? Or is there something
different/special we should consider?
I'm not at all an expert of the matter, I was just reading about it and
started wondering whether it would still be possible to have xen binary
packages for Fedora (and of course for other distros too)...
Some of the links I found about the subject:
Thanks and Regards,
<<This happens because I choose it to happen!>> (Raistlin Majere)
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
I am attempting to run Xen on an AMD FX-4170 Quad-Core Processor.
I have installed Fedora 17 to serve as Dom0.
I am finding that Python does not run well on this
configuration. Specifically, "import random" causes the Python interpreter
to terminate with "Illegal instruction". This means that xend and yum will
I filed a bug under yum , but just realized that things work if I
boot Fedora 17 on bare metal.
Under Xen, /proc/cpuinfo reports the following flags:
fpu de tsc msr pae cx8 apic cmov pat clflush mmx fxsr sse sse2 ht syscall
nx mmxext fxsr_opt lm constant_tsc rep_good nopl nonstop_tsc extd_apicid
aperfmperf pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 popcnt aes hypervisor
lahf_lm cmp_legacy extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch
xop fma4 perfctr_core arat cpb hw_pstate
Has anyone had similar trouble?
I am using xen hypervisor in fedora 17. I want to use LVM storage for domU.
On Wed, Jun 27, 2012 at 5:12 PM, Joseph Hom <jhom(a)softlayer.com> wrote:
> What Xen are you using? OS? XCP? XenServer?****
> ** **
> Also what storage are you using?****
> ** **
> *From:* xen-users-bounces(a)lists.xen.org [mailto:
> xen-users-bounces(a)lists.xen.org] *On Behalf Of *Arindam Choudhury
> *Sent:* Wednesday, June 27, 2012 5:42 AM
> *To:* xen users
> *Subject:* [Xen-users] provisioning virtual machine****
> ** **
> I am trying to provision virtual machines to create a virtual machine
> cluster. If I try to transfer a pre-build virtual machine, its too time
> consuming and hard on network. So the idea of using bootstrap or kickstart
> seems better. Can any body point a good tutorial how to do this?
> Actually I have a master image and I have to copy it on all the nodes and
> create virtual machines. Is there any other way to do it?
> Arindam ****
I am trying to provision virtual machines to create a virtual machine
cluster. If I try to transfer a pre-build virtual machine, its too time
consuming and hard on network. So the idea of using bootstrap or kickstart
seems better. Can any body point a good tutorial how to do this?
Actually I have a master image and I have to copy it on all the nodes and
create virtual machines. Is there any other way to do it?