similar to: Security disclosure process discussion update

$ git checkout RELEASE-4.2.2 $ git clean -ffdx [do a build, install, reboot] $ xl create a0 $ xl cd-eject a0 hdc [However, the guest OS still sees the CD inserted] $ xl block-list a0 Segmentation fault $ xl cd-insert a0 hdc file:/images/xs-tools-6.0.0.iso Segmentation fault The problem seems to be that xl cd-eject is writing corrupt values to xenstore. Note that vbd/1/5632 is still there

I believe both mailing lists are great but there are so may postings that many issues get missed. There are some bugs that hand never been resolved because developers are unaware of it. I just setup forum for xen users at sam.hebe.us/forums please be free to join _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

I believe both mailing lists are great but there are so may postings that many issues get missed. There are some bugs that hand never been resolved because developers are unaware of it. I just setup forum for xen users at sam.hebe.us/forums please be free to join _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

# HG changeset patch # User George Dunlap <george.dunlap@eu.citrix.com> # Date 1345022863 -3600 # Node ID 0982bad392e4f96fb39a025d6528c33be32c6c04 # Parent dc56a9defa30312a46cfb6ddb578e64cfbc6bc8b xl: Suppress spurious warning message for cpupool-list libxl_cpupool_list() enumerates the cpupools by "probing": calling cpupool_info, starting at 0 and stopping when it gets an error.

This information will be mirrored on the Xen 4.4 Roadmap wiki page: http://wiki.xen.org/wiki/Xen_Roadmap/4.4 We''re nearly to the completion of the code freeze, scheduled for tomorrow. After the code freeze, only bug fixes and features marked as "blockers" will be considered. At the moment, the only feature considered a blocker is experimental PVH dom0 support. In early RCs,

This took me a while to post, but given that we are not starting 4.4 just yet, this may be appropriate now. I may have misrepresented some stuff as it has been 4 weeks since I wrote these. Cheers Lars = Purpose of Roadmap = * Set a vision for interesting features * Track items * Help consumers of Xen with their planning = Release Models that work well = There was a brief discussion on two

Hi folks, From the roadmap for Xen 4.3 development, Xen 4.3 will use upstream QEMU (partially done). So I''d like to confirm the following questions. 1. Will Xen 4.3 really use upstream QEMU by default ? I have the question because so far the xen.git tree still uses qemu-xen-unstable by default. 2. If ''yes'' for 1st question, which QEMU upstream will be used in Xen

This is problem 1 of 3 problems we are having with live migration and/or ACPI on Xen-4.3 and Xen-4.2. Any help would be appreciated. Detailed description of problem: We are using Xen-4.3-rc1 with dom0 running Ubuntu Precise and 3.5.0-23-generic kernel, and domU running Ubuntu Precise (12.04) cloud images running 3.2.0-39-virtual. We are using the xl.conf below on qemu-upstream-dm and HVM and

Overriding PATH but not LD_LIBRARY_PATH is bogus, as it may result in the use of mismatched binaries and libraries. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/tools/hotplug/Linux/xen-hotplug-common.sh +++ b/tools/hotplug/Linux/xen-hotplug-common.sh @@ -31,6 +31,7 @@ dir=$(dirname "$0") exec 2>>/var/log/xen/xen-hotplug.log export

flight 13383 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/13383/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 16 guest-start fail REGR. vs. 13379 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-qemuu-win7-amd64 12

The hypervisor side changes for XSA-46 require the tool stack to now always map the guest pIRQ before granting access permission to the underlying host IRQ (GSI). This in particular requires that pciif.py no longer can skip this step (assuming qemu would do it) for HVM guests. This in turn exposes, however, an inconsistency between xend and qemu: The former wants to always establish 1:1 mappings

Signed-off-by: Matthew Fioravante <matthew.fioravante@jhuapl.edu> --- stubdom/configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/stubdom/configure.ac b/stubdom/configure.ac index db44d4a..384a94a 100644 --- a/stubdom/configure.ac +++ b/stubdom/configure.ac @@ -18,7 +18,7 @@ m4_include([../m4/depends.m4]) # Enable/disable stub domains

Hi experts,'' I build xen on my 64 bit redhat with "make xen", I got the image xen-4.0.0.gz then $gunzip xen-4.0.0.gz $file xen-4.0.0 it tells me it''s 32 bit,but I saw it link the 64 bit lib Thanks Lei -- "We learn from failure, not from success!" _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi experts,'' I build xen on my 64 bit redhat with "make xen", I got the image xen-4.0.0.gz then $gunzip xen-4.0.0.gz $file xen-4.0.0 it tells me it''s 32 bit,but I saw it link the 64 bit lib Thanks Lei -- "We learn from failure, not from success!" _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Add commands to automatically prep devices for pass-through The current method for passing through devices requires users to either modify cryptic Linux boot parameters and reboot, or do a lot of manual reads and writes into sysfs nodes. This set of patches introduces commands to make this easier. It expands on the concept of "assignable" (from the list_assignable_devices command).

This small series reintroduces OVMF support in Xen You can fetch working OVMF tree on: git://xenbits.xen.org/people/liuw/ovmf.git master Working changeset that can be sticked in Config.mk is: 8833370303d3bf3153760ee42760ef1b9b5c562 Note that VNC doesn''t work properly when using OVMF, but that''s not OVMF''s problem. This issue should be addressed in Xen and I''m

This is a patch to forward-port a Xend behaviour. Xend writes IO ABI used for all frontends. Blkfront before 2.6.26 relies on this behaviour otherwise guest cannot boot when running in 32-on-64 mode. Blkfront after 2.6.26 writes that node itself, in which case it''s just an overwrite to an existing node which should be OK. In fact Xend writes the ABI for all frontends including console

Hi everybody, just a quick reminder that the Xen Hackathon is in Oracle, March 6-8, Santa Clara, CA, USA. We have originally planned for about 25 people, but already we have 14 people signed up. If you are planning to attend please sign up quickly, such that I get a feeling for the number of attendees. I can then go back to Oracle and see whether we can accommodate more people than we