Hi,
i need to understand what is causing troubles on a kvm that works on 2.6.18 but fails with blue screen on 2.6.32. it is nt4server. ok i know it's old, but i need to run this for a transition step, then it will go.
meanwhile, i wish to understand how kvm is configured here.
it is my testing machine, standard lenny + proxmox . i've always run the base kernel 2.6.18, but recently installed higher kernels, and was running 2.6.32 when discovered that the nt4 kvm wouldn't boot anymore. after struggling a bit, decided to revert to the old kernel 2.6.18 and there nt4 boots perfectly.
here is pveversion -v
dadmin@debian:~$ pveversion -v
pve-manager: 1.5-10 (pve-manager/1.5/4822)
running kernel: 2.6.18-2-pve
proxmox-ve-2.6.32: 1.5-7
pve-kernel-2.6.18-1-pve: 2.6.18-4
pve-kernel-2.6.32-2-pve: 2.6.32-7
pve-kernel-2.6.24-11-pve: 2.6.24-23
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-16
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.4-1
ksm-control-daemon: 1.0-3
i'm i but puzzled because on production server, standard pve 1.5 with only 2.6.18 installed, where the nt4 vm is going to end, has
proxmox1:~# pveversion -v
pve-manager: 1.5-10 (pve-manager/1.5/4822)
running kernel: 2.6.18-2-pve
proxmox-ve-2.6.18: 1.5-5
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-16
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-5
so i see that the test machine has
running kernel: 2.6.18-2-pve and
pve-qemu-kvm: 0.12.4-1
and the prod pve has
running kernel: 2.6.18-2-pve
pve-qemu-kvm-2.6.18: 0.9.1-5
... am i doing something wrong?
what could cause that nt4 to fail on 2.6.32 kernel? i thought of a newer kvm, but it appears, as i understand it, that also 2.618 is now running 0.12.4-1 (test machine)... so.. what should i test to run that nt4?
Marco
i need to understand what is causing troubles on a kvm that works on 2.6.18 but fails with blue screen on 2.6.32. it is nt4server. ok i know it's old, but i need to run this for a transition step, then it will go.
meanwhile, i wish to understand how kvm is configured here.
it is my testing machine, standard lenny + proxmox . i've always run the base kernel 2.6.18, but recently installed higher kernels, and was running 2.6.32 when discovered that the nt4 kvm wouldn't boot anymore. after struggling a bit, decided to revert to the old kernel 2.6.18 and there nt4 boots perfectly.
here is pveversion -v
dadmin@debian:~$ pveversion -v
pve-manager: 1.5-10 (pve-manager/1.5/4822)
running kernel: 2.6.18-2-pve
proxmox-ve-2.6.32: 1.5-7
pve-kernel-2.6.18-1-pve: 2.6.18-4
pve-kernel-2.6.32-2-pve: 2.6.32-7
pve-kernel-2.6.24-11-pve: 2.6.24-23
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-16
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.4-1
ksm-control-daemon: 1.0-3
i'm i but puzzled because on production server, standard pve 1.5 with only 2.6.18 installed, where the nt4 vm is going to end, has
proxmox1:~# pveversion -v
pve-manager: 1.5-10 (pve-manager/1.5/4822)
running kernel: 2.6.18-2-pve
proxmox-ve-2.6.18: 1.5-5
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-16
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-5
so i see that the test machine has
running kernel: 2.6.18-2-pve and
pve-qemu-kvm: 0.12.4-1
and the prod pve has
running kernel: 2.6.18-2-pve
pve-qemu-kvm-2.6.18: 0.9.1-5
... am i doing something wrong?
what could cause that nt4 to fail on 2.6.32 kernel? i thought of a newer kvm, but it appears, as i understand it, that also 2.618 is now running 0.12.4-1 (test machine)... so.. what should i test to run that nt4?
Marco
Last edited: