CentOS - May 2017 - CentOS 7 cloned VM cannot boot

On 5/5/2017 1:19 ??, Gianluca Cecchi wrote:
> Could you verify, if /dev/sda is your boot disk, with the command
>
> fdisk -l /dev/sda
> ?
It's /dev/vda in my case:

# fdisk -l /dev/vda

Disk /dev/vda: 21.5 GB, 21474836480 bytes, 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x942d1f03

   Device Boot    Start      End   Blocks Id System
dev/vdal   *      2048  1026047   512000 83 Linux
dev/vda2   *   1026048 41943039 20458496 8e Linux LVM

Hmm, it seems that the boot flag should be removed from /dev/vda2 
partition? (How we do that?)
> BTW: are you using virt-manager to configure/run your VMs? Or direct virsh
> commans or what?
It's a hosted VPS service, and I have a virtual console to the VM.

Thanks,
Nick

On 5/5/2017 1:42 ??, Nikolaos Milas wrote:
> Hmm, it seems that the boot flag should be removed from /dev/vda2 
> partition?
Actually, I tried this and left the boot flag only to /dev/vda1. I 
rebooted and I am still getting the same error. :-(

I was hoping we were close to a solution...

Nick

On Fri, May 5, 2017 at 12:52 PM, Nikolaos Milas <nmilas at noa.gr> wrote:
> On 5/5/2017 1:42 ??, Nikolaos Milas wrote:
>
> Hmm, it seems that the boot flag should be removed from /dev/vda2
>> partition?
>>
>
> Actually, I tried this and left the boot flag only to /dev/vda1. I
> rebooted and I am still getting the same error. :-(
>
> I was hoping we were close to a solution...
>
>
> Nick
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
what do you get when you boot the VM (I imagine with supergrub2 you
described) and run this

lspci
lspci -kn

in particular in respect with scsi devices ad kernel modules used
eg in a VM of mine under oVirt

[root at ractorshe ~]# lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton
II]
00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton
II] (rev 01)
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:02.0 Unclassified device [00ff]: Red Hat, Inc Virtio RNG
00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
00:04.0 SCSI storage controller: Red Hat, Inc Virtio SCSI
00:05.0 Communication controller: Red Hat, Inc Virtio console
00:06.0 SCSI storage controller: Red Hat, Inc Virtio block device
[root at ractorshe ~]#


[root at ractorshe ~]# lspci -kn
00:00.0 0600: 8086:1237 (rev 02)
Subsystem: 1af4:1100
00:01.0 0601: 8086:7000
Subsystem: 1af4:1100
00:01.1 0101: 8086:7010
Subsystem: 1af4:1100
Kernel driver in use: ata_piix
Kernel modules: ata_piix, pata_acpi, ata_generic
00:01.2 0c03: 8086:7020 (rev 01)
Subsystem: 1af4:1100
Kernel driver in use: uhci_hcd
00:01.3 0680: 8086:7113 (rev 03)
Subsystem: 1af4:1100
Kernel driver in use: piix4_smbus
Kernel modules: i2c_piix4
00:02.0 00ff: 1af4:1005
Subsystem: 1af4:0004
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci
00:03.0 0200: 1af4:1000
Subsystem: 1af4:0001
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci
00:04.0 0100: 1af4:1004
Subsystem: 1af4:0008
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci
00:05.0 0780: 1af4:1003
Subsystem: 1af4:0003
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci
00:06.0 0100: 1af4:1001
Subsystem: 1af4:0002
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci
[root at ractorshe ~]#