http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1779
Summary: pv-grub in xen-4.1.0 cannot boot kernel in graphical
mode (vfb)
Product: Xen
Version: unstable
Platform: x86-64
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Linux-pv_ops domU
AssignedTo: xen-bugs@lists.xensource.com
ReportedBy: johneed@hotmail.com
Have a gentoo64 guest made with a stable kernel 2.6.38-r6 compiled in pvops
mode.
Have adjusted the kernel config extensively. It now boots to a console in the
host gentoo console.
# This PV domU can be started after you finishes the installation under HVM
mode.
name = 'gentoo64'
# Virtual FrameBuffer + extra configuration
# vfb = [ 'type=vnc,vncdisplay=20' ]
extra = '(hd0,0)/grub/menu.lst console=hvc0'
kernel = '/usr/lib64/xen/boot/pv-grub-x86_64.gz'
memory = '1256'
disk = [ 'file:/mnt/karmic/xen/gentoo64/disk.img,xvda,w' ]
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
vif = [ 'mac=e6:1b:4e:4c:d8:66, bridge=virbr0' ]
On inquiry in irc, discovered a number of past entries in xen-devel re this
flaw.
On using the vfb, the grub list is displayed in the vnc console with the entry
extra = '(hd0,0)/grub/menu.lst console=hvc0'
in the .cfg file. On selecting the kernel, results in either a hang (freeze)
or a reboot. On selecting 'c' to a grub console, the kernel never is setup.
selecting root (hd0,0) yields result as expected
selecting kernel /vmlinuz-version ......
yields a blank line. ie. the kernel is recognized by grub but is never setup
with loading a address. On selecting 'b' to boot, it does not boot.
De-selecting the vfb entry in the .cfg file, or commenting out the vfb line,
and booting with xm create -c does get to boot it, but ofcourse is restricted
to a system console. There is the option of installing a vnc server, but the
aim is to get pv-grub to boot as it should with vfb.
from a host console, one can acquire the following
idella@gentoo64 ~ $ sudo xm create -c PVM-gen.cfg
Using config file "/etc/xen/PVM-gen.cfg".
Started domain gentoo64 (id=82)
Xen Minimal OS!
start_info: 0xc15000(VA)
nr_pages: 0x4e800
shared_inf: 0xbbd96000(MA)
pt_base: 0xc18000(VA)
nr_pt_frames: 0xb
mfn_list: 0x9a1000(VA)
mod_start: 0x0(VA)
mod_len: 0
flags: 0x0
cmd_line: (hd0,0)/grub/menu.lst console=hvc0
stack: 0x9609e0-0x9809e0
MM: Init
_text: 0x0(VA)
_etext: 0x6fccf(VA)
_erodata: 0x8a000(VA)
_edata: 0x92c60(VA)
stack start: 0x9609e0(VA)
_end: 0x9a0fe0(VA)
start_pfn: c26
max_pfn: 4e800
Mapping memory range 0x1000000 - 0x4e800000
setting 0x0-0x8a000 readonly
skipped 0x1000
GNU GRUB version 0.97 (1286144K lower / 0K upper memory)
[. Minimal BASH-like line editing is supported. For
the first word, TAB lists possible command
completions. Anywhere else TAB lists the possible
completions of a device/filename. ESC at any time
exits. ]
grubdom> root (hd0,0)
Error ENOENT when reading the backend path device/vkbd/0/backend
Thread "kbdfront" exited.
This line has a number of entries in the xen-devel archives. They all appear
to pertain to the use of pv-grub, just as I am using. I cannot find an entry
that offers a resolution.
Instead of hanging, it boots
grubdom> kernel /vmlinuz-2.6.38-gentoo-r6 ro console=hvc0 root=/dev/xvda2
video=uvesafb
grubdom> boot
close blk: backend=/local/domain/0/backend/vbd/82/51712 node=device/vbd/51712
.............................
It is still missing the line that sets up the kernel to a loading address.
So the resultant boot is absent of vnc or sdl graphical.
The host's
gentoo64 grub # uname -r
3.0.0-gentoo-amd64
I could add kernel configs and such; to keep it short, will wait for your
perusal and request for more config info.
The hypervisor is
/boot/xen-4.1.0-rc7-pre.gz
--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
Summary: pv-grub in xen-4.1.0 cannot boot kernel in graphical
mode (vfb)
Product: Xen
Version: unstable
Platform: x86-64
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Linux-pv_ops domU
AssignedTo: xen-bugs@lists.xensource.com
ReportedBy: johneed@hotmail.com
Have a gentoo64 guest made with a stable kernel 2.6.38-r6 compiled in pvops
mode.
Have adjusted the kernel config extensively. It now boots to a console in the
host gentoo console.
# This PV domU can be started after you finishes the installation under HVM
mode.
name = 'gentoo64'
# Virtual FrameBuffer + extra configuration
# vfb = [ 'type=vnc,vncdisplay=20' ]
extra = '(hd0,0)/grub/menu.lst console=hvc0'
kernel = '/usr/lib64/xen/boot/pv-grub-x86_64.gz'
memory = '1256'
disk = [ 'file:/mnt/karmic/xen/gentoo64/disk.img,xvda,w' ]
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
vif = [ 'mac=e6:1b:4e:4c:d8:66, bridge=virbr0' ]
On inquiry in irc, discovered a number of past entries in xen-devel re this
flaw.
On using the vfb, the grub list is displayed in the vnc console with the entry
extra = '(hd0,0)/grub/menu.lst console=hvc0'
in the .cfg file. On selecting the kernel, results in either a hang (freeze)
or a reboot. On selecting 'c' to a grub console, the kernel never is setup.
selecting root (hd0,0) yields result as expected
selecting kernel /vmlinuz-version ......
yields a blank line. ie. the kernel is recognized by grub but is never setup
with loading a address. On selecting 'b' to boot, it does not boot.
De-selecting the vfb entry in the .cfg file, or commenting out the vfb line,
and booting with xm create -c does get to boot it, but ofcourse is restricted
to a system console. There is the option of installing a vnc server, but the
aim is to get pv-grub to boot as it should with vfb.
from a host console, one can acquire the following
idella@gentoo64 ~ $ sudo xm create -c PVM-gen.cfg
Using config file "/etc/xen/PVM-gen.cfg".
Started domain gentoo64 (id=82)
Xen Minimal OS!
start_info: 0xc15000(VA)
nr_pages: 0x4e800
shared_inf: 0xbbd96000(MA)
pt_base: 0xc18000(VA)
nr_pt_frames: 0xb
mfn_list: 0x9a1000(VA)
mod_start: 0x0(VA)
mod_len: 0
flags: 0x0
cmd_line: (hd0,0)/grub/menu.lst console=hvc0
stack: 0x9609e0-0x9809e0
MM: Init
_text: 0x0(VA)
_etext: 0x6fccf(VA)
_erodata: 0x8a000(VA)
_edata: 0x92c60(VA)
stack start: 0x9609e0(VA)
_end: 0x9a0fe0(VA)
start_pfn: c26
max_pfn: 4e800
Mapping memory range 0x1000000 - 0x4e800000
setting 0x0-0x8a000 readonly
skipped 0x1000
GNU GRUB version 0.97 (1286144K lower / 0K upper memory)
[. Minimal BASH-like line editing is supported. For
the first word, TAB lists possible command
completions. Anywhere else TAB lists the possible
completions of a device/filename. ESC at any time
exits. ]
grubdom> root (hd0,0)
Error ENOENT when reading the backend path device/vkbd/0/backend
Thread "kbdfront" exited.
This line has a number of entries in the xen-devel archives. They all appear
to pertain to the use of pv-grub, just as I am using. I cannot find an entry
that offers a resolution.
Instead of hanging, it boots
grubdom> kernel /vmlinuz-2.6.38-gentoo-r6 ro console=hvc0 root=/dev/xvda2
video=uvesafb
grubdom> boot
close blk: backend=/local/domain/0/backend/vbd/82/51712 node=device/vbd/51712
.............................
It is still missing the line that sets up the kernel to a loading address.
So the resultant boot is absent of vnc or sdl graphical.
The host's
gentoo64 grub # uname -r
3.0.0-gentoo-amd64
I could add kernel configs and such; to keep it short, will wait for your
perusal and request for more config info.
The hypervisor is
/boot/xen-4.1.0-rc7-pre.gz
--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs