Using fedora14 and running xen-4.0.1 but when executing "xm info" the
following is displayed:
xen_caps: xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p
Should I ignore this and assume it is actually xen-4?
----- Forwarded message from Keir Fraser <keir.xen(a)gmail.com> -----
From: Keir Fraser <keir.xen(a)gmail.com>
To: "xen-devel(a)lists.xensource.com" <xen-devel(a)lists.xensource.com>,
Date: Fri, 25 Mar 2011 15:11:53 +0000
Subject: [Xen-devel] [ANNOUNCE] Xen 4.1 released!
The Xen team is pleased to announce the release of Xen 4.1.
The result of nearly 12 months of development, new features include:
* A re-architected and improved XL toolstack replacing XM/XEND
* Prototype credit2 scheduler designed for latency-sensitive workloads and
very large systems.
* CPU Pools for advanced partitioning.
* Support for large systems (>255 processors)
* Support for x86 Advanced Vector eXtension (AVX).
* New Memory Access API enabling integration of 3rd party security
solutions into Xen virtualized environments.
* Many IOMMU fixes (both Intel VT-d IOMMU and AMD IOMMU).
* Many toolstack and buildsystem fixes for Linux and NetBSD hosts.
* Thirdparty libs: libvirt driver for libxl has been merged to upstream
* HVM guest PXE boot enhancements, replacing gPXE with iPXE.
* Even better stability through our new automated regression tests.
Detailed release notes, including a more extensive feature list:
To download tarballs:
Or the Mercurial source repository (tag 'RELEASE-4.1.0'):
And the announcement on the Xen blog:
Thanks to the many people who have contributed to this release!
The Xen Team
Xen-devel mailing list
----- End forwarded message -----
Very confused as to which list I should post: xen, fedora, fedora-xen.
Apologies if this is the wrong one. Pointer to the most appropriate
list is welcome.
Current system is f14 with full updates, myoung's kernel 2.6.32.+,
booted with xen 4.0.1. Hardware is AMD with svm, lotsa ram.
After fighting with the all-in-one GUIs for virtmanager I gave up and
tried to recycle my configs from a 2006 box running xen3 (which still
purrs) and can't even get past scripts/network-bridge without a hang or
I'm not asking for help on creating a vm, just on getting dom0 to
recognize even one single bridge, even the default one. My feeling is
that if I can get that far I can take it from here.
Does anybody have a working example of a current xend-config.sxp for a
machine running xend with f14?
Using f14-x86_64 installed from the LiveCD with myoung's f12-xendom0.
It boots both standalone and with xen.
/sys/hypervisor is populated.
/proc/cpuinfo reports CPU is AMD Phenom II X4 B60 "Black Edition".
Virtualization is [ENABLED] in the BIOS.
I'm trying to add a virtual machine using Virtual Machine Manager 0.8.5
but when I select *New* I receive the following:
"Warning: Host does not appear to support hardware virtualization.
Install options may be limited."
According to this link (s.b. one line) it does.
Now according to another webpage the AMD processor must have the flag
"svm" to have virtualization. My CPU does NOT have that flag but it
does have one called "hypervisor".
The question becomes "will this CPU work with Xen?". If it will, does
this mean there is a bug in virtinst? Can I ignore the warning?
Thanks for any help,
I was wondering about the progress towards dom0 support in F15. The
feature page  hasn't been updated for a while, so I'm not clear on
how close the feature is to completion.
Specifically, I am looking to find out what kind of testing has been
done or is being done for this new feature. As far as I know, the Fedora
QA community is not very aware of xen dom0 support and it isn't a part
of the test cases that we have been running.
If dom0 support is likely to be complete in time for F15, we would
certainly welcome assistance in writing test cases and/or helping out
with the upcoming virtualization test day on 2011-04-14 .