New kernel release (pvetest repository) with kvm-kmod-2.6.31.6

tom

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
15,887
1,109
273
Hi all,

We just uploaded a new kernel (pve-kernel-2.6.24-9-pve_2.6.24-17) to the pvetest repository.

Release notes:

  • update kvm to kvm-kmod-2.6.31.6.tar.bz2
  • update e1000e to e1000e-1.0.15.tar.gz
  • kernel security fixes
in order to use this kernel, you need to change your sources.list:

Code: 
# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian lenny pvetest
everybody experiences problems with kvm is asked to test this kernel.
 
Last edited:
BiagioParuolo said:
Is stable for production system?
Click to expand...

pvetest repository is for testing. pve repository is for production.

this kernel is tested here in our labs, lets see if it also works for others.

as soon as we think its stable enough, we will move it to the pve repository.
 
Command for update (after changed the source.list to use the pvetest repository):

apt-get update

and

apt-get dist-upgrade

Are ok?
 
Last edited by a moderator:
BiagioParuolo said:
Command for update (after changed the source.list to use the pvetest repository):

apt-get update

and

apt-get dist-upgrade

Are ok?
Click to expand...

yes. and reboot.
 
Hrm - I've changed the sources.list line, and run update/upgrade/dist-upgrade - but apt-get doesn't see any new packages.

This is on a fully updated 1.4 install...

vmserver:~# pveversion
pve-manager/1.4/4403
vmserver:~# uname -r
2.6.24-8-pve
 
obrienmd said:
Hrm - I've changed the sources.list line, and run update/upgrade/dist-upgrade - but apt-get doesn't see any new packages.

This is on a fully updated 1.4 install...

vmserver:~# pveversion
pve-manager/1.4/4403
vmserver:~# uname -r
2.6.24-8-pve
Click to expand...

run the following:

Code: 
apt-get install pve-kernel-2.6.24-9-pve

and reboot.
 
Just updated and getting some nasty errors on kvm startups..

Code: 
Unable to handle kernel NULL pointer dereference at 000000000000001a RIP:
 [<ffffffff88419906>] :kvm_amd:svm_get_msr+0x146/0x300
PGD 119928067 PUD 119929067 PMD 0
Oops: 0002 [1] PREEMPT SMP
CPU: 2
Modules linked in: kvm_amd kvm vzethdev vznetdev simfs vzrst vzcpt tun vzdquota vzmon vzdev xt_tcpudp xt_length ipt_ttl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit ipt_tos ipt_REJECT ip_tables x_tables ipv6 ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi scsi_transport_iscsi bridge psmouse r8169 pcspkr serio_raw mii evdev sg scsi_wait_scan virtio_blk virtio dm_mod usbhid hid usb_storage libusual sd_mod sr_mod ide_disk ide_generic ide_cd cdrom shpchp pci_hotplug ahci ehci_hcd i2c_piix4 i2c_core atiixp ide_core pata_atiixp pata_acpi ata_generic libata scsi_mod ohci_hcd usbcore ssb isofs msdos fat
Pid: 3230, comm: kvm Not tainted 2.6.24-9-pve #1 ovz005
RIP: 0010:[<ffffffff88419906>]  [<ffffffff88419906>] :kvm_amd:svm_get_msr+0x146/0x300
RSP: 0018:ffff81011451fd80  EFLAGS: 00010286
RAX: ffffffffcd3a609a RBX: ffffc2000222d040 RCX: ffffffff9a1dec07
RDX: 000000000000001a RSI: 0000000000000010 RDI: ffff81011a860000
RBP: 0000000000000004 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: ffffffff884197c0 R12: ffff81011a860000
R13: ffffffff883e5d30 R14: 0000000000000001 R15: 00000000000000a0
FS:  0000000040d40950(0063) GS:ffff81011b402c00(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000000001a CR3: 0000000119925000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process kvm (pid: 3230, veid=0, threadinfo ffff81011451e000, task ffff81011a8df1c0)
Stack:  ffffffff883e9e79 ffff8101199b0200 0000000000f96ef8 ffffc2000222d000
 000000a0806ea690 00007fd80000000a 0000000000000000 0000000000000000
 fffffffffffffffb 0000000000000000 0000000000f96ef0 ffff81011a860000
Call Trace:
 [<ffffffff883e9e79>] :kvm:msr_io+0x119/0x170
 [<ffffffff883ea261>] :kvm:kvm_arch_vcpu_ioctl+0x391/0x610
 [<ffffffff883e5e1e>] :kvm:kvm_arch_vcpu_put+0xe/0x40
 [<ffffffff883e5562>] :kvm:vcpu_put+0x22/0x60
 [<ffffffff883e2525>] :kvm:kvm_vcpu_ioctl+0x145/0x5b0
 [<ffffffff802e18cf>] do_ioctl+0x2f/0xb0
 [<ffffffff802e1bdb>] vfs_ioctl+0x28b/0x300
 [<ffffffff802d2f29>] vfs_read+0x129/0x180
 [<ffffffff802e1c99>] sys_ioctl+0x49/0x80
 [<ffffffff8020c69e>] system_call+0x7e/0x83


Code: 48 89 02 eb 95 0f 1f 44 00 00 48 8b 87 e0 27 00 00 48 8b 80
RIP  [<ffffffff88419906>] :kvm_amd:svm_get_msr+0x146/0x300
 RSP <ffff81011451fd80>
CR2: 000000000000001a
---[ end trace 571ced9c8f0ff481 ]---
Unable to handle kernel NULL pointer dereference at 000000000000001a RIP:
 [<ffffffff88419906>] :kvm_amd:svm_get_msr+0x146/0x300
PGD 117cf0067 PUD 117cf1067 PMD 0
Oops: 0002 [2] PREEMPT SMP
CPU: 3
Modules linked in: kvm_amd kvm vzethdev vznetdev simfs vzrst vzcpt tun vzdquota vzmon vzdev xt_tcpudp xt_length ipt_ttl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit ipt_tos ipt_REJECT ip_tables x_tables ipv6 ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi scsi_transport_iscsi bridge psmouse r8169 pcspkr serio_raw mii evdev sg scsi_wait_scan virtio_blk virtio dm_mod usbhid hid usb_storage libusual sd_mod sr_mod ide_disk ide_generic ide_cd cdrom shpchp pci_hotplug ahci ehci_hcd i2c_piix4 i2c_core atiixp ide_core pata_atiixp pata_acpi ata_generic libata scsi_mod ohci_hcd usbcore ssb isofs msdos fat
Pid: 3198, comm: kvm Tainted:  G      D 2.6.24-9-pve #1 ovz005
RIP: 0010:[<ffffffff88419906>]  [<ffffffff88419906>] :kvm_amd:svm_get_msr+0x146/0x300
RSP: 0018:ffff810114509d90  EFLAGS: 00010017
RAX: 000000007ad75a77 RBX: ffff81011400c058 RCX: fffffffff42fdc1d
RDX: 000000000000001a RSI: 0000000000000010 RDI: ffff81011400c000
RBP: ffff81011400c000 R08: ffff810000000000 R09: 0000000000000000
R10: 0000000000000000 R11: ffffffff88419ac0 R12: 0000000000000246
R13: ffff8101145e1000 R14: 0000000000000000 R15: ffff81011400d6c0
FS:  00000000423a2950(0063) GS:ffff81011b402f80(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000000001a CR3: 0000000117cef000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process kvm (pid: 3198, veid=0, threadinfo ffff810114508000, task ffff8101150d71c0)
Stack:  ffffffff883eb369 0000000000ba1000 ffffffff806ea690 0000000000000000
 0000000000000000 0000000000000000 0000000000000000 0000000000000400
 00000000ffff0ff0 ffff81011400c1a0 ffff81011400ca40 ffff81011400cc40
Call Trace:
 [<ffffffff883eb369>] :kvm:kvm_arch_vcpu_ioctl_run+0x559/0xd20
 [<ffffffff883e26db>] :kvm:kvm_vcpu_ioctl+0x2fb/0x5b0
 [<ffffffff80233dca>] set_next_entity+0x3a/0x80
 [<ffffffff8020ac9f>] __switch_to+0x1df/0x320
 [<ffffffff8023c9c8>] finish_task_switch+0x28/0xc0
 [<ffffffff802e18cf>] do_ioctl+0x2f/0xb0
 [<ffffffff802e1bdb>] vfs_ioctl+0x28b/0x300
 [<ffffffff802d3539>] generic_file_llseek+0x69/0xd0
 [<ffffffff802e1c99>] sys_ioctl+0x49/0x80
 [<ffffffff8020c69e>] system_call+0x7e/0x83


Code: 48 89 02 eb 95 0f 1f 44 00 00 48 8b 87 e0 27 00 00 48 8b 80
RIP  [<ffffffff88419906>] :kvm_amd:svm_get_msr+0x146/0x300
 RSP <ffff810114509d90>
CR2: 000000000000001a
---[ end trace 571ced9c8f0ff481 ]---
vmtab102i0: no IPv6 routers present
vmtab101i0: no IPv6 routers present
vmtab103i0: no IPv6 routers present
Unable to handle kernel NULL pointer dereference at 000000000000001b RIP:
 [<ffffffff88419906>] :kvm_amd:svm_get_msr+0x146/0x300
PGD 1145e7067 PUD 1145e8067 PMD 0
Oops: 0002 [3] PREEMPT SMP
CPU: 3
Modules linked in: kvm_amd kvm vzethdev vznetdev simfs vzrst vzcpt tun vzdquota vzmon vzdev xt_tcpudp xt_length ipt_ttl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit ipt_tos ipt_REJECT ip_tables x_tables ipv6 ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi scsi_transport_iscsi bridge psmouse r8169 pcspkr serio_raw mii evdev sg scsi_wait_scan virtio_blk virtio dm_mod usbhid hid usb_storage libusual sd_mod sr_mod ide_disk ide_generic ide_cd cdrom shpchp pci_hotplug ahci ehci_hcd i2c_piix4 i2c_core atiixp ide_core pata_atiixp pata_acpi ata_generic libata scsi_mod ohci_hcd usbcore ssb isofs msdos fat
Pid: 3215, comm: kvm Tainted:  G      D 2.6.24-9-pve #1 ovz005
RIP: 0010:[<ffffffff88419906>]  [<ffffffff88419906>] :kvm_amd:svm_get_msr+0x146/0x300
RSP: 0018:ffff81011a87fd80  EFLAGS: 00010207
RAX: 000000008735b88d RBX: ffffc2000222f040 RCX: ffffffffdfc46802
RDX: 000000000000001b RSI: 0000000000000010 RDI: ffff81011a850000
RBP: 0000000000000004 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: ffffffff884197c0 R12: ffff81011a850000
R13: ffffffff883e5d30 R14: 0000000000000001 R15: 00000000000000a0
FS:  000000004085b950(0063) GS:ffff81011b402f80(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000000001b CR3: 00000001145e6000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process kvm (pid: 3215, veid=0, threadinfo ffff81011a87e000, task ffff81011a8c68e0)
Stack:  ffffffff883e9e79 ffff81011a422900 0000000001085d18 ffffc2000222f000
 000000a0806ea690 00007f550000000a 0000000000000000 0000000000000000
 fffffffffffffffb 0000000000000000 0000000001085d10 ffff81011a850000
Call Trace:
 [<ffffffff883e9e79>] :kvm:msr_io+0x119/0x170
 [<ffffffff883ea261>] :kvm:kvm_arch_vcpu_ioctl+0x391/0x610
 [<ffffffff883e5e1e>] :kvm:kvm_arch_vcpu_put+0xe/0x40
 [<ffffffff883e5562>] :kvm:vcpu_put+0x22/0x60
 [<ffffffff883e2525>] :kvm:kvm_vcpu_ioctl+0x145/0x5b0
 [<ffffffff804cbb76>] do_page_fault+0x176/0x890
 [<ffffffff802e18cf>] do_ioctl+0x2f/0xb0
 [<ffffffff802e1bdb>] vfs_ioctl+0x28b/0x300
 [<ffffffff802d2a5c>] vfs_write+0x12c/0x190
 [<ffffffff802e1c99>] sys_ioctl+0x49/0x80
 [<ffffffff8020c69e>] system_call+0x7e/0x83


Code: 48 89 02 eb 95 0f 1f 44 00 00 48 8b 87 e0 27 00 00 48 8b 80
RIP  [<ffffffff88419906>] :kvm_amd:svm_get_msr+0x146/0x300
 RSP <ffff81011a87fd80>
CR2: 000000000000001b
---[ end trace 571ced9c8f0ff481 ]---
Going to revert back to 2.4.26-8 for now, everything goes back to stable.

CPU is a AMD Athlon II 620, any ideas?
 
Last edited:
Hi,
i test also the new kernel on a new server.
After upgrade to 2.6.24-9 i got an kernel-oops in the terminal if i start a new vm (perhaps is something wrong with the vm, it's a converted vmwareimage).

Code: 
Message from syslogd@bigproxmox at Nov 14 21:17:59 ...
 kernel:Oops: 0002 [1] PREEMPT SMP 

Message from syslogd@bigproxmox at Nov 14 21:17:59 ...
 kernel:CR2: 0000000000000112
The load is at 1 but no prozess with cpuload in top is visible:

Code: 
# top

top - 21:32:36 up 20 min,  1 user,  load average: 1.00, 0.96, 0.61
Tasks: 124 total,   1 running, 123 sleeping,   0 stopped,   0 zombie
Cpu(s):  3.1%us,  0.1%sy,  0.0%ni, 96.8%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   3786220k total,   639308k used,  3146912k free,    36244k buffers
Swap:  4194296k total,        0k used,  4194296k free,   158976k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                                                                   
 4302 1000      20   0 50844  32m 5404 S   12  0.9   0:09.16 x2goagent                                                                 
 3411 root      20   0 94344  23m 2320 S    1  0.6   0:01.56 pvedaemon                                                                 
 4648 1000      30  10  3516 1448 1204 S    1  0.0   0:00.14 popsquares                                                                
    1 root      20   0 10316  748  616 S    0  0.0   0:01.14 init
The Concole of the new vm show nothing, and if i try to stop the vm its stay in mode stop (in maintenance task). A kill on the kvm-process dosn't help:
Code: 
#ps aux | grep kvm
root      3604  1.0  0.7 623336 27660 ?        D    21:17   0:04 /usr/bin/kvm -monitor unix:/var/run/qemu-server/103.mon,server,nowait -vnc unix:/var/run/qemu-server/103.vnc,password -pidfile /var/run/qemu-server/103.pid -daemonize -usbdevice tablet -name opsi-kvm -smp sockets=1,cores=1 -boot menu=on -vga cirrus -tdf -k de -drive file=/var/lib/vz/images/103/vm-103-disk-1.raw,if=ide,index=0,boot=on -drive file=/dev/cdrom,if=ide,index=2,media=cdrom -m 512 -net tap,vlan=0,ifname=vmtab103i0,script=/var/lib/qemu-server/bridge-vlan -net nic,vlan=0,model=e1000,macaddr=26:70:7B:99:47:AB -id 103 -cpuunits 1000
root      4554  0.0  0.0   8388   820 pts/0    R+   21:25   0:00 grep kvm
bigproxmox:/var/lib/vz# kill 3604
bigproxmox:/var/lib/vz# kill 3604
bigproxmox:/var/lib/vz# kill -9 3604
bigproxmox:/var/lib/vz# kill 3604
Messages:
Code: 
# tail -100 /var/log/messages 
Nov 14 21:12:48 bigproxmox kernel: iscsi: registered transport (iser)
Nov 14 21:12:48 bigproxmox rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="3097" x-info="http://www.rsyslog.com"] restart
Nov 14 21:12:50 bigproxmox kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Nov 14 21:12:50 bigproxmox kernel: tun: Universal TUN/TAP device driver, 1.6
Nov 14 21:12:50 bigproxmox kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov 14 21:12:57 bigproxmox kernel: kvm: Nested Paging enabled
Nov 14 21:12:57 bigproxmox kernel: loaded kvm module (kvm-kmod-2.6.31.6)
Nov 14 21:17:50 bigproxmox kernel: device vmtab103i0 entered promiscuous mode
Nov 14 21:17:50 bigproxmox kernel: audit(1258229870.920:3): dev=vmtab103i0 prom=256 old_prom=0 auid=4294967295
Nov 14 21:17:50 bigproxmox kernel: vmbr0: port 2(vmtab103i0) entering learning state
Nov 14 21:17:50 bigproxmox kernel: vmbr0: topology change detected, propagating
Nov 14 21:17:50 bigproxmox kernel: vmbr0: port 2(vmtab103i0) entering forwarding state
Nov 14 21:17:59 bigproxmox kernel: PGD 11499c067 PUD 11499d067 PMD 0 
Nov 14 21:17:59 bigproxmox kernel: CPU: 3 
Nov 14 21:17:59 bigproxmox kernel: Modules linked in: kvm_amd kvm vzethdev vznetdev simfs vzrst vzcpt tun vzdquota vzmon vzdev xt_tcpudp xt_length ipt_ttl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit ipt_tos ipt_REJECT ip_tables x_tables ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi scsi_transport_iscsi ipv6 bridge snd_hda_intel snd_pcm snd_timer snd_page_alloc serio_raw snd_hwdep r8169 mii floppy psmouse snd thermal pcspkr evdev wmi_acer soundcore button processor sg scsi_wait_scan virtio_blk virtio dm_mod usbhid hid usb_storage libusual sd_mod sr_mod ide_disk ide_generic ide_cd cdrom shpchp pci_hotplug ahci ehci_hcd i2c_piix4 i2c_core atiixp ide_core pata_atiixp pata_acpi ata_generic libata ohci_hcd usbcore ssb arcmsr scsi_mod ohci1394 ieee1394 isofs msdos fat
Nov 14 21:17:59 bigproxmox kernel: Pid: 3616, comm: kvm Not tainted 2.6.24-9-pve #1 ovz005
Nov 14 21:17:59 bigproxmox kernel: RIP: 0010:[<ffffffff88537906>]  [<ffffffff88537906>] :kvm_amd:svm_get_msr+0x146/0x300
Nov 14 21:17:59 bigproxmox kernel: RSP: 0018:ffff810118467d90  EFLAGS: 00010013
Nov 14 21:17:59 bigproxmox kernel: RAX: 000000009ac187f7 RBX: ffff81011846c058 RCX: fffffffff69774bc
Nov 14 21:17:59 bigproxmox kernel: RDX: 0000000000000112 RSI: 0000000000000010 RDI: ffff81011846c000
Nov 14 21:17:59 bigproxmox kernel: RBP: ffff81011846c000 R08: ffff810000000000 R09: 0000000000000000
Nov 14 21:17:59 bigproxmox kernel: R10: 0000000000000000 R11: ffffffff88537ac0 R12: 0000000000000246
Nov 14 21:17:59 bigproxmox kernel: R13: ffff810118461000 R14: 0000000000000000 R15: ffff81011846d6c0
Nov 14 21:17:59 bigproxmox kernel: FS:  0000000042473950(0063) GS:ffff81011b402f80(0000) knlGS:0000000000000000
Nov 14 21:17:59 bigproxmox kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 14 21:17:59 bigproxmox kernel: CR2: 0000000000000112 CR3: 000000011499b000 CR4: 00000000000006e0
Nov 14 21:17:59 bigproxmox kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Nov 14 21:17:59 bigproxmox kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Nov 14 21:17:59 bigproxmox kernel: Process kvm (pid: 3616, veid=0, threadinfo ffff810118466000, task ffff81011417f1c0)
Nov 14 21:17:59 bigproxmox kernel: Stack:  ffffffff88509369 0000000000ba1000 ffffffff806ea690 0000000000000000
Nov 14 21:17:59 bigproxmox kernel: 0000000000000000 0000000000000000 0000000000000000 0000000000000400
Nov 14 21:17:59 bigproxmox kernel: 00000000ffff0ff0 ffff81011846c1a0 ffff81011846ca40 ffff81011846cc40
Nov 14 21:17:59 bigproxmox kernel: Call Trace:
Nov 14 21:17:59 bigproxmox kernel: [<ffffffff88509369>] :kvm:kvm_arch_vcpu_ioctl_run+0x559/0xd20
Nov 14 21:17:59 bigproxmox kernel: [<ffffffff885006db>] :kvm:kvm_vcpu_ioctl+0x2fb/0x5b0
Nov 14 21:17:59 bigproxmox kernel: [<ffffffff804cbb76>] do_page_fault+0x176/0x890
Nov 14 21:17:59 bigproxmox kernel: [<ffffffff802e18cf>] do_ioctl+0x2f/0xb0
Nov 14 21:17:59 bigproxmox kernel: [<ffffffff802e1bdb>] vfs_ioctl+0x28b/0x300
Nov 14 21:17:59 bigproxmox kernel: [<ffffffff802d2f29>] vfs_read+0x129/0x180
Nov 14 21:17:59 bigproxmox kernel: [<ffffffff802e1c99>] sys_ioctl+0x49/0x80
Nov 14 21:17:59 bigproxmox kernel: [<ffffffff8020c69e>] system_call+0x7e/0x83
Nov 14 21:17:59 bigproxmox kernel:
Nov 14 21:17:59 bigproxmox kernel:
Nov 14 21:17:59 bigproxmox kernel: Code: 48 89 02 eb 95 0f 1f 44 00 00 48 8b 87 e0 27 00 00 48 8b 80 
Nov 14 21:17:59 bigproxmox kernel: RSP <ffff810118467d90>
Nov 14 21:17:59 bigproxmox kernel: ---[ end trace 5cef8c94e4f34347 ]---
Nov 14 21:18:39 bigproxmox kernel: CT: 101: started
Nov 14 21:18:40 bigproxmox kernel: device veth101.0 entered promiscuous mode
Nov 14 21:18:40 bigproxmox kernel: audit(1258229920.032:4): dev=veth101.0 prom=256 old_prom=0 auid=4294967295
Nov 14 21:18:40 bigproxmox kernel: vmbr0: port 3(veth101.0) entering learning state
Nov 14 21:18:40 bigproxmox kernel: vmbr0: topology change detected, propagating
Nov 14 21:18:40 bigproxmox kernel: vmbr0: port 3(veth101.0) entering forwarding state
Nov 14 21:18:40 bigproxmox kernel: ioctl32(mount:3741): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bfda3448) on /
Nov 14 21:18:40 bigproxmox kernel: ioctl32(mount:3741): Unknown cmd fd(3) cmd(00001260){t:12;sz:0} arg(bfda3450) on /
Nov 14 21:18:40 bigproxmox kernel: ioctl32(mount:3741): Unknown cmd fd(3) cmd(801c0204){t:02;sz:28} arg(bfda342c) on /
Nov 14 21:18:40 bigproxmox kernel: ioctl32(mount:3741): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bfda3448) on /
Nov 14 21:18:40 bigproxmox kernel: ioctl32(mount:3741): Unknown cmd fd(3) cmd(00001260){t:12;sz:0} arg(bfda3450) on /
Nov 14 21:18:40 bigproxmox kernel: ioctl32(mount:3741): Unknown cmd fd(3) cmd(801c0204){t:02;sz:28} arg(bfda342c) on /
Nov 14 21:27:08 bigproxmox kernel: device vmtab102i0 entered promiscuous mode
Nov 14 21:27:08 bigproxmox kernel: audit(1258230428.399:5): dev=vmtab102i0 prom=256 old_prom=0 auid=4294967295
Nov 14 21:27:08 bigproxmox kernel: vmbr0: port 4(vmtab102i0) entering learning state
Nov 14 21:27:08 bigproxmox kernel: vmbr0: topology change detected, propagating
Nov 14 21:27:08 bigproxmox kernel: vmbr0: port 4(vmtab102i0) entering forwarding state
Nov 14 21:27:18 bigproxmox kernel: PGD ceda1067 PUD ceda2067 PMD 0 
Nov 14 21:27:18 bigproxmox kernel: CPU: 3 
...
Code: 
# pveversion -v
pve-manager: 1.4-10 (pve-manager/1.4/4403)
qemu-server: 1.1-9
pve-kernel: 2.6.24-16
pve-qemu-kvm: 0.11.0-2
pve-firmware: 1
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
After switching to 2.6.24-8-pve the kvm-vm starts (also the convertet vmware-image - it's stop on mounting the root-fs, but this is another problem).

My testserver has an AMD Phenom II X4 945 Processor.

Udo
 
tom said:
Hi all,

We just uploaded a new kernel (pve-kernel-2.6.24-9-pve_2.6.24-17) to the pvetest repository.

Release notes:

  • update kvm to kvm-kmod-2.6.31.6.tar.bz2
  • update e1000e to e1000e-1.0.15.tar.gz
  • kernel security fixes
in order to use this kernel, you need to change your sources.list:

Code: 
# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian lenny pvetest
everybody experiences problems with kvm is asked to test this kernel.
Click to expand...


I have experienced problens with live migration with AMD + 2 cpus guest in 1.4 original kernel. You think this problem can solved with this new release ?

I found this in kvm 2.6.30.1 changelog:

Major KVM changes since kvm-kmod-2.6.30.1:
- MSI-X support
- MCE support
- SVM: Reworked&fixed IRQ injection, added NMI injection
- Host security: Limit lapic periodic timer frequency
- Guest security: CPL check on hypercalls and debug register access
- x86 emulator: lcall and soft INT support, interrupt shadow handling
- Guest migration fixes

Major kvm-kmod changes:
- Reanimated support down to 2.6.24 hosts
- Fixed building against out-of-tree kernel builds / split kernels
- udev script with auto-modprobe on boot
- Installation fixes (DESTDIR)
 
Last edited:
tom said:
Hi all,

We just uploaded a new kernel (pve-kernel-2.6.24-9-pve_2.6.24-17) to the pvetest repository.

Release notes:

  • update kvm to kvm-kmod-2.6.31.6.tar.bz2
  • update e1000e to e1000e-1.0.15.tar.gz
  • kernel security fixes
in order to use this kernel, you need to change your sources.list:

Code: 
# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian lenny pvetest
everybody experiences problems with kvm is asked to test this kernel.
Click to expand...


I take all steps but no new kernel is dowload from apt-get dist-upgrade. Any hint ?
 
Hi, everybody!

I have upgraded one of the two nodes on my cluster to pvetest and I have tried to migrate the VM with Windows XP from stable pve 1.4 node to new node. After migration my VM stoped and I found the next in syslog:
Code: 
Nov 16 11:02:11 cl9 qm[3620]: VM 101 start
Nov 16 11:02:11 cl9 kernel: device vmtab101i0 entered promiscuous mode
Nov 16 11:02:11 cl9 kernel: audit(1258351331.341:3): dev=vmtab101i0 prom=256 old_prom=0 auid=4294967295
Nov 16 11:02:11 cl9 kernel: vmbr0: port 2(vmtab101i0) entering learning state
Nov 16 11:02:11 cl9 kernel: vmbr0: topology change detected, propagating
Nov 16 11:02:11 cl9 kernel: vmbr0: port 2(vmtab101i0) entering forwarding state
Nov 16 11:02:21 cl9 kernel: vmtab101i0: no IPv6 routers present
Nov 16 11:02:36 cl9 kernel: Unable to handle kernel NULL pointer dereference at 00000000000000a5 RIP:
Nov 16 11:02:36 cl9 kernel: [<ffffffff88488906>] :kvm_amd:svm_get_msr+0x146/0x300
Nov 16 11:02:36 cl9 kernel: PGD 11a04a067 PUD 11a04b067 PMD 0
Nov 16 11:02:36 cl9 kernel: Oops: 0002 [1] PREEMPT SMP
Nov 16 11:02:36 cl9 kernel: CPU: 1
Nov 16 11:02:36 cl9 kernel: Modules linked in: sha1_generic drbd cn kvm_amd kvm vzethdev vznetdev simfs vzrst vzcpt tun vzdquota vzmon vzdev xt_tcpudp xt_length ipt_ttl xt_
tcpmss xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit ipt_tos ipt_REJECT ip_tables x_tables ipv6 bridge loop snd_hda_intel snd_pcm snd_timer snd_page_alloc e
vdev snd_hwdep serio_raw pcspkr floppy snd psmouse k8temp soundcore r8169 mii thermal button processor sg scsi_wait_scan virtio_blk virtio dm_mod usbhid hid usb_storage lib
usual sd_mod sr_mod ide_disk ide_generic ide_cd cdrom shpchp pci_hotplug ahci ehci_hcd i2c_piix4 i2c_core atiixp ide_core pata_atiixp pata_acpi ata_generic libata scsi_mod
ohci_hcd usbcore ssb isofs msdos fat
Nov 16 11:02:36 cl9 kernel: Pid: 3663, comm: kvm Not tainted 2.6.24-9-pve #1 ovz005
Nov 16 11:02:36 cl9 kernel: RIP: 0010:[<ffffffff88488906>]  [<ffffffff88488906>] :kvm_amd:svm_get_msr+0x146/0x300
Nov 16 11:02:36 cl9 kernel: RSP: 0018:ffff81011a02dd80  EFLAGS: 00010206
Nov 16 11:02:36 cl9 kernel: RAX: 00000000d6225935 RBX: ffffc20001f09040 RCX: 0000000000000000
Nov 16 11:02:36 cl9 kernel: RDX: 00000000000000a5 RSI: 0000000000000010 RDI: ffff81011b894000
Nov 16 11:02:36 cl9 kernel: RBP: 0000000000000004 R08: 0000000000000001 R09: 0000000000000000
Nov 16 11:02:36 cl9 kernel: R10: 0000000000000000 R11: ffffffff884887c0 R12: ffff81011b894000
Nov 16 11:02:36 cl9 kernel: R13: ffffffff88454d30 R14: 0000000000000001 R15: 00000000000000a0
Nov 16 11:02:36 cl9 kernel: FS:  0000000041927950(0063) GS:ffff81012b002880(0000) knlGS:0000000000000000
Nov 16 11:02:36 cl9 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Nov 16 11:02:36 cl9 kernel: CR2: 00000000000000a5 CR3: 000000011a049000 CR4: 00000000000006e0
Nov 16 11:02:36 cl9 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Nov 16 11:02:36 cl9 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Nov 16 11:02:36 cl9 kernel: Process kvm (pid: 3663, veid=0, threadinfo ffff81011a02c000, task ffff81011a0e71c0)
Nov 16 11:02:36 cl9 kernel: Stack:  ffffffff88458e79 0000000000000000 0000000000cab818 ffffc20001f09000
Nov 16 11:02:36 cl9 kernel: 000000a01a02dcb8 00007f4e0000000a 0000000200000202 000000011b894000
Nov 16 11:02:36 cl9 kernel: fffffffffffffffb 0000000000000000 0000000000cab810 ffff81011b894000
Nov 16 11:02:36 cl9 kernel: Call Trace:
Nov 16 11:02:36 cl9 kernel: [<ffffffff88458e79>] :kvm:msr_io+0x119/0x170
Nov 16 11:02:36 cl9 kernel: [<ffffffff88459261>] :kvm:kvm_arch_vcpu_ioctl+0x391/0x610
Nov 16 11:02:36 cl9 kernel: [<ffffffff88454e1e>] :kvm:kvm_arch_vcpu_put+0xe/0x40
Nov 16 11:02:36 cl9 kernel: [<ffffffff88454562>] :kvm:vcpu_put+0x22/0x60
Nov 16 11:02:36 cl9 kernel: [<ffffffff88451525>] :kvm:kvm_vcpu_ioctl+0x145/0x5b0
Nov 16 11:02:36 cl9 kernel: [<ffffffff80251f3a>] dequeue_signal+0x9a/0x170
Nov 16 11:02:36 cl9 kernel: [<ffffffff802522ea>] sys_rt_sigtimedwait+0x2da/0x300
Nov 16 11:02:36 cl9 kernel: [<ffffffff802e18cf>] do_ioctl+0x2f/0xb0
Nov 16 11:02:36 cl9 kernel: [<ffffffff802e1bdb>] vfs_ioctl+0x28b/0x300
Nov 16 11:02:36 cl9 kernel: [<ffffffff802e1c99>] sys_ioctl+0x49/0x80
Nov 16 11:02:36 cl9 kernel: [<ffffffff8020c69e>] system_call+0x7e/0x83
Nov 16 11:02:36 cl9 kernel:
Nov 16 11:02:36 cl9 kernel:
Nov 16 11:02:36 cl9 kernel: Code: 48 89 02 eb 95 0f 1f 44 00 00 48 8b 87 e0 27 00 00 48 8b 80
Nov 16 11:02:36 cl9 kernel: RIP  [<ffffffff88488906>] :kvm_amd:svm_get_msr+0x146/0x300
Nov 16 11:02:36 cl9 kernel: RSP <ffff81011a02dd80>
Nov 16 11:02:36 cl9 kernel: CR2: 00000000000000a5
Nov 16 11:02:36 cl9 kernel: ---[ end trace c607ca9f48d18b57 ]---
Code: 
AMD Athlon(tm) 64 X2 Dual Core Processor 5400+ stepping 02
Linux version 2.6.24-9-pve (root@oahu) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP PREEMPT Fri Nov 13 08:54:39 CET 2009 (Ubuntu 2.6.24-4.6-server)

And now I can't run this VM on new node.
 
Last edited:
udo said:
After switching to 2.6.24-8-pve the kvm-vm starts (also the convertet vmware-image - it's stop on mounting the root-fs, but this is another problem).

My testserver has an AMD Phenom II X4 945 Processor.
Click to expand...

I just reported the problem to the kvm mailing list.

Besides, do you have a nice 'x2go' setup? If so, it would be nice to have a wiki page for that ;-)
 
Hi Dietmar,
the x2go is just for test - i want to change our free-nx to x2go and at home for a terminal-client. If i got more experience with it, i can write something...

Udo
 
Last edited:
udo said:
Hi Dietmar,
the x2go is just for test - i want to change our free-nx to x2go and at home for a terminal-client. If i got more experience with it, i can write something...

Udo
Click to expand...

I am awaiting for your x2go howto!
 
I install 2.6.24-9 kernel and the kvms guest can't load. I using AMD processors.

Anybody have sucess using this kernel ? maybe is broken.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back