upgrade issue from 1.2 to 1.3

Cybodog · Jun 6, 2009

I had x64 Centos 5.3 kvm machines. I upgraded to 1.3 from 1.2 and now when I try to boot my kvms I get:

Your CPU does not support long mode. Use a 32bit distribution.

cat /proc/cpuinfo (only one core shown for clarity)

proxinternal01:~# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5405 @ 2.00GHz
stepping : 10
cpu MHz : 1999.999
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm
bogomips : 4003.23
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

So: What happened between 1.2 and 1.3 that made it impossible for me to boot my x64 Cenos 5.3 kvm? I did try to re-install the kvm OS (in the event the config was obsoleted in the upgrade) and the installer also reports my cpu does not support x64.

adis · Jun 8, 2009

Maybe it's a bug in KVM-86?
http://www.mail-archive.com/kvm@vger.kernel.org/msg16449.html

It seems there are issues with 64-bit guests. Can someone from proxmox team confirm that?

tom · Jun 8, 2009

Cybodog said:
I had x64 Centos 5.3 kvm machines. I upgraded to 1.3 from 1.2 and now when I try to boot my kvms I get:

Your CPU does not support long mode. Use a 32bit distribution.

cat /proc/cpuinfo (only one core shown for clarity)

proxinternal01:~# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5405 @ 2.00GHz
stepping : 10
cpu MHz : 1999.999
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm
bogomips : 4003.23
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

So: What happened between 1.2 and 1.3 that made it impossible for me to boot my x64 Cenos 5.3 kvm? I did try to re-install the kvm OS (in the event the config was obsoleted in the upgrade) and the installer also reports my cpu does not support x64.

how do you start the VM? (I mean via web interface or do you run something special - special command to start)

64-bit centos is running well here - Intel Xeon 32xx CPU´s.

Cybodog · Jun 8, 2009

tom said:
how do you start the VM? (I mean via web interface or do you run something special - special command to start)

64-bit centos is running well here - Intel Xeon 32xx CPU´s.

I use the "restart/start" function of proxmox web interface to start/restart my kvms.

Cybodog · Jun 8, 2009

adis said:
Maybe it's a bug in KVM-86?
http://www.mail-archive.com/kvm@vger.kernel.org/msg16449.html

It seems there are issues with 64-bit guests. Can someone from proxmox team confirm that?

Looking through those links I found this:

http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=commitdiff;h=8fa3b3ce6e

"KVM_GET_SUPPORTED_CPUID has been known to fail to return -E2BIG
when it runs out of entries. Detect this by always trying again
with a bigger table if the ioctl() fills the table.

diff --git a/kvm/libkvm/libkvm-x86.c b/kvm/libkvm/libkvm-x86.c

index a2f6320..4f9539a 100644 (file)

--- a/kvm/libkvm/libkvm-x86.c
+++ b/kvm/libkvm/libkvm-x86.c
@@ -575,6 +575,8 @@ static struct kvm_cpuid2 *try_get_cpuid(kvm_context_t kvm, int max)
r = ioctl(kvm->fd, KVM_GET_SUPPORTED_CPUID, cpuid);
if (r == -1)
r = -errno;
+ else if (r == 0 && cpuid->nent >= max)
+ r = -E2BIG;
if (r < 0) {
if (r == -E2BIG) {
free(cpuid);

End quote"

but I am to stupid to know how to apply the above. Apply the patch and recompile the kernel?

If that is the case:

1. Do we have the Proxmox source to do that?

2. Will Proxmox make a new kernel?

mandrake · Jun 8, 2009

I have the same problem with VM running on kvm, Debian Lenny 64bit, and Slamd 64,
the openvz containers have no problem

i have read http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=commitdiff;h=8fa3b3ce6e

but i dont understand how to apply the patch, can someone help me?

Thanks!

btw: sorry but i speak a little english

edit: it happends when updated 1.2 to 1.3, running on Core 2 Quad 9950 CPU

tom · Jun 8, 2009

can you post the output of 'pveversion - v'?

mandrake · Jun 8, 2009

tom said:
can you post the output of 'pveversion - v'?

Code:

vm:~# pveversion -v
pve-manager: 1.3-1 (pve-manager/1.3/4023)
qemu-server: 1.0-14
pve-kernel: 2.6.24-8
pve-kvm: 86-1
pve-firmware: 1
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.1-2
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1

Thanks!

tom · Jun 8, 2009

mandrake said:

Code:

vm:~# pveversion -v
pve-manager: 1.3-1 (pve-manager/1.3/4023)
qemu-server: 1.0-14
pve-kernel: 2.6.24-8
pve-kvm: 86-1
pve-firmware: 1
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.1-2
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1

Thanks!

I tried to reproduce the issue without success.

My win2008-64-bit and my centos-53-64-bit installed on Proxmox VE 1.2 worked without any problems after upgrading to V1.3 (just the network card reinstalled on windows)

what cpu do you have?

mandrake · Jun 8, 2009

tom said:
I tried to reproduce the issue without success.

My win2008-64-bit and my centos-53-64-bit installed on Proxmox VE 1.2 worked without any problems after upgrading to V1.3 (just the network card reinstalled on windows)

what cpu do you have?

its an intel core 2 quad 9550

Code:

vm:~# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz
stepping        : 10
cpu MHz         : 2833.501
cache size      : 6144 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov                                         pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant                                        _tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx smx est tm2 ssse3 cx1                                        6 xtpr sse4_1 lahf_lm
bogomips        : 6889.23
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz
stepping        : 10
cpu MHz         : 2833.501
cache size      : 6144 KB
physical id     : 0
siblings        : 4
core id         : 1
cpu cores       : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov                                         pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant                                        _tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx smx est tm2 ssse3 cx1                                        6 xtpr sse4_1 lahf_lm
bogomips        : 6884.98
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 2
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz
stepping        : 10
cpu MHz         : 2833.501
cache size      : 6144 KB
physical id     : 0
siblings        : 4
core id         : 2
cpu cores       : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov                                         pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant                                        _tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx smx est tm2 ssse3 cx1                                        6 xtpr sse4_1 lahf_lm
bogomips        : 6885.00
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 3
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz
stepping        : 10
cpu MHz         : 2833.501
cache size      : 6144 KB
physical id     : 0
siblings        : 4
core id         : 3
cpu cores       : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov                                         pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant                                        _tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx smx est tm2 ssse3 cx1                                        6 xtpr sse4_1 lahf_lm
bogomips        : 6885.00
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

i heard that this issue is on intel only, but dont know if is on an specific intel models

here's a screenshot:

mandrake · Jun 8, 2009

tom wich stepping is your cpu?

i think that is on the latests steppings the problem

tomorrow i will try to install a new fresh install proxmox 1.3 in other hd

rehar · Jun 9, 2009

Same problem here. I updated from 1.2 to 1.3 yesterday night, after that the 64Bit VMs doesn't want to start anymore.
They complain that the CPU has no 64Bit support!

CPU is a Intel Xeon E3110

Code:

 cat /proc/cpuinfo 
processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 23
model name    : Intel(R) Xeon(R) CPU           E3110  @ 3.00GHz
stepping    : 10
cpu MHz        : 2982.855
cache size    : 6144 KB
physical id    : 0
siblings    : 2
core id        : 0
cpu cores    : 2
fpu        : yes
fpu_exception    : yes
cpuid level    : 13
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr sse4_1 lahf_lm
bogomips    : 5969.52
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:

processor    : 1
vendor_id    : GenuineIntel
cpu family    : 6
model        : 23
model name    : Intel(R) Xeon(R) CPU           E3110  @ 3.00GHz
stepping    : 10
cpu MHz        : 2982.855
cache size    : 6144 KB
physical id    : 0
siblings    : 2
core id        : 1
cpu cores    : 2
fpu        : yes
fpu_exception    : yes
cpuid level    : 13
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr sse4_1 lahf_lm
bogomips    : 5965.74
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:

dietmar · Jun 9, 2009

Please can you test the updated version:

Code:

wget ftp://pve.proxmox.com/debian/dists/lenny/pvetest/binary-amd64/pve-kvm_86-2_amd64.deb
dpkg -i pve-kvm_86-2_amd64.deb

mandrake · Jun 9, 2009

dietmar said:
Please can you test the updated version:

Code:

wget ftp://pve.proxmox.com/debian/dists/lenny/pvetest/binary-amd64/pve-kvm_86-2_amd64.deb dpkg -i pve-kvm_86-2_amd64.deb

It fixed the problem!! thank you so much!!

rehar · Jun 9, 2009

It really does fix the problem.
Thanks for the quick fix.

Rene

Cybodog · Jun 9, 2009

dietmar said:
Please can you test the updated version:

Code:

wget ftp://pve.proxmox.com/debian/dists/lenny/pvetest/binary-amd64/pve-kvm_86-2_amd64.deb dpkg -i pve-kvm_86-2_amd64.deb

Confirmed, fixes the problems here. Thanks.

Albrecht · Jun 11, 2009

I have the same problem with a new installation of proxmox 1.3. It would be great if a fix could be made available.
Thanks

Cybodog · Jun 11, 2009

Albrecht said:
I have the same problem with a new installation of proxmox 1.3. It would be great if a fix could be made available.
Thanks

See the entry just above yours:

wget ftp://pve.proxmox.com/debian/dists/lenny/pvetest/binary-amd64/pve-kvm_86-2_amd64.deb
dpkg -i pve-kvm_86-2_amd64.deb

dietmar · Jun 11, 2009

I already uploaded the fix into the standard repositories. Just update your system with 'apt-get'.

# apt-get update
# apt-get upgrade

Cybodog · Jun 11, 2009

dietmar said:
I already uploaded the fix into the standard repositories. Just update your system with 'apt-get'.

# apt-get update
# apt-get upgrade

Good work! Thanks!

upgrade issue from 1.2 to 1.3

New Member

New Member

Proxmox Staff Member

New Member

New Member

mandrake

Guest

Proxmox Staff Member

mandrake

Guest

Proxmox Staff Member

mandrake

Guest

mandrake

Guest

New Member

Proxmox Staff Member

mandrake

Guest

New Member

New Member

New Member

New Member

Proxmox Staff Member

New Member