Hi

I am trying out the PV-GRUB boot and having some problems.

Stock Fedora 15 build with kernels:

GNU GRUB version 0.97 (1048576K lower / 0K upper memory)

+-------------------------------------------------------------------------+
| Fedora (2.6.41.4-1.fc15.i686.PAE) |
| Fedora (2.6.38.6-27.fc15.i686.PAE) |
| |
| |

I selected the pv-grub-x86_32 kernel and made sure /dev/xvda was root:

I get this when I try to boot:

Booting 'Fedora (2.6.41.4-1.fc15.i686.PAE)'
[linode156033@dallas422 lish] !p
    Press enter to boot the selected OS, 'e' to edit the
  Booting 'Fedora (2.6.41.4-1.fc15.i686.PAE)'

root (hd0)
 Filesystem type is ext2fs, using whole disk
kernel /boot/vmlinuz-2.6.41.4-1.fc15.i686.PAE root=/dev/xvda console=tty0 conso
le=hvc0 ro
initrd /boot/initramfs-2.6.41.4-1.fc15.i686.PAE.img

close blk: backend at /local/domain/0/backend/vbd/373/51712
close blk: backend at /local/domain/0/backend/vbd/373/51728

Both kernels return the same output with no errors but don't boot and return a failed boot. Anyone have any ideas?

Thanks

James Turnbull

I had the same issue a few minutes ago the boot hung at that point, I shutdown and booted up again via the linode manager and it worked the second time (note the close blk: bits aren't errors they're normal)

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

I've tried a few times. I know the blk bits are normal but I get zero additional output in lish or via logview. Very strange.

Ah just spotted your problem, edit console=tty0 to console=hvc0

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

Nope sadly not. Tried that:

# boot=/dev/xvda
# kopt=root=/dev/xvda console=hvc0 ro quiet
# groot=(hd0)

default=0
timeout=5

title Fedora (2.6.41.4-1.fc15.i686.PAE)
        root (hd0)
        kernel /boot/vmlinuz-2.6.41.4-1.fc15.i686.PAE root=/dev/xvda console=hvc0 ro
        initrd /boot/initramfs-2.6.41.4-1.fc15.i686.PAE.img
title Fedora (2.6.38.6-27.fc15.i686.PAE)
        root (hd0)
        kernel /boot/vmlinuz-2.6.38.6-27.fc15.i686.PAE root=/dev/xvda console=hvc0 ro
        initrd /boot/initramfs-2.6.38.6-27.fc15.i686.PAE.img

And no joy.

Can you ssh in normally or ping your server so we can tell if it's actually booting and not displaying the list console or just not booting properly at all.

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

It's not booting at all. Can't ping or SSH to it and when it fails it drops me out of the Lish screen session.

Well that's about as much as I know about fedora without trying it myself hopefully someone else who uses fedora will pop up and be able to help.

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

No problems - thanks for trying.

It's weird because there's no error output which makes troubleshooting somewhat tricky.

Cheers

James

I assume you've had a read of this? http://library.linode.com/linode-platfo ... _fedora-15

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

That's what I based my config on.

I have the same issue with Centos 6.2.
The strange part is that it works on one linode (newark405) and not on another (newark394).

I think it's a problem with the hosting machine, not with the linode

It might be but difficult to test that. I am just disappointed I can't seem to get it working.