On 14.04.2015 15:16, Jatin Davey wrote:
On 4/14/2015 6:32 PM, Tom Hughes wrote:
> On 14/04/15 13:33, Jatin Davey wrote:
>
>> Thanks Dominique & Daniel.
>>
>> Looks like i need to upgrade my VMs kernel to make it aware of virtio.
>>
>> Found this information from this link:
>>
>>
http://wiki.libvirt.org/page/Virtio#Disk_.28block.29_device_driver
>>
>> I tried without upgrading the Kernel and as soon as i start my VM it got
>> into Kernel Panic. I will try using virtio after upgrading my VMs
>> kernel.
>
> As somebody has already said it would have to be a really old kernel
> to not handle virtio-block, and it's more likely that your bootloader
> and/or initrd are confused by sda becoming vda.
>
> However if your kernel supports it then virtio-scsi should be even
> better than virtio-block and shouldn't cause the device name to change.
>
> Tom
>
My VM is using the kernel 2.6.18-164.el5
[root@localhost ~]# uname -a
Linux localhost 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64
x86_64 x86_64 GNU/Linux
Should this be fine ?
Is there any particular reason why you are using RHEL 5? The current
version is RHEL 7 which contains much more up-to-date versions of
kernel, qemu and other virtualization tools.
Regards,
Dennis