Trying to Run Slackware 13.7 as guest on KVM

baboo

Member
Nov 14, 2010
58
0
6
I am running 1.8 with 2.6.38 kernel. All my guests have been Slackware. However, since I upgraded to 1.8 I cannot boot a Slackware install. Slackware does not see the partitions as /dev/vda. So, after install but before rebooting I 'chroot /mnt' and make modifications to kernel and lilo for boot. However, it just want boot.

I am wondering if something in the 1.8 release having to do with virtio drivers is the cause? Proxmox has been working just great, so no complaints there. Any insights would be greatly appreciated.

thanks
 
2.6.38 is not a Proxmox VE kernel - switch to a Proxmox kernel, post your 'pveversion -v' and try again - if you fail I will try to reproduce the issue if you give full details, e.g. your VMID.conf and the uses iso image (slackware).
 
sorry tom: I am running 2.6.35-1-pve. My post had a typo. Here is pveversion -v output:

pveversion -v
pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.8-11
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.35-1-pve: 2.6.35-11
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: 0.14.1-1
ksm-control-daemon: 1.0-6


and thanks for taking the time to reply.
 
can you answer all question?
 

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!