https://www.danube.cloud | https://github.com/erigones/esdc-ce/wiki/Release-Notes
Hi, Paolo.
You can use api with refreservation defined
https://docs.danubecloud.org/api-reference/api/vm_define.html#vm-hostname-or-uuid-define-disk-disk-id
Or just do zfs set refreservation=None <fs>
after deploy. You can create smaller disk and grow it later.
es
command
svcs erigonesd
Hi,
I'm trying to install danube cloud 4.6 compute-node (no 4.6 head-node available ?) on a Gigabyte BRIX GB-BRR7-4800.
Detailed specs are available at: https://www.gigabyte.com/be/Mini-PcBarebone/GB-BRR7-4800-rev-10#ov
It looks like I'm running into an issue with the onboard NIC during the installation.
When I boot the pc, I get to the Danube boot menu and booting starts.
Loading unix...
Loading /platform/i86pc/amd64/boot_archive...
Loading /platform/i86pc/amd64/boot_archive.hash...
Booting...
WARNING: Couldn't read ACPI SRAT table from BIOS. lgrp... -> this is no issue ; I see the same on my NUC
Illuminos Version esdc_20220127T211339Z 64-bit
ERROR: failed to attach AMD IOMMU -> Seems not to be an issue (https://illumos.topicbox.com/groups/developer/Ted97385c7e5bfb1f/illumos-8679-failed-to-attach-amd-iommu)
Running from USB...
skipping USB copy setup: no zones zpool
Error: unable to initialize empty mac!
/usr/bin/nictagadm: line 212: LINKS[$mac]: bad array subscript
ERROR: cannot configure the system, no NICs were found.
May 11... svc.startd[8]: svc:/network/physical:default: Method "/lib/svc/method/net-physical" failed with exit status 96
May 11... svc.startd[8]: network/physical:default misconfigured: transitioned to maintenance. (see 'svcs -xv' ...)
Some more services (missing hostname, audit,...) report an issue, and I end at the prompt:
Welcome to Danube Cloud node (20220127T211339Z)
unknown wscons login:
Any idea how to get around this ?
esbackup
process on the destination server.
we have found a NFS performance issue connected with bhyve, with NFS, the Vm is stuck and it does not work
https://smartos.topicbox.com/groups/smartos-discuss/Ta60043d861986cca
It is caused by the
NAPI tx mode in virtio_net, which seems to conflict with bhyve somehow.
As a workaround, it can be disabled again by running:
ethtool -C net0 tx-frames 0
inside the bhyve VM
rc-pre-network.d
-> networking -> rc-pre-vmadmd.d
-> start VMs -> rc-post-vmadmd.d