Hi,
So I updated my guest from 5.1 to 5.8 via a complete yum update, many many packages BTW.
I shutdown the guest, change its "Disk bus" from IDE to Virtio and then upon boot, I get kernel panics as no disk can be found. I do get the splash screen at first however.
My guest has /dev/hda, should I change its fstab to reflect /dev/vda instead?
Thans in advance, - aurf
On 29.04.2012 23:49, aurfalien wrote:
Hi,
So I updated my guest from 5.1 to 5.8 via a complete yum update, many many packages BTW.
I shutdown the guest, change its "Disk bus" from IDE to Virtio and then upon boot, I get kernel panics as no disk can be found. I do get the splash screen at first however.
My guest has /dev/hda, should I change its fstab to reflect /dev/vda instead?
Thans in advance,
- aurf
CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Yes.. Or you can use LABELs. Any way might work. If it doesn't try to rebuild the initrd --with virtio_blk.
On Apr 29, 2012, at 7:18 PM, Nux! wrote:
On 29.04.2012 23:49, aurfalien wrote:
Hi,
So I updated my guest from 5.1 to 5.8 via a complete yum update, many many packages BTW.
I shutdown the guest, change its "Disk bus" from IDE to Virtio and then upon boot, I get kernel panics as no disk can be found. I do get the splash screen at first however.
My guest has /dev/hda, should I change its fstab to reflect /dev/vda instead?
Thans in advance,
- aurf
CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Yes.. Or you can use LABELs. Any way might work. If it doesn't try to rebuild the initrd --with virtio_blk.
Hi,
I know you mentioned the labels before. They currently have labels so I will initrd it with the argument, thanks for that.
- aurf
On Apr 29, 2012, at 7:18 PM, Nux! wrote:
On 29.04.2012 23:49, aurfalien wrote:
Hi,
So I updated my guest from 5.1 to 5.8 via a complete yum update, many many packages BTW.
I shutdown the guest, change its "Disk bus" from IDE to Virtio and then upon boot, I get kernel panics as no disk can be found. I do get the splash screen at first however.
My guest has /dev/hda, should I change its fstab to reflect /dev/vda instead?
Thans in advance,
- aurf
CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Yes.. Or you can use LABELs. Any way might work. If it doesn't try to rebuild the initrd --with virtio_blk.
Hi,
That didn't work.
I did mkinitrd --with virtio_blk initrd-2.6.18-308.4.1.el5.img 2.6.8-308.4.1.el5
It boots fine as long as I leave the dik bus at IDE.
I even changed the fstab to use /dev/vda# rather then the labels.
- aurf
On 04/30/2012 07:09 AM, aurfalien wrote:
Hi,
That didn't work.
I did mkinitrd --with virtio_blk initrd-2.6.18-308.4.1.el5.img 2.6.8-308.4.1.el5
It boots fine as long as I leave the dik bus at IDE.
I even changed the fstab to use /dev/vda# rather then the labels.
Try this:
mkinitrd --with virtio_pci --with virtio_blk -f /boot/initrd-$(uname -r).img $(uname -r)
That is what I used when I switched to using virtio for both disk and networking.
Also, make sure you got the Virtio declaration correct:
<target dev='vda' bus='virtio'/>
On Apr 29, 2012, at 7:18 PM, Nux! wrote:
On 29.04.2012 23:49, aurfalien wrote:
Hi,
So I updated my guest from 5.1 to 5.8 via a complete yum update, many many packages BTW.
I shutdown the guest, change its "Disk bus" from IDE to Virtio and then upon boot, I get kernel panics as no disk can be found. I do get the splash screen at first however.
My guest has /dev/hda, should I change its fstab to reflect /dev/vda instead?
Thans in advance,
- aurf
CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Yes.. Or you can use LABELs. Any way might work. If it doesn't try to rebuild the initrd --with virtio_blk.
Hi,
I added a fe more args;
mkinitrd --with virtio_pci --with virtio_blk ---with virtio -f and it fixed.
Your reply caused me to dig around a bit.
Thanks for the help.
- aurf
-
aurfalien -
Benjamin Franz -
Nux!