[PVE-User] DAS Storage

[Gilberto Nunes]

Hi

Is there PVE support to DAS Storage. like Dell PowerVault MD1200??


Thanks
--
--
"A única forma de chegar ao impossível, é acreditar que é possível."
Lewis Carroll - Alice no País das Maravilhas

""*The only way* to achieve *the impossible is to believe* it is *possible*
."
Lewis Carroll - Alice in Wonderland

Gilberto Ferreira
(47) 9676-7530

[Benjamin Redling]

Hi,

Post by Gilberto Nunes
Is there PVE support to DAS Storage. like Dell PowerVault MD1200??

What do you aim for?
Since when does direct attached storage need extra support?
Where is the difference to a local disc/device?

(The FC-SAN I managed were DAS-RAIDs before. Apart from a fabric nothing
was added.)

/BR

[Gilberto Nunes]

Thanks

Post by Benjamin Redling
Hi,

Post by Gilberto Nunes
Is there PVE support to DAS Storage. like Dell PowerVault MD1200??

What do you aim for?
Since when does direct attached storage need extra support?
Where is the difference to a local disc/device?
(The FC-SAN I managed were DAS-RAIDs before. Apart from a fabric nothing
was added.)
/BR
_______________________________________________
pve-user mailing list
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

--
--
"A única forma de chegar ao impossível, é acreditar que é possível."
Lewis Carroll - Alice no País das Maravilhas

""*The only way* to achieve *the impossible is to believe* it is *possible*
."
Lewis Carroll - Alice in Wonderland

Gilberto Ferreira
(47) 9676-7530

[Holger Hampel | RA Consulting]

Hello,

After the last no-supscription update all VM's and CT's lost IPv6 connectivity:

- Ubuntu 8.04 / virtio
- Win2003 / E1000 (virtio lost IPv6 connectivity several months ago)

The CT's are pingable from the host, but not from the network.

On another system I hold back "proxmox-ve-2.6.32 pve-manager pve-qemu-kvm" - there IPv6 seems to work normal.

As workaround I booted the old kernel 2.6.32-34-pve.

Similar experience? Solution (beside migration to the subscription machines)?

From the trouble with virtio 0.1.81 in Win2003: the cause seemed to be the neighbour discovery, which stuck.

Regards

Holger Hampel

----------------------------------------------------
RA Consulting GmbH
Zeiloch 6a
D-76646 Bruchsal
Tel: [phone] / 38 62 - 25
Fax: [phone] / 38 62 - 11
E-Mail: <mailto:***@rac.de>
Web: www.rac.de
Sitz der Gesellschaft: Bruchsal
Amtsgericht Mannheim HRB 231127
Geschäftsführer: Armin Rupalla, Andreas Hege, Heiko Bauer
---------------------------------------------------
ORACLE Partner
---------------------------------------------------
DIN EN ISO 9001:2000 zertifiziert

[Laurent CARON]

Hi,

I'm experiencing the very same issue. Seems not lots of people is using
IPv6 with Proxmox.

It seems to be described here:
http://patchwork.ozlabs.org/patch/326048/
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310586

As a workaround I used this:

echo 0 > /sys/class/net/vmbrXX/bridge/multicast_snooping

Cheers,

Laurent

[Dietmar Maurer]

Please test with latest kernel from pvetest:

http://download1.proxmox.com/debian/dists/wheezy/pvetest/binary-amd64/proxmox-ve-2.6.32_3.4-148_all.deb

Post by Laurent CARON
Hi,
I'm experiencing the very same issue. Seems not lots of people is using
IPv6 with Proxmox.
http://patchwork.ozlabs.org/patch/326048/
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310586
echo 0 > /sys/class/net/vmbrXX/bridge/multicast_snooping

[Laurent CARON]

Even though this is a production boix, I can install the pvetest kernel ?

Thanks

Post by Dietmar Maurer
http://download1.proxmox.com/debian/dists/wheezy/pvetest/binary-amd64/proxmox-ve-2.6.32_3.4-148_all.deb

Post by Laurent CARON
Hi,
I'm experiencing the very same issue. Seems not lots of people is using
IPv6 with Proxmox.
http://patchwork.ozlabs.org/patch/326048/
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310586
echo 0 > /sys/class/net/vmbrXX/bridge/multicast_snooping

!DSPAM:54f4230e8491540912099!

[Dietmar Maurer]

Post by Laurent CARON
Even though this is a production boix, I can install the pvetest kernel ?

That is up to you. I general, it is better to test on non-production systems
first.

[Steffen Wagner]

Hi Dietmar,

it may be the same on 3.10.X kernel, is it?

Regards,
Steffen

Post by Dietmar Maurer
http://download1.proxmox.com/debian/dists/wheezy/pvetest/binary-amd64/proxmox-ve-2.6.32_3.4-148_all.deb

Post by Laurent CARON
Hi,
I'm experiencing the very same issue. Seems not lots of people is using
IPv6 with Proxmox.
http://patchwork.ozlabs.org/patch/326048/
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310586
echo 0 > /sys/class/net/vmbrXX/bridge/multicast_snooping

_______________________________________________
pve-user mailing list
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

[Holger Hampel | RA Consulting]

Hello,

I tested the new kernel. Some VMs seemed to have IPv6 connectivity (e1000). On one (linux,virtio) I had incoming connectivity after pinging the requesting system from the VM. CTs have no IPv6 connectivity.

On our cluster I switched back (rebooted) to kernel 2.6.32-34 (replacing -37 with -34 in /boot/grub/grub.cfg) and one node I upgraded to kernel 3.10. Both configuration give me IPv6.

Regards
Holger Hampel

-----Ursprüngliche Nachricht-----
Von: pve-user [mailto:pve-user-***@pve.proxmox.com] Im Auftrag von Dietmar Maurer
Gesendet: Montag, 2. März 2015 09:34
An: pve-***@pve.proxmox.com; Laurent CARON
Betreff: Re: [PVE-User] IPv6 issues after last update

Please test with latest kernel from pvetest:

http://download1.proxmox.com/debian/dists/wheezy/pvetest/binary-amd64/proxmox-ve-2.6.32_3.4-148_all.deb

Post by Laurent CARON
Hi,
I'm experiencing the very same issue. Seems not lots of people is using
IPv6 with Proxmox.
http://patchwork.ozlabs.org/patch/326048/
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310586
echo 0 > /sys/class/net/vmbrXX/bridge/multicast_snooping

[Sten Aus]

Hi

Same bug here, went back to 2.6.32-34-pve and everything working
smoothly with IPv6.

Post by Holger Hampel | RA Consulting
Hello,
I tested the new kernel. Some VMs seemed to have IPv6 connectivity (e1000). On one (linux,virtio) I had incoming connectivity after pinging the requesting system from the VM. CTs have no IPv6 connectivity.
On our cluster I switched back (rebooted) to kernel 2.6.32-34 (replacing -37 with -34 in /boot/grub/grub.cfg) and one node I upgraded to kernel 3.10. Both configuration give me IPv6.
Regards
Holger Hampel
-----Ursprüngliche Nachricht-----
Gesendet: Montag, 2. März 2015 09:34
Betreff: Re: [PVE-User] IPv6 issues after last update
http://download1.proxmox.com/debian/dists/wheezy/pvetest/binary-amd64/proxmox-ve-2.6.32_3.4-148_all.deb

Post by Laurent CARON
Hi,
I'm experiencing the very same issue. Seems not lots of people is using
IPv6 with Proxmox.
http://patchwork.ozlabs.org/patch/326048/
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310586
echo 0 > /sys/class/net/vmbrXX/bridge/multicast_snooping

_______________________________________________
pve-user mailing list
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________
pve-user mailing list
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user