I installed xen-3.0.3 in Fedora Core 6, the guest OS can be boot up, but it can not enter the KDE or GNOME though I set the run level to 5 in the configuration file. The kernel is 2.6.16-xen0 in domain0 and 2.6.16-xenU in guest domain. The disk of the guest OS is a img file which containes the whole copy of the Fedora Core 6 installed in the host. Is there any way to solve this problem? It''s not comfortable for me without the GUI environment. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 1/31/07, Henning Sprang <henning_sprang@gmx.de> wrote:> On 1/31/07, Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote: > > You have CONFIG_FB switched on though, right? Otherwise the above will fail. > > This is all correct - But still the same. I will try again later, but > I think I run out of ideas what might be wrong...Hmm, only one thing that I might change: Mark, on which distribution did you test it for dom0 and domU? I have all major ones available here for testing, and might try the same combination as you did. Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > This is all correct - But still the same. I will try again later, but > > I think I run out of ideas what might be wrong... > > Hmm, only one thing that I might change: > > Mark, on which distribution did you test it for dom0 and domU? > I have all major ones available here for testing, and might try the > same combination as you did.I used CentOS 4.4 in both, but I don''t think it''s probably worth you reinstalling just to get this working... there must be something going on in the config somewhere... Any chance you could stick your kernel image on the web somewhere, then let me know privately where it is? I''ll try booting it on my system and see if the framebuffer works there - that should narrow things down somewhat! 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
On 2/1/07, Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote:> Any chance you could stick your kernel image on the web somewhere, then let me > know privately where it is? I''ll try booting it on my system and see if the > framebuffer works there - that should narrow things down somewhat!Just wanted to do this, but looked at it again first: I now started a SuSE domU on the same system, and after a while I got some output in the sdl window(I also started to think it doesn''t work, it seems to take w ahile until output is redirected to that console). the first time the sdl window crashed after I tried to enter login data, the second time I had other problems, but that''s probably due to the fact that this image is generally broken. So it can be assumed that it''s not a kernel issue, but maybe some setting inside the domU. I''m gonna try again now with a new debian domU and see what happens, otherwise I''ll create a clean SuSE domU and try to find why the one works and the other not. Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/4/07, Henning Sprang <henning_sprang@gmx.de> wrote:> I''m gonna try again now with a new debian domU and see what happens, > otherwise I''ll create a clean SuSE domU and try to find why the one > works and the other not.Yes. It Works with a default debian vm without any changes to any console settings. So all the config changes described here aren''t necessary for me. Not sure if these settings made oit not work, or if I just did not wait long enough, because it takes some time until something show up on the screen. Can be that I did never wait long enough. A problem that remains is that when using sdl the sdl windows crashes quite easily. VNC seems to do better. And I have some local/keymap issues. In SDL I seem to have some english keymap, and I know how to handle this with my german keyboard. On VNC I seem to have a german keymap, but some keys are twisted. For example, but that''s not all, shift-7 should give me a backslash, but it gives a question mark. (the key that is supposed to give me a question mark gives one, also). A bit strange... _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/4/07, Henning Sprang <henning_sprang@gmx.de> wrote:> A problem that remains is that when using sdl the sdl windows crashes > quite easily. VNC seems to do better. And I have some local/keymap > issues. In SDL I seem to have some english keymap, and I know how to > handle this with my german keyboard. On VNC I seem to have a german > keymap, but some keys are twisted. For example, but that''s not all, > shift-7 should give me a backslash, but it gives a question mark. (the > key that is supposed to give me a question mark gives one, also). > A bit strange... >Hmm, and starting X with this seems also not really to work. I guess I give up now, seems the current stable solution is defintely using vnc or trying some other way. Will look at this in 3.0.5 or .6 again :) Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi all, I did get also the black screen using sdl. I suspect not correctly loading of the xenkbd driver in domU. Tested this with a centOS 4.4 DomU, running in a FC 6 Dom0 and centos4.4 Dom0. It works in both the overall xen linux kernel, as the xen0 and xenU kernels. In short the solution is to compile both xenfb and xenkbd as module, put them in the initrd to load at system startup. The problem I still have when using the --preload=xenfb and --preload=xenkbd, is that the xenkbd is not loaded. When i add the xenkbd module manually in the deps list of xenfb, it works without manual intervention. When inserting the xenfb and xenkbd modules manually in the domU kernel, a restart of the /usr/lib/xen/bin/sldfb --domid <number> --title <window title> could be needed to get rid of the black screen. I''ve include a more detailed description of my compilation steps for the FC6 dom0 setup. Here I opted for the xen0 and xenU approach. (note: this is specific for my setup, so please adapt) I hope this solves the black screen issue. In my setup I have a resolution of 800x600. I would like it higher, so this is the next issue to solve. Greetings Johan On Thu, 2007-01-04 at 14:28 +0000, Mark Williamson wrote:> Assuming you guys are having problems with X in the domu... > > 3.0.3 doesn''t have support for a graphical framebuffer. The most > straightforward way to get graphical apps to run would be to connect to the > domain from dom0 using ssh -X so that graphical apps are displayed within > your dom0 desktop. This is just treating the domUs as if they were separate > machines. > > 3.0.4 contains support for a graphical framebuffer so you can run X within the > guest directly. > > I''ve written some instructions below for you guys, in case you want to try > this. There might be mistakes, or omissions, so please please exercise > caution! Feel free to ask on anything you''re not sure about. > > You''d need to upgrade to 3.0.4, edit Config.mk to change XENFB_TOOLS to =y and > do a make-install tools. This''ll give you the dom0 components for accessing > the framebuffer. > > The, compile a domU kernel with framebuffer support in (it''s selectable in the > kernel menuconfig). If you want to be able to run virtual terminals on the > framebuffer, you''d also need to select the generic Linux options for the > framebuffer console. I''d recommend you do this. > > Configure the domain to run a getty on /dev/ttyS0, add the following line > to /etc/inittab, just after the lines starting the other gettys on your > system: > S0:2345:respawn:/sbin/mingetty ttyS0 > > add ttyS0 to /etc/securetty or /etc/securettys (whichever you have). This is > to enable root login on ttyS0. > > Once this is done, change your config file for the domain to include the > following: > > add "xencons=ttyS0 console=ttyS0 video=xenfb" > > This redirects your console to go through ttyS0, where you''re now running a > getty. > > Now add the following to the domain''s config file: > vfb=[''type=sdl''] > to get a local display of the domain''s framebuffer > > *or* > > vfb=[''type=vnc''] > to export the display over VNC. Change this to: > vfb=[''type=vnc,vnclisten=ipaddr''] > substituting the ip address of an interface, if you want the VNC server to > listen to connections on some network (default is to listen on localhost). > > Now try booting the domain and see if it works :-) For VNC, the display will > be exported on port 5900 + domain_id. > > If anything doesn''t work and you want to get back into the guest in > the "normal" way, just remove the "xencons=ttyS0 console=ttyS0 video=xenfb" > and the vfb= line from its config file and you should be able to boot it > normally. Otherwise, you could mount the guest''s filesystem directly (after > shutting it down!!!!!) and fix config there. > > Again, these instructions might include mistakes, or omissions, so please > please exercise caution! Feel free to ask on anything you''re not sure about. > > If you try it, please let us know how it works (or if it doesn''t!) > > Hope that helps you some. > > Cheers, > Mark > > On Thursday 04 January 2007 09:47, Andrew McGregor wrote: > > Hi, > > > > Are you saying a DomU cannot load X or the Dom0? > > > > Andy > > > > Thomas Miller wrote: > > > I am having the same problem on openSuse 10.2 . Hope someone can help > > > us out ;-) > > > > > > chenbin wrote: > > >> I installed xen-3.0.3 in Fedora Core 6, the guest OS can be boot up, > > >> but it can not enter the KDE or GNOME though I set the run level to 5 > > >> in the configuration file. > > >> The kernel is 2.6.16-xen0 in domain0 and 2.6.16-xenU in guest > > >> domain. The disk of the guest OS is a img file which containes the > > >> whole copy of the Fedora Core 6 installed in the host. > > >> > > >> Is there any way to solve this problem? It''s not comfortable for me > > >> without the GUI environment. > > >> ------------------------------------------------------------------------ > > >> > > >> _______________________________________________ > > >> Xen-users mailing list > > >> Xen-users@lists.xensource.com > > >> http://lists.xensource.com/xen-users > > >> > > >> __________ NOD32 1924 (20061215) Information __________ > > >> > > >> This message was checked by NOD32 antivirus system. > > >> http://www.eset.com > > > > > > -- > > > Thomas Miller > > > Chrome Portal Project Manager > > > CPCUG Programmers SIG Chairperson (formally Delphi) > > > Delphi Client/Server Certified Developer > > > BSS Accounting & Distribution Software > > > BSS Enterprise Accounting FrameWork > > > > > > http://www.bss-software.com > > > http://programmers.cpcug.org/ > > > http://sourceforge.net/projects/chromeportal/ > > > http://sourceforge.net/projects/uopl/ > > > http://sourceforge.net/projects/dbexpressplus > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Daniel P. Berrange
2007-Mar-19 13:46 UTC
Re: [Xen-users] how to start X in the guest domain
On Mon, Mar 19, 2007 at 02:40:00PM +0100, Johan De Wit wrote:> In my setup I have a resolution of 800x600. I would like it higher, so > this is the next issue to solve.Not gonna change without a serious amount of coding. The paravirt framebuffer driver is fixed to be 800x600x32 in guest kernel code & the Dom0 daemons. To make it changable on the fly, or even at compile time will require re-writing major parts of the kernel & userspace stack for the PVFB. Certainly this would be a desirable & welcome patch, but don''t expect it to be easy.... Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, Only a nice to ... And far above m,y capability to DIY (Y = me) Greetings Johan On Mon, 2007-03-19 at 13:46 +0000, Daniel P. Berrange wrote:> On Mon, Mar 19, 2007 at 02:40:00PM +0100, Johan De Wit wrote: > > In my setup I have a resolution of 800x600. I would like it higher, so > > this is the next issue to solve. > > Not gonna change without a serious amount of coding. The paravirt framebuffer > driver is fixed to be 800x600x32 in guest kernel code & the Dom0 daemons. To > make it changable on the fly, or even at compile time will require re-writing > major parts of the kernel & userspace stack for the PVFB. Certainly this would > be a desirable & welcome patch, but don''t expect it to be easy.... > > Regards, > Dan._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users