> -----Original Message----- > From: Nahum Shalman [mailto:nshal...@omniti.com] > Sent: 星期五, 十二月 09, 2016 2:12 > To: smartos-discuss@lists.smartos.org > Subject: Re: [smartos-discuss] vnc resolution configurable? > > Wow, resurrecting a thread from 2013 with my email address from my previous > employer. Okay, let's jump in. > > > On Thu, Dec 8, 2016 at 3:47 AM, Fred Liu <fred_...@issi.com > <mailto:fred_...@issi.com> > wrote: > > > We noticed that GUI since SL7.2 did not work with the low resolution > 1024x768 which is the default-detected resolution from SmartOS vnc server. > > > > That might have to do with the default amount of video memory QEMU gives > the VM. You may be able to change that with qemu_extra_opts. I've only ever > done that to the QXL device rather than the default VGA device so I don't know > what the variable you'd need to set would be. > > > > Is there a way to configure the vnc to run in higher resolution like > 1280x1024? And I don't need to hack Linux to forcedly run in higher > resolution. > > > > I think what you're asking is "How do I make all changes on the > SmartOS/QEMU/Client side so that I don't have to make any changes within the > guest OS?" > > The first thing I would try to do is force the VNC client to try to connect > at a > higher resolution. That might be enough to jolt the X server up to the higher > resolution so that the login UI will be able to render correctly. > > Figuring out what arguments to add to qemu_extra_opts is what I would > explore second.
Yes. It is exactly. I have tried tuning resolution in VNC client(RealVNC and TigerVNC) and got no luck. I also tried to switch vga to other device, it still didn't help. > > > > > BTW, is spice stable enough on SmartOS? > > > > My old email address which was CCd on your message was from my time at > Elysium Digital which was acquired by Stroz Friedberg[1] in 2015 and which I > left in March of this year (2016). > When I left, ~50 people in that Boston office were still using Spice enabled > VMs > (running Fedora as the guest OS) on SmartOS as their primary work systems > every day which they had been doing for years. > > I would have argued then that for some value of stable, that counted. > > I do not know if that system is still in use, and even if it is, it probably > won't be > for much longer. > For a while after I left I was still regularly using a Spice enabled Fedora > VM on > my home server for most of my personal stuff. > At this point most of what I was doing on it has been split apart between a > Mac > laptop and a Centos 7 LX branded zone on the SmartOS machine. > Which means that the Spice for SmartOS work is currently dormant in terms of > my time and I'm pretty sure no one else is actively developing it. > > So it may be somewhat stable, but it's kind of rotting on the vine at this > point. > Looks really promising but it is sad to see this endeavor is paused. I am gonna play your bits to taste the vine. ;-) Thanks for your contribution! VDI should be an import direction for SmartOS and OmniOS. > <shameless self promotion> > If anyone out there is using the Spice enabled QEMU code and needs support, > my current employer, OmniTI, is a consulting company and can sell you my time > to work on it. > </shameless self promotion> +1, cheers! Fred > > > -Nahum > > [1] Stroz Friedberg has since been acquired by Aon > > > > > -----Original Message----- > > From: Nahum Shalman [mailto:nshalman-smar...@elys.com > <mailto:nshalman-smar...@elys.com> ] > > Sent: 星期一, 三月 25, 2013 21:01 > > To: smartos-discuss@lists.smartos.org > <mailto:smartos-discuss@lists.smartos.org> > > Cc: Alain O'Dea > > Subject: Re: [smartos-discuss] Cannot get working VNC Viewer onto > KVM Zone > > > > On 03/23/2013 09:56 PM, Alain O'Dea wrote: > > > Is SPICE a feasible option here? I notice the experimental > > > configuration options for it. I'm really only looking at having a > > > console long enough to install the OS and bootstrap a Bomgar session > > > onto the desktop. > > > > Feasible, possibly. Ideal, probably not. > > In order to use Spice, you need to use an alternate QEMU binary rather > than > > the one that ships with the platform. > > (See http://wiki.smartos.org/display/DOC/Spice+on+SmartOS > <http://wiki.smartos.org/display/DOC/Spice+on+SmartOS> for details) > > > > The benefit of using "my" QEMU is that you can use Spice. The biggest > down > > side is that if you run into problems, you're not using the Joyent > supported > > QEMU. > > > > One option if you're trying to build a fresh image to use later as a > template that > > will have SSH already working, you could try using the Spice enabled > QEMU for > > the stage of building your image, verify that a fresh boot of that > image > does > > bring up SSH as desired, then use that image with the platform QEMU. > > > > So, order of preference from best to worst from my perspective: > > Try to get VNC working. > > Use Spice enabled QEMU for image building, platform QEMU for > production > > workload. > > Use Spice enabled QEMU for building and running in production > > > > I do run "my" QEMU in production, but I can't provide support. > > > > -Nahum > > > > P.S. I might not-so-secretly be hoping that you'll choose #3 *and* > that > you'll > > then ask Joyent to support it... A guy can dream. > > > smartos-discuss | Archives > <https://www.listbox.com/member/archive/184463/=now> > <https://www.listbox.com/member/archive/rss/184463/21991222-c237e945> > | Modify > <https://www.listbox.com/member/?&; > 222-4dea25e5> Your Subscription <http://www.listbox.com> ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
