Re: [pve-devel] Two-Node HA

FYI, there was support to use a quorum Disk in 3.X: https://pve.proxmox.com/wiki/Two-Node_High_Availability_Cluster But corosync developers decided to drop support for that. AFAIK this technology is a leftover from old days, and nobody was happy with that complex and error prone software. That

Re: [pve-devel] pve-manager and disk IO monitoring

> So my question is: Why use scsi-generic instead of scsi-block when > scsi-generic prevents blockstats? commit d454d040338a6216c8d3e5cc9623d6223476cb5a Author: Alexandre Derumier Date: Tue Aug 28 12:46:07 2012 +0200 use scsi-generic by default with libiscsi This

Re: [pve-devel] pve-manager and disk IO monitoring

"Running a fio test also only shows marginal performance difference between scsi-block and scsi-generic" I think that 11% difference is not so marginal. I'm curious to see difference with full flash array, if we have the same cpu iothread bottleneck like ceph, with scsi-block vs scsi-generic.

Re: [pve-devel] pve-manager and disk IO monitoring

On Thu, 29 Sep 2016 09:17:56 +0300 Dmitry Petuhov wrote: > It's side effect of scsi pass-through, which is being used by default for > [libi]scsi volumes with scsi VM disk interface. QEMU is just not aware of VM > block IO in that case. Also, cache settings for volumes

Re: [pve-devel] pve-manager and disk IO monitoring

On Thu, 29 Sep 2016 09:41:35 +0300 Dmitry Petuhov wrote: > In QemuServer.pm (some code omitted): > > if ($drive->{interface} eq 'scsi') > my $devicetype = 'hd'; > if($path =~ m/^iscsi\:\/\//){ > $devicetype = 'generic'; > } > $device =

Re: [pve-devel] student question about ha "restricted" option

> Maybe could we improve the documentation, and add some examples ? We are working on that since several months. People can also send patches ;-) BTW, do you know the HA simulator? ___ pve-devel mailing list pve-devel@pve.proxmox.com

Re: [pve-devel] [PATCH] Improvement for pve-installation

this patch make some changes, but it is not clear why exactly? There are some simple fixes, but also some bigger rewrites. Please can you split that into smaller patches, and add a reasonable commit message to each change? ___ pve-devel mailing list

Re: [pve-devel] pve-manager and disk IO monitoring

On Thu, 29 Sep 2016 07:38:09 +0200 (CEST) Alexandre DERUMIER wrote: > iostats are coming from qemu. > > what is the output of monitor "info blockstats" for the vm where you don't > have stats ? > > Two examples below: # info blockstats drive-ide2: rd_bytes=0 wr_bytes=0

Re: [pve-devel] Two-Node HA

Hi Andreas, On 09/28/2016 05:53 PM, Andreas Steinel wrote: Hi Thomas, Thank you for your time and your answer. I wonder why e.g. an Oracle Real Application Cluster (RAC) works so well with a 2 node in a HA setup. We deployed 50+ clusters in the last years and never had a split-brain-like

Re: [pve-devel] pve-manager and disk IO monitoring

29.09.2016 09:05, Michael Rasmussen wrote: On Thu, 29 Sep 2016 07:38:09 +0200 (CEST) Alexandre DERUMIER wrote: iostats are coming from qemu. what is the output of monitor "info blockstats" for the vm where you don't have stats ? Two examples below: # info blockstats

Re: [pve-devel] pve-manager and disk IO monitoring

29.09.2016 09:21, Michael Rasmussen пишет: On Thu, 29 Sep 2016 09:17:56 +0300 Dmitry Petuhov wrote: It's side effect of scsi pass-through, which is being used by default for [libi]scsi volumes with scsi VM disk interface. QEMU is just not aware of VM block IO in that

Re: [pve-devel] [PATCH v3 storage 0/4] improve SMART handling

applied ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH] ha-manager: add examples to group settings

Signed-off-by: Thomas Lamprecht --- This should help people to understand the settings better. ha-manager.adoc | 22 ++ 1 file changed, 22 insertions(+) diff --git a/ha-manager.adoc b/ha-manager.adoc index 4a9e81a..c7c65f4 100644 ---

Re: [pve-devel] Two-Node HA

Hello, another option for 2-Node HA would be what HA-Lizzard for XenServer does. Basically they test if some external ip`s (e.g. storage/switches) can be reached to ensure quorum/majority in the two-node setup. This is maybe not the best solution but way better than running into split-brain.

[pve-devel] backup suspend mode with guest agent enable : fsfreeze timeout

Hi, if we try to run backup in pause mode with guest agent, it seem that the fsfreeze qmp command is send after the suspend, so the guest agent is not responding. INFO: suspend vm INFO: snapshots found (not included into backup) INFO: creating archive

Re: [pve-devel] [PATCH v2 common] Network: add disable_ipv6 and use it

applied ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH v2 common] Network: add disable_ipv6 and use it

Many interfaces used to get an ipv6 link-local address which was usually unusable and therefore pointless. In order to ensure consistency this is called in various places: * $bridge_add_interface() and $ovs_bridge_add_port() because it's generally a good choice for bridge ports. * tap_create()

Re: [pve-devel] pve-manager and disk IO monitoring

On Fri, 30 Sep 2016 00:51:06 +0200 Michael Rasmussen wrote: > > So my question is: Why use scsi-generic instead of scsi-block when > scsi-generic prevents blockstats? > Running a fio test also only shows marginal performance difference between scsi-block and scsi-generic

Re: [pve-devel] pve-manager and disk IO monitoring

On Thu, 29 Sep 2016 07:38:09 +0200 (CEST) Alexandre DERUMIER wrote: > iostats are coming from qemu. > > what is the output of monitor "info blockstats" for the vm where you don't > have stats ? > I have just tested with replacing -device scsi-generic with -device