(why 0.6.0-3?))
Sorry, I think I had already do some previous changes I my own git, indeed
0.6.0-2 is the good next version.
- Mail original -
De: Dietmar Maurer diet...@proxmox.com
À: Alexandre Derumier aderum...@odiso.com, pve-devel@pve.proxmox.com
Envoyé: Lundi 15 Juillet 2013
Please can you cleanup this patch (comments inline)?
PVE/QemuServer.pm | 25 +++--
1 file changed, 15 insertions(+), 10 deletions(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm index
31d8103..196ad0a 100644
--- a/PVE/QemuServer.pm
+++ b/PVE/QemuServer.pm
@@
Hi,
I wonder if we could steam the lock status ?
It could be great to display a new icon in pve-manager when a migration occur
or disk is move for example.
Also, I don't known if it's possible, but I could be great to display running
tasks on top of task list.
(Ex: When live migrate a lot
I wonder if we could steam the lock status ?
It could be great to display a new icon in pve-manager when a migration
occur or disk is move for example.
# pvesh get /nodes/localhost/qemu/VMID/status/current
that call provides = 'qmpstatus'
should we distribute that around the cluster?
Need for win8 boot.
This flag was missing from rhel 6.4 host kernel. It's ok now.
But it's also missing from kvm64 model. (It's exist in other cpu models, amd or
intel).
So it's pretty safe to enable it.
If the host kernel is older, qemu filter the flag.
This also improve performance of winxp
This reduce context switch with multicore guests.
Even if the host cpu don't have x2apic, it's working because qemu have an
virtual x2apic implementation for guest.
We need in-kernel irqchip support for this, which is enable for kvm guest
since qemu 1.3.
(I don't enable it if nokvm param is
This add special hyper-v cpu flags for windows guests.
This improve performance and avoid some bsod related to timer.
(I currently disable the hv_vapic flag because I can't get it working).
I have tested all theses flags with: win2003, win2008R2, winxp, linux debian
64bit, on intel and amd
changelog :
cleanup first commit
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
should we distribute that around the cluster?
I'm not sure we have all informations from qmp status
From the doc, the status values are:
- status: one of the following values (json-string)
debug - QEMU is running on a debugger
inmigrate - guest is paused waiting for an incoming
From the doc, the status values are:
- status: one of the following values (json-string)
debug - QEMU is running on a debugger
inmigrate - guest is paused waiting for an incoming migration
internal-error - An internal error that prevents further guest
execution has
Or maybe we should add the missing states to qemu?
-Original Message-
From: pve-devel-boun...@pve.proxmox.com [mailto:pve-devel-
boun...@pve.proxmox.com] On Behalf Of Dietmar Maurer
Sent: Montag, 15. Juli 2013 09:24
To: Alexandre DERUMIER
Cc: pve-devel@pve.proxmox.com
Subject: Re:
running = running, migrate , backup, snapshot, rollback
What do you think?
Yes, something like that. (But I don't known if mixing running with other
values could break something in proxmox code)
I introduced 'qmpstatus' for that purpose (instead of using 'status') - to make
sure that
we do
running = running, migrate , backup, snapshot, rollback
What do you think?
Yes, something like that. (But I don't known if mixing running with
other values could break something in proxmox code)
I introduced 'qmpstatus' for that purpose (instead of using 'status') - to
make
sure
I introduced 'qmpstatus' for that purpose (instead of using 'status') - to
make sure that
we do not break something.
Oh, ok, perfect !
So, maybe do we just need to extend:
PVE::QemuServer::vmstatus
# fixme: better status?
$d-{status} = $list-{$vmid}-{pid} ? 'running' : 'stopped';
-
I introduced 'qmpstatus' for that purpose (instead of using 'status')
- to make sure that we do not break something.
Oh, ok, perfect !
So, maybe do we just need to extend:
PVE::QemuServer::vmstatus
# fixme: better status?
$d-{status} = $list-{$vmid}-{pid} ? 'running' : 'stopped';
I don’t want to do that now, so I introduced 'qmpstatus' instead.
Ok, so we just need to put new values in qmpstatus, right ?
yes
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
16 matches
Mail list logo
