OS Solaris 10 work very slow.

acceptor

New Member
Jan 28, 2014
4
0
1
i have a trouble:
I configured guest vm on OS solaris 10 x86 by this manual: https://pve.proxmox.com/wiki/Solaris_Guests. I was very confused by the speed of vm. During installation guest works very slow comparing to solaris on real hardware or another guests OS on the same server.
After installation solaris boots very slow too and i have time to drink cup of tea until I get access to ssh or while copying file...


I'm using proxmox v3.1 on one server and proxmox v2.3 on other, problem affects both servers.
 
Last edited:
i have a trouble:
I configured guest vm on OS solaris 10 x86 by this manual: https://pve.proxmox.com/wiki/Solaris_Guests. I was very confused by the speed of vm. During installation guest works very slow comparing to solaris on real hardware or another guests OS on the same server.
After installation solaris boots very slow too and i have time to drink cup of tea until I get access to ssh or while copying file...


I'm using proxmox v3.1 on one server and proxmox v2.3 on other, problem affects both servers.


I found this link http://www.linux-kvm.org/page/Guest_Support_Status#UNIX_Family:_Solaris.2FOpenSolaris

There is INTEL cpu written in column 'Host cpu' for all Solaris versions. But I don't know what does it mean: Solaris + kvm was tested only on this configurations or only this config works and AMD won't work at all.
 
did you try the relatively new ostype "solaris", with KVM enabled?
(see http://forum.proxmox.com/threads/16265-New-Kernel-for-Proxmox-VE-3-1-and-bug-fixes)

seems the wiki page is needs some updates.

Yes, i did. Below i show my proxmox versions and config of guests os.

- first server is:
root@bear:~# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-96
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-18-pve: 2.6.32-88
pve-kernel-2.6.32-19-pve: 2.6.32-96
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1


root@bear:~# cat /etc/pve/qemu-server/450.conf
boot: cd
bootdisk: ide0
cores: 1
cpu: qemu64
ide0: local:450/root.qcow2,size=32G
ide2: local:iso/sol-10-u11-ga-x86-dvd.iso,media=cdrom,size=2201280K
kvm: 0
localtime: 1
memory: 2048
name: ORACLE-SOLARIS10
net0: e1000=6A:EB:10:26:FE:F6,bridge=vmbr1
ostype: l26
sockets: 1
tablet: 0
vga: std

root@bear:~# qm showcmd 450
/usr/bin/kvm -id 450 -chardev socket,id=qmp,path=/var/run/qemu-server/450.qmp,server,nowait -mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/450.vnc,x509,password -pidfile /var/run/qemu-server/450.pid -daemonize -name ORACLE-SOLARIS10 -smp sockets=1,cores=1 -cpu qemu64 -nodefaults -boot menu=on -vga std -k en-us -m 2048 -cpuunits 1000 -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -drive file=/var/lib/vz/images/450/root.qcow2,if=none,id=drive-ide0,aio=native,cache=none -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100 -drive file=/var/lib/vz/template/iso/sol-10-u11-ga-x86-dvd.iso,if=none,id=drive-ide2,media=cdrom,aio=native -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 -netdev type=tap,id=net0,ifname=tap450i0,script=/var/lib/qemu-server/pve-bridge -device e1000,romfile=,mac=6A:EB:10:26:FE:F6,netdev=net0,bus=pci.0,addr=0x12,id=net0 -rtc base=localtime -machine accel=tcg



- second server is:
root@proxmox:~# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-17
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1


root@proxmox:~# cat /etc/pve/qemu-server/103.conf
bootdisk: sata0
cores: 1
cpu: qemu64
kvm: 0
localtime: 1
memory: 2048
name: solaris
net0: e1000=AE:E4:98:46:43:75,bridge=vmbr0
ostype: solaris
sata0: local:103/vm-103-disk-1.raw,format=raw,cache=writeback,backup=no,size=32G
sata2: local:iso/sol-10-u11-ga-x86-dvd.iso,media=cdrom,size=2201280K
sockets: 1
vga: std

root@proxmox:~# qm showcmd 103
/usr/bin/kvm -id 103 -chardev socket,id=qmp,path=/var/run/qemu-server/103.qmp,server,nowait -mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/103.vnc,x509,password -pidfile /var/run/qemu-server/103.pid -daemonize -name solaris -smp sockets=1,cores=1 -nodefaults -boot menu=on -vga std -cpu qemu64,-x2apic -k en-us -m 2048 -cpuunits 1000 -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -device usb-tablet,id=tablet,bus=uhci.0,port=1 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -device ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7 -drive file=/var/lib/vz/template/iso/sol-10-u11-ga-x86-dvd.iso,if=none,id=drive-sata2,media=cdrom,aio=native -device ide-drive,bus=ahci0.2,drive=drive-sata2,id=sata2,bootindex=200 -drive file=/var/lib/vz/images/103/vm-103-disk-1.raw,if=none,id=drive-sata0,format=raw,cache=writeback,aio=native -device ide-drive,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=100 -netdev type=tap,id=net0,ifname=tap103i0,script=/var/lib/qemu-server/pve-bridge -device e1000,mac=AE:E4:98:46:43:75,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300 -rtc base=localtime -machine accel=tcg
 
I know this topic is from a long time ago, but was anyone been able to solve it? In my tests on Proxmox 8, Solaris is also 2/3 slower than an Ubuntu 22.04 when writing to a virtual drive, even with virtio drivers. It makes no difference whether ZFS or UFS is used. Nor does it matter which cache is set.

Also, it seems that only one CPU core is used.
https://forum.proxmox.com/threads/solaris-11-vm-not-recognizing-cores.110363/
 

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 yours easily in our online shop.

Buy now!