[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [fedora-virt] pv_ops dom0 kernel RPM, configuration & setup help anyone?



On Wed, Jul 8, 2009 at 10:49 AM, Pasi Kärkkäinen <pasik iki fi> wrote:
On Wed, Jul 08, 2009 at 05:45:53PM +0300, Pasi Kärkkäinen wrote:
> 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/%7Emyoung/dom0/>
> > )
> >
> > 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
>

Heh.. forgot to finish this sentence. If you're having problems getting the
console output from xen and/or pv_ops dom0 kernel, you should set up a
serial console.

There are instructions for that on the XenParavirtOps wiki page.

-- Pasi

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

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]