> So right now the only way to get a consistent backup is to use stop mode?
I use modern software, so I get consistent backups in snapshot mode too.
Note: Every FS and DB I use supports transaction.
But we also improved 'stop' mode. I just stops, then immediately restarts the
VM.
So you can us
I agree.
All networking measurements are in bits/s Megabits, Kilobits
Having Proxmox's in MB/s is inconsistent with the way the rest of the
industry measures network bandwidth.
Regards,
Andrew
On 2/17/2013 8:13 PM, Stefan Priebe - Profihost AG wrote:
Right but people are u
tested with raw,qcow2,rbd,sheepdog
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Signed-off-by: Alexandre Derumier
---
PVE/VZDump/QemuServer.pm |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/PVE/VZDump/QemuServer.pm b/PVE/VZDump/QemuServer.pm
index ad85cc2..69130d7 100644
--- a/PVE/VZDump/QemuServer.pm
+++ b/PVE/VZDump/QemuServer.pm
@@ -94,9 +
> All networking measurements are in bits/s Megabits, Kilobits
>
> Having Proxmox's in MB/s is inconsistent with the way the rest of the
> industry measures network bandwidth.
But 'tc' limits transferred bytes, not physically transferred bits.
__
> > All networking measurements are in bits/s Megabits, Kilobits
> >
> > Having Proxmox's in MB/s is inconsistent with the way the rest of the
> > industry measures network bandwidth.
Besides, is there any other reason why 'Bits' are better that 'Bytes'?
I already updated our git to include the new qemu 1.4 code.
>From the changelog:
> * usb: usb-tablet can be connected as an USB 2.0 device, lowering the CPU
> usage substantially
Any idea who we can use that?
___
pve-devel mailing list
pve-devel@pve
> Right but people are used to use Mbit/s for everything network related. So I
> think a lot of people who want to use it will use it incorrect.
Maybe It would be nice to have an extjs widget where we can select the unit?
___
pve-devel mailing list
pve-
>>Any idea who we can use that?
Simply connect the usb-tablet to ehci controller ?
Maybe is it time to use ehci by default ? (It's migratable now).
And seem that is use lower cpu (maybe less interrupts ?)
the qemu git commit is here :
http://git.qemu.org/?p=qemu.git;a=commit;h=427e3aa151c74922
I had tried to connect usb-tablet on ehci,
with 2003/2008 && debian guests, I have around 2% lower cpu on my old xeon.
Which is good, with a lot of vms, that can be an huge benefit.
I have also tried live migration of ehci, it's works perfectly now.
So maybe can we switch to full usb2 ? (I think
usb2.0 as default + usb-tablet hotplug/unplug
- This add ehci as default usb controller. (always activated)
- Full usb2 withtout usb1 compagnon (Don't need anymore the external usb.cfg)
as we don't need usb1 anymore
- hotplug/unplug usb-tablet on console task start/stop.
tablet config:
tablet
- This add ehci as default usb controller. (always activated)
- Full usb2 withtout usb1 compagnon (Don't need anymore the external usb.cfg)
as we don't need usb1 anymore
- hotplug/unplug usb-tablet on console task start/stop.
tablet config:
tablet:0 no tablet
tablet:1 always tablet
no confi
I have just send a patch to enable usb2 as default and hotplug/unplug
usb-tablet on demand on console open.
- Mail original -
De: "Alexandre DERUMIER"
À: "Dietmar Maurer"
Cc: pve-devel@pve.proxmox.com
Envoyé: Lundi 18 Février 2013 05:20:02
Objet: Re: [pve-devel] qemu 1.4 and usb
applied, thanks
> -Original Message-
> From: pve-devel-boun...@pve.proxmox.com [mailto:pve-devel-
> boun...@pve.proxmox.com] On Behalf Of Alexandre Derumier
> Sent: Samstag, 16. Februar 2013 08:53
> To: pve-devel@pve.proxmox.com
> Subject: [pve-devel] [PATCH] template_create : check has_fe
applied, thanks.
> -Original Message-
> From: pve-devel-boun...@pve.proxmox.com [mailto:pve-devel-
> boun...@pve.proxmox.com] On Behalf Of Alexandre Derumier
> Sent: Samstag, 16. Februar 2013 17:24
> To: pve-devel@pve.proxmox.com
> Subject: [pve-devel] [PATCH] rbd : rework pool - username
> - die "no such volume '$volid'\n" if ! -e $path;
> + if (! -e $path){
> + my $dl = PVE::Storage::vdisk_list($self->{storecfg}, $storeid,
> undef);
> + my $foundvolid = undef;
> +
> + PVE::Storage::foreach_volid($dl, sub {
> + my ($volumeid) = @_;
> +
> But this does not raise an exception if the volume does not exists? Maybe we
> want:
Ignore me (locke at the wrong patch).
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied, thanks.
> -Original Message-
> From: pve-devel-boun...@pve.proxmox.com [mailto:pve-devel-
> boun...@pve.proxmox.com] On Behalf Of Alexandre Derumier
> Sent: Sonntag, 17. Februar 2013 11:02
> To: pve-devel@pve.proxmox.com
> Subject: [pve-devel] [PATCH] vzdump : check if volid exist
> - hotplug/unplug usb-tablet on console task start/stop.
This will not work - please can you remove that?
Note: There can be multiple open consoles.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/
see inline comments:
> --- a/PVE/API2/Qemu.pm
> +++ b/PVE/API2/Qemu.pm
> @@ -1100,8 +1100,13 @@ __PACKAGE__->register_method({
> # also redirect stderr (else we get RFB protocol errors)
> my $cmd = ['/bin/nc', '-l', '-p', $port, '-w', $timeout, '-c',
> "$qmstr
> 2>/dev/null"];
> - Full usb2 withtout usb1 compagnon (Don't need anymore the external
> usb.cfg) as we don't need usb1 anymore
OK, we really do not need them? What if someone tries to pass-through an usb1
device?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
h
oh, you are right, I'll make the patch
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre Derumier" , pve-devel@pve.proxmox.com
Envoyé: Lundi 18 Février 2013 06:40:32
Objet: RE: [pve-devel] [PATCH] vzdump : fix check if volid exist for "virtual"
storage : rbd, sheepdog, nexenta
no, wait.
I have use your old patch! The new one you sent is OK.
> -Original Message-
> From: Alexandre DERUMIER [mailto:aderum...@odiso.com]
> Sent: Montag, 18. Februar 2013 07:31
> To: Dietmar Maurer
> Cc: pve-devel@pve.proxmox.com
> Subject: Re: [pve-devel] [PATCH] vzdump : fix check i
mmm,I'm not sure about it.
Currently:
if ($d->{vendorid} && $d->{productid}) {
push @$devices, '-device',
"usb-host,vendorid=0x$d->{vendorid},productid=0x$d->{productid}";
} elsif (defined($d->{hostbus}) && defined($d->{hostport})) {
push @$devices, '-device',
"
> -Original Message-
> From: pve-devel-boun...@pve.proxmox.com [mailto:pve-devel-
> boun...@pve.proxmox.com] On Behalf Of Dietmar Maurer
> Sent: Montag, 18. Februar 2013 07:24
> To: Alexandre Derumier; pve-devel@pve.proxmox.com
> Subject: Re: [pve-devel] [PATCH] usb2.0 as default + usb-ta
oh yes, indeed ;)
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER"
Cc: pve-devel@pve.proxmox.com
Envoyé: Lundi 18 Février 2013 07:31:39
Objet: RE: [pve-devel] [PATCH] vzdump : fix check if volid exist for "virtual"
storage : rbd, sheepdog, nexenta
no, wait.
I ha
> so If we passthrough an usb1 device, does it goes on ehci or uhci compagnon
> controller ?
I guess to the uhci controller.
> It'll make sense we can passthrough an usb1 device on an usb2 controller.
> (like with real hardware)
Is there any need to remove the emulated uhci controllers? I guess
>>I guess to the uhci controller.
Yes, after reading the doc, it's going to uhci controller is usb1.
As we use only ehci.0 bus, it's plugged on this bus, but goes to the companion
uhci.
>>Is there any need to remove the emulated uhci controllers? I guess they do
>>not need and
>>resources if
> Any objection to always activate ehci by default ?
> Like this we can hotplug/unplug tablet.
>
>
> I can remake the patch if you agree.
Yes, please remake the patch.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/
29 matches
Mail list logo
