------- Comment #4 from johneed@xxxxxxxxxxx 2011-08-29 10:43 -------
Hi again. The line vfb has a sl different trouble
kernel = "/boot/vmlinuz-2.6.38-gentoo-r6"
memory = 1524
name = "trial"
vif = [ 'mac=e6:1b:4e:4c:d8:66, bridge=virbr0' ]
disk = [ 'file:/mnt/karmic/xen/gentoo64/disk.img,xvda,w',
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
root = "/dev/xvda2 ro earlyprintk=xen video=uvesafb raid=noautodetect
#extra = "2 console=hvc0"
extra = "(hd0,0)/grub/menu.lst console=hvc0"
vfb = [ 'vnc=1' ]
Point 1., gentoo style, no initramfs.
Point 2. The imagefile has part 1 a boot partition and part 2 /root.
Your suggested change has taken pv-grub out of the equation.
Trying a few variations, I get a black screen in the vnc console of the vm.
Checking the performance tab, it is doing something around 95%.
This prob. means it's not displaying the menu.lst, so it may or may not boot.
Without a grub display, I can't tell. Perhaps you can tweak this .cfg file to
make it display grub at the boot.
I have copied the guest gentoo kernel to host /boot which am pretty sure
amounts to what you were attempting to achieve.
pv-grub can load grub with extra="(hd0,0)/grub/menu.lst.
Taking pv-grub out takes away that loading of grub.
Point 3, gentoo still uses for reasons unknown grub 1. While I can emerge
grub2, have not done so on the basis that grub1 ought work without issue.
Point 4. what of the vkbd driver?
Error ENOENT when reading the backend path device/vkbd/0/backend
is the essence of the failure.
Curiously in the gentoo minimal install cd .iso, this driver of xen is not even
listed in its kernel 2.6.39 config.
The gentoo guest is 2.6.38 and the input VKBD driver is set.
It is CONFIG_XEN_KBDDEV_FRONTEND.
I would not have thought an input driver like this would interfere so???
I am about to try with another kernel
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
Xen-bugs mailing list