[PVE-User] Upgrade kernel

[Steffen Wagner]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Hi,

I have done this... its running fine so far (ofc except OVZ)...

# pveversion
pve-manager/3.4-1/3f2d890e (running kernel: 3.10.0-7-pve)

Regards,
Steffen

Am 28.02.2015 um 20:44 schrieb Yoandy Madrazo Gómez:
> Hi, it's possible upgrade the 2.6.32-37-pve kernel to the 3.10 version??
>
> I have this:
>
> proxmox-ve-2.6.32: 3.3-147 (running kernel: 2.6.32-37-pve)
> pve-manager: 3.4-1 (running version: 3.4-1/3f2d890e)
> pve-kernel-2.6.32-37-pve: 2.6.32-147
> lvm2: 2.02.98-pve4
> clvm: 2.02.98-pve4
> corosync-pve: 1.4.7-1
> openais-pve: 1.1.4-3
> libqb0: 0.11.1-2
> redhat-cluster-pve: 3.2.0-2
> resource-agents-pve: 3.9.2-4
> fence-agents-pve: 4.0.10-2
> pve-cluster: 3.0-15
> qemu-server: 3.3-20
> pve-firmware: 1.1-3
> libpve-common-perl: 3.0-24
> libpve-access-control: 3.0-16
> libpve-storage-perl: 3.0-31
> pve-libspice-server1: 0.12.4-3
> vncterm: 1.1-8
> vzctl: 4.0-1pve6
> vzprocps: 2.0.11-2
> vzquota: 3.1-2
> pve-qemu-kvm: 2.1-12
> ksm-control-daemon: 1.1-1
> glusterfs-client: 3.5.2-1
>
> Best Regard
>
>
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (MingW32)
 
iQEcBAEBAgAGBQJU8huqAAoJEIo0BvtGiO6ZCnQH/1/AvSMcZXuH0Os6tBRfrcsT
jF/pixwWKR9TCS5loJ3UslbOYToZ66bEinklZ40CBMjs29XxEhEtieK0/gv8AIy5
GamcF1NYjkahadBHmXzuZr6LYW9QeYx/l6EDKBa/3Iu+PWGcasGBO82qJ9SPk+Zb
SrMulvOIOq1buIc79DtTpNLuuU9PkClxtvdm8UjZ+xFWjx3eAvxNEMgPDQtzbZQ9
qo+LJmeA6MCL32bRI5aRRhCl18MFkqzm13tnhIvuiB3aTC8THI1+/9MEUBptD2af
USK0yyB1Ir0c6PLOXMbknjv2yNdR2Ba4NdJ3PGlUQmkS6xU1vyvpad+8Dvko6LM=
=sro2
-----END PGP SIGNATURE-----

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-user/attachments/20150228/600fe888/attachment.htm>