similar to: preparing for 4.3.1

Aiming at a release some time in August, I''d like to cut RC1-s by Thursday next week (as I''ll be on a two week vacation starting Friday). Please indicate any bug fixes that so far may have been missed in the backports already done. A few fixes are currently stuck in master''s staging branch (or pending to make it there) - these don''t need to be named explicitly,

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

i''m the Mageia Xen package maintainer, and a user reported that i had missing symbols in my ocaml bindings: https://bugs.mageia.org/show_bug.cgi?id=5199 i''m using Xen 4.2.1 and ocaml 3.12.1 the problem is that if you just to a simple hello world and you''re using certain bindings (eg: xeneventch): you get missing symbols. (others appear to be fine). I know next to

Hi, I''m the Mageia XEN packager and during QA, we stumbled into a problem. in fact, we wanted to test Mageia 3 installation on a HVM. so, we had a sparse image and a iso file: [ ''file:/opt/testhvm.img,sda,w'', ''file:/opt/mageialive.iso,hdb:cdrom,r'' ] the live booted, and was able to install to disk, but it never seemed to boot after the install...

2013/10/29, mail fetch <fetchmail.0104@gmail.com>: > Hi all, > > I just saw a know bug from wiki that network doesn''t work in guest in > arndale board : > > Network doesn''t work in the guest > > Contact: julien.grall@citrix.com > Status: In progress > Description: Network doesn''t work in the guest when an ehternet cable is > plugged

Folks, I am pleased to announce the release of Xen 4.1.4. This is available immediately from its mercurial repository: http://xenbits.xen.org/xen-4.1-testing.hg (tag RELEASE-4.1.4) This fixes the following critical vulnerabilities: * CVE-2012-3494 / XSA-12: hypercall set_debugreg vulnerability * CVE-2012-3495 / XSA-13: hypercall physdev_get_free_pirq vulnerability * CVE-2012-3496 /

Hi Everyone, According to this CVE: http://lists.xen.org/archives/html/xen-announce/2012-06/msg00001.html The patch has been added to xen-3.4-testing.hg. However, when I look here: http://xenbits.xen.org/hg/xen-3.4-testing.hg/ I don''t see any recent commits. Am I missing something? I feel it is very important that these patches make its way into this branch, and tagged as 3.4.5

On Fri, 2014-05-23 at 08:52 +0100, Jan Beulich wrote: > > I am a noob when working with source code. How do I bump my xen up to 4.3.3? > > I guess this > http://wiki.xenproject.org/wiki/Compiling_Xen_From_Source > should help you. Since this only needs a new hypervisor binary and not a full set of tools etc to reproduce I think it can be simplified to replacing the previous

I just wonder why xen 4.4 unstable presents it self as xen 4.3 unstable ? boot message states 4.3 unstable and efi is 4.3 unstable? I wonder what is the reason behind it ? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

>>> On 22.05.14 at 19:19, <mike at estone.ca> wrote: > "Jan Beulich" <JBeulich at suse.com> writes: > #Okay, this at least clarifies there is a (relatively big) RMRR. There is > #a change to the handling of these among the ones that'll become > #4.3.3 - mind giving > #http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=6c63041428cc348bcb2 >

On Fri, 2014-05-23 at 10:35 +0100, Jan Beulich wrote: > >>> On 23.05.14 at 11:21, <Ian.Campbell at citrix.com> wrote: > > On Fri, 2014-05-23 at 08:52 +0100, Jan Beulich wrote: > >> > I am a noob when working with source code. How do I bump my xen up to > > 4.3.3? > >> > >> I guess this > >>

A couple months ago, there was a thread discussing various opinions for directory structures for including xenlinux code into the Linux tree. (The current structure is not architecture independent and also uses some names/terminology that might need to change to be more acceptable to Linux kernel developers.) I think Chris Wright said at the time that he would be working on a patch to

Dom0: Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 3.2.41-2+deb7u2, package blktap-dkms and all dependency packages for xen, spice and usb redirection. Seabios 1.7.2-3 and latest spice and usbredir compiled from debian unstable sources. ------------------------- /etc/modules ------------ loop max_loop=64 xenfs xen-evtchn blktap ------------------------- git clone

>>> On 23.05.14 at 11:21, <Ian.Campbell at citrix.com> wrote: > On Fri, 2014-05-23 at 08:52 +0100, Jan Beulich wrote: >> > I am a noob when working with source code. How do I bump my xen up to > 4.3.3? >> >> I guess this >> http://wiki.xenproject.org/wiki/Compiling_Xen_From_Source >> should help you. > > Since this only needs a new

"Jan Beulich" <JBeulich at suse.com> writes: #Okay, this at least clarifies there is a (relatively big) RMRR. There is #a change to the handling of these among the ones that'll become #4.3.3 - mind giving #http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=6c63041428cc348bcb2887afabd606bc4bd5523f #a try on top of your 4.3.2 (or trying the tip of the stable-4.3 branch)? #

After a guest is live migrated, the xen-netfront driver emits a gratuitous ARP message, so that networking hardware on the target host's subnet can take notice, and public routing to the guest is re-established. However, if the packet appears on the backend interface before the backend is added to the target host's bridge, the packet is lost, and the migrated guest's peers become

After a guest is live migrated, the xen-netfront driver emits a gratuitous ARP message, so that networking hardware on the target host's subnet can take notice, and public routing to the guest is re-established. However, if the packet appears on the backend interface before the backend is added to the target host's bridge, the packet is lost, and the migrated guest's peers become

After a guest is live migrated, the xen-netfront driver emits a gratuitous ARP message, so that networking hardware on the target host's subnet can take notice, and public routing to the guest is re-established. However, if the packet appears on the backend interface before the backend is added to the target host's bridge, the packet is lost, and the migrated guest's peers become

X86: expose HLE/RTM features to dom0 Intel recently release 2 new features, HLE and TRM. Refer to http://software.intel.com/file/41417. This patch expose them to dom0. Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com> diff -r 92e03310878f xen/arch/x86/traps.c --- a/xen/arch/x86/traps.c Wed Feb 08 21:05:52 2012 +0800 +++ b/xen/arch/x86/traps.c Mon Feb 27 02:23:42 2012 +0800 @@ -857,9

Hi, I have just applied IGD VGA Passthrough patches to Xen 4.4-unstable changeset 27238. Please refer to the 2 attached patches. 1. [Xen-devel] [PATCH 2/3] V4 qemu-xen-trad: Correctly expose PCH ISA bridge for IGD passthrough Link: http://lists.xenproject.org/archives/html/xen-devel/2013-06/msg01720.html 2. [Xen-devel] [PATCH 3/3] qemu-xen-trad: IGD passthrough: Expose vendor specific pci