Am 18.02.2015 um 07:12 schrieb Nathan Whitehorn nwhiteh...@freebsd.org:
It seems like KVM doesn't implement the H_CLEAR_REF and H_CLEAR_MOD
hypervisor calls, which are absolutely critical for memory management in the
FreeBSD kernel (and are marked mandatory in the PAPR manual). It seems
Am 18.02.2015 um 07:12 schrieb Nathan Whitehorn nwhiteh...@freebsd.org:
It seems like KVM doesn't implement the H_CLEAR_REF and H_CLEAR_MOD
hypervisor calls, which are absolutely critical for memory management in the
FreeBSD kernel (and are marked mandatory in the PAPR manual). It seems
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 17 Feb 2015 11:03:11 -0700
Eric Blake ebl...@redhat.com wrote:
On 02/17/2015 07:24 AM, Michael Mueller wrote:
This patch implements a new QMP request named 'query-cpu-model'.
It returns the cpu model of cpu 0 and its backing accelerator.
On Mon, Feb 16, 2015 at 06:19:04PM +0100, Henry Noack wrote:
it is possible to decrypt a kvm volume only by using the command line after
starting it?
Encryption can be done at 3 levels:
1. Inside the guest. Just like you do on a physical machine with LUKS
(dm-crypt), ecryptfs, TrueCrypt,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 17 Feb 2015 12:16:20 -0700
Eric Blake ebl...@redhat.com wrote:
On 02/17/2015 07:24 AM, Michael Mueller wrote:
The option --probe allows to switch into probe mode also for machines
different from none. If one or more accelerators are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 17 Feb 2015 11:09:34 -0700
Eric Blake ebl...@redhat.com wrote:
On 02/17/2015 07:24 AM, Michael Mueller wrote:
This patch implements the QMP command 'query-cpu-definitions' in the S390
context. The command returns a in terms of machine
On Tue, Feb 17, 2015 at 07:07:21PM +0100, Jan Kiszka wrote:
On 2015-02-17 19:00, Bandan Das wrote:
Kashyap Chamarthy kcham...@redhat.com writes:
..
Does enable_apicv make a difference?
Actually, I did perform a test (on Paolo's suggestion on IRC) with
enable_apicv=0 on physical
On Wed, Feb 18, 2015 at 09:34:54AM +0100, Alexander Graf wrote:
Am 18.02.2015 um 07:12 schrieb Nathan Whitehorn nwhiteh...@freebsd.org:
It seems like KVM doesn't implement the H_CLEAR_REF and H_CLEAR_MOD
hypervisor calls, which are absolutely critical for memory management in
the
On Wed, Feb 18, 2015 at 09:34:54AM +0100, Alexander Graf wrote:
Am 18.02.2015 um 07:12 schrieb Nathan Whitehorn nwhiteh...@freebsd.org:
It seems like KVM doesn't implement the H_CLEAR_REF and H_CLEAR_MOD
hypervisor calls, which are absolutely critical for memory management in
the
Точно удачный презент девушке к празднику 8 марта
http://www.google.com/url?q=http%3A%2F%2F%73h%69%63ot%72%61%6es%2e%72u%2F%23%6e%33%32%797zn%667%71%7605dksa=Dsntz=1usg=AFQjCNHJZTyi9yGyNHxWGuUtNghdvCSLQg
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to
On Tue, Feb 17, 2015 at 06:44:19PM +0100, Sebastian Andrzej Siewior wrote:
* Peter Zijlstra | 2015-01-21 16:07:16 [+0100]:
On Tue, Jan 20, 2015 at 01:16:13PM -0500, Steven Rostedt wrote:
I'm actually wondering if we should just nuke the _interruptible()
version of swait. As it should only
Hi Andre,
Thanks for doing this. Since it looks unlikely that kvmtool will ever be
merged back into the kernel tree, it makes sense to cut the dependency
in my opinion.
On Fri, Feb 13, 2015 at 10:39:33AM +, Andre Przywara wrote:
as I found it increasingly inconvenient to use kvmtool[1] as
Stefan Hajnoczi stefa...@gmail.com writes:
On Mon, Feb 16, 2015 at 06:19:04PM +0100, Henry Noack wrote:
it is possible to decrypt a kvm volume only by using the command line after
starting it?
Encryption can be done at 3 levels:
[...]
2. In QEMU with qcow2, although this feature is not
On 17/02/2015 12:24, Kashyap Chamarthy wrote:
Afraid, I didn't bisect it, but I just wanted to note that the above
specific WARN was introduced in the above commit.
I'm sure this Kernel (on L0) does not exhibit the problem:
kernel-3.17.4-301.fc21.x86_64. But, if I had either of these two
On 02/18/15 14:00, Paul Mackerras wrote:
On Wed, Feb 18, 2015 at 09:34:54AM +0100, Alexander Graf wrote:
Am 18.02.2015 um 07:12 schrieb Nathan Whitehorn nwhiteh...@freebsd.org:
It seems like KVM doesn't implement the H_CLEAR_REF and H_CLEAR_MOD hypervisor calls,
which are absolutely critical
On 02/18/15 14:00, Paul Mackerras wrote:
On Wed, Feb 18, 2015 at 09:34:54AM +0100, Alexander Graf wrote:
Am 18.02.2015 um 07:12 schrieb Nathan Whitehorn nwhiteh...@freebsd.org:
It seems like KVM doesn't implement the H_CLEAR_REF and H_CLEAR_MOD hypervisor calls,
which are absolutely critical
16 matches
Mail list logo
