You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The VM didn't have enough space, so I set the new flexible_disk_size in the same payload, this still doesn't work.
cannot create 'zones/e8bfab59-cc76-4dc0-af02-9c5f5c2f5e51/disk1': out of space
The entire update then stops, I assume it is doing the create of disk1 zvol before updating the zfs reservations with the new value of flexible_disk_size, but VM.js is a confusing beast.
Doing vmadm update $(vmadm lookup hostname=bhyvetest) flexible_disk_size=14592 before doing the add_disks payload works fine. Which seem to indeed indicate that the ordering is somehow wrong internally when both are in the same payload.
The text was updated successfully, but these errors were encountered:
The VM didn't have enough space, so I set the new flexible_disk_size in the same payload, this still doesn't work.
cannot create 'zones/e8bfab59-cc76-4dc0-af02-9c5f5c2f5e51/disk1': out of space
The entire update then stops, I assume it is doing the create of disk1 zvol before updating the zfs reservations with the new value of flexible_disk_size, but VM.js is a confusing beast.
Doing
vmadm update $(vmadm lookup hostname=bhyvetest) flexible_disk_size=14592
before doing the add_disks payload works fine. Which seem to indeed indicate that the ordering is somehow wrong internally when both are in the same payload.The text was updated successfully, but these errors were encountered: