Hi all, I''m trying to expand the screen resolution of my guest when using vnc. It appears I need to use the extra variable in my guest config file and xenfb. I pass it in like this: extra = ''xenfb.video=8,1024,768'' I can see this being passed to the kernel when it boots but it doesn''t change the vnc screen resolution. I also see this when I type ps -ef | grep vnc # ps -ef | grep vnc root 7187 2103 0 10:18 ? 00:00:04 /usr/lib/xen-4.0/bin/qemu-dm -d 6 -serial pty -domain-name ubuntuWork -videoram 4 -vnc 0.0.0.0:1-vncunused -M xenpv root 7445 2688 0 10:46 pts/0 00:00:00 grep vnc So it appears the video ram is still 4MB. Here''s the line for vnc in my guest config file. vfb = [ ''type=vnc,vncdisplay=1,vnclisten=0.0.0.0'' ] My using Xen 4.0, Debian Squeeze for my dom0 and Ubuntu Maverick for the guest. Thanks! Ted On Fri, Feb 25, 2011 at 9:16 AM, Fajar A. Nugraha <list@fajar.net> wrote:> On Fri, Feb 25, 2011 at 9:20 PM, Ted Brenner <griztown@gmail.com> wrote: > >> Although personally I like xrdp or NX better than vnc, the consep is > >> the same: you run it domU instead of relying on Xen''s vfb. > >> > > > > Thanks. How are these differ performance wise? Is vnc through Xen > faster? > > How does these compare graphically to say, running an OS in Virtual Box? > > If you''re going to use it for desktop/laptop then I suggest go with > virtualbox instead. It''s far ahead of Xen, being able to do seamless > and scale desktop. > > Acessing vnc/xrdp/nx running in a domU is no different than acessing > vnc/xrdp/nx running in a physical server on the network. Good, but not > as good as virtualbox''s seamless window. > > vnc access thru domU''s vfb should really only be use for > administrative purposes. Sometimes you''ll get mismatched mouse pointer > or other problems. > > -- > Fajar >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Is it possible that in Xen 4.0+, the ''xenfb.video'' should be added to the kernel line of the /boot/grub/menu.lst file? On Sun, Feb 27, 2011 at 10:49 AM, Ted Brenner <griztown@gmail.com> wrote:> Hi all, > > I''m trying to expand the screen resolution of my guest when using vnc. It > appears I need to use the extra variable in my guest config file and xenfb. > I pass it in like this: > > extra = ''xenfb.video=8,1024,768'' > > I can see this being passed to the kernel when it boots but it doesn''t > change the vnc screen resolution. I also see this when I type ps -ef | grep > vnc > > # ps -ef | grep vnc > root 7187 2103 0 10:18 ? 00:00:04 > /usr/lib/xen-4.0/bin/qemu-dm -d 6 -serial pty -domain-name ubuntuWork > -videoram 4 -vnc 0.0.0.0:1 -vncunused -M xenpv > root 7445 2688 0 10:46 pts/0 00:00:00 grep vnc > > So it appears the video ram is still 4MB. Here''s the line for vnc in my > guest config file. > > vfb = [ ''type=vnc,vncdisplay=1,vnclisten=0.0.0.0'' ] > > My using Xen 4.0, Debian Squeeze for my dom0 and Ubuntu Maverick for the > guest. > > Thanks! > Ted > > On Fri, Feb 25, 2011 at 9:16 AM, Fajar A. Nugraha <list@fajar.net> wrote: > >> On Fri, Feb 25, 2011 at 9:20 PM, Ted Brenner <griztown@gmail.com> wrote: >> >> Although personally I like xrdp or NX better than vnc, the consep is >> >> the same: you run it domU instead of relying on Xen''s vfb. >> >> >> > >> > Thanks. How are these differ performance wise? Is vnc through Xen >> faster? >> > How does these compare graphically to say, running an OS in Virtual Box? >> >> If you''re going to use it for desktop/laptop then I suggest go with >> virtualbox instead. It''s far ahead of Xen, being able to do seamless >> and scale desktop. >> >> Acessing vnc/xrdp/nx running in a domU is no different than acessing >> vnc/xrdp/nx running in a physical server on the network. Good, but not >> as good as virtualbox''s seamless window. >> >> vnc access thru domU''s vfb should really only be use for >> administrative purposes. Sometimes you''ll get mismatched mouse pointer >> or other problems. >> >> -- >> Fajar >> > > > >-- Ted Brenner _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Feb 28, 2011 at 10:15 AM, Ted Brenner <griztown@gmail.com> wrote:> Is it possible that in Xen 4.0+, the ''xenfb.video'' should be added to the > kernel line of the /boot/grub/menu.lst file? > > On Sun, Feb 27, 2011 at 10:49 AM, Ted Brenner <griztown@gmail.com> wrote: >> >> Hi all, >> >> I''m trying to expand the screen resolution of my guest when using vnc. It >> appears I need to use the extra variable in my guest config file and xenfb. >> I pass it in like this: >> >> extra = ''xenfb.video=8,1024,768'' >> >> I can see this being passed to the kernel when it boots but it doesn''t >> change the vnc screen resolution.Thanks for pointing out that parameter. There are three parts answer to your question. The first part, being how to pass a parameter to kernel. That would depend on how you boot domU: - If you use pygrub/pv-grub, then the correct way to pass it would be to edit domU''s grub config file (or some other config file that is used to generate it, like /etc/default/grub). - If you use pygrub, you might be able to use "args" to add it without editing domU''s grub config file - If you use "kernel" and "ramdisk", then the right way to add it is on "extra" line (which should already contain things like "root=") You can check with "cat /proc/cmdline" inside domU to see if the parameter is correctly passed to domU kernel. The second part is where to put the parameter: - If xen vfb support is compiled built-in in domU kernel, then the only place to pass it is on domU kernel command line, using one oh the three options mentioned above - If xen vfb support is built as a module, you can pass it on domU kernel command line, or by simply creating a .conf file on /etc/modprobe.d (recommended) The third part is what''s the correct module name, and what parameter to pass. In Ubuntu maverick, the module name is xen-fbfront. $ modinfo xen-fbfront filename: /lib/modules/2.6.35-25-generic/kernel/drivers/video/xen-fbfront.ko alias: xen:vfb license: GPL description: Xen virtual framebuffer device frontend srcversion: 0EB34742ACF8D2559403034 depends: fb_sys_fops,syscopyarea,sysfillrect,sysimgblt vermagic: 2.6.35-25-generic SMP mod_unload modversions parm: video:Video memory size in MB, width, height in pixels (default 2,800,600) (array of int) So considering all three parts, if you use Ubuntu maverick and want to use 1280x1024, you can just create a file like this: $ cat /etc/modprobe.d/xen-fbfront.conf options xen-fbfront video=32,1280,1024 A "depmod -a" and "update-initramfs -u" might be needed afterwards. After reboot, it should correctly use 1280x1024 resolution. I still say you should use things like NX/xrdp/vnc server inside domU though (my favorite is xrdp). It''s smooth, easy to install (apt-get install xrdp), can allow you to choose different resolution without having to reboot (just specify the desired resolution and color depth when you connect), and allows you to have multiple GUI session to the client (using idfferent user-resolution-depth combination) -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks Fajar! This is a big help. I tried xrdp but there were a few issues. If I used tightvncserver it would connect but then crash immediately. If I used vnc4server, I couldn''t connect from dom0 but could from my wife''s laptop. But even when I connected it was very slow. One thought I had was to use this parameter to pass in more video memory than 4MB hoping that would helping things out. Perhaps there is a better way to do this? The other issue I had with this approach is that I was trying to use vpn in the guest. Once the vpn is connected, the xrdp connection gets dropped. Perhaps I shouldn''t be running vpn in a guest or using VirtualBox instead. Can you use VirtualBox on a xen server? Do they play well together? Thanks again! I''ll test this out tonight and let you know how it works. On Sun, Feb 27, 2011 at 10:27 PM, Fajar A. Nugraha <list@fajar.net> wrote:> On Mon, Feb 28, 2011 at 10:15 AM, Ted Brenner <griztown@gmail.com> wrote: > > Is it possible that in Xen 4.0+, the ''xenfb.video'' should be added to the > > kernel line of the /boot/grub/menu.lst file? > > > > On Sun, Feb 27, 2011 at 10:49 AM, Ted Brenner <griztown@gmail.com> > wrote: > >> > >> Hi all, > >> > >> I''m trying to expand the screen resolution of my guest when using vnc. > It > >> appears I need to use the extra variable in my guest config file and > xenfb. > >> I pass it in like this: > >> > >> extra = ''xenfb.video=8,1024,768'' > >> > >> I can see this being passed to the kernel when it boots but it doesn''t > >> change the vnc screen resolution. > > Thanks for pointing out that parameter. > > There are three parts answer to your question. > > The first part, being how to pass a parameter to kernel. That would > depend on how you boot domU: > - If you use pygrub/pv-grub, then the correct way to pass it would be > to edit domU''s grub config file (or some other config file that is > used to generate it, like /etc/default/grub). > - If you use pygrub, you might be able to use "args" to add it without > editing domU''s grub config file > - If you use "kernel" and "ramdisk", then the right way to add it is > on "extra" line (which should already contain things like "root=") > You can check with "cat /proc/cmdline" inside domU to see if the > parameter is correctly passed to domU kernel. > > The second part is where to put the parameter: > - If xen vfb support is compiled built-in in domU kernel, then the > only place to pass it is on domU kernel command line, using one oh the > three options mentioned above > - If xen vfb support is built as a module, you can pass it on domU > kernel command line, or by simply creating a .conf file on > /etc/modprobe.d (recommended) > > The third part is what''s the correct module name, and what parameter > to pass. In Ubuntu maverick, the module name is xen-fbfront. > $ modinfo xen-fbfront > filename: > /lib/modules/2.6.35-25-generic/kernel/drivers/video/xen-fbfront.ko > alias: xen:vfb > license: GPL > description: Xen virtual framebuffer device frontend > srcversion: 0EB34742ACF8D2559403034 > depends: fb_sys_fops,syscopyarea,sysfillrect,sysimgblt > vermagic: 2.6.35-25-generic SMP mod_unload modversions > parm: video:Video memory size in MB, width, height in pixels > (default 2,800,600) (array of int) > > > So considering all three parts, if you use Ubuntu maverick and want to > use 1280x1024, you can just create a file like this: > $ cat /etc/modprobe.d/xen-fbfront.conf > options xen-fbfront video=32,1280,1024 > > A "depmod -a" and "update-initramfs -u" might be needed afterwards. > After reboot, it should correctly use 1280x1024 resolution. > > I still say you should use things like NX/xrdp/vnc server inside domU > though (my favorite is xrdp). It''s smooth, easy to install (apt-get > install xrdp), can allow you to choose different resolution without > having to reboot (just specify the desired resolution and color depth > when you connect), and allows you to have multiple GUI session to the > client (using idfferent user-resolution-depth combination) > > -- > Fajar >-- Ted Brenner _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
So I made these changes but now I get the following error after typing in #xm vncviewer domainID invoking vncviewer 0.0.0.0:1 No protocol specified Error: Can''t open display: :0.0 I''m currently listening on 0.0.0.0 but I''ve also tried 127.0.0.1 with the same affect. What would cause this error? On Sun, Feb 27, 2011 at 10:27 PM, Fajar A. Nugraha <list@fajar.net> wrote:> On Mon, Feb 28, 2011 at 10:15 AM, Ted Brenner <griztown@gmail.com> wrote: > > Is it possible that in Xen 4.0+, the ''xenfb.video'' should be added to the > > kernel line of the /boot/grub/menu.lst file? > > > > On Sun, Feb 27, 2011 at 10:49 AM, Ted Brenner <griztown@gmail.com> > wrote: > >> > >> Hi all, > >> > >> I''m trying to expand the screen resolution of my guest when using vnc. > It > >> appears I need to use the extra variable in my guest config file and > xenfb. > >> I pass it in like this: > >> > >> extra = ''xenfb.video=8,1024,768'' > >> > >> I can see this being passed to the kernel when it boots but it doesn''t > >> change the vnc screen resolution. > > Thanks for pointing out that parameter. > > There are three parts answer to your question. > > The first part, being how to pass a parameter to kernel. That would > depend on how you boot domU: > - If you use pygrub/pv-grub, then the correct way to pass it would be > to edit domU''s grub config file (or some other config file that is > used to generate it, like /etc/default/grub). > - If you use pygrub, you might be able to use "args" to add it without > editing domU''s grub config file > - If you use "kernel" and "ramdisk", then the right way to add it is > on "extra" line (which should already contain things like "root=") > You can check with "cat /proc/cmdline" inside domU to see if the > parameter is correctly passed to domU kernel. > > The second part is where to put the parameter: > - If xen vfb support is compiled built-in in domU kernel, then the > only place to pass it is on domU kernel command line, using one oh the > three options mentioned above > - If xen vfb support is built as a module, you can pass it on domU > kernel command line, or by simply creating a .conf file on > /etc/modprobe.d (recommended) > > The third part is what''s the correct module name, and what parameter > to pass. In Ubuntu maverick, the module name is xen-fbfront. > $ modinfo xen-fbfront > filename: > /lib/modules/2.6.35-25-generic/kernel/drivers/video/xen-fbfront.ko > alias: xen:vfb > license: GPL > description: Xen virtual framebuffer device frontend > srcversion: 0EB34742ACF8D2559403034 > depends: fb_sys_fops,syscopyarea,sysfillrect,sysimgblt > vermagic: 2.6.35-25-generic SMP mod_unload modversions > parm: video:Video memory size in MB, width, height in pixels > (default 2,800,600) (array of int) > > > So considering all three parts, if you use Ubuntu maverick and want to > use 1280x1024, you can just create a file like this: > $ cat /etc/modprobe.d/xen-fbfront.conf > options xen-fbfront video=32,1280,1024 > > A "depmod -a" and "update-initramfs -u" might be needed afterwards. > After reboot, it should correctly use 1280x1024 resolution. > > I still say you should use things like NX/xrdp/vnc server inside domU > though (my favorite is xrdp). It''s smooth, easy to install (apt-get > install xrdp), can allow you to choose different resolution without > having to reboot (just specify the desired resolution and color depth > when you connect), and allows you to have multiple GUI session to the > client (using idfferent user-resolution-depth combination) > > -- > Fajar >-- Ted Brenner _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
That''s an X Windows error (Can''t open display). What is your DISPLAY set to? Are you running an X Server? Mel On Tue, Mar 1, 2011 at 6:51 PM, Ted Brenner <griztown@gmail.com> wrote:> So I made these changes but now I get the following error after typing in > #xm vncviewer domainID > > invoking vncviewer 0.0.0.0:1 > No protocol specified > Error: Can''t open display: :0.0 > > I''m currently listening on 0.0.0.0 but I''ve also tried 127.0.0.1 with the > same affect. What would cause this error? > > On Sun, Feb 27, 2011 at 10:27 PM, Fajar A. Nugraha <list@fajar.net> wrote: >> >> On Mon, Feb 28, 2011 at 10:15 AM, Ted Brenner <griztown@gmail.com> wrote: >> > Is it possible that in Xen 4.0+, the ''xenfb.video'' should be added to >> > the >> > kernel line of the /boot/grub/menu.lst file? >> > >> > On Sun, Feb 27, 2011 at 10:49 AM, Ted Brenner <griztown@gmail.com> >> > wrote: >> >> >> >> Hi all, >> >> >> >> I''m trying to expand the screen resolution of my guest when using vnc. >> >> It >> >> appears I need to use the extra variable in my guest config file and >> >> xenfb. >> >> I pass it in like this: >> >> >> >> extra = ''xenfb.video=8,1024,768'' >> >> >> >> I can see this being passed to the kernel when it boots but it doesn''t >> >> change the vnc screen resolution. >> >> Thanks for pointing out that parameter. >> >> There are three parts answer to your question. >> >> The first part, being how to pass a parameter to kernel. That would >> depend on how you boot domU: >> - If you use pygrub/pv-grub, then the correct way to pass it would be >> to edit domU''s grub config file (or some other config file that is >> used to generate it, like /etc/default/grub). >> - If you use pygrub, you might be able to use "args" to add it without >> editing domU''s grub config file >> - If you use "kernel" and "ramdisk", then the right way to add it is >> on "extra" line (which should already contain things like "root=") >> You can check with "cat /proc/cmdline" inside domU to see if the >> parameter is correctly passed to domU kernel. >> >> The second part is where to put the parameter: >> - If xen vfb support is compiled built-in in domU kernel, then the >> only place to pass it is on domU kernel command line, using one oh the >> three options mentioned above >> - If xen vfb support is built as a module, you can pass it on domU >> kernel command line, or by simply creating a .conf file on >> /etc/modprobe.d (recommended) >> >> The third part is what''s the correct module name, and what parameter >> to pass. In Ubuntu maverick, the module name is xen-fbfront. >> $ modinfo xen-fbfront >> filename: >> /lib/modules/2.6.35-25-generic/kernel/drivers/video/xen-fbfront.ko >> alias: xen:vfb >> license: GPL >> description: Xen virtual framebuffer device frontend >> srcversion: 0EB34742ACF8D2559403034 >> depends: fb_sys_fops,syscopyarea,sysfillrect,sysimgblt >> vermagic: 2.6.35-25-generic SMP mod_unload modversions >> parm: video:Video memory size in MB, width, height in pixels >> (default 2,800,600) (array of int) >> >> >> So considering all three parts, if you use Ubuntu maverick and want to >> use 1280x1024, you can just create a file like this: >> $ cat /etc/modprobe.d/xen-fbfront.conf >> options xen-fbfront video=32,1280,1024 >> >> A "depmod -a" and "update-initramfs -u" might be needed afterwards. >> After reboot, it should correctly use 1280x1024 resolution. >> >> I still say you should use things like NX/xrdp/vnc server inside domU >> though (my favorite is xrdp). It''s smooth, easy to install (apt-get >> install xrdp), can allow you to choose different resolution without >> having to reboot (just specify the desired resolution and color depth >> when you connect), and allows you to have multiple GUI session to the >> client (using idfferent user-resolution-depth combination) >> >> -- >> Fajar > > > > -- > Ted Brenner > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Melody Bliss Usenix, SAGE and LOPSA Charter Member Patron Member of the NRA _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yeah, I can connect via rdesktop. I''m running gnome, this is an ubuntu maverick guest. Where would I find what my display is set to? Thanks for the help! On Tue, Mar 1, 2011 at 9:30 PM, Melody Bliss <melodybliss@gmail.com> wrote:> That''s an X Windows error (Can''t open display). What is your DISPLAY > set to? Are you running an X Server? > > Mel > > On Tue, Mar 1, 2011 at 6:51 PM, Ted Brenner <griztown@gmail.com> wrote: > > So I made these changes but now I get the following error after typing in > > #xm vncviewer domainID > > > > invoking vncviewer 0.0.0.0:1 > > No protocol specified > > Error: Can''t open display: :0.0 > > > > I''m currently listening on 0.0.0.0 but I''ve also tried 127.0.0.1 with the > > same affect. What would cause this error? > > > > On Sun, Feb 27, 2011 at 10:27 PM, Fajar A. Nugraha <list@fajar.net> > wrote: > >> > >> On Mon, Feb 28, 2011 at 10:15 AM, Ted Brenner <griztown@gmail.com> > wrote: > >> > Is it possible that in Xen 4.0+, the ''xenfb.video'' should be added to > >> > the > >> > kernel line of the /boot/grub/menu.lst file? > >> > > >> > On Sun, Feb 27, 2011 at 10:49 AM, Ted Brenner <griztown@gmail.com> > >> > wrote: > >> >> > >> >> Hi all, > >> >> > >> >> I''m trying to expand the screen resolution of my guest when using > vnc. > >> >> It > >> >> appears I need to use the extra variable in my guest config file and > >> >> xenfb. > >> >> I pass it in like this: > >> >> > >> >> extra = ''xenfb.video=8,1024,768'' > >> >> > >> >> I can see this being passed to the kernel when it boots but it > doesn''t > >> >> change the vnc screen resolution. > >> > >> Thanks for pointing out that parameter. > >> > >> There are three parts answer to your question. > >> > >> The first part, being how to pass a parameter to kernel. That would > >> depend on how you boot domU: > >> - If you use pygrub/pv-grub, then the correct way to pass it would be > >> to edit domU''s grub config file (or some other config file that is > >> used to generate it, like /etc/default/grub). > >> - If you use pygrub, you might be able to use "args" to add it without > >> editing domU''s grub config file > >> - If you use "kernel" and "ramdisk", then the right way to add it is > >> on "extra" line (which should already contain things like "root=") > >> You can check with "cat /proc/cmdline" inside domU to see if the > >> parameter is correctly passed to domU kernel. > >> > >> The second part is where to put the parameter: > >> - If xen vfb support is compiled built-in in domU kernel, then the > >> only place to pass it is on domU kernel command line, using one oh the > >> three options mentioned above > >> - If xen vfb support is built as a module, you can pass it on domU > >> kernel command line, or by simply creating a .conf file on > >> /etc/modprobe.d (recommended) > >> > >> The third part is what''s the correct module name, and what parameter > >> to pass. In Ubuntu maverick, the module name is xen-fbfront. > >> $ modinfo xen-fbfront > >> filename: > >> /lib/modules/2.6.35-25-generic/kernel/drivers/video/xen-fbfront.ko > >> alias: xen:vfb > >> license: GPL > >> description: Xen virtual framebuffer device frontend > >> srcversion: 0EB34742ACF8D2559403034 > >> depends: fb_sys_fops,syscopyarea,sysfillrect,sysimgblt > >> vermagic: 2.6.35-25-generic SMP mod_unload modversions > >> parm: video:Video memory size in MB, width, height in pixels > >> (default 2,800,600) (array of int) > >> > >> > >> So considering all three parts, if you use Ubuntu maverick and want to > >> use 1280x1024, you can just create a file like this: > >> $ cat /etc/modprobe.d/xen-fbfront.conf > >> options xen-fbfront video=32,1280,1024 > >> > >> A "depmod -a" and "update-initramfs -u" might be needed afterwards. > >> After reboot, it should correctly use 1280x1024 resolution. > >> > >> I still say you should use things like NX/xrdp/vnc server inside domU > >> though (my favorite is xrdp). It''s smooth, easy to install (apt-get > >> install xrdp), can allow you to choose different resolution without > >> having to reboot (just specify the desired resolution and color depth > >> when you connect), and allows you to have multiple GUI session to the > >> client (using idfferent user-resolution-depth combination) > >> > >> -- > >> Fajar > > > > > > > > -- > > Ted Brenner > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > > -- > Melody Bliss > Usenix, SAGE and LOPSA Charter Member > Patron Member of the NRA >-- Ted Brenner _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
in the shell you''re executing "xm vncviewer domainID", you can type echo $DISPLAY is it set to anything? if it looks something like this bash-3.2$ echo $DISPLAY :0.0 then your X Windows display is set to localhost. If this is a remote machine (not your local machine), then this won''t work for you. You need to export the display back to your local machine. So, starting from my local desktop, connect to the remote (xen dom0) using "ssh -Y" (for trusted X11 forwarding). For example, if your remote (dom0) system is called xenhost, use ssh -Y root@xenhost This will enable (hopefully if it''s allowed) X11 forwarding back to your desktop over an encrypted ssh session and allow you to do your "xm vncviewer domID" successfully. Mel On Tue, Mar 1, 2011 at 7:30 PM, Melody Bliss <melodybliss@gmail.com> wrote:> That''s an X Windows error (Can''t open display). What is your DISPLAY > set to? Are you running an X Server? > > Mel > > On Tue, Mar 1, 2011 at 6:51 PM, Ted Brenner <griztown@gmail.com> wrote: >> So I made these changes but now I get the following error after typing in >> #xm vncviewer domainID >> >> invoking vncviewer 0.0.0.0:1 >> No protocol specified >> Error: Can''t open display: :0.0 >> >> I''m currently listening on 0.0.0.0 but I''ve also tried 127.0.0.1 with the >> same affect. What would cause this error? >> >> On Sun, Feb 27, 2011 at 10:27 PM, Fajar A. Nugraha <list@fajar.net> wrote: >>> >>> On Mon, Feb 28, 2011 at 10:15 AM, Ted Brenner <griztown@gmail.com> wrote: >>> > Is it possible that in Xen 4.0+, the ''xenfb.video'' should be added to >>> > the >>> > kernel line of the /boot/grub/menu.lst file? >>> > >>> > On Sun, Feb 27, 2011 at 10:49 AM, Ted Brenner <griztown@gmail.com> >>> > wrote: >>> >> >>> >> Hi all, >>> >> >>> >> I''m trying to expand the screen resolution of my guest when using vnc. >>> >> It >>> >> appears I need to use the extra variable in my guest config file and >>> >> xenfb. >>> >> I pass it in like this: >>> >> >>> >> extra = ''xenfb.video=8,1024,768'' >>> >> >>> >> I can see this being passed to the kernel when it boots but it doesn''t >>> >> change the vnc screen resolution. >>> >>> Thanks for pointing out that parameter. >>> >>> There are three parts answer to your question. >>> >>> The first part, being how to pass a parameter to kernel. That would >>> depend on how you boot domU: >>> - If you use pygrub/pv-grub, then the correct way to pass it would be >>> to edit domU''s grub config file (or some other config file that is >>> used to generate it, like /etc/default/grub). >>> - If you use pygrub, you might be able to use "args" to add it without >>> editing domU''s grub config file >>> - If you use "kernel" and "ramdisk", then the right way to add it is >>> on "extra" line (which should already contain things like "root=") >>> You can check with "cat /proc/cmdline" inside domU to see if the >>> parameter is correctly passed to domU kernel. >>> >>> The second part is where to put the parameter: >>> - If xen vfb support is compiled built-in in domU kernel, then the >>> only place to pass it is on domU kernel command line, using one oh the >>> three options mentioned above >>> - If xen vfb support is built as a module, you can pass it on domU >>> kernel command line, or by simply creating a .conf file on >>> /etc/modprobe.d (recommended) >>> >>> The third part is what''s the correct module name, and what parameter >>> to pass. In Ubuntu maverick, the module name is xen-fbfront. >>> $ modinfo xen-fbfront >>> filename: >>> /lib/modules/2.6.35-25-generic/kernel/drivers/video/xen-fbfront.ko >>> alias: xen:vfb >>> license: GPL >>> description: Xen virtual framebuffer device frontend >>> srcversion: 0EB34742ACF8D2559403034 >>> depends: fb_sys_fops,syscopyarea,sysfillrect,sysimgblt >>> vermagic: 2.6.35-25-generic SMP mod_unload modversions >>> parm: video:Video memory size in MB, width, height in pixels >>> (default 2,800,600) (array of int) >>> >>> >>> So considering all three parts, if you use Ubuntu maverick and want to >>> use 1280x1024, you can just create a file like this: >>> $ cat /etc/modprobe.d/xen-fbfront.conf >>> options xen-fbfront video=32,1280,1024 >>> >>> A "depmod -a" and "update-initramfs -u" might be needed afterwards. >>> After reboot, it should correctly use 1280x1024 resolution. >>> >>> I still say you should use things like NX/xrdp/vnc server inside domU >>> though (my favorite is xrdp). It''s smooth, easy to install (apt-get >>> install xrdp), can allow you to choose different resolution without >>> having to reboot (just specify the desired resolution and color depth >>> when you connect), and allows you to have multiple GUI session to the >>> client (using idfferent user-resolution-depth combination) >>> >>> -- >>> Fajar >> >> >> >> -- >> Ted Brenner >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > > > -- > Melody Bliss > Usenix, SAGE and LOPSA Charter Member > Patron Member of the NRA >-- Melody Bliss Usenix, SAGE and LOPSA Charter Member Patron Member of the NRA _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Fajar, I was able to get this working with video=32,1280,1024. What are the limits on these numbers? Is the 32MB actually using 32MB of the RAM on my video card or just taking 32MB from system ram? Could I pass in something like video=128,1280,1024 or even 128,1680,1050? I''ve tried the latter and it tells my the rectangle is too large. Are there any websites out there with instructions for using this functionality? I''m only planning on using this for one of my VMs since I''d like to vpn from that VM. I''ll definitely stick with xrdp for the rest. Thanks again for all your help, Ted On Sun, Feb 27, 2011 at 10:27 PM, Fajar A. Nugraha <list@fajar.net> wrote:> On Mon, Feb 28, 2011 at 10:15 AM, Ted Brenner <griztown@gmail.com> wrote: > > Is it possible that in Xen 4.0+, the ''xenfb.video'' should be added to the > > kernel line of the /boot/grub/menu.lst file? > > > > On Sun, Feb 27, 2011 at 10:49 AM, Ted Brenner <griztown@gmail.com> > wrote: > >> > >> Hi all, > >> > >> I''m trying to expand the screen resolution of my guest when using vnc. > It > >> appears I need to use the extra variable in my guest config file and > xenfb. > >> I pass it in like this: > >> > >> extra = ''xenfb.video=8,1024,768'' > >> > >> I can see this being passed to the kernel when it boots but it doesn''t > >> change the vnc screen resolution. > > Thanks for pointing out that parameter. > > There are three parts answer to your question. > > The first part, being how to pass a parameter to kernel. That would > depend on how you boot domU: > - If you use pygrub/pv-grub, then the correct way to pass it would be > to edit domU''s grub config file (or some other config file that is > used to generate it, like /etc/default/grub). > - If you use pygrub, you might be able to use "args" to add it without > editing domU''s grub config file > - If you use "kernel" and "ramdisk", then the right way to add it is > on "extra" line (which should already contain things like "root=") > You can check with "cat /proc/cmdline" inside domU to see if the > parameter is correctly passed to domU kernel. > > The second part is where to put the parameter: > - If xen vfb support is compiled built-in in domU kernel, then the > only place to pass it is on domU kernel command line, using one oh the > three options mentioned above > - If xen vfb support is built as a module, you can pass it on domU > kernel command line, or by simply creating a .conf file on > /etc/modprobe.d (recommended) > > The third part is what''s the correct module name, and what parameter > to pass. In Ubuntu maverick, the module name is xen-fbfront. > $ modinfo xen-fbfront > filename: > /lib/modules/2.6.35-25-generic/kernel/drivers/video/xen-fbfront.ko > alias: xen:vfb > license: GPL > description: Xen virtual framebuffer device frontend > srcversion: 0EB34742ACF8D2559403034 > depends: fb_sys_fops,syscopyarea,sysfillrect,sysimgblt > vermagic: 2.6.35-25-generic SMP mod_unload modversions > parm: video:Video memory size in MB, width, height in pixels > (default 2,800,600) (array of int) > > > So considering all three parts, if you use Ubuntu maverick and want to > use 1280x1024, you can just create a file like this: > $ cat /etc/modprobe.d/xen-fbfront.conf > options xen-fbfront video=32,1280,1024 > > A "depmod -a" and "update-initramfs -u" might be needed afterwards. > After reboot, it should correctly use 1280x1024 resolution. > > I still say you should use things like NX/xrdp/vnc server inside domU > though (my favorite is xrdp). It''s smooth, easy to install (apt-get > install xrdp), can allow you to choose different resolution without > having to reboot (just specify the desired resolution and color depth > when you connect), and allows you to have multiple GUI session to the > client (using idfferent user-resolution-depth combination) > > -- > Fajar >-- Ted Brenner _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users