Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 27 23:44

    YanChii on master

    workaround new bootparams varia… (compare)

  • Jan 25 16:02

    YanChii on new_release_20190117

    fixed boot.manifest (compare)

  • Jan 25 16:00

    YanChii on new_release_20190117

    fixed manifest (compare)

  • Jan 25 15:42

    YanChii on new_release_20190117

    OS-7436 vminfod can be overwhel… OS-6795 illumos-joyent build to… OS-7488 vm delete fails after O… and 8 more (compare)

  • Jan 25 15:39

    YanChii on master

    removed VM.js (TSC workaround n… (compare)

  • Jan 25 15:34

    YanChii on master

    moved postboot-rc manifests (compare)

  • Jan 25 15:33

    YanChii on merge-sysinfo

    (compare)

  • Jan 25 15:33

    YanChii on master

    merge sysinfo upstream changes (compare)

  • Jan 25 15:33
    YanChii closed #10
  • Jan 25 14:46

    YanChii on new_release_20190103

    updated boot copyright year (compare)

  • Jan 23 13:48

    YanChii on master

    allow consistently reexecute he… (compare)

  • Jan 23 13:48
    YanChii closed #119
  • Jan 23 13:46
    YanChii synchronize #385
  • Jan 22 21:58
    YanChii synchronize #384
  • Jan 22 21:43
    YanChii synchronize #384
  • Jan 22 19:58
    YanChii synchronize #385
  • Jan 21 09:50

    dn0 on master

    Fixed links to issues (compare)

  • Jan 21 09:08
    YanChii synchronize #385
  • Jan 21 09:02
    YanChii review_requested #385
  • Jan 21 09:02
    YanChii milestoned #385
Jan Poctavek
@YanChii
you can set it using DC on a vnic
but it is purposely only in the API
so use the es command to set it
you can use: es help /vm/<vmname>/define/nic (or something simmilar)
don't set it using
dladm
even in plain smartos you need to put it into vmadm nic properties
and of course you need to shut down and start the VM (reboot is not enough)
see POST command
klebed
@klebed
Thanks! Very helpful comments, really appreciate it!
But some details a bit confusing... previously I've used virt-manager with libvirt and LVM2 a lot... hosts was on Ubuntu 12.04 and even there almost every change (memory, volume resize, adding nics and other devices...) was done online without need to reboot. It seems like the danube cloud suffers a bit from elderly base it just can't offer functionality of modern hypervisors.
Also... vmadm update nics.2.allow-unfiltered-promisc=true reports successful update, but does nothing. =(
Jan Poctavek
@YanChii
not sure if vmadm works that way for nested properties
use this howto:
but I still recommend setting it using Danube Cloud es command (jist download pre-configured command from web GUI help)
regarding reboot:
DC "suffers" from SmartOS secure architecture
KVM and bhyve processes are placed inside a SunOS zone… and zone needs to be rebooted to reflect disk changes
and zfs volume cannot be resized when it's open (by KVM process)
so there's no (easy) way how to workaround disk changes withou reboot
Jan Poctavek
@YanChii
the advantage of this design is very high security and very high flexibility given by zfs backed volumes (quick snapshots that don't slow the system, incremental backups, VM migrations with disk copy in the background while VM is still operating, etc.)
klebed
@klebed
image.png
Is it expected behaviour, that I can't choose any of monitoring templates in VM options?
Jan Poctavek
@YanChii
@klebed default setting is to restrict monitoring templates to the allowed list… and the list is empty after install
the best way is go to virtual datacenter settings and uncheck MON_ZABBIX_TEMPLATES_VM_RESTRICT
(it is secure-by-default way after install)
klebed
@klebed
ahhh... this wasn't obvious. might be worth adding to post-install tasks. Monitoring is essential part of every infrastructure and should be easily managed though.
klebed
@klebed
esdc-mon has same problem with clocksource, as any other machine. There's something we should do about it, because even installation of linux from livecd may randomly fail because of random time jumps. Sometimes it hangs 3-4 times before success, focing to strat all over again.
klebed
@klebed
image.png
and another stuff on node console
Jan Poctavek
@YanChii
this is really strange
I've seen VM hangs on Intel i7
but you say this is Xeon
did you try the plain smartos?
as a first thing we need to find out if the problem is only in DC platform or in every smartos
just replace the usb with smartos release-20190328 and maybe also with the latest
that will tell us direction what to do next
@klebed ^^
klebed
@klebed
@YanChii It wasn't exactly hangs... but when one step dependent from successful start of another one, but it doesn't start because of time jumps, so different systemd (fo example) services, just waits infinitelly. When you booting livecd or freshly installed machine it happens too often. Only after adding clocksource=hpet it normalizes.
I'll try mentioned release this week
and raw smartos too
klebed
@klebed
One short question... is it safe to re-write bootable USB, while node is running? I believe it doesn't depend on it while it's running?
Jan Poctavek
@YanChii
try just those two plain smartos versions
running DC or smartos doesn't depend on usb
it is safe to rewrite it
as long as it is unmounted
ls /mnt/usb