How to create sda partition on VM
Hi,
Is there any way to create sda partitions instead of vda on new VM.
Please let us know the steps!!!
Thanks



Responses
Hi Nani Babu Mutte,
why do you explicity need sda?
Full Virtualization vs. Paravirtualization
/dev/sda is the first detected disk of IDE/SATA/SCSI type. In this case, emulated(full virtualized) by the hypervisor.
/dev/vda is the first detected paravirtualizated disk driver. It is faster than emulated sdX devices.
Hi Nani,
I don't quite get the point ... when you insert the virtual disk into a SATA controller, it is shown as sda and when you insert the virtual disk into a VirtIO controller, it is shown as vda ... so when you want to see sda - just insert the virtual disk into the SATA controller. :)
Regards,
Christian
My guess is that the "WindRiver" OS does not have the virtio-scsi drivers necessary to make use of the para-virtualized disk device you're attempting to present to it.
As a result, the disk is being represented as fully-virtualized (/dev/vda) disk by the OS despite your selecting virtio-scsi as the interface type.
To test this, you can attempt to locate the virtio-scsi drivers on your WindRiver VM (note that these drivers are installed by default in RHEL):
locate virtio_scsi.ko
If you're unable to locate the virtio-scsi driver, then your system will probably not be able to make use of the virtio-scsi interface type, and your disk devices will likely always be represented as /dev/vda, vdb, vdc, etc.
Hi Nani,
One thing, you say that you installed RHEL in VM-1 and Wind River in VM-2 as host. I guess you mean you installed these systems as guest systems on a RHEL host system. So it is possible that the explanation from Russell is valid and in that case there's nothing you can do, you have to live with the situation as it is. But is this a problem at all ? Important is that the virtual systems are running properly - right ?
Regards,
Christian
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
