Hello! I managed to set up paravirtualized Gentoo 2007.0 on my Fedora Core7 amd64 Dom0 (2.6.20-2936.fc7xen kernel). I use pygrub, to boot Gentoo with fedora kernel and manually copied modules directory inside gentoo DomU image. Some problems (boot and 100% cpu usage by nash-hotplug) resolved by upgrading gentoo baselayout and making init.d script for killing nash on boot, plus added modules xennet and xenblk in autoload. But it seems to me very dirty approach. So the question is: do I always need to use exact fedora''s Dom0 kernel for DomUs for paravirtualization? Or I can make own gentoo domU kernel, like linux-2.6.20-xen-r5 and boot from it? Or it''s completely wrong? I tried to make gentoo linux-2.6.20-xen-r5 DomU kernel and boot from it, but couldn''t get vnc console up for that kernel, althought DomU was active and running. Also if I update Dom0 kernel, do I need to do it for my paravirtualized DomU''s too? ---------------------------------------------------------------- This message was sent from webmail.kndati.lv _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson
2007-Oct-16 15:37 UTC
Re: [Xen-users] paravirtualised gentoo on Fedora Core 7
> I managed to set up paravirtualized Gentoo 2007.0 on my Fedora Core7 amd64 > Dom0 (2.6.20-2936.fc7xen kernel). I use pygrub, to boot Gentoo with fedora > kernel and manually copied modules directory inside gentoo DomU image. Some > problems (boot and 100% cpu usage by nash-hotplug) resolved by upgrading > gentoo baselayout and making init.d script for killing nash on boot, plus > added modules xennet and xenblk in autoload. But it seems to me very dirty > approach. > > So the question is: do I always need to use exact fedora''s Dom0 > kernel for DomUs for paravirtualization? Or I can make own gentoo domU > kernel, like linux-2.6.20-xen-r5 and boot from it?That should work, yes. If a guest kernel requires newer features than your Xen offers (which is technically possible) then it mightn''t work. However, with compatibility code compiled into the guest kernel it''ll run even on rather old Xens. Since your Xen comes from Fedora 7 it''ll be fairly recent anyhow.> Or it''s completely > wrong? I tried to make gentoo linux-2.6.20-xen-r5 DomU kernel and boot from > it, but couldn''t get vnc console up for that kernel, althought DomU was > active and running.Well, that''s a start. Did you configure the Xen framebuffer device (and framebuffer console) into the kernel? If not then you wouldn''t be able to access the PV framebuffer from dom0.> Also if I update Dom0 kernel, do I need to do it for my paravirtualized > DomU''s too?No, they''re independent. Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
andris@lemon.lv
2007-Oct-16 18:23 UTC
Re: [Xen-users] paravirtualised gentoo on Fedora Core 7
Tank you for answer, I got some basic understanding... Yes indeed I hadn''t compiled a framebuffer support into my gentoo kernel. I added xen fb an console fb support and modified grub with video=vesafb:ywrap,mtrr:0 vga=0x311 (nothing know about mttr value :) ) Now I am able to get vnc screen at boot startup, but just till "Freeing unused kernel memory" line, further nothing... console hangs. At the same time DomU is still alive and booted. I can ssh into it. Something missed to add to kernel? andris Mark Williamson wrote:> Well, that''s a start. Did you configure the Xen framebuffer device (and > framebuffer console) into the kernel? If not then you wouldn''t be able to > access the PV framebuffer from dom0. >> Cheers, > Mark >---------------------------------------------------------------- This message was sent from webmail.kndati.lv _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson
2007-Oct-16 19:21 UTC
Re: [Xen-users] paravirtualised gentoo on Fedora Core 7
> Tank you for answer, > > I got some basic understanding... > > Yes indeed I hadn''t compiled a framebuffer support into my gentoo kernel. > I added xen fb an console fb support and modified grub with > video=vesafb:ywrap,mtrr:0 vga=0x311 (nothing know about mttr value :) )You shouldn''t need the vga= line for a paravirtualised kernel. My kernel is configured with video= set to "video=xenfb" to tell it explicitly to use the Xen Framebuffer. There isn''t a vesa framebuffer available to a paravirt guest.> Now I am able to get vnc screen at boot startup, but just till "Freeing > unused kernel memory" line, further nothing... console hangs. At the same > time DomU is still alive and booted. I can ssh into it. Something missed to > add to kernel?I wanted to make sure that would work first! Now we need to add to it... Add "console=tty1" to your kernel command line. This should tell the OS to output boot console output to tty1, which should display on the framebuffer console. Does that help? Cheers, Mark> > andris > > Mark Williamson wrote: > > Well, that''s a start. Did you configure the Xen framebuffer device (and > > framebuffer console) into the kernel? If not then you wouldn''t be able > > to access the PV framebuffer from dom0. > > > > > > Cheers, > > Mark > > ---------------------------------------------------------------- > This message was sent from webmail.kndati.lv > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson wrote:>> Tank you for answer, >> >> I got some basic understanding... >> >> Yes indeed I hadn''t compiled a framebuffer support into my gentoo kernel. >> I added xen fb an console fb support and modified grub with >> video=vesafb:ywrap,mtrr:0 vga=0x311 (nothing know about mttr value :) ) >> > > You shouldn''t need the vga= line for a paravirtualised kernel. My kernel is > configured with video= set to "video=xenfb" to tell it explicitly to use the > Xen Framebuffer. There isn''t a vesa framebuffer available to a paravirt > guest. > > >> Now I am able to get vnc screen at boot startup, but just till "Freeing >> unused kernel memory" line, further nothing... console hangs. At the same >> time DomU is still alive and booted. I can ssh into it. Something missed to >> add to kernel? >> > > I wanted to make sure that would work first! Now we need to add to it... > > Add "console=tty1" to your kernel command line. This should tell the OS to > output boot console output to tty1, which should display on the framebuffer > console. > > Does that help? > > Cheers, > Mark > > >> andris >> >> Mark Williamson wrote: >> >>> Well, that''s a start. Did you configure the Xen framebuffer device (and >>> framebuffer console) into the kernel? If not then you wouldn''t be able >>> to access the PV framebuffer from dom0. >>> >>> >>> Cheers, >>> Mark >>> >> ---------------------------------------------------------------- >> This message was sent from webmail.kndati.lv >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > > >Thanks for help, I read also this thread "Re: [Xen-users] dom0 no longer showing serial console output" , and modified my grub.conf accordingly. My kernel boot parameters now is kernel /boot/vmlinuz-2.6.20.r6-gentoo-xenU root=/dev/xvda video=xenfb console=ttyS0 xencons=ttyS vga=0x311 Now I am able to use vnc console, the only thing is that I do not see kernel boot messages any more, but only login prompt. Of course it is ok for me :). Then what method is used for fedora kernel? I put no kernel boot parameters for fedora kernel and see everything. I just want to understand howo kompile xen pv DomU kernel for everything to work properly. Sometimes it is useful to see kernel boot messages when something goes wrong. andris _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson wrote:>> Tank you for answer, >> >> I got some basic understanding... >> >> Yes indeed I hadn''t compiled a framebuffer support into my gentoo kernel. >> I added xen fb an console fb support and modified grub with >> video=vesafb:ywrap,mtrr:0 vga=0x311 (nothing know about mttr value :) ) >> > > You shouldn''t need the vga= line for a paravirtualised kernel. My kernel is > configured with video= set to "video=xenfb" to tell it explicitly to use the > Xen Framebuffer. There isn''t a vesa framebuffer available to a paravirt > guest. > > >> Now I am able to get vnc screen at boot startup, but just till "Freeing >> unused kernel memory" line, further nothing... console hangs. At the same >> time DomU is still alive and booted. I can ssh into it. Something missed to >> add to kernel? >> > > I wanted to make sure that would work first! Now we need to add to it... > > Add "console=tty1" to your kernel command line. This should tell the OS to > output boot console output to tty1, which should display on the framebuffer > console. > > Does that help? > > Cheers, > Mark > > >> andris >> >> Mark Williamson wrote: >> >>> Well, that''s a start. Did you configure the Xen framebuffer device (and >>> framebuffer console) into the kernel? If not then you wouldn''t be able >>> to access the PV framebuffer from dom0. >>> >>> >>> Cheers, >>> Mark >>> >> ---------------------------------------------------------------- >> This message was sent from webmail.kndati.lv >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > > >Thanks for help, I read also this thread "Re: [Xen-users] dom0 no longer showing serial console output" , and modified my grub.conf accordingly. My kernel boot parameters now is kernel /boot/vmlinuz-2.6.20.r6-gentoo-xenU root=/dev/xvda video=xenfb console=ttyS0 xencons=ttyS vga=0x311 Now I am able to use vnc console, the only thing is that I do not see kernel boot messages any more, but only login prompt. Of course it is ok for me :). Then what method is used for fedora kernel? I put no kernel boot parameters for fedora kernel and see everything. I just want to understand howo kompile xen pv DomU kernel for everything to work properly. Sometimes it is useful to see kernel boot messages when something goes wrong. andris _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson
2007-Oct-19 13:37 UTC
Re: [Xen-users] paravirtualised gentoo on Fedora Core 7
> I read also this thread "Re: [Xen-users] dom0 no longer showing serial > console output" , and modified my grub.conf accordingly. > My kernel boot parameters now is kernel > /boot/vmlinuz-2.6.20.r6-gentoo-xenU root=/dev/xvda video=xenfb > console=ttyS0 xencons=ttyS vga=0x311 > Now I am able to use vnc console, the only thing is that I do not see > kernel boot messages any more, but only login prompt. Of course it is > ok for me :).You shouldn''t need the vga= bit, since there''s no real or emulated VGA going on for a PV guest. The way you''ve set up console= and xencons= the boot messages will probably be going to the domain''s virtual serial console (use xm console or xm create -c to access this). If you want them to appear on the framebuffer console, change your "console=" line to "console=tty1". Does that work? Cheers, Mark> Then what method is used for fedora kernel? I put no kernel boot > parameters for fedora kernel and see everything. I just want to > understand howo kompile xen pv DomU kernel for everything to work > properly. Sometimes it is useful to see kernel boot messages when > something goes wrong. > > andris > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson wrote:>> I read also this thread "Re: [Xen-users] dom0 no longer showing serial >> console output" , and modified my grub.conf accordingly. >> My kernel boot parameters now is kernel >> /boot/vmlinuz-2.6.20.r6-gentoo-xenU root=/dev/xvda video=xenfb >> console=ttyS0 xencons=ttyS vga=0x311 >> Now I am able to use vnc console, the only thing is that I do not see >> kernel boot messages any more, but only login prompt. Of course it is >> ok for me :). >> > > You shouldn''t need the vga= bit, since there''s no real or emulated VGA going > on for a PV guest. > > The way you''ve set up console= and xencons= the boot messages will probably be > going to the domain''s virtual serial console (use xm console or xm create -c > to access this). If you want them to appear on the framebuffer console, > change your "console=" line to "console=tty1". > > Does that work? > > Cheers, > Mark >Thanks, Now it works as expected. /boot/vmlinuz-2.6.20.r6-gentoo-xenU root=/dev/xvda console=tty1 xencons=ttyS andris _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users