Hello,
When we tried to start a VM instance Image(VMDK), just with OpenStack tool “nova boot”. But this results to a kernel panic.
How we can analyze/debug the below issue in VIO.
FYI.
Can anyone help on above request.
Thanks,
Maghesh
Can you provide us with some more information about this problem :-
VIO Version
Guest OS
How did you obtain this VMDK ?
What is the vmdk subformat (sparse, flat, streamOptimized) ? Can you paste the output of "head -20 <path_to_vmdk>" if it has a some header information. Otherwise, it should be a flat disk (a.k.a preallocated).
Finally, can you also upload the output of "glance image-show <image_id>" corresponding to your vmdk image.
Thanks, we will help you troubleshoot.
Please find details below:
The Image INFO.MEDIA.0463 is based on RHEL 6.7. It was loaded via glance. From this image a software volume was created and used as boot volume for the ssb instance:
Login on mgm1 (192.168.129.226)
root@mgm1 # glance image-create \
--name INFO.MEDIA.0463 \
--disk-format vmdk \
--container-format bare \
--is-public True \
--min-disk 32 \
--min-ram 4096 \
--file /media/CIPD_cloud_f07_3__160314_135021/images/INFO.MEDIA.0463/INFO.MEDIA.0463/INFO.MEDIA.0463-disk1.vmdk \
--progress
root@mgm1 # glance image-show INFO.MEDIA.0463
/usr/lib/python2.6/site-packages/urllib3/connectionpool.py:769: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.org/en/latest/security.html
InsecureRequestWarning)
/usr/lib/python2.6/site-packages/glanceclient/client.py:26: DeprecationWarning: `version` keyword is being deprecated. Please pass the version as part of the URL. http://$HOST:$PORT/v$VERSION_NUMBER
DeprecationWarning)
-------------------------------------------------------------------+
Property Value
-------------------------------------------------------------------+
Property 'vmware_adaptertype' busLogic
Property 'vmware_disktype' streamOptimized
checksum 23209c6fa6427bf17a7abc0e14ac73f8
container_format bare
created_at 2016-04-06T09:49:30.000000
deleted False
disk_format vmdk
id 24a17191-49e1-42f9-bb67-cbc7e50678b6
is_public True
min_disk 32
min_ram 4096
name INFO.MEDIA.0463
owner 709f3bdda0304431be346405eec30d16
protected False
size 3307144192
status active
updated_at 2016-04-06T09:58:09.000000
-------------------------------------------------------------------+
root@mgm1 # head -20 /media/CIPD_cloud_f07_3__160314_135021/images/INFO.MEDIA.0463/INFO.MEDIA.0463/INFO.MEDIA.0463-disk1.vmdk
KDMVÀÿÿÿÿÿÿÿÿ
Disk DescriptorFile
version=1
CID=14b80013
parentCID=ffffffff
createType="streamOptimized"
Extent description
RDONLY 62914560 SPARSE "generated-stream.vmdk"
The Disk Data Base
#DDB
ddb.adapterType = "buslogic"
ddb.geometry.cylinders = "3916"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.longContentID = "a90dade7f1c994c24bbe6faa2e90fd4b"
ddb.toolsVersion = "2147483647"
root@mgm1 # cinder create \
--image-id 24a17191-49e1-42f9-bb67-cbc7e50678b6 \
--display-name ssb01-software \
--display-description INFO.MEDIA.0463 \
--availability-zone nova 42
root@mgm1 # cinder create --display-name ssb01-data --availability-zone nova 12
root@mgm1 # neutron port-create --name ssb01_Backup --fixed-ip subnet_id=Backup,ip_address=172.16.1.10 --security-group SecGroup_RS Backup
root@mgm1 # neutron port-create --name ssb01_Payload --fixed-ip subnet_id=Payload_subnet,ip_address=172.16.6.10 --security-group SecGroup_RS Payload
root@mgm1 # nova boot --flavor 4 --user-data /media/user-data --security-groups default,SecGroup_RS --block-device-mapping vda=`cinder list | grep ssb01-software| awk -F" " '
{print $2}'`:::0 --block-device-mapping vdb=`cinder list | grep ssb01-data | awk -F" " '{print $2}
'`:::0 --nic port-id=`neutron port-list | grep ssb01_Backup| awk -F" " '
{print $2}'` --nic port-id=`neutron port-list | grep ssb01_Payload| awk -F" " '{print $2}
'` ssb01
We are still facing the kernel panic while setup of an node.
Any idea on this issue?
Hi,
could we get your image to have a try internally? thanks.
-steven
There are 2 ways to make it work
Looks like the VMDK has busLogic in its header but in order to boot this successfully you had to specify the controller type as paraVirtual.
I wonder how you created this VMDK ? Did you use any conversion tools to convert the disk from other formats or did you take this from an existing VM (which was working) ?