vmadm core dump

[Licenser]

The core file can be found here: https://www.dropbox.com/s/3iufhrfqo3x4su3/core.vmadm.80260.gz

I can reproduce it with vmadm delete

running: SunOS 00-25-90-a6-48-0d 5.11 joyent_20130222T000747Z i86pc i386 i86pc

The situation happend after:

1. creating a vm with this load:

{                                                                                                                                                                                                                                               "alias": "server",                                                                                                                                                                                                                            "brand": "kvm",                                                                                                                                                                                                                               "cpu_cap": 300,                                                                                                                                                                                                                               "cpu_shares": 513,
  "customer_metadata": {
    "root_authorized_keys": "..."
  },
  "disk_driver": "virtio",
  "disks": [
    {
      "boot": true,
      "image_size": "16384",
      "image_uuid": "3162a91e-8b5d-11e2-a78f-9780813f9142"
    },
    {
      "boot": false,
      "size": 20480
    }
  ],
  "internal_metadata": {
    "package": "fc239e55-e6aa-4b42-88b2-9b7981fda038"
  },
  "max_physical_memory": 9216,
  "nic_driver": "virtio",
  "nics": [
    {
      "gateway": "192.168.0.1",
      "ip": "192.168.0.213",
      "netmask": "255.255.255.0",
      "nic_tag": "admin",
      "primary": true
    }
  ],
  "ram": 8192,
  "resolvers": [
    "8.8.8.8",
    "8.8.4.4"
  ],
  "uuid": "0f118d50-fe4c-42e0-aab7-c9b166e27ca7",
  "vcpus": 3,
  "zfs_io_priority": 1024
}

Which failed with:

[root@00-25-90-a6-48-0d ~]# vmadm create -f /zones/s.json
Command failed: zoneadm: zone '0f118d50-fe4c-42e0-aab7-c9b166e27ca7': (priv=privileged,limit=1026,action=none) is not a valid value for rctl 'zone.zfs-io-priority'
zoneadm: zone 0f118d50-fe4c-42e0-aab7-c9b166e27ca7 failed to verify

After that the VM was deleted and tried to recreate (with adjusted io priority):

[root@00-25-90-a6-48-0d ~]# vmadm delete 0f118d50-fe4c-42e0-aab7-c9b166e27ca7
Successfully deleted 0f118d50-fe4c-42e0-aab7-c9b166e27ca7
[root@00-25-90-a6-48-0d ~]# vmadm create -f /zones/s.json
Command failed: cannot create snapshot 'zones/3162a91e-8b5d-11e2-a78f-9780813f9142@0f118d50-fe4c-42e0-aab7-c9b166e27ca7-disk0': dataset already exists

It is not existing in zoneadm list nor /etc/zones.

[root@00-25-90-a6-48-0d /zones]# zoneadm list -ivc
  ID NAME             STATUS     PATH                           BRAND    IP
   0 global           running    /                              liveimg  shared
   1 6889a3c8-b630-44fb-9e35-c740020c3361 running    /zones/6889a3c8-b630-44fb-9e35-c740020c3361 joyent   excl
   2 8f343844-f1ec-4338-920c-194bfb9f9228 running    /zones/8f343844-f1ec-4338-920c-194bfb9f9228 joyent   excl

[joshwilsdon]

Can you also provide /var/log/vm/1365099746582-080260-vmadm.log file and the output of:

bunyan -o json-0 -c 'this.vm === "0f118d50-fe4c-42e0-aab7-c9b166e27ca7"' /var/log/vm/* 

those would help me track down what's going on here.

[Licenser]

here you go: https://gist.github.com/Licenser/5313378

That said I don't think it's related with the VM itself, I can reproduce it with any uuid that is valid but not an existing VM.