No problem - easily worked around.
Andy
On Wed, 4 Jan 2017, Dan McDonald wrote:
; It was a build accident, not intentional.
;
; Next time kernels get updated, it'll be fixed. If this is breaking scripts,
I'll push an update that fixes it (at the cost of requiring another reboot).
;
; I'm very
Hi,
"Michael Rasmussen" írta 2017-01-05 19:44-kor:
> On Thu, 5 Jan 2017 13:34:40 -0500
> Dan McDonald wrote:
>
> > I notice you're running on vmxnet... I wonder if your host is preventing
> > you from creating vNICs through some sort of address filtering?
>
> On Jan 5, 2017, at 2:14 PM, Mini Trader wrote:
>
> Just access and hopefully recognition of sparse files.
You should be able to use zonecfg(1M) to share things appropriately.
Dan
___
OmniOS-discuss mailing list
On Thu, 5 Jan 2017 13:48:18 -0500
Dan McDonald wrote:
> > On Jan 5, 2017, at 1:44 PM, Michael Rasmussen wrote:
> >
> > Does it not require promiscuous mode to be able to create a nic alias?
> > I do not think this is supported with default settings in VmWare.
Only added the vnic because I saw it in some other install manual.
Obviously not needed - thank you for pointing that out! I added a third
NIC on the same network and wham I am up and running :) Thank you for the
help.
Is there any documentation on what I need to do to make my datasets visible?
> On Jan 5, 2017, at 1:44 PM, Michael Rasmussen wrote:
>
> Does it not require promiscuous mode to be able to create a nic alias?
> I do not think this is supported with default settings in VmWare.
I don't know my VMware-fu very well, but this sounds like what I was talking
On Thu, 5 Jan 2017 13:34:40 -0500
Dan McDonald wrote:
> I notice you're running on vmxnet... I wonder if your host is preventing you
> from creating vNICs through some sort of address filtering?
>
Does it not require promiscuous mode to be able to create a nic alias?
I do
root@storage1:/root# dladm show-link
LINKCLASS MTUSTATEBRIDGE OVER
vmxnet3s0 phys 1500 up -- --
vmxnet3s1 phys 9000 up -- --
lx0 vnic 1500 up -- vmxnet3s0
root@storage1:/root#
root@storage1:/root#
Hmmm.
So now we do have to go back to the global zone... but not what you showed me.
Please show:
dladm show-link
dladm show-vnic
dladm show-ether
I notice you're running on vmxnet... I wonder if your host is preventing you
from creating vNICs through some sort of
The only machine I can ping is the host. Nothing else.
root@debian-8:~# ifconfig -a
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MULTICAST MTU:8232 Metric:1
RX packets:0
Why are you showing me global-zone things when the problem is in the LX zone?
Dan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
Having trouble with networking. Any thoughts on this?
ipadm show-addr
ADDROBJ TYPE STATEADDR
vmxnet3s0/v4 static ok 10.255.0.15/24
dladm show-vnic
LINK OVER SPEED MACADDRESSMACADDRTYPE VID
lx0 vmxnet3s01
https://omnios.omniti.com/wiki.php/LXZones
See the zonecfg example where you add properties to the "net" instance. For
now, this is the only way to support network configurations on LX Zones. We
plan to have /native/sbin/ipadm working before r151022 ships.
Dan
I deleted and re-created. And it seems to be fine now. Odd.
My ifconfig settings keep getting overwritten. Is there something special
that needs to be done to have these settings maintained? Looking for a
simple DHCP or Static IP config.
On Thu, Jan 5, 2017 at 11:19 AM, Rafael Pardinas
It may be useful to take a look at your config file then.
On Thu, 5 Jan 2017 at 15:51 Mini Trader wrote:
> Yes. Doesn't seem to make a difference.
>
> On Thu, Jan 5, 2017 at 10:47 AM, Rafael Pardinas wrote:
>
> Have you tried rebooting the LX zone?
root@storage1:/main/zones# zlogin -e ! lx0
[Connected to zone 'lx0' pts/2]
Last login: Thu Jan 5 15:43:39 UTC 2017 on console
Linux debian-8 3.16.0 BrandZ virtual linux x86_64
__. .
_| |_ | .-. . . .-. :--. |-
|__| ;| || |(.-' | | |
|__| `--'
Yes. Doesn't seem to make a difference.
On Thu, Jan 5, 2017 at 10:47 AM, Rafael Pardinas wrote:
> Have you tried rebooting the LX zone? Sometimes they don't load correctly
> the first time.
>
> On Thu, 5 Jan 2017 at 15:45 Mini Trader wrote:
>
>>
Have you tried rebooting the LX zone? Sometimes they don't load correctly
the first time.
On Thu, 5 Jan 2017 at 15:45 Mini Trader wrote:
> root@storage1:/main/zones# zlogin -e ! lx0
> [Connected to zone 'lx0' pts/2]
> Last login: Thu Jan 5 15:43:39 UTC 2017 on console
My system is acting funny.
If I login via zlogin nameofzone
I don't get dumped into the command prompt right away. I was able to
change the password via zlogin nameofzone passwd
If I login via zlogin -C nameofzone
Everything seems normal. It's like the shell is not properly feeding back
if
As someone else already said - there's no root password on these images and you
need to use zlogin to get a "console" root prompt.
General thing is, is that these images are essentially what you would download
directly from Ubuntu or CentOS/Redhat, but with some specific tweaks to make
them
I have not used the tool but it doesn't seem to offer the same intelligence
you would get with something like BORG or hashbackup.
I did not know about the LX feature so that seems like it can help
significantly - trying to get it going but currently unable to login to the
zones system!
On Thu,
>From your host you should be able to do:
~ $ zlogin -e ! lxbox <-- lxbox is the name you've given to your Debian
machine.
>From there you can assign passwords. By default there isn't one assigned to
the root user as far as I know.
-Rafa
On Thu, 5 Jan 2017 at 15:14 Mini Trader
On Thu, Jan 5, 2017 at 3:56 PM, Olaf Marzocchi wrote:
> I'm using right now Crashplan under OmniOS but it's been already declared
> as discontinued and I may need an alternative sometimes in the future, even
> if it still works fine.
>
same here, althouth since the lx
Hello all,
I am trying to use a Debian LX Image based on the instructions from:
https://omnios.omniti.com/wiki.php/LXZones
The UUID I am using is: 9a8d53c0-c15b-11e6-9c4f-3bcedc82f8e1
I've been able to get my zone to start up no problems. But I cannot login.
Is there a default password for
Their Linux tool is working with Backblaze B2, but it's a python tool, not a
native closed source application. They do not offer the normal backup agent for
anything but Win/Mac.
At that point it may be possible to run the pytjon tool directly on OmniOS?
I thought about it but never went on
This could work :) Thank you.
On Wed, Jan 4, 2017 at 7:27 PM, Michael Talbott wrote:
> You can create an LX zone with the latest stable Omni release, share the
> dataset(s) with the zone and run the backup agent in there. That's what I'm
> using for a bunch of things such as
They are .10 per GB. Backblaze is 0.005 per GB. About $2400/yr vs $120/yr.
On Wed, Jan 4, 2017 at 7:25 PM, Michael Rasmussen wrote:
> On Thu, 5 Jan 2017 01:15:18 +0100
> Michael Rasmussen wrote:
>
> > Would it be possible to use rsync with backblaze?
> > rsync
27 matches
Mail list logo