New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32) [UPDATE]

Re: New Proxmox VE Kernels (2.6.32) Feedback, HR-RTC issue solved

ProxmoxVE1.5 solves the time drift issue (RTC stalled for several seconds depending on load when putting Windows VMs to higher resolution clock
für Quicktime, SAP, LabView). This happend on AMD PhenomII and probably was the same for others platforms using dynamic clocking of CPU/Chipset togehter with higer resolution clock settings.
This at least is true for the 2.6.32 Kernel, we didn't check the others!

Thanks a lot.

JP
 
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

chopeta said:
OK, the new firmware was in there:

Code: 
# ls -l /lib/firmware/bnx2/bnx2-mips-06-5.0.0.j3.fw
-rw-r--r-- 1 root root 93172 Dec 29 05:04 /lib/firmware/bnx2/bnx2-mips-06-5.0.0.j3.fw

Looks like I was just had to update my initrd image (thanks dietmar!)

Code: 
# update-initramfs -u -t

Testing new kernel now, with virtio and 2 cores...
Click to expand...


Does this replace the 'firmware-bnx' from the non-free repo?
 
Hello Dietmar,

I am wondering, i was checking and reading a lot in the forums but it seems this is not explained or was not asked for:

Why does 2.6.32 not have OpenVZ support? Is it because there are no native OpenVZ Patches available for 2.6.32? I thought OpenVZ is in vanilla? Isn't it?

So to speak, i am in the "need" of KVM+KSM+OpenVZ, will the 2.6.32 kernel eventually get OpenVZ support?

Best,
Ray
 
Ray said:
Hello Dietmar,

I am wondering, i was checking and reading a lot in the forums but it seems this is not explained or was not asked for:

Why does 2.6.32 not have OpenVZ support? Is it because there are no native OpenVZ Patches available for 2.6.32? I thought OpenVZ is in vanilla? Isn't it?

So to speak, i am in the "need" of KVM+KSM+OpenVZ, will the 2.6.32 kernel eventually get OpenVZ support?

Best,
Ray
Click to expand...

There is no OpenVZ for 2.6.32. See http://wiki.openvz.org/Download/kernel

We expect some news on the container virtualization on Kernel 2.6.32 later this year.
 
Hi Tom,

Ah, I was under the impression that OpenVZ is included in the vanilla kernel sources, i thought I read about it some time ago, but it seems I was mistaken,

thanks,
best regards
 
Hi and Hello, after the upgrade from 1.4 to 1.5, stopped my virtual machine and i can't restart it.
The proxmox works fine, also the new installed virtual machine is working perfect. But in the old one are some data witch i didn't backed up. Is there a possibility to extract the files from the raw disk file(local:101/vm-101-disk-1.raw) or is it possible to fix the virtual machine.
I hope some one can help me and thank you.
Down hire are my system logs:


/usr/sbin/qm start 101
qemu: 'file=/var/lib/vz/images/101/vm-101-disk-1.raw,if=scsi,index=0,boot=on' unsupported bus type 'scsi'
start failed: command '/usr/bin/kvm -monitor unix:/var/run/qemu-server/101.mon,server,nowait -vnc unix:/var/run/qemu-server/101.vnc,password -pidfile /var/run/qemu-server/101.pid -daemonize -usbdevice tablet -name ClarkConnect -smp 2 -boot cd -vga cirrus -tdf -k de -drive file=/var/lib/vz/template/iso/community-5.0.iso,if=ide,index=2,media=cdrom -drive file=/var/lib/vz/images/101/vm-101-disk-1.raw,if=scsi,index=0,boot=on -m 3072 -net tap,vlan=0,ifname=vmtab101i0,script=/var/lib/qemu-server/bridge-vlan -net nic,vlan=0,model=rtl8139,macaddr=12:04:D5:23:F5:07 -net tap,vlan=1,ifname=vmtab101i1,script=/var/lib/qemu-server/bridge-vlan -net nic,vlan=1,model=rtl8139,macaddr=22:57:AF:3A:69:77 -id 101 -cpuunits 1000' failed with exit code 1
VM 101 start failed -




Feb 11 19:08:47
pvedaemon
5341
starting VM 101 on node 0 (localhost)
Feb 11 19:08:47
qm
5342
VM 101 start
Feb 11 19:08:47
kernel

device vmtab101i0 entered promiscuous mode
Feb 11 19:08:47
kernel

audit(1265911727.593:15): dev=vmtab101i0 prom=256 old_prom=0 auid=4294967295
Feb 11 19:08:47
kernel

vmbr0: port 2(vmtab101i0) entering learning state
Feb 11 19:08:47
kernel

vmbr0: topology change detected, propagating
Feb 11 19:08:47
kernel

vmbr0: port 2(vmtab101i0) entering forwarding state
Feb 11 19:08:47
kernel

device vmtab101i1 entered promiscuous mode
Feb 11 19:08:47
kernel

audit(1265911727.609:16): dev=vmtab101i1 prom=256 old_prom=0 auid=4294967295
Feb 11 19:08:47
kernel

vmbr1: port 2(vmtab101i1) entering learning state
Feb 11 19:08:47
qm
5342
VM 101 start failed: command '/usr/bin/kvm -monitor unix:/var/run/qemu-server/101.mon,server,nowait -vnc unix:/var/run/qemu-server/101.vnc,password -pidfile /var/run/qemu-server/101.pid -daemonize -usbdevice tablet -name ClarkConnect -smp 2 -boot cd -vga cirrus -tdf -k de -drive file=/var/lib/vz/template/iso/community-5.0.iso,if=ide,index=2,media=cdrom -drive file=/var/lib/vz/images/101/vm-101-disk-1.raw,if=scsi,index=0,boot=on -m 3072 -net tap,vlan=0,ifname=vmtab101i0,script=/var/lib/qemu-server/bridge-vlan -net nic,vlan=0,model=rtl8139,macaddr=12:04:D5:23:F5:07 -net tap,vlan=1,ifname=vmtab101i1,script=/var/lib/qemu-server/bridge-vlan -net nic,vlan=1,model=rtl8139,macaddr=22:57:AF:3A:69:77 -id 101 -cpuunits 1000' failed with exit code 1
Feb 11 19:08:47
kernel

vmbr1: topology change detected, propagating
Feb 11 19:08:47
kernel

vmbr1: port 2(vmtab101i1) entering forwarding state
Feb 11 19:08:47
pvedaemon
5341
VM 101 start failed -
Feb 11 19:08:47
kernel

vmbr0: port 2(vmtab101i0) entering disabled state
Feb 11 19:08:47
kernel

vmbr0: port 2(vmtab101i0) entering disabled state
Feb 11 19:08:47
kernel

vmbr1: port 2(vmtab101i1) entering disabled state
Feb 11 19:08:47
kernel

vmbr1: port 2(vmtab101i1) entering disabled state
Feb 11 19:09:31
proxwww
5407
Starting new child 5407
 
unsupported bus type 'scsi'

looks like you have scsi disk and your run 2.6.18 - no scsi bus for KVM guest available. change your guest to IDE disk, depending on your guest OS this will just work or needs adaption.
 
Thank you for the tip, but i can't delete my drive. Because then my data will be lost. Is there a way to install a kernel with scsi support? Or to down grade to a older kernel? Thanks
 
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

When you delete a drive from a guest in PVE, it simply becomes un-allocated & sits in a purgatory until you delete it from disk or re-apply it to the machine- and you can change the interface with which it communicates with that guest at the time you re-allocate it. You don't lose data. It's useful.
 
hal2056 said:
Thank you for the tip, but i can't delete my drive. Because then my data will be lost. Is there a way to install a kernel with scsi support? Or to down grade to a older kernel? Thanks
Click to expand...

  1. go to the hardware tab, remove the SCSI drive (from the config, not from the disk).
  2. add a new harddrive - the old one should be available and add it with IDE
  3. go to options and select the IDE disk for booting
maybe you try this with a another KVM guest that you get familiar with this process.

or go for 2.6.24 (with scsi KVM guest support). but 2.6.18 has the stable OpenVZ.
 
Thanks for the detailed work sheet, and i madded to change from scsi to ide. but i can't start it neither. I hope there is a way to get the data back!
 
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

After install a new Proxmox 1.5 I update to the new Proxmox VE Kernel 2.6.24 and 2.6.32. But when I boot from xx.24- or xx.26-Kernel the system will a filesytem-check. Why that? When I boot from xx.18-2 kernel the system starts normal. The file-system is OK with the xx.18-2 kernel.

regards
K.W.
 
Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

do you have the right time in the server bios? and does ntp work? any logs from the file-system?
 
Re: New Proxmox VE Kernels (2.6.32) Feedback, HR-RTC issue solved

The openvz teams now seems to be working on a 2.6.32 kernel. Would proxmox continue openvz if they include their work into the new kernels?
 
Re: New Proxmox VE Kernels (2.6.32) Feedback, HR-RTC issue solved

we follow all news on OpenVZ in detail.
 
Re: New Proxmox VE Kernels (2.6.32) Feedback, HR-RTC issue solved

we use on a windows xp kvm a time critical application under Kernel 2.6.18 but have a time drift from 10 second within one minute. We changed the kernel from 2.6.18 to 2.6.24 an the time drift issue is gone but now i cant do live migration with the kernel that works with 2.6.18 :(
 
Last edited:
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