Re: [smartos-discuss] X11 over VNC

[Jason Schmidt]

Hi,
For what it's worth - I use Jolly's Fast VNC - it works consistently 
well for me, and it's available through the app store on the mac.
JayDave Finster wrote:
I’ve had success with TigerVNC 1.7.0 (latest release) - seems a lot more
 stable than Chicken in my experience
  - DaveOn 19 Sep 2016, at 9:23 AM, Gjermund Gusland Thorsen 
 wrote: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.GOn 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 cyberspaceOn 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 Configured"    
Screen  0  "Screen0" 0 0    
InputDevice    "Mouse0" "CorePointer"    
InputDevice    "Keyboard0" "CoreKeyboard"EndSectionSection
 "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/"EndSectionSection
 "Module"    Load  "glx"EndSectionSection
 "InputDevice"    
Identifier  "Keyboard0"    
Driver  "kbd"EndSectionSection
 "InputDevice"    
Identifier  "Mouse0"    
Driver  "mouse"    
Option        "Protocol" "auto"    
Option        "Device" "/dev/sysmouse"    
Option        "ZAxisMapping" "4 5 6 7"EndSectionSection
 "Monitor"    Identifier   "Monitor0"    
VendorName   "Monitor Vendor"    
ModelName    "Monitor Model"EndSectionSection
 "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"EndSectionSection
 "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    
EndSubSectionEndSection---smartos-discussArchives: https://www.listbox.com/member/archive/184463/=nowRSS Feed: https://www.listbox.com/member/archive/rss/184463/27861131-64318a9bModify Your Subscription: https://www.listbox.com/member/?&Powered by Listbox: http://www.listbox.com
  smartos-discuss | Archives

 | Modify
 Your Subscription

Re: [smartos-discuss] Gitlab on LX zone - cannot allocate memory

[Jason Schmidt]

Hi Tommy,I just tried this in US-EAST-1
 with….triton create debian-8 g4-general-8GThen….1  sudo apt-get install curl openssh-server ca-certificates postfix
2  curl -sS https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh | sudo bash
3  sudo apt-get install gitlab-ce
4  sudo gitlab-ctl reconfigure
5  ifconfig
6  exit
And I’m able to 
log in just fine. When I get some time I’ll try with less memory and see
 if I can recreate the error - but in the interim you may want to retry 
with a bigger package and see if that fixes things?Jaytom my wrote:Hey all,just a try.I
 installed Gitlab on LX zone (tested centos, ubuntu, debian) using 
Gitlab's recommended Omnibus installation. I configured 
lx-zone with 4GB memory.Installation went ok, however I can't
 access Gitlab's web, receiving error "Cannot allocate memory - fork(2) 
(Errno::ENOMEM)" even all system uses only just under 1G.My
 guess is that some part of Gitlab checks available memory "in no 
standard" place.Is there any chance that 
somebody of you tried / experienced the same?Any idea what / 
how can I debug?Under KVM is everything ok.thanks.Tommy​
  smartos-discuss | Archives

 | Modify
 Your Subscription

Re: [smartos-discuss] Re: Importing VM form Hyper-V

[Jason Schmidt]

Hi Ian,

Thanks! This is really good to know; appreciate you writing it up in 
such detail. I have a Windows 10 VM I was thinking of importing - this 
gives me hope that I will be able to do that.


Jay


Ian Collins wrote:

On 09/ 9/16 11:32 PM, Jason Schmidt wrote:

Hi Ian,

I would be interested in seeing how you got around this, if you don't
mind sharing.


Sure..

The process was somewhat convoluted and some of steps I took may have 
been unnecessary but I was working stuff out and leaning windows tools 
as I went along.


First off I'm pretty sure this will only work with Hyper-V machines 
with a fixed drive, which in my case gave me a 500GB file to work with...


My first step was to convert the vhdx file to a raw with virtual box.  
I did this to get a format I know works with qemu-img on SmartOS.  If 
I had to do this again, I'd see if this step can be skipped.


VBoxManage clonehd fixed-bld-01.vhdx --format RAW fixed-bld-01.raw

On the SmartOS host I created a KVM with two 501GB IDE drives and 
wrote the image over the first drive:


qemu-img convert -f raw -O host_device fixed-bld-01.raw 
/dev/zvol/rdsk/zones/-disk0


The extra GB on the drive prevents qemu-img convert complaining about 
lack of space on the volume.


The next phase creates a clean copy of the the drive without a 
bootloader using windows imaging tools to image the drive and restore it.


* boot the VM using a windows PE ISO (created using the windows ADK 
tools) with a couple of extra utilities (diskpart and imagex) copied 
from a running windows system.


* use diskpart to create a partition on the second drive.
* use imagex to create a backup image of the first drive on the second.

* use diskpart to wipe and create a clean partition on the original 
drive.
* use imagex to restore the backup image of the first drive from the 
second.


I then halted the VM, deleted the second drive and rebooted from a 
server 2012 ISO and followed the repair computer steps to get a 
command shell.  From there I setup the bootloader:


bootrec /fixmbr
bootsect /nt60 all /force
bootrec /rebuildbcd
bcdboot c:\windows

At this point I had a bootable system :)

After that, add a small virtio dive and a virtio NIC, boot the machine 
with a virtio driver ISO attached and install the virtio drivers.  
Shutdown the VM, update the first drive to virtio, restart and you 
will have a system disk ready for imaging.


Phew, did I say the process was convoluted?





---
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