Problem with Sybase and logical CPU

khayman

Member
Sep 15, 2010
38
0
6
Hello.

I have big problem with KVM machine with Centos and Sybase DB. I defined for this machine 1 CPU with 4 cores. Sybase are checking what kind cpu kvm is using and where cores comes from, and it detected, that cores are coming from different CPU's (hipervisor has 2 CPU with 4 cores both, HyperThreading is on, so i have 16 virtual cores.)

So i must bond cores from only one CPU to KVM machine with Sybase.
I found two solutions for this:
1. with libvirt: http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/ch25s06.html
2. without libvurt: http://www.linux-kvm.com/content/tip-running-your-vm-specific-cpus

My hipervisor is Proxmox 1.8:
pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.18-6-pve
proxmox-ve-2.6.18: 1.8-15
pve-kernel-2.6.18-6-pve: 2.6.18-15
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.28-1pve1
vzdump: 1.2-14
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-15


Without libvirt solution demand qemu-system package, but when i tried to install it, new package want to change main qemu package, which is part of pvedaemon package, so installation failed.

Proxmox has not libvirt.

If someone had this problem? How to solved this?
 

dietmar

Proxmox Staff Member
Staff member
Apr 28, 2005
17,125
526
133
Austria
www.proxmox.com
This is the forum for PVE 2.0, but you are still using 1.8. I suggest you upgrade your system.
 

khayman

Member
Sep 15, 2010
38
0
6
Right, but meanwhile I've tested this on Proxmox 2.1 kernel 2.6.32-12:
pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
running kernel: 2.6.32-12-pve
proxmox-ve-2.6.32: 2.1-68
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-12-pve: 2.6.32-68
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-16
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

and this problem is exactly the same. Only difference is that i can install qemu-system by apt-get, not manually.

Maybe someone install libvirt libraries on Proxmox and using it similiarly ?
 
Last edited:

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
15,554
925
163
you still have the old version, use latest, includes KVM 1.1.1.

and never install libvirt on Proxmox VE.
 

khayman

Member
Sep 15, 2010
38
0
6
Right, i don't noticed that was released new kernel and kvm. But i read, that there were many problems with them. Is it safe to upgrade now?
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
15,554
925
163
where did you read about many problems?

if you have any issues, post it here.
 

khayman

Member
Sep 15, 2010
38
0
6
I have upgraded server to the newest kernel (pveversion -v):
pve-manager: 2.1-13 (pve-manager/2.1/bdd3663d)
running kernel: 2.6.32-13-pve
proxmox-ve-2.6.32: 2.1-72
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-13-pve: 2.6.32-72
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-47
pve-firmware: 1.0-17
libpve-common-perl: 1.0-28
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-29
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-6
ksm-control-daemon: 1.1-1


next i run apt-get install qemu-system, effect:
root@xxxxxxxxxxxx:~# apt-get install qemu-system
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
qemu-utils
Suggested packages:
samba debootstrap
The following NEW packages will be installed:
qemu-system qemu-utils
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/14.4 MB of archives.
After this operation, 39.9 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Selecting previously deselected package qemu-system.
(Reading database ... 32551 files and directories currently installed.)
Unpacking qemu-system (from .../qemu-system_0.12.5+dfsg-3squeeze1_amd64.deb) ...
Unpacking qemu-utils (from .../qemu-utils_0.12.5+dfsg-3squeeze1_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/qemu-utils_0.12.5+dfsg-3squeeze1_amd64.deb (--unpack):
trying to overwrite '/usr/share/man/man8/qemu-nbd.8.gz', which is also in package pve-qemu-kvm 1.1-6
configured to not write apport reports
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Processing triggers for man-db ...
Errors were encountered while processing:
/var/cache/apt/archives/qemu-utils_0.12.5+dfsg-3squeeze1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Packages are seems to incompatible. What can I do, to install qemu-system without destroying anything ?
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
15,554
925
163
Proxmox VE uses latest stable KVM 1.1.1, you cannot install KVM from Debian (0.12.5).
 

khayman

Member
Sep 15, 2010
38
0
6
Ok, so what should I do?

I have the newest kernel of Proxmox, pveversion -v results are according with this: http://forum.proxmox.com/threads/10408-KVM-1-1-and-new-Kernel . I've tried to install newest qemu-system, but i get many messages that my .deb packages are old. If I instrall new one, that I propably crach all system.

Maybe should you consider to add additional packages like qemu-system or qemu-utils to Proxmox ?
 

udo

Famous Member
Apr 22, 2009
5,934
183
83
Ahrensburg; Germany
Ok, so what should I do?

I have the newest kernel of Proxmox, pveversion -v results are according with this: http://forum.proxmox.com/threads/10408-KVM-1-1-and-new-Kernel . I've tried to install newest qemu-system, but i get many messages that my .deb packages are old. If I instrall new one, that I propably crach all system.

Maybe should you consider to add additional packages like qemu-system or qemu-utils to Proxmox ?
Hi,
in your case I would try the pve-packages and use cgroups to use only one real cpu for the VM (and first do an test on a simple Motherboard with an single multicore cpu with pve if sybase do the right thing there).

Udo
 

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!

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 your own in 60 seconds.

Buy now!