All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Jan Peter Stotz <Jan-Peter.Stotz@sit.fraunhofer.de>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	stefanb@us.ibm.com, vincent.r.scarlata@intel.com
Subject: Re: Xen 3.0.5 Second Release Candidate
Date: Mon, 23 Apr 2007 10:54:35 +0100	[thread overview]
Message-ID: <C25240EB.DB5D%keir@xensource.com> (raw)
In-Reply-To: <462C7FDE.9060700@sit.fraunhofer.de>

This is a bug for either Vinnie Scarlata or Stefan Berger to look into, I
think. That code hasn't been touched in quite a while, so I'm not even sure
it's being actively maintained any more (in which case we'll remove it).

 Thanks for the bug report!
 -- Keir

On 23/4/07 10:43, "Jan Peter Stotz" <Jan-Peter.Stotz@sit.fraunhofer.de>
wrote:

> Keir Fraser schrieb:
>> Well, that didn't take long! This candidate fixes a regression which causes
>> 32-bit x86 builds not to work out of the box (Xen is built for PAE, but the
>> Linux kernels are not). Also includes Tim Deegan's fix for SDL HVM
>> save/restore.
> 
> I found a bug in the tools part of xen: The vtpm_manager fails to
> establish a correct connection to the tpm_emulator (activated DDUMMY_TPM
> flag). In xen-3.0.4-1 it works but not in the release candidates of
> xen-3.0.5
> 
> See bug ID 966:
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=966
> 
> Jan

       reply	other threads:[~2007-04-23  9:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <462C7FDE.9060700@sit.fraunhofer.de>
2007-04-23  9:54 ` Keir Fraser [this message]
2007-04-23 16:36   ` Xen 3.0.5 Second Release Candidate Cihula, Joseph
2007-04-23 17:13     ` Keir Fraser
2007-04-23 19:11     ` Cihula, Joseph
2007-04-20 16:55 Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C25240EB.DB5D%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=Jan-Peter.Stotz@sit.fraunhofer.de \
    --cc=stefanb@us.ibm.com \
    --cc=vincent.r.scarlata@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.