Michael Rasmussen writes:
> If you are talking about the iSCSI/LVM bug then a fix for this has been
> found and should come to a repo near you soon;-)
That would be great :-)
Cheers,
--Denys
___
pve-user mailing list
Mikhail writes:
> Can you share what's the problem with iSCSI in current 4.1 PVE? We're
> looking to install new cluster based on latest PVE, and we're going to
> rely on iSCSI in terms of storage.
The problem is you can't write to your SAN (if it uses SMR-HDDs, I
gathered).
On Thu, 25 Feb 2016 17:49:04 +0100
Denys Duchier wrote:
>
> due to the iSCSI bug in PVE 4.1, this is currently not a great option if
> you have one of the affected SANs (which we do).
>
If you are talking about the iSCSI/LVM bug then a fix for this has been
found
Martin Maurer writes:
> If you are still running on Proxmox VE 3.4, we recommend to move to the
> current
> Proxmox VE 4.x as soon as possible.
due to the iSCSI bug in PVE 4.1, this is currently not a great option if
you have one of the affected SANs (which we do).
Cheers,
They are also a bug in qemu-server
It's fixed in qemu-server 4.0-59
https://git.proxmox.com/?p=qemu-server.git;a=commit;h=d1363934b81c5336f59987a9f958f09fcc11d038
(need to be installed on source host)
- Mail original -
De: "Eneko Lacunza"
À: "proxmoxve"
Hi Thomas,
I just upgraded node1 and node4 to pve-qemu-kvm_2.5-7_amd64.deb in
pvetest but the issue remains. Shall I try some other package upgrade?
Maybe qemu-server?
Thanks
El 25/02/16 a las 13:01, Thomas Lamprecht escribió:
This should be fixed with pve-qemu-kvm 2.5-7
AFAIK it's
This should be fixed with pve-qemu-kvm 2.5-7
AFAIK it's available, at least, on pvetest.
cheers,
Thomas
On 02/25/2016 12:45 PM, Eneko Lacunza wrote:
> Hi all,
>
> I'm in the process of patching our office 4-node Proxmox cluster. It
> seems I'm unable to online migrate VMs between the newest
Hi all,
I'm in the process of patching our office 4-node Proxmox cluster. It
seems I'm unable to online migrate VMs between the newest PVE version
and our previous installed versions:
node1, node4: (updated nodes)
# pveversion -v
proxmox-ve: 4.1-37 (running kernel: 4.2.6-1-pve)
pve-manager: