| View previous topic :: View next topic |
| Author |
Message |
direwolf
Tux's lil' helper
Joined: 11 Jun 2003
Posts: 90
Location: Richmond, VA
|
 Posted: Wed Jul 04, 2012 8:06 pm Post subject: Gentoo KVM host cannot boot Gentoo guest |
 |
|
I have just had the most frustrating couple of days ever using KVM virtualization.
I've been using a Gentoo host for years to host several VMs, including many Windows flavors, various Linux distributions, etc. So I decided to P2V one of my physical Gentoo servers. Massive fail! There seems to be no way to boot this thing, or I am missing something very fundamental.
The Gentoo installation ISO boots just fine. I created a QCOW2 disk and copied all the files (yes, ALL) from my physical server disk to the QCOW2 image. I LILO'd the boot when everything was in place, but it will not boot, every time giving me the same logically inconsistent message:
| Code: |
List of all partitions:
0800 146800640 sda driver: sd
0801 146799616 sda1 00000000-0000-0000-0000-000000000000
0810 146800640 sdb driver: sd
0b00 1048575 sr0 driver: sr
No filesystem could mount root, tried: ext3 vfat msdos iso9660
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,0)
|
I've been through all the kernel settings, and I could have missed something, but the message above seems to indicate everything is correct.
I'm stuck on this. Anybody have a Gentoo guest running in Gentoo KVM host? I think it just won't work.
_________________
========================================================
"Somebody has to do something, and it's just incredibly pathetic that it has to be us."
- Jerry Garcia |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 29983
Location: 56N 3W
|
| Posted: Wed Jul 04, 2012 8:18 pm Post subject: |
|
|
direwolf,
I have hardened gentoo guests running in a hardended gentoo host. I'm having problems with the latest libvirtd not wanting to see any guests but thats not your problem.
I don't even get as far as a failed boot in the guests.
Your QCOW image appears as /dev/sda and has one partition that the kernel can see at /dev/sda1.
The error shows that the kernel is trying to mount /dev/sda (the entire disk) as root, not the first partition, which is what you probably intended.
LILO gives me the willies. Look at your /etc/lilo.conf file. What do you have in the append= statement.
If it looks right, did you run /sbin/lilo ?
Run /sbin/lilo anyway. Fix the append= if you need to.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
direwolf
Tux's lil' helper
Joined: 11 Jun 2003
Posts: 90
Location: Richmond, VA
|
| Posted: Wed Jul 04, 2012 9:03 pm Post subject: |
|
|
Good catch! I knew it had to be something obvious I had missed - I was converting it from md0 to a sda1 so I guess I edited the lilo.conf wrong. Dumb.
So I'm past THAT error (progress), and now it just hangs after mounting root read-only (!!), and I gotta figure out all the module config changes I *actually* need...
Thanks!
_________________
========================================================
"Somebody has to do something, and it's just incredibly pathetic that it has to be us."
- Jerry Garcia |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
