KVM Kernel Panic When Additional Virtio Disks Added

Home » CentOS » KVM Kernel Panic When Additional Virtio Disks Added
CentOS No Comments

CentOS-6.6
virt-manager 0.9.0

I have cloned a template server with a 32GB virtio HDD already defined and am attempting to add additional virtio disks. The basic cloned system boots without error.

If I create a virtio disk with 32000/32000 megabytes I can add it and the system reboots; providing that I do not first create a partition:

fdisk -l /dev/vg_vhost03/lv_vm_inet11.harte-lyne.ca_03

Disk /dev/vg_vhost03/lv_vm_inet11.harte-lyne.ca_03: 33.6 GB,
33554432000 bytes
255 heads, 63 sectors/track, 4079 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x02ec08ff

Device Boot Start
End Blocks Id System

However, in that event I cannot see the new disk:

/dev/mapper/vg_inet01b-lv_root /
ext4 defaults 1 1

UUID!8fd81f-6811-4965-b8d5-b0098a569598 /boot
ext4 defaults 1 2

/dev/mapper/vg_inet01b-lv_tmp /tmp
ext4 defaults 1 2

/dev/mapper/vg_inet01b-lv_log /var/log
ext4 defaults 1 2

/dev/mapper/vg_inet01b-lv_spool /var/spool
ext4 defaults 1 2

/dev/mapper/vg_inet01b-lv_swap swap
swap defaults 0 0
tmpfs /dev/shm
tmpfs defaults 0 0
devpts /dev/pts
devpts gid=5,modeb0 0 0
sysfs /sys
sysfs defaults 0 0
proc /proc
proc defaults 0 0

If I do partition the disk thus:

fdisk -l /dev/vg_vhost03/lv_vm_inet11.harte-lyne.ca_03

Disk /dev/vg_vhost03/lv_vm_inet11.harte-lyne.ca_03: 33.6 GB,
33554432000 bytes
109 heads, 61 sectors/track, 9856 cylinders Units = cylinders of 6649 * 512 = 3404288 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x02ec08ff

Device Boot Start
End Blocks Id System
/dev/vg_vhost03/lv_vm_inet11.harte-lyne.ca_03p1 1
9857 32766976 83 Linux

Then when I boot the vm it fails with a kernel panic. If I remove the disk or remove the partition from that disk then the cloned system will boot successfully.

Does anyone have any idea what is going on and how to fix it?