Here again,
please excuse me for the late replays but the kernel compilation takes a lot
of time and I have to wait very much between one test and the other.
On 9 November 2011 04:35, jim burns <jim_burn@xxxxxxxxxxxxx> wrote:
> This won't work for another reason: 'extra=' is a pv config option for passing
> extra kernel options to the boot process, as reflected by /proc/cmdline. Only
> adding it to menu.lst would work, IF xen-fbfront is builtin, and the syntax is
> as Fajar suggested - xen-fbfront.video=32,1280,1024. If it is not builtin, you
> must use the /etc/modprobe.d approach.
OK, I am still actually compiling the kernel after having put the xen-fbfront as
module, in order to use the /etc/modprobe.d approach.
>
> However, beyond syntax problems. I doubt this would work at all in an hvm
> domu, as they don't use fbfront - that's a pv driver. (Fajar - you can verify
> this, right?)
Indeed it is just what I've thought too, but I did want to make tests even I
think that this is not the right way to proceed (what I am doing is of course
not recommended).
What am I doing?
1) I've got the vanilla sources (3.1.0) and extracted to /usr/src/
2) cp /boot/config-2.6.37.1-1.2-desktop /usr/src/linux/.config
3) make menuconfig
4) I selected all the modules needed by domU (including XEN_FBDEV):
CONFIG_XEN=y
CONFIG_XEN_DOM0=y
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_PVHVM=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=128
CONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
# CONFIG_XEN_DEBUG is not set
CONFIG_PCI_XEN=y
CONFIG_XEN_PCIDEV_FRONTEND=y
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_NETXEN_NIC=m
CONFIG_XEN_NETDEV_FRONTEND=y
CONFIG_INPUT_XEN_KBDDEV_FRONTEND=y
CONFIG_HVC_XEN=y
# CONFIG_XEN_WDT is not set
CONFIG_XEN_FBDEV_FRONTEND=y
# CONFIG_XEN_BALLOON is not set
# CONFIG_XEN_DEV_EVTCHN is not set
# CONFIG_XEN_BACKEND is not set
# CONFIG_XENFS is not set
# CONFIG_XEN_SYS_HYPERVISOR is not set
CONFIG_XEN_XENBUS_FRONTEND=y
# CONFIG_XEN_GNTDEV is not set
# CONFIG_XEN_GRANT_DEV_ALLOC is not set
# CONFIG_XEN_PLATFORM_PCI is not set
CONFIG_SWIOTLB_XEN=y
5) I compiled using make rpm
6) I installed the new kernel and rebooted with the option in menu.lst
I've written in my previous message.
After reboot, the only problem (apart the screen) is that xennet (or
similar) and another module
were not available. So the network didn't work (but this is another
issue). Let's concentrate on
the screen now.
Now, I am trying to recompile the kernel but setting the
XEN_FBDEV_FRONTEND as module.
Meanwhile I am replying you, it is still compiling.
> 'lspci -vvv' will tell you what driver is loaded for your video
> controller. Pls post the output of 'lspci -vvv -s video-device-number', and
> then for the driver mentioned at the end, post 'modinfo driver-name'.
# lspci -vvv -s 00:02.0
00:02.0 VGA compatible controller: Cirrus Logic GD 5446 (prog-if 00
[VGA controller])
Subsystem: XenSource, Inc. Device 0001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Region 0: Memory at f0000000 (32-bit, prefetchable) [size=32M]
Region 1: Memory at f3000000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at <unassigned> [disabled]
And it seems no kernel module is used! O_O
>
> A further note: if you ever intend to convert this domu to boot as a pv domu,
> the above syntax for /dev/disk-by-id won't work, since pv domus don't use
> qemu disks. (That's one of those device differences between pv and hvm domus I
> was talking about.) I suppose this is a worry for much further down the road.
> In my opensuse memu.lst, it is sufficient to say:
>
> kernel /vmlinuz root=/dev/system/root resume=/dev/system/swap [...]
OK.
For sure I am doing something wrong, even for the fact that I am using a domU
kernel in a hvm guest. Anyway I don't want to convert it as a pv domU.
I tried to install opensuse as a pv domu, but the installation doesn't
wont to start
for a screen problem (I mean the setup using qemu-system-x86_64).
>
> if you are using lvm, or simply /dev/sda?, where ?=partition number. Then
> /etc/fstab would have a similar problem, where you would have to use
> /dev/sda?, or /dev/disk/by-uuid. As I say, this is much further down the road.
I am not using lvm and this is my /etc/fstab:
/dev/disk/by-id/ata-QEMU_HARDDISK_QM00001-part1 swap
swap defaults 0 0
/dev/disk/by-id/ata-QEMU_HARDDISK_QM00001-part2 /
ext4 acl,user_xattr 1 1
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
> Btw, opensuse's kernel-xen-2.6.37 is still using the old xenlinux module
> names, even tho' it has modern modules like evtchn, gntdev and blktap2. It
> would appear that the framebuffer is built in (CONFIG_XEN_FRAMEBUFFER=y).
I tried to install kernel-xen-2.6.37.6-0.9.1 but no luck with it.
Actually, even the info says that: "This kernel can be used both as the domain0
("xen0") and as an unprivileged ("xenU") kernel." I tried to boot with it but:
1) it create an entry in menu.lst and it is for a dom0, since it
create the "kernel /xen.gz"
line, so it can't boot, since the hypervisor has noot been installed.
Furthermore, I don't
want to install the hypervisor, since it is a hvm domU.
2) if I delete the kernel line and I leave only the two following
(i.e. the kernel and the
initrd lines) the domU doesn't start.
So I decided to uninstall that kernel-xen package and to compile the
sources by myself.
On 9 November 2011 06:55, Fajar A. Nugraha <list@xxxxxxxxx> wrote:
> I lost track of what Flavio is using.
I hope that my previous clarifications were useful to get you on the right way
to understand what I am doing! ;-)
>
> Anyway, if it's PV, using something like
> "xen-fbfront.video=16,1280,1024" on kernel command line should work
> regardless whether its built-on or module. If it's module, you also
> have the option of using /etc/modprobe.d
>
> with stdvga=0, you'd get
>
> 00:02.0 VGA compatible controller: Cirrus Logic GD 5446 (prog-if 00
> [VGA controller])
> Subsystem: XenSource, Inc. Device 0001
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Region 0: Memory at f0000000 (32-bit, prefetchable) [size=32M]
> Region 1: Memory at f3000000 (32-bit, non-prefetchable) [size=4K]
> Expansion ROM at <unassigned> [disabled]
> Kernel modules: cirrusfb
>
> and starting X directly would get you lots of entries like this on Xorg.0.log
>
> [ 89.540] (II) CIRRUS(0): Not using default mode "1280x1024" (bad
> mode clock/interlace/doublescan)
> [ 89.540] (II) CIRRUS(0): Not using default mode "1600x1200"
> (insufficient memory for mode)
> [ 89.540] (II) CIRRUS(0): Not using default mode "800x600" (bad
> mode clock/interlace/doublescan)
>
> ... and
>
> [ 89.541] (--) CIRRUS(0): Virtual size is 1024x768 (pitch 1024)
> [ 89.542] (**) CIRRUS(0): *Default mode "1024x768": 65.0 MHz, 48.4
> kHz, 60.0 Hz
> [ 89.542] (II) CIRRUS(0): Modeline "1024x768"x60.0 65.00 1024
> 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
> [ 89.542] (**) CIRRUS(0): *Default mode "800x600": 40.0 MHz, 37.9
> kHz, 60.3 Hz
> [ 89.542] (II) CIRRUS(0): Modeline "800x600"x60.3 40.00 800 840
> 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
OK, but it's hvm. And I get nothing of that.
On 9 November 2011 09:27, jim burns <jim_burn@xxxxxxxxxxxxx> wrote:
> Flavio - besides the lspci and modinfo output I asked for, post your
> Xorg.0.log as well. Then I can compare it to what Fajar posted.
Of course, here we go: http://pastebin.com/d49wcUxD
In conclusion, I am aware that what I am doing is not properly
correct, and I would
simply be able to install a rpm kernel without compiling a new one
every time, because
it is something insane.
I've found this: http://forum.3tera.com/showthread.php?t=2161
Maybe there is some rpm ready to use, and to solve the problem, but I
would like to
try with the kernel I am still compiling now.
Cheers,
--
Flavio
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home