James B. Byrne
2015-Mar-18 13:59 UTC
[CentOS] Kernel panic when adding partitioned virtio disk
I have a cloned kvm (that I can now get started following a shutdown and reboot of the hypervisor host). When it starts with its original virtio disk there is no problem. If I create a virtio disk and add it via virt-manager it also boots without issue, although one cannot see the new 'physical' disk. If I shutodwon the kvm guest, partition the new virtio disk, and reboot the guest then I see this: Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.32-504.12.2.el6.x86_64 #1 Call Trace: [ffffffff8152933c] ? panic+0xa7/0x16f [ffffffff8107a5f2] ? do_exit+0x862/0x870 [ffffffff8118fa25] ? fput+0x25/0x30 [ffffffff8107a658] ? do_group-exit+0x58/0xd0 [ffffffff8107a6e7] ? sys_exit_group+0x17/0x20 [ffffffff8100b072] ? system_call_fastpath+0x16/0x1b Does anyone have any idea what partitioning does to cause this behaviour? I have deleted and recreated the virtio disk several times with differing sizes and it always comes down to whether or not the disk is partitioned. I have added virtio disks to other kvm guests in the same fashion many times and have never run into this. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3
m.roth at 5-cent.us
2015-Mar-18 14:59 UTC
[CentOS] Kernel panic when adding partitioned virtio disk
Hi, James, James B. Byrne wrote:> I have a cloned kvm (that I can now get started following a shutdown > and reboot of the hypervisor host). When it starts with its original > virtio disk there is no problem. If I create a virtio disk and add it > via virt-manager it also boots without issue, although one cannot see > the new 'physical' disk. If I shutodwon the kvm guest, partition the > new virtio disk, and reboot the guest then I see this: > > Kernel panic - not syncing: Attempted to kill init!<snip> Now, admittedly, a) I really haven't been following this thread, and b) haven't worked a lot with VMs, and not with KVM, but could you clarify something for me? Are you trying to make the virtual root disk larger, or are you creating a new one, and just adding it the the VM, like mounting another drive on an existing system? If the latter, can't you mount it? Oh, and is the new virtual drive formatted? mark