Re: [smartos-discuss] boot-ncpus ... is there a workaround for?

2016-10-23 Thread David Preece 



On 24/10/16 6:00 AM, Robert Mustacchi wrote:

On 10/22/16 15:54 , David Preece wrote:

I have a hosting provider that's just swapped from (apparently)
emulating 4 cpu's to emulating 1 cpu with 4 cores. I remember something
about --boot-ncpus not working because SmartOS only "sees" the cpu's
themselves. Is there a workaround? No biggie if not but if there is some
quick workaround, I'd like to know what it is.

I'm not familiar with this failure mode? Are you only seeing a single
processor show up in psrinfo? If the emulation's using 1 core with 4
threads or 4 cores, both should be detected.

It *found* it (http://imgur.com/a/Onsc6)

In psrinfo:

[root@56-00-00-3c-f4-89 ~]# psrinfo -v
Status of virtual processor 0 as of: 10/23/2016 20:32:59
  on-line since 10/23/2016 20:29:54.
  The i386 processor operates at 2400 MHz,
and has an i387 compatible floating point processor.


prtpicl (http://pastebin.com/RQ7SG3wj) does see the cores:

 socket (acpicontainer, ae402a8)
 cpu (cpu, ae402bf)
 cpu (acpicpu, ae402e9)
 cpu (acpicpu, ae402fb)
 cpu (acpicpu, ae4030d)

And dmesg

2016-10-23T20:30:26.605720+00:00 56-00-00-3c-f4-89 unix: [ID 950921 
kern.info] cpu0: x86 (chipid 0x0 GenuineIntel 306D2 family 6 model 61 
step 2 clock 2400 MHz)
2016-10-23T20:30:26.605723+00:00 56-00-00-3c-f4-89 unix: [ID 950921 
kern.info] cpu0: Virtual CPU a7769a6388d5
2016-10-23T20:30:26.605726+00:00 56-00-00-3c-f4-89 unix: [ID 608849 
kern.notice] NOTICE: System detected 4 cpus, but only 1 cpu(s) were 
enabled during boot.
2016-10-23T20:30:26.605728+00:00 56-00-00-3c-f4-89 unix: [ID 458440 
kern.notice] NOTICE: Use "boot-ncpus" parameter to enable more CPU(s). 
See eeprom(1M).


-Dave


---
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_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] boot-ncpus ... is there a workaround for?

2016-10-23 Thread Robert Mustacchi 
On 10/22/16 15:54 , David Preece wrote:
> I have a hosting provider that's just swapped from (apparently)
> emulating 4 cpu's to emulating 1 cpu with 4 cores. I remember something
> about --boot-ncpus not working because SmartOS only "sees" the cpu's
> themselves. Is there a workaround? No biggie if not but if there is some
> quick workaround, I'd like to know what it is.

I'm not familiar with this failure mode? Are you only seeing a single
processor show up in psrinfo? If the emulation's using 1 core with 4
threads or 4 cores, both should be detected.

Robert



---
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_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] X11 over VNC

2016-10-23 Thread Jorge Schrauwen 
There is a vnc_password property that can be fed to vmadm during create,
does that not work?

Regards 

Jorge 

On 2016-10-23 01:48, Gjermund Gusland Thorsen wrote:

> Is there a way to set vnc_password in the zone file? 
> 
> G 
> 
> On 19 Sep, 2016, at 10:21, Peter Kelm  wrote: 
> 
> For the KVM VM in question: 
> vmadm update  vnc_password= 
> 
> Then launch the „Screen Sharing" app (e.g. by entering „screen" in Spotlight) 
> and enter the hostname or ip address of the SmartOS host (not the KVM zone) 
> followed by the port: :. You will be prompted for the 
> password set via vmadm (above) and VNC will connect. 
> 
> Alternatively you can also press Command-K in the Finder to bring up the 
> „Connect to Server" dialog, Enter „vnc://:" under 
> „Server address" and press „Connect" and OS X will launch „Screen Sharing" 
> and establish the VNC connection. As above you will be prompted for the 
> password. 
> 
> Am 19.09.2016 um 09:23 schrieb Gjermund Gusland Thorsen 
> : 
> 
> How does that work? 
> 
> On 19 Sep, 2016, at 9:14, Peter Kelm  wrote: 
> 
> No need for a third party VNC client on OS X/OSX/macOS - the builtin „Screen 
> Sharing" applications does the job nicely. To make it work you need to set a 
> „vnc_password" through vmadm, though. 
> 
> Peter 
> 
> P.S. And yes, I did use Chicken myself before… 
> 
> Am 19.09.2016 um 01:23 schrieb Gjermund Gusland Thorsen 
> : 
> 
> For example on Mac the only VNC client that actually manages to login to the 
> KVM using VNC is Chicken 2.2b2 to my knowledge. 
> 
> G
> 
> On 18 Sep, 2016, at 22:26, G B via smartos-discuss 
>  wrote: 
> 
> Yes, I'm using the internal vnc in kvm.
> 
> On Sunday, September 18, 2016 12:16 PM, Gjermund ॐ Gusland Thorsen 
>  wrote:
> 
> Are you using the internal VNC in the KVM? I believe certain VNC clients are 
> incompatible. 
> Sent from cyberspace 
> 
> On 18 Sep 2016, at 16:20, G B via smartos-discuss 
>  wrote:
> 
> I'm running SmartOS 20160818T234814Z and using freebsd-10 20160415 in a KVM.  
> I've installed a number of window managers but the mouse never works.  Has 
> anyone been able to use a window manager like WindowMaker, wmii, twm, etc., 
> over Xming? 
> 
> I tried generating an xorg.conf which typically isn't needed, but it doesn't 
> work.  Here are the contents. 
> Section "ServerLayout"
> Identifier "X.org [1] Configured"
> Screen  0  "Screen0" 0 0
> InputDevice"Mouse0" "CorePointer"
> InputDevice"Keyboard0" "CoreKeyboard"
> EndSection
> 
> Section "Files"
> ModulePath   "/usr/local/lib/xorg/modules"
> FontPath "/usr/local/share/fonts/misc/"
> FontPath "/usr/local/share/fonts/TTF/"
> FontPath "/usr/local/share/fonts/OTF/"
> FontPath "/usr/local/share/fonts/Type1/"
> FontPath "/usr/local/share/fonts/100dpi/"
> FontPath "/usr/local/share/fonts/75dpi/"
> EndSection
> 
> Section "Module"
> Load  "glx"
> EndSection
> 
> Section "InputDevice"
> Identifier  "Keyboard0"
> Driver  "kbd"
> EndSection
> 
> Section "InputDevice"
> Identifier  "Mouse0"
> Driver  "mouse"
> Option"Protocol" "auto"
> Option"Device" "/dev/sysmouse"
> Option"ZAxisMapping" "4 5 6 7"
> EndSection
> 
> Section "Monitor"
> Identifier   "Monitor0"
> VendorName   "Monitor Vendor"
> ModelName"Monitor Model"
> EndSection
> 
> Section "Device"
> ### Available Driver options are:-
> ### Values: : integer, : float, : "True"/"False",
> ### : "String", : " Hz/kHz/MHz",
> ### : "%"
> ### [arg]: arg optional
> #Option "ShadowFB"   # []
> #Option "DefaultRefresh" # []
> #Option "ModeSetClearScreen" # []
> Identifier  "Card0"
> Driver  "vesa"
> BusID   "PCI:0:2:0"
> EndSection
> 
> Section "Screen"
> Identifier "Screen0"
> Device "Card0"
> Monitor"Monitor0"
> SubSection "Display"
> Viewport   0 0
> Depth 1
> EndSubSection
> SubSection "Display"
> Viewport   0 0
> Depth 4
> EndSubSection
> SubSection "Display"
> Viewport   0 0
> Depth 8
> EndSubSection
> SubSection "Display"
> Viewport   0 0
> Depth 15
> EndSubSection
> SubSection "Display"
> Viewport   0 0
> Depth 16
> EndSubSection
> SubSection "Display"
> Viewport   0 0
> Depth 24
> EndSubSection
> EndSection
 
 http://www.listbox.com [2]
 
 http://www.listbox.com [2]
 
 Links:
 --
 [1]  http://x.org/
  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_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com