Hi all,
we just updated the wiki page:
http://pve.proxmox.com/wiki/ISCSI_Multipath
Please review. Comments are appreciated ;-)
- Dietmar
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>>The idea is to save the state into an external file. That will work for all
>>storage
>>types.
Great :) so it'll work for rbd or nexenta :)
>>Sorry, I do not understand what you mean?
When I have done tests with savevm, the qmp socket timeout each time during the
vmstate save.
It's also t
> what is the statefile argument ?
> I thinked that the state was saved inside the (first) disk. (so vmstate is
> snapshoted and we can rollback it easily) Or it's for doing some tests ?
The idea is to save the state into an external file. That will work for all
storage
types.
> I don't know if
Ok, I have tested it,
snapshot of drive works fine,
But I don't understand how the vm state is saved.
what is the statefile argument ?
I thinked that the state was saved inside the (first) disk. (so vmstate is
snapshoted and we can rollback it easily)
Or it's for doing some tests ?
I don't know i
> chardev: backend "qga_proxy" not found
>
> so it's not implemented yet.
> (I don't know if it's on the qemu roamap, I didn't find any info)
> So Do you need to implemented the current procotol ?
> (We need guest agent to freeze filesystem for snapshots
I just want to avoid unnecessary work. So
just tested with -chardev qga_proxy,id=qga0
chardev: backend "qga_proxy" not found
so it's not implemented yet.
(I don't know if it's on the qemu roamap, I didn't find any info)
So Do you need to implemented the current procotol ?
(We need guest agent to freeze filesystem for snapshots
- Ma
I'll read the code this afternoon, thanks !
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER"
Cc: pve-devel@pve.proxmox.com
Envoyé: Mardi 4 Septembre 2012 14:22:12
Objet: RE: [pve-devel] create snapshots
I just uploaded a patch - I consider that experimental - I have
Oh I miss that !
"
When QAPI-based QMP is available (somewhere around the QEMU 0.16 timeframe), a
different host-side invocation that doesn't involve access to the guest agent
outside of QMP will be used. Something like:
qemu \
...
-chardev qga_proxy,id=qga0 \
-device virtio-serial \
-devi
Documentation states that we can do all those thing via qmp in future! So why
do we want to add all that code now?
> -Original Message-
> From: pve-devel-boun...@pve.proxmox.com [mailto:pve-devel-
> boun...@pve.proxmox.com] On Behalf Of Alexandre Derumier
> Sent: Dienstag, 04. September 20
I just uploaded a patch - I consider that experimental - I have not done any
tests so far.
https://git.proxmox.com/?p=pve-qemu-kvm.git;a=commitdiff;h=7378b84a5f739a19b6ba4210598b301b5630b109
What do you think - will that fit our needs?
- Dietmar
___
I have tried to tunned the cachesize dynamically, but it doesn't help.
This is strange, as xbzrle should help for vm with intensive memory workload.
(and it seem to take more time )
I have send a message to the qemu mailing, waiting for a response
- Mail original -
De: "Dietm
> after which time have you seen the endless running xbzrle? Did the
> remaining bytes size raise again in your case?
yes. I guess we should test again when final 1.2 is out.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cg
> -Original Message-
> From: pve-devel-boun...@pve.proxmox.com [mailto:pve-devel-
> boun...@pve.proxmox.com] On Behalf Of Alexandre DERUMIER
> Sent: Dienstag, 04. September 2012 08:51
> To: Dietmar Maurer
> Cc: pve-devel@pve.proxmox.com
> Subject: Re: [pve-devel] lsi boot
>
> yes. It seem
This implement qemu guest agent client.
I Have take the qmp client code and try to adapt it.
We cannot pass id in the quest agent client,so I always execute
{ "execute": "guest-sync", "arguments": { "id": sequenceid } }
before each command
exemple:
sending commands
---
{ "execute":
14 matches
Mail list logo
