On Thu, Jun 11, 2015 at 09:38:24 +0800, zhang bo wrote:
On 2015/6/10 17:31, Daniel P. Berrange wrote:
On Wed, Jun 10, 2015 at 10:28:08AM +0100, Daniel P. Berrange wrote:
On Wed, Jun 10, 2015 at 05:24:50PM +0800, zhang bo wrote:
On 2015/6/10 16:39, Vasiliy Tolstov wrote:
2015-06-10
2015-06-11 11:42 GMT+03:00 Jiri Denemark jdene...@redhat.com:
Such guests would need an update qemu-guest-agent anyway. And installing
a new version of qemu-guest-agent is not any easier than installing an
updated udev or a new udev rule. That is, I don't think the
qemu-guest-agent way has any
On Wed, Jun 10, 2015 at 10:28:08AM +0100, Daniel P. Berrange wrote:
On Wed, Jun 10, 2015 at 05:24:50PM +0800, zhang bo wrote:
On 2015/6/10 16:39, Vasiliy Tolstov wrote:
2015-06-10 11:37 GMT+03:00 Daniel P. Berrange berra...@redhat.com:
The udev rules are really something the OS vendor
On Wed, Jun 10, 2015 at 02:05:16PM +0800, zhang bo wrote:
On 2015/6/10 13:40, Vasiliy Tolstov wrote:
2015-06-10 5:28 GMT+03:00 zhang bo oscar.zhan...@huawei.com:
Thank you for your reply.
Before this patch, we needed to manually online memory blocks inside the
guest, after dimm memory
2015-06-10 11:37 GMT+03:00 Daniel P. Berrange berra...@redhat.com:
The udev rules are really something the OS vendor should setup, so
that it just works
I think so, also for vcpu hotplug this also covered by udev. May be we
need something to hot remove memory and cpu, because in guest we need
On 2015/6/10 16:39, Vasiliy Tolstov wrote:
2015-06-10 11:37 GMT+03:00 Daniel P. Berrange berra...@redhat.com:
The udev rules are really something the OS vendor should setup, so
that it just works
I think so, also for vcpu hotplug this also covered by udev. May be we
need something to hot
On Wed, Jun 10, 2015 at 05:24:50PM +0800, zhang bo wrote:
On 2015/6/10 16:39, Vasiliy Tolstov wrote:
2015-06-10 11:37 GMT+03:00 Daniel P. Berrange berra...@redhat.com:
The udev rules are really something the OS vendor should setup, so
that it just works
I think so, also for vcpu
On 2015/6/10 13:40, Vasiliy Tolstov wrote:
2015-06-10 5:28 GMT+03:00 zhang bo oscar.zhan...@huawei.com:
Thank you for your reply.
Before this patch, we needed to manually online memory blocks inside the
guest, after dimm memory hotplug
for most *nix OSes. (Windows guests automatically get
On 2015/6/10 17:31, Daniel P. Berrange wrote:
On Wed, Jun 10, 2015 at 10:28:08AM +0100, Daniel P. Berrange wrote:
On Wed, Jun 10, 2015 at 05:24:50PM +0800, zhang bo wrote:
On 2015/6/10 16:39, Vasiliy Tolstov wrote:
2015-06-10 11:37 GMT+03:00 Daniel P. Berrange berra...@redhat.com:
The udev
Logically memory hotplug via guest agent, by enabling/disabling memory blocks.
The corresponding qga commands are: 'guest-get-memory-blocks',
'guest-set-memory-blocks' and 'guest-get-memory-block-info'.
detailed flow:
1 get memory block list, each member has 'phy-index', 'online' and
On Tue, Jun 09, 2015 at 05:33:24PM +0800, Zhang Bo wrote:
Logically memory hotplug via guest agent, by enabling/disabling memory blocks.
The corresponding qga commands are: 'guest-get-memory-blocks',
'guest-set-memory-blocks' and 'guest-get-memory-block-info'.
detailed flow:
1 get
On Tue, Jun 09, 2015 at 11:05:16 +0100, Daniel Berrange wrote:
On Tue, Jun 09, 2015 at 05:33:24PM +0800, Zhang Bo wrote:
Logically memory hotplug via guest agent, by enabling/disabling memory
blocks.
The corresponding qga commands are: 'guest-get-memory-blocks',
'guest-set-memory-blocks'
On Tue, Jun 09, 2015 at 01:22:49PM +0200, Peter Krempa wrote:
On Tue, Jun 09, 2015 at 11:05:16 +0100, Daniel Berrange wrote:
On Tue, Jun 09, 2015 at 05:33:24PM +0800, Zhang Bo wrote:
Logically memory hotplug via guest agent, by enabling/disabling memory
blocks.
The corresponding qga
On Tue, Jun 09, 2015 at 12:46:27 +0100, Daniel Berrange wrote:
On Tue, Jun 09, 2015 at 01:22:49PM +0200, Peter Krempa wrote:
On Tue, Jun 09, 2015 at 11:05:16 +0100, Daniel Berrange wrote:
On Tue, Jun 09, 2015 at 05:33:24PM +0800, Zhang Bo wrote:
Logically memory hotplug via guest agent,
On Tue, Jun 09, 2015 at 02:03:13PM +0200, Peter Krempa wrote:
On Tue, Jun 09, 2015 at 12:46:27 +0100, Daniel Berrange wrote:
On Tue, Jun 09, 2015 at 01:22:49PM +0200, Peter Krempa wrote:
On Tue, Jun 09, 2015 at 11:05:16 +0100, Daniel Berrange wrote:
On Tue, Jun 09, 2015 at 05:33:24PM
On Tue, Jun 09, 2015 at 13:05:35 +0100, Daniel Berrange wrote:
On Tue, Jun 09, 2015 at 02:03:13PM +0200, Peter Krempa wrote:
On Tue, Jun 09, 2015 at 12:46:27 +0100, Daniel Berrange wrote:
On Tue, Jun 09, 2015 at 01:22:49PM +0200, Peter Krempa wrote:
On Tue, Jun 09, 2015 at 11:05:16
On Tue, Jun 09, 2015 at 02:12:39PM +0200, Peter Krempa wrote:
On Tue, Jun 09, 2015 at 13:05:35 +0100, Daniel Berrange wrote:
On Tue, Jun 09, 2015 at 02:03:13PM +0200, Peter Krempa wrote:
On Tue, Jun 09, 2015 at 12:46:27 +0100, Daniel Berrange wrote:
On Tue, Jun 09, 2015 at 01:22:49PM
On 2015/6/9 20:47, Daniel P. Berrange wrote:
On Tue, Jun 09, 2015 at 02:12:39PM +0200, Peter Krempa wrote:
On Tue, Jun 09, 2015 at 13:05:35 +0100, Daniel Berrange wrote:
On Tue, Jun 09, 2015 at 02:03:13PM +0200, Peter Krempa wrote:
On Tue, Jun 09, 2015 at 12:46:27 +0100, Daniel Berrange
2015-06-10 5:28 GMT+03:00 zhang bo oscar.zhan...@huawei.com:
Thank you for your reply.
Before this patch, we needed to manually online memory blocks inside the
guest, after dimm memory hotplug
for most *nix OSes. (Windows guests automatically get their memory blocks
online after
19 matches
Mail list logo
