Re: [smartos-discuss] Dell R740s

[Gjermund ॐ Gusland Thorsen]

I run SmartOS on R710
Check illumos hardware compatibility list: Illumos.org/hcl for your NICs

Sent from my iPhone

> On 9 May 2018, at 04:56, Ian Collins  wrote:
> 
> Hello,
> 
> Does anyone here have any experience with SmartOS on a Dell R740 (with HBA330 
> and Intel NICs) ?
> 
> I'm about to order a couple and don't want to get burned - they are expensive 
> beasts...
> 
> Cheers,
> 
> --
> 
> Ian.
> 


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] DHCP server in a zone?

[Gjermund ॐ Gusland Thorsen]

Did you enable the service?

Sent from my iPhone

> On 19 Dec 2017, at 16:55, Matthias Teege  wrote:
> 
> Hello!
> 
> I've installed SmartOS, created a zone and installed the isc-dhcpd
> from the packages. I can see the DHCPDISCOVER and a DHCPOFFER in
> the logs but dont see an answer packet on the network interfaces.
> The client gets not address. I've also tried an lx branded zone
> with the same result.
> 
> Do I have "tune" the zone or the root zone to handle DHCP?
> 
> Thanks!
> Matthias
> 


---
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: Update SmartOS QEMU to a more recent version, e.g. to enable macOS support on Apple hardware / was: Re: [smartos-discuss] I run Joyent SmartOS on an Apple XServ( xserv 2,1 ) w/96 GB RAM

[Gjermund ॐ Gusland Thorsen]

So you were at the same stage then that I am now

Sent from my iPhone

> On 28 Nov 2017, at 12:58, Peter Kelm <peter.k...@peterkelm.com> wrote:
> 
> Gjermund,
> 
> Sorry for the confusion - no, we did not make it work through option 1 due to 
> the lack of adequate patches. From what I recall we were able to boot the 
> Chameleon boot loader but that was it - and we only tried rather old OSX 
> versions (10.6 and 10.8).
> 
> I pasted the JSON below mainly to illustrate that there’s an interface in 
> vmadm that can setup such options to a KVM zone description.
> 
> To make this work one would probably need to back-port patches for CPU type 
> and Q35 platform support first. These could then also be tested with other 
> KVM VM’s apart from OSX/macOS. The second step would then be to resolve/fix 
> boot issues with OSX/macOS itself.
> 
> BTW: We haven’t seen huge issues with Windows KVM performance at vcpus=1 
> although it can be slow occasionally. We only use that OS in a few server 
> VMs, so bigger issues could go unnoticed...
> 
> Hmm, I have quite some C/C++ programming expertise myself but haven’t spent 
> much time hacking QEMU. One’s ability to support such an effort would of 
> course be very limited without programming experience...
> 
> Peter
> 
>> Am 28.11.2017 um 11:33 schrieb Gjermund ॐ Gusland Thorsen 
>> <gjermundpri...@gmail.com>:
>> 
>> My intial thought on your section 1 is did you make it work? I see there is 
>> vcpus = 1 in which at least for Windows is brutally slow; however with vcpus 
>> = 16 the running instance appears to be running at an enjoyable pace.
>> 
>> I would be interested in helpings out on rejuvenating qemu in smartos, but 
>> not sure which part of me is needed. I have the "barebones" knowledge of 
>> scripting in several languages yet no experience in the field of KVM/qemu 
>> other than being a user of SmartOS.
>> 
>> Sent from my iPhone
>> 
>>> On 28 Nov 2017, at 11:21, Peter Kelm <peter.k...@peterkelm.com> wrote:
>>> 
>>> Gjermund,
>>> 
>>> We looked into the very same question ourselves a few months ago and came 
>>> up with the following approaches:
>>> 
>>> 1) Fix KVM on SmartOS.
>>> 
>>> This could be accomplished by either „upgrading“ the SmartOS supplied 
>>> version of QEMU or patching the existing version to make it boot macOS. 
>>> Each KVM zone on SmartOS has a „startvm" file in its root directory that 
>>> would need to be modified for a macOS VM. This could be accomplished by 
>>> passing the correct parameters to "vmadm create“, e.g. via 
>>> „qemu_extra_opts“, e.g.:
>>> 
>>> {
>>> "brand": "kvm",
>>> "vcpus": 1,
>>> "autoboot": false,
>>> "alias": "OSX",
>>> "ram": 2048,
>>> "resolvers": ["192.168.17.1", "192.168.18.1"],
>>> "disks": [
>>> {
>>> "boot": true,
>>> "model": "ide",
>>> "size": 20480
>>> }
>>> ],
>>> "nics": [
>>> {
>>> "nic_tag": "admin",
>>> "model": "virtio",
>>> "ip": "192.168.17.106",
>>> "netmask": "255.255.255.0",
>>> "gateway": "192.168.17.1"
>>> }
>>> ],
>>> "qemu_extra_opts": "-kernel boot -device usb-kbd -device usb-mouse 
>>> -device isa-applesmc,osk=\“whatever\"“
>>> }
>>> 
>>> Note that the patches published at 
>>> https://www.contrib.andrew.cmu.edu/~somlo/OSXKVM/ are for a much newer 
>>> version of QEMU (it was mentioned already on this thread that the version 
>>> ported to SmartOS is fairly ancient from today’s perspective)!
>>> 
>>> Recent versions of OSX/macOS also require the Penryn CPU type and a Q35 
>>> machine type. Such patches exist(ed) - at least in parts - for older QEMU 
>>> versions, but are completely in current QEMU.
>>> 
>>> The SeaBIOS file referenced by Gabriel Somlo’s website should be fine as is 
>>> - but again: requires a newer version of QEMU.
>>> 
>>> Helpful information - in

Re: Update SmartOS QEMU to a more recent version, e.g. to enable macOS support on Apple hardware / was: Re: [smartos-discuss] I run Joyent SmartOS on an Apple XServ( xserv 2,1 ) w/96 GB RAM

[Gjermund ॐ Gusland Thorsen]

I can do stuff in c/cpp/objc/swift, but i never did any hardware emulation or 
KVM

Sent from my iPhone

> On 28 Nov 2017, at 12:58, Peter Kelm <peter.k...@peterkelm.com> wrote:
> 
> Gjermund,
> 
> Sorry for the confusion - no, we did not make it work through option 1 due to 
> the lack of adequate patches. From what I recall we were able to boot the 
> Chameleon boot loader but that was it - and we only tried rather old OSX 
> versions (10.6 and 10.8).
> 
> I pasted the JSON below mainly to illustrate that there’s an interface in 
> vmadm that can setup such options to a KVM zone description.
> 
> To make this work one would probably need to back-port patches for CPU type 
> and Q35 platform support first. These could then also be tested with other 
> KVM VM’s apart from OSX/macOS. The second step would then be to resolve/fix 
> boot issues with OSX/macOS itself.
> 
> BTW: We haven’t seen huge issues with Windows KVM performance at vcpus=1 
> although it can be slow occasionally. We only use that OS in a few server 
> VMs, so bigger issues could go unnoticed...
> 
> Hmm, I have quite some C/C++ programming expertise myself but haven’t spent 
> much time hacking QEMU. One’s ability to support such an effort would of 
> course be very limited without programming experience...
> 
> Peter
> 
>> Am 28.11.2017 um 11:33 schrieb Gjermund ॐ Gusland Thorsen 
>> <gjermundpri...@gmail.com>:
>> 
>> My intial thought on your section 1 is did you make it work? I see there is 
>> vcpus = 1 in which at least for Windows is brutally slow; however with vcpus 
>> = 16 the running instance appears to be running at an enjoyable pace.
>> 
>> I would be interested in helpings out on rejuvenating qemu in smartos, but 
>> not sure which part of me is needed. I have the "barebones" knowledge of 
>> scripting in several languages yet no experience in the field of KVM/qemu 
>> other than being a user of SmartOS.
>> 
>> Sent from my iPhone
>> 
>>> On 28 Nov 2017, at 11:21, Peter Kelm <peter.k...@peterkelm.com> wrote:
>>> 
>>> Gjermund,
>>> 
>>> We looked into the very same question ourselves a few months ago and came 
>>> up with the following approaches:
>>> 
>>> 1) Fix KVM on SmartOS.
>>> 
>>> This could be accomplished by either „upgrading“ the SmartOS supplied 
>>> version of QEMU or patching the existing version to make it boot macOS. 
>>> Each KVM zone on SmartOS has a „startvm" file in its root directory that 
>>> would need to be modified for a macOS VM. This could be accomplished by 
>>> passing the correct parameters to "vmadm create“, e.g. via 
>>> „qemu_extra_opts“, e.g.:
>>> 
>>> {
>>> "brand": "kvm",
>>> "vcpus": 1,
>>> "autoboot": false,
>>> "alias": "OSX",
>>> "ram": 2048,
>>> "resolvers": ["192.168.17.1", "192.168.18.1"],
>>> "disks": [
>>> {
>>> "boot": true,
>>> "model": "ide",
>>> "size": 20480
>>> }
>>> ],
>>> "nics": [
>>> {
>>> "nic_tag": "admin",
>>> "model": "virtio",
>>> "ip": "192.168.17.106",
>>> "netmask": "255.255.255.0",
>>> "gateway": "192.168.17.1"
>>> }
>>> ],
>>> "qemu_extra_opts": "-kernel boot -device usb-kbd -device usb-mouse 
>>> -device isa-applesmc,osk=\“whatever\"“
>>> }
>>> 
>>> Note that the patches published at 
>>> https://www.contrib.andrew.cmu.edu/~somlo/OSXKVM/ are for a much newer 
>>> version of QEMU (it was mentioned already on this thread that the version 
>>> ported to SmartOS is fairly ancient from today’s perspective)!
>>> 
>>> Recent versions of OSX/macOS also require the Penryn CPU type and a Q35 
>>> machine type. Such patches exist(ed) - at least in parts - for older QEMU 
>>> versions, but are completely in current QEMU.
>>> 
>>> The SeaBIOS file referenced by Gabriel Somlo’s website should be fine as is 
>>> - but again: requires a newer version of QEMU.
>>

Re: [smartos-discuss] P410i failure or bug

[Gjermund ॐ Gusland Thorsen]

Do you run smartos or sdc?

Sent from my iPhone

> On 28 Nov 2017, at 11:33, Nigel Magnay  wrote:
> 
> Yep, I'll progress trying to get another disk, (though god knows how long our 
> IT will take for that!)
> 
> I belive I configured it up as JBOD - though my memory is hazy. It's 
> certainly possible it's in 'whatever the closest I could get' mode, which is 
> a good point and one I hadn't thought of. 
> 
> In any event, each of the drives appears to the O/S and Triton 
> auto-configured the zpool.
> 
>> On Tue, Nov 28, 2017 at 10:25 AM, Paul Sture  wrote:
>> On 28 Nov 2017, at 11:09, Nigel Magnay wrote:
>> 
>> > So I managed after much faff to find out which disk that was. After pulling
>> > it out, the system no longer reboots every 15 mins or so (albeit I now have
>> > a degraded pool).
>> >
>> > It feels therefore like there's a bug somewhere - is this just the P410i
>> > being rubbish, drive firmware, something else? It's not a new machine, so
>> > my guess is sooner or later anoter disk is going to start misbehaving.
>> 
>> Putting another disk into that slot should enable you to see whether the
>> original disk is the cause of the problem, or the problem lies elsewhere.
>> 
>> Replacing that disk with a new one and bringing it into the existing pool
>> will cause it to be silvered, which will give it plenty of exercise.
>> 
> 
> smartos-discuss | Archives  | Modify Your Subscription 



---
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: Update SmartOS QEMU to a more recent version, e.g. to enable macOS support on Apple hardware / was: Re: [smartos-discuss] I run Joyent SmartOS on an Apple XServ( xserv 2,1 ) w/96 GB RAM

[Gjermund ॐ Gusland Thorsen]

My intial thought on your section 1 is did you make it work? I see there is 
vcpus = 1 in which at least for Windows is brutally slow; however with vcpus = 
16 the running instance appears to be running at an enjoyable pace.

I would be interested in helpings out on rejuvenating qemu in smartos, but not 
sure which part of me is needed. I have the "barebones" knowledge of scripting 
in several languages yet no experience in the field of KVM/qemu other than 
being a user of SmartOS.

Sent from my iPhone

> On 28 Nov 2017, at 11:21, Peter Kelm  wrote:
> 
> Gjermund,
> 
> We looked into the very same question ourselves a few months ago and came up 
> with the following approaches:
> 
> 1) Fix KVM on SmartOS.
> 
> This could be accomplished by either „upgrading“ the SmartOS supplied version 
> of QEMU or patching the existing version to make it boot macOS. Each KVM zone 
> on SmartOS has a „startvm" file in its root directory that would need to be 
> modified for a macOS VM. This could be accomplished by passing the correct 
> parameters to "vmadm create“, e.g. via „qemu_extra_opts“, e.g.:
> 
> {
>   "brand": "kvm",
>   "vcpus": 1,
>   "autoboot": false,
>   "alias": "OSX",
>   "ram": 2048,
> "resolvers": ["192.168.17.1", "192.168.18.1"],
>   "disks": [
>   {
>   "boot": true,
>   "model": "ide",
>   "size": 20480
>   }
>   ],
>   "nics": [
>   {
>   "nic_tag": "admin",
>   "model": "virtio",
>   "ip": "192.168.17.106",
>   "netmask": "255.255.255.0",
>   "gateway": "192.168.17.1"
>   }
>   ],
>   "qemu_extra_opts": "-kernel boot -device usb-kbd -device usb-mouse 
> -device isa-applesmc,osk=\“whatever\"“
> }
> 
> Note that the patches published at 
> https://www.contrib.andrew.cmu.edu/~somlo/OSXKVM/ are for a much newer 
> version of QEMU (it was mentioned already on this thread that the version 
> ported to SmartOS is fairly ancient from today’s perspective)!
> 
> Recent versions of OSX/macOS also require the Penryn CPU type and a Q35 
> machine type. Such patches exist(ed) - at least in parts - for older QEMU 
> versions, but are completely in current QEMU.
> 
> The SeaBIOS file referenced by Gabriel Somlo’s website should be fine as is - 
> but again: requires a newer version of QEMU.
> 
> Helpful information - in addition to Gabriel’s website:
> - https://github.com/kholia/OSX-KVM
> - https://github.com/jibaron/q35-qemu (I believe these were the original 
> patches for a Q35 machine type in QEMU)
> 
> 2) Use VirtualBox on SmartOS?
> 
> The other possibility we came up with would be using macOS inside a 
> VirtualBox VM on SmartOS. macOS support in VirtualBox exists and there’s a 
> Solaris version that would need to be unpacked and integrated into the GZ 
> image (drivers!). From what I read it should run in a (non-global) zone but 
> information is scarce on that aspect. At the very least one would need to 
> integrate the VBox drivers into the SmartOS image and permit a zone to see 
> and access them. VBox itself can be controlled via the command line, so no 
> GUI would be needed.
> 
> 3) There’s a newer QEMU version in pkgsrc
> Jan Poctavek of Erigones (CC'd) mentioned this potential option to me some 
> weeks ago during a meeting. I haven’t looked into this at all and I am not 
> too sure whether it would help in the end (a second KVM version, similar 
> issues than VBox). But he might be able to give additional details.
> 
> With all this said we would lean towards option 1) as it would have the best 
> long(er) term potential for the SmartOS platform. Additionally, other KVM’s 
> (incl. Windows) might also benefit from such a move by enabling additional 
> features and keeping closer track of QEMU’s development outside of SmartOS - 
> instead of rolling our own patchy version.
> 
> Getting macOS KVM VM’s going would be very interesting for us. We lacked the 
> time to do it alone but with the coordinated effort of a (small) group of 
> people and it might be achievable… 
> 
> In this light it would also be interesting to hear from Joyent what their 
> take would be on „rejuvenating“ QEMU on SmartOS.
> 
> Peter
> 
>> Am 27.11.2017 um 19:17 schrieb Gjermund Gusland Thorsen 
>> :
>> 
>> This should work for any intel Mac with the appropriate amount of CPU / RAM. 
>> I did not try on my MacPro yet.
>> 
>> The challenge is in making the MacOS X boot inside the KVM zone as MacOS X 
>> boots using UEFI, and not legacy. In essence I have a preinstalled image 
>> made with CCC from the time when the xserve ran natively; yet I'm not able 
>> to make it boot inside the zone. Perhaps I'll just have to dd the image 
>> mounted CCC image to a file. I'm still not able to imagine how to tell the 
>> KVM zone how 

Re: [smartos-discuss] Re: P410i failure or bug

[Gjermund ॐ Gusland Thorsen]

How did you configure the P410i?

Sent from my iPhone

> On 28 Nov 2017, at 11:09, Nigel Magnay  wrote:
> 
> So I managed after much faff to find out which disk that was. After pulling 
> it out, the system no longer reboots every 15 mins or so (albeit I now have a 
> degraded pool).
> 
> It feels therefore like there's a bug somewhere - is this just the P410i 
> being rubbish, drive firmware, something else? It's not a new machine, so my 
> guess is sooner or later anoter disk is going to start misbehaving.
> 
> 
>> On Mon, Nov 27, 2017 at 2:25 PM, Nigel Magnay  wrote:
>> HP DL380 with a P410i controller is failing. dmesg shows (Before reboot) :
>> 
>> 2017-11-27T14:15:55.804472+00:00 headnode smrt: [ID 745811 kern.info] 
>> NOTICE: smrt0: controller event class/sub-class/detail 5, 1, 0: Fatal drive 
>> error, Port=1I Box=1 Bay=2; rescanning devices
>> 2017-11-27T14:16:00.845994+00:00 headnode smrt: [ID 745811 kern.info] 
>> NOTICE: smrt0: controller event class/sub-class/detail 5, 1, 0: Fatal drive 
>> error, Port=1I Box=1 Bay=2; rescanning devices
>> 
>> 2017-11-27T14:17:02.825141+00:00 headnode smrt: [ID 523928 kern.warning] 
>> WARNING: smrt0: controller ping timed out
>> 2017-11-27T14:17:02.825171+00:00 headnode smrt: [ID 784599 kern.warning] 
>> WARNING: smrt0: controller ping failed; resetting controller
>> 2017-11-27T14:17:02.825176+00:00 headnode smrt: [ID 370623 kern.warning] 
>> WARNING: smrt0: attempting controller soft reset
>> 2017-11-27T14:17:08.925109+00:00 headnode smrt: [ID 795144 kern.notice] 
>> NOTICE: smrt0: soft reset: controller unready
>> 2017-11-27T14:17:12.825173+00:00 headnode smrt: [ID 140962 kern.notice] 
>> NOTICE: smrt0: soft reset: controller ready
>> 2017-11-27T14:17:51.256233+00:00 headnode smrt: [ID 148604 kern.info] 
>> NOTICE: smrt0: firmware rev 6.64
>> 2017-11-27T14:17:51.256260+00:00 headnode smrt: [ID 673390 kern.notice] 
>> NOTICE: smrt0: soft reset: controller configured
>> (rebooted)
>> 
>> Is this the controller simply failing, or an interaction of a disk failure? 
>> (All the lights are green on the front, so it's hard to identfy which 1I Box 
>> 1 Bay 2 refers to, otherwise I'd simply yank it to see if it helps..
>> 
> 
> smartos-discuss | Archives  | Modify Your Subscription 



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

[smartos-discuss] Anyone able to compile swift4 yet? I would love to be able to run Kitura / Vapor

[Gjermund ॐ Gusland Thorsen]

Sent from my iPhone


---
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] Re: [smartos-discuss] AMD Ryzen 7 Support

[Gjermund ॐ Gusland Thorsen]

Considered open indiana?

Sent from my iPhone

> On 26 Jul 2017, at 04:42, karthik  wrote:
> 
> Hello Ganapathy,
> 
> Can SmartOS be used at all as a workstation for web app development,say for 
> java/php development with Eclipse? AFAIK we can use it as a live image booted 
> off CD/USB with everything in memory, except for /opt . This is akin to a 
> liveCD of linux like Knoppix. I do some of my personal web development on 
> illumos but I use XStreamOS which has a desktop version. So for XStreamOS, 
> apart from the native IPS package set, I have options of Joyent's 
> pkgsrc,OpenCSW or gentoo prefix as package sets.
> 
> Thanks
> Karthik
> 
> From: "Heinz N. Gies" 
> Sent: Tue, 25 Jul 2017 22:12:21
> To: SmartOs Discuss 
> Subject: Re: [smartos-discuss] AMD Ryzen 7 Support
> 
> My test cluster runs 4 nodes with dual AMD Opteron 6127 which work fine with 
> SmartOS zones but of cause no KVM. They’ve been with me for over a year and 
> I’ve never had any SmartOs related problems.
>> On 25. Jul 2017, at 06:15, Ganapathy S A  wrote:
>>  
>> Hello Roberto,
>>  
>> I'm planning to buy a new PC for web app development in SmartOS platform 
>> (only OS zones). Were you able to run SmartOS without any issues? Or any 
>> other person? I still don't see AMD Ryzen (or any other AMD except one ☺️) 
>> here https://wiki.smartos.org/pages/viewpage.action?pageId=755673 
>>  
>> Any advice would be helpful.
>>  
>> Thanx,
>> Ganapathy
>>  
>>> On 24-Mar-2017 23:59, "Roberto Rivera"  wrote:
>>> Thanks for the video card insight Garrett. I swapped in an older Nvidia 
>>> Geforce GTX 745 card to see the impact. Regardless, the same errors show up 
>>> for both SmartOS and OmniOS.
>>>  
>>> Would the bios setting have an impact? I have assumed that NX, SVM (virtual 
>>> machine), and IOMMU settings should be enabled and maybe that's incorrect. 
>>> Maybe other bios settings are impactful as well?
>>>  
>>> Thanks again,
>>> Rob
>>>  
 On Fri, Mar 24, 2017 at 12:40 AM, Garrett D'Amore  
 wrote:
 The RX470 card probably won’t work except in basic VGA mode; this 
 generation of AMD GPU requires a very new driver set from AMD (their 
 amdgpu-pro drivers) which I don’t believe have been ported to illumos yet?)
  
 (For various reasons, I’m acutely aware of current AMD GPU stuff, owing to 
 $dayjob.)
  
   - Garrett
  
> On Thu, Mar 23, 2017 at 9:52 PM, Dan McDonald  wrote:
> 
> > On Mar 23, 2017, at 11:55 PM, Roberto Rivera 
> >  wrote:
> >
> > Tried OmniOS as suggested... after hitting the enter at the boot menu 
> > got the following:
> >
> > loading /platform/i86pc/amd64/boot_archive
> > No rootfs module provided, aborting
> > booting /platform/i86pc/kernel/amd64/unix
> > No rootfs module provided, aborting
> >
> > Then was dropped to an "OK" prompt.
> 
> Weird.  That normally would indicate a malformed ISO or USB stick, but 
> I'm pretty sure these work on other HW and VMs.
> 
> Thanks for the data.  You can also try this one, just in case:
> 
> http://kebe.com/~danmcd/webrevs/r151021-kayak.iso
> 
> I spun it more recently than the 0314 ones.  It'll likely fail the same 
> way for you, but it's worth a check.
> 
> Thanks,
> Dan
> 
> 
> 
> 
> 
> 
> http://www.listbox.com
> smartos-discuss | Archives  | Modify Your Subscription 



---
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] Asterisx on native zone?

[Gjermund ॐ Gusland Thorsen]

Pls try to spin up a native zone, import your settings and tell us the results.

Sent from my iPhone

> On 5 May 2017, at 03:07, Rob Seastrom  wrote:
> 
> Haven't seen anyone here ask about Asterisk in a couple of years.
> 
> Our situation is that we're running a very long in the tooth release of 
> Astlinux on even more long in the tooth (PC Engines ALIX) hardware...  oddly 
> enough that platform is still supported.
> 
> Needs are modest.  Only a handful of users.  No DAHDI - it's VoIP in, VoIP 
> out.
> 
> I see that the Asterisk release in pkgsrc for native zones is fairly modern 
> *and* is 1.8 branch, which would minimize my pain factor for the migration.
> 
> Anyone running Asterisk in a native zone?  An LX zone?  Happy with it?  I 
> want to get rid of the little ALIX boxes.  Worst case I could spin up some 
> KVM zones and just put Astlinux in them, but I feel that's a step in the 
> wrong direction.  Astlinix reputedly works just fine under Proxmox, which is 
> a fancy wrapper around KVM.
> 
> Thanks,
> 
> -r
> 


---
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] Virtio driver versions for Windows

[Gjermund ॐ Gusland Thorsen]

http://wethecomputerabusersamongst.blogspot.nl/2015/08/install-kvm-smartos-install-windows.html?m=1

Sent from my iPhone

> On 18 Jan 2017, at 17:18, TRITONIA SOLUTIONS LIMITED  
> wrote:
> 
> Hi, 
> 
> I'm trying to find the appropriate version of the Virtio drivers for use with 
> Windows 7, 8.1, 10, Server 2012R2 and Server 2016. It seems from my tests 
> that the latest Virtio-win-0.1.126 drivers from RHEL do not work with Windows 
> 7 or 8.1 (maybe just the NIC driver doesnt work). 
> 
> I'm interested to know which versions people use with each version of 
> Windows. 
> 
> Thanks in advance
> 
> Sean Weatherall
> smartos-discuss | Archives  | Modify Your Subscription 



---
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] 'Defrag' a KVM disk

[Gjermund ॐ Gusland Thorsen]

Did you consider to make the file pool of the KVM a native ZFS file pool? CIFS 
or other

Sent from my iPhone

> On 18 Jan 2017, at 08:31, Matthias Goetzke  wrote:
> 
> We have a machine which temporarily got 98% full and the boot time of a KVM 
> windows server has gotten quite extreme (minutes on the black part of the 
> boot alone).
> Apart from over-allocating, we guess it might have to do with fragmentation 
> of the underlying C drive (just a hunch due to the number of writes on C and 
> the fact that overall fragmentation was temporarily >78%) since another win 
> machine still booted up quite quickly.
>  
> If a kvm disk were just a file then I could just make a copy of the C drive 
> (I have enough space now) into a new file which should (in theory) just 
> create new aligned blocks and once I delete the old file it should be 
> defragmented mostly.
>  
> Is this correct ? And if so, kvm disks are mounted as raw devices, so I guess 
> my idea wont work anyway. Is there an alternative or is this a fools errant ?
>  
> Cheers,
> matthias
> smartos-discuss | Archives  | Modify Your Subscription 



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

[Gjermund ॐ Gusland Thorsen]

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 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
> 
> 
> 
> smartos-discuss | Archives  | Modify Your Subscription 



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