At 17:14 + on 15 Mar (1331831693), Stefano Stabellini wrote:
> On Thu, 15 Mar 2012, Julien Grall wrote:
> > When an IOREQ_TYPE_INVALIDATE is sent to QEMU, it invalidates all entry
> > of the map cache even if it's locked.
> >
> > QEMU is not able to know that entry was invalidated, so when an
At 10:32 -0700 on 15 Mar (1331807562), Andres Lagar-Cavilla wrote:
> > At 17:14 + on 15 Mar (1331831693), Stefano Stabellini wrote:
> >> On Thu, 15 Mar 2012, Julien Grall wrote:
> >> > When an IOREQ_TYPE_INVALIDATE is sent to QEMU, it invalidates all
> >> entry
> >> > of the map cache even if i
Hi,
At 15:59 + on 22 Mar (1332431961), Julien Grall wrote:
> Julien Grall (15):
> xc: Add the hypercall for multiple servers
> xc: Add argument to allocate more special pages
> xc: Fix python build
Shouldn't something here update xc_domain_save/xc_domain_restore?
Cheers,
Tim.
At 11:07 +0100 on 19 Jun (1371640052), Ian Campbell wrote:
> On Wed, 2013-06-19 at 10:43 +0100, Paul Durrant wrote:
> > > -Original Message-
> > > From: Ian Campbell
> > > Sent: 19 June 2013 10:42
> > > To: Paul Durrant
> > > Cc: qemu-devel@nongnu.org; xen-de...@lists.xen.org
> > > Subject:
At 11:23 + on 19 Jun (1371641017), Paul Durrant wrote:
> The problem is that the old Citrix PV drivers bind their version of
> xenvbd directly to the platform device (id=1). The new PV drivers bind
> their xenbus driver to their platform device, because to go onto
> Windows Update you cannot ha
At 11:21 -0700 on 19 Jun (1371640904), Matt Wilson wrote:
> On Wed, Jun 19, 2013 at 11:42:06AM +0100, Alex Bligh wrote:
> >
> > --On 19 June 2013 10:13:17 + Paul Durrant
> > wrote:
> >
> > >>We obviously can't say to users "Are you running Windows and are you
> > >>running PV drivers >= X.Y,
At 07:47 + on 20 Jun (1371714432), Paul Durrant wrote:
> > > I agree. If this is really the only solution, we would need to have
> > > both versions presented to the guest so that old drivers continue to
> > > work without any intervention.
> >
> > I suspect that if we expose both, both sets o
At 11:23 + on 26 Jun (1372245783), Paul Durrant wrote:
> We could blacklist all existing Citrix PV drivers in upstream QEMU,
> to avoid the clash, but that seems like a very unfriendly
> approach. Also, it's not going to stop someone with an existing VM,
> who happens to be using legacy Citrix
At 12:06 + on 26 Jun (1372248391), Paul Durrant wrote:
> > -Original Message-
> > From: Tim Deegan [mailto:t...@xen.org]
> > Sent: 26 June 2013 12:58
> > To: Paul Durrant
> > Cc: Ian Campbell; Matt Wilson; Alex Bligh; xen-de...@lists.xen.org; qemu-
> &
At 10:56 +0100 on 02 Jul (1372762607), Ian Campbell wrote:
> On Tue, 2013-07-02 at 10:14 +0100, Paul Durrant wrote:
> > I had actually coded up a solution based on the existing Xen platform
> > device, by having it synthesize a device ID based on the Xen version
> > to which we could then host the
At 10:31 + on 02 Jul (1372761105), Paul Durrant wrote:
> > > Well, the WU drivers could refuse to install except as upgrade to
> > > themselves (i.e. fail if there's any unknown driver bound to the xen
> > > platform device, and also fail if there's _no_ driver bound). Then the
> > > guest adm
Two small changes: fix the buffer wraparound code for 64k ring-buffers,
and enable (and fix) the crc32 checksum calculation. These changes are
needed for the the Realtek driver that shipped with 32-bit Vista.
Cheers,
Tim.
--
Tim Deegan <[EMAIL PROTECTED]>, XenSource UK Limited
Regi
12 matches
Mail list logo
