On Wed, Jul 08, 2009 at 01:22:30AM +0000, Lester M. wrote: > I downloaded the following rpms from M. Youngs fedora-people page. ( > http://fedorapeople.org/~myoung/dom0/<http://fedorapeople.org/%7Emyoun... ) > > kernel-firmware-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.noarch.rpm > kernel-headers-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i586.rpm > kernel-PAE-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.rpm > kernel-PAE-devel-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.rpm > > I am interested in *Testing* under the understanding that this is in beta. > My question is, after installation of the rpms, what configuration (config > files, grub, et al) is needed to successfully boot into dom0? I recall there > were a few hoops to jump through to get a working dom0. > > I also have compiled the xen3.4 tools (hg clone > http://xenbits.xensource.com/xen-3.4-testing.hg) > You could also get the xen 3.4.0 hypervisor/tools RPMs from rawhide.. although from that xen-3.4-testing.hg repo you'll get 3.4.1-rc6 atm with a lot of fixes after 3.4.0. (I think the plan was to upload xen 3.4.1 to F11, later when it has been released upstream.) > Could somebody please post a workflow for getting this running? I have > installed the rpms and I am now like "Now what?" :-P Modify your grub.conf to boot the xen hypervisor, add line /etc/fstab to mount xenfs and hmm.. I guess that's it :) See: http://wiki.xensource.com/xenwiki/XenParavirtOps Pasting from that page: Working example grub.conf with VGA text console: title Xen 3.4-unstable, kernel 2.6.30-rc3-tip root (hd0,0) kernel /boot/xen-3.4-unstable.gz dom0_mem=512M module /boot/vmlinuz-2.6.30-rc3-tip root=/dev/sda1 ro module /boot/initrd.img-2.6.30-rc3-tip -- Pasi

On Wed, Jul 08, 2009 at 10:05:55AM -0400, Lester M. wrote: > > Thank you Pasi, > > Here is what my grub.conf entry looks like (with the xen-3.4.1 tools > compiled,) after you install all 4 rpms from myoung's fedorapeople page: ( > http://fedorapeople.org/~myoung/dom0/<http://fedorapeople.org/%7Emyoun... > ) > > title Fedora (2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE) > root (hd0,0) > kernel /vmlinuz-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE ro > root=/dev/mapper/vg01-lv_root rhgb quiet nomodeset > initrd /initrd-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE.img > > > When you compile and install xen-3.4.1 the following is created in /boot: > > -rw-r--r--. 1 root root 498660 2009-07-07 17:08 xen-3.4.1-rc6.gz > lrwxrwxrwx. 1 root root 16 2009-07-07 17:08 xen-3.4.gz -> > xen-3.4.1-rc6.gz > lrwxrwxrwx. 1 root root 16 2009-07-07 17:08 xen-3.gz -> > xen-3.4.1-rc6.gz > lrwxrwxrwx. 1 root root 16 2009-07-07 17:08 xen.gz -> xen-3.4.1-rc6.gz > > > I modified it per the pvops wiki page: ( > http://wiki.xensource.com/xenwiki/XenParavirtOps) > > title Fedora (2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE) > root (hd0,0) > kernel /xen-3.4.1-rc6.gz dom0_mem=512M > module /vmlinuz-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE ro root=/dev/mapper/vg01-lv_root rhgb quiet > module /initrd-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE.img > > This looks correct.. > > This is what is in my /etc/fstab: > > none /proc/xen xenfs defaults 0 0 > > > So now I boot. When I boot the system the dom0 starts up instantly...., to > the point where it says "scrubbing free ram" then the screen goes blank and > all system activity ceases. > Hmm.. try removing the "rhgb quiet" from the vmlinuz line in grub.conf. Is the last line you see something like this?: (XEN) Scrubbing Free RAM: ..........done. You could also try adding "loglvl=all guest_loglvl=all noreboot" to the xen.gz line to grub.conf. So try with this grub.conf: title Fedora (2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE) root (hd0,0) kernel /xen-3.4.1-rc6.gz dom0_mem=512M loglvl=all guest_loglvl=all noreboot module /vmlinuz-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE ro root=/dev/mapper/vg01-lv_root module /initrd-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE.img > Has anyone tried these rpms? I am not sure if i can scream out "bug!" "bug!" > because I cannot find anyone that has actually installed these rpms as part > of a deployment process, (a workflow, a howto, a "step by step" edit "this" > or edit "that".) so I am not sure if it is that I am missing a config > parameter or not. > I've used self-compiled pv_ops dom0 successfully on my testing box, but I haven't really tried this RPMs.. If you don't

Hello Pasi, Unfortunately with adding "loglvl=all guest_loglvl=all noreboot" and removing "rhgb quiet" from the vmlinuz the result stayed the same. After the boot process gets to the "(XEN) Scrubbing Free RAM: ..........done." the screen still goes blank, and the system ceases to respond. This forces me to do a "hard reset" on my laptop. :-(

This is my grub entry with the "loglvl=all guest_loglvl=all noreboot" added: title Fedora (2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE) root (hd0,0) kernel /xen-3.4.1-rc6.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 module /vmlinuz-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE ro root=/dev/mapper/vg01-lv_root module /initrd-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE.img

When I set up a serial console and boot the system, the screen immediately goes "blank" and the system ceases to function as well. The difference is that this occurs sooner using the serial console than after the "(XEN) Scrubbing Free RAM: ..........done." occurrence.

This is my grub entry with the serial console setup from the xenpvops page: title Fedora (2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE) root (hd0,0) kernel /xen-3.4.1-rc6.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 module /vmlinuz-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE ro root=/dev/mapper/vg01-lv_root console=hvc0 earlyprintk=xen module /initrd-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE.img

So all of this works on your system and not mine. Unfortunately this is all the hardware I am able to test on at this time. I don't know how many people are running this xen configuration on a Lenovo T60 laptop but there is clearly something missing. What more should I test to get this working? :-) Anything goes at this point, but I do hope the developers / maintainers are reading this thread. :-P

On Wed, Jul 8, 2009 at 3:29 PM, Pasi Kärkkäinen <pasik(a)iki.fi&gt; wrote: > On Wed, Jul 08, 2009 at 02:05:35PM -0400, Lester M. wrote: > > > > Hello Pasi, > > > > Unfortunately with adding "loglvl=all guest_loglvl=all noreboot" and > > removing "rhgb quiet" from the vmlinuz the result stayed the same. > > > > After the boot process gets to the "(XEN) Scrubbing Free RAM: > > ..........done." the screen still goes blank, and the system ceases to > > respond. This forces me to do a "hard reset" on my laptop. :-( > > > > Hmm.. The boot process should look something like this: > > .. > (XEN) Scrubbing Free RAM: ..........done. > (XEN) Xen trace buffers: disabled > (XEN) Std. Loglevel: All > (XEN) Guest Loglevel: All > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input > to Xen) > (XEN) Freed 104kB init memory. > mapping kernel into physical memory > Xen: setup ISA identity maps > about to get started... > Reserving virtual address space above 0xf5800000 > PAT disabled on Xen > Initializing cgroup subsys cpuset > Initializing cgroup subsys cpu > Linux version 2.6.30-rc6-tip (root(a)dom0test.localdomain) (gcc version > 4.4.0 > 20090506 (Red Hat 4.4.0-4) (GCC) ) #15 SMP T > ue Jun 9 19:36:50 EEST 2009 > KERNEL supported cpus: > Intel GenuineIntel > AMD AuthenticAMD > NSC Geode by NSC > Cyrix CyrixInstead > Centaur CentaurHauls > Transmeta GenuineTMx86 > Transmeta TransmetaCPU > UMC UMC UMC UMC > BIOS-provided physical RAM map: > Xen: 0000000000000000 - 000000000009f400 (usable) > Xen: 000000000009f400 - 0000000000100000 (reserved) > Xen: 0000000000100000 - 0000000040000000 (usable) > Xen: 000000007f6e0000 - 000000007f6e3000 (ACPI NVS) > Xen: 000000007f6e3000 - 000000007f6f0000 (ACPI data) > Xen: 000000007f6f0000 - 000000007f700000 (reserved) > Xen: 00000000e0000000 - 00000000f0000000 (reserved) > Xen: 00000000fec00000 - 0000000100000000 (reserved) > console [xenboot0] enabled > > etc > > So the dom0 kernel should get booted up pretty shortly after that Scrubbing > Free RAM.. > > > > This is my grub entry with the "loglvl=all guest_loglvl=all noreboot" > added: > > > > title Fedora (2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE) > > root (hd0,0) > > kernel /xen-3.4.1-rc6.gz dom0_mem=1024M loglvl=all > guest_loglvl=all > > com1=19200,8n1 console=com1 > > module /vmlinuz-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE ro > > root=/dev/mapper/vg01-lv_root > > module /initrd-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE.img > > > > You shouldn't have the "com1=19200,8n1 console=com1" there if you want to > use > the VGA text console.. > > > > > > > When I set up a serial console and boot the system, the screen > immediately > > goes "blank" and the system ceases to function as well. The difference is > > that this occurs sooner using the serial console than after the "(XEN) > > Scrubbing Free RAM: ..........done." occurrence. > > > > When you have a serial console in use, the screen _should_ go blank > immediately, > because the console output is redirected to the serial port/console. > > So the behaviour you're seeing there is expected. > > > This is my grub entry with the serial console setup from the xenpvops > page: > > > > title Fedora (2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE) > > root (hd0,0) > > kernel /xen-3.4.1-rc6.gz dom0_mem=1024M loglvl=all > guest_loglvl=all > > com1=19200,8n1 console=com1 > > module /vmlinuz-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE ro > > root=/dev/mapper/vg01-lv_root console=hvc0 earlyprintk=xen > > module /initrd-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE.img > > > > That looks correct, if your laptop serial port actually is com1. > Do you see the Xen and dom0 kernel boot messages on the serial console? > > > > > So all of this works on your system and not mine. Unfortunately this is > all > > the hardware I am able to test on at this time. I don't know how many > people > > are running this xen configuration on a Lenovo T60 laptop but there is > > clearly something missing. > > > > What more should I test to get this working? :-) Anything goes at this > > point, but I do hope the developers / maintainers are reading this > thread. > > :-P > > Do you have to specify any non-default parameters to xen or dom0 kernel > when > you use RHEL 5.3 on the laptop? > > -- Pasi > Pasi, and M A Young; Thank you so much for the information thus far, I really appreciate the feedback in resolving this. :-) What Kernel options should I use to get a vga console? (to just have *everything* dump on my screen?) I do not have a "real" serial console on my consumer laptop.

On RHEL 5.3 I have no extra options than the defaults (which includes the "rhgb quiet" on the vmlinuz line), it just boots! I took a look at that earlier. I will try out your 32bit .config, did you get your kernel checkout from: (git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.gitlinux-2.6-xen) ? Also, did you use the latest branch? (from: git checkout origin/xen-tip/next -b xen-tip/next) ?

I downloaded the following rpms from M. Youngs fedora-people page. (http://fedorapeople.org/~myoung/dom0/) kernel-firmware-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.noarch.rpm kernel-headers-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i586.rpm kernel-PAE-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.rpm kernel-PAE-devel-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.rpm