IIRC setting the zone to exclusive netstack works to include the
/dev/net/vnicX device:
---
set ip-type=exclusive
add net
set physical=zleonov0
end
---
-(~)-[.]-{ ls -l /dev/net
}-(root@leonov)-
total 0
crw-rw-rw- 1 root sys 263, 1010 Dec 20
On Tue, 23 Dec 2014 09:01:16 +0100
Jorge Schrauwen sjorge...@blackdot.be wrote:
IIRC setting the zone to exclusive netstack works to include the
/dev/net/vnicX device:
That gets it a bit closer but I still need the real interface (e1000g1)
for vnc and sshing in etc. and I can't give that to
Well just use a socket for vnc, then you can spawn socat in the gz to
explose the socket over tcp :)
This deals with a serial port as a socket...
https://blackdot.be/2013/07/qemu-kvm-monitor-and-serial-console-over-sockets-with-minicom/
But:
socat unix-listen:/vms/leonov/run/vnc.sock
On Tue, Dec 23 2014 19:28:47 +1000, Michael Mounteney wrote:
That gets it a bit closer but I still need the real interface (e1000g1)
for vnc and sshing in etc. and I can't give that to the zone
exclusively.
You can create a vnic over your physical interface (with dladm(1M)) and
then give that
On Tue, Dec 23, 2014 at 10:44 AM, Lauri Tirkkonen loth...@iki.fi wrote:
On Tue, Dec 23 2014 19:28:47 +1000, Michael Mounteney wrote:
That gets it a bit closer but I still need the real interface (e1000g1)
for vnc and sshing in etc. and I can't give that to the zone
exclusively.
You can
On Tue, 23 Dec 2014 10:56:30 +0100
Natxo Asenjo natxo.ase...@gmail.com wrote:
Thanks to you and everyone else for their help. I hope I'm not
polluting the list with newbie noise but hopefully this will stay on
record and help out someone else later. My knowledge of vnics, sockets
etc. is thin,
Hi Dan!
Thanks for all of your efforts. OmniOS is a solid part of our
IT infrastucture here.
You wrote (to Michael Mounteney):
Did you pkg update to the very latest NTP server? There's a
security vulnerability attached to it, you know.
As an aside, I just updated from 10 to 12 and am now
On Dec 23, 2014, at 10:20 AM, Volker A. Brandt v...@bb-c.de wrote:
Update was straightforward and worked just fine. But I noticed a strange
path in the /usr/share/doc/ntp4 subdirectory:
# pkg list -Hv ntp@latest
pkg://omnios/service/network/ntp@4.2.8,5.11-0.151012:20141219T194032Z
Brilliant, with a bit more fiddling I've got it so that the KVM
instances can be started within the child zone, AND shut down cleanly
via the command echo system_powerdown | nc -U /var/run/KDE.monsock so
the next step is to put them into a service so that they can be brought
up and down within
Michael,
you might wanna give kvmadm a try ( https://github.com/hadfl/kvmadm ).
that'll help you putting your kvms under smf control.
at least you should be able to extract all the infos from there...
On 12/23/2014 09:14 PM, Michael Mounteney wrote:
Brilliant, with a bit more fiddling I've
On Wed, 24 Dec 2014 00:00:03 +0100
Dominik Hassler hassl...@gmx.li wrote:
Michael,
you might wanna give kvmadm a try ( https://github.com/hadfl/kvmadm ).
that'll help you putting your kvms under smf control.
at least you should be able to extract all the infos from there...
Thanks
11 matches
Mail list logo
