DE · EN

Call us

build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | built 2026-10-21 12:35 UTC format run

$ soultec get post/cannot-power-on-view-vms-after-deleting-resource-pools -o yaml$ soultec get post/cannot-power-on-view-vms-after-deleting-resource-pools -o json$ soultec get post/cannot-power-on-view-vms-after-deleting-resource-pools -o toml$ soultec get post/cannot-power-on-view-vms-after-deleting-resource-pools -o xml$ python3 cannot-power-on-view-vms-after-deleting-resource-pools.pyPS> ./cannot-power-on-view-vms-after-deleting-resource-pools.ps1$ go run cannot-power-on-view-vms-after-deleting-resource-pools.go$ node cannot-power-on-view-vms-after-deleting-resource-pools.js

apiVersion: soultec.ch/v1kind: Postmetadata: name: cannot-power-on-view-vms-after-deleting-resource-pools locale: en labels: author: dario-doerflinger series: lessons-learned capability/modern-workplace: 1.69 capability/virtualization: 1.42 vendor/omnissa: 1.99 vendor/vmware: 0.98 annotations: source: blog-content/posts/en/cannot-power-on-view-vms-after-deleting-resource-pools.md route: /en/insights/cannot-power-on-view-vms-after-deleting-resource-pools/ schema: /nerd/schema/posts.json markdown: /en/insights/cannot-power-on-view-vms-after-deleting-resource-pools.mdspec: title: Cannot power on VMs after deleting resource pools date: 2017-07-27 author: dario-doerflinger locale: en summary: >- One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected. capabilities: [modern-workplace, virtualization] vendors: [omnissa, vmware] series: lessons-learned legacySlug: cannot-power-on-view-vms-after-deleting-resource-pools migrated: 2026-08-24 draft: false sections: - body: | One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected. One thing he did during the cleaning up was to get rid of a number of resource pools that were only created for the purpose of putting the VMs into "folders" when viewed from the old C# Client. After fixing other errors he was ready to create new linked clones. But they could not power on. The error message said: > The available memory resources in the parent resource pool are insufficient for this operation Turns out the hosts had a file in /etc/vmware which referred to the resource pools and was not properly cleaned up. In order to solve this problem the following had to be run on each esxi host: > rm /etc/vmware/pools.xml > /etc/init.d/hostd restart > /etc/init.d/vpxa restart After that the VMs were able to power-on as expected and the environment was up and running again.status: corpus: 315 alsoLike: - {ref: posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus, score: 1.00} - {ref: posts/ubersicht-omnissa-horizon-fur-citrix-kunden, score: 1.00} - {ref: solutions/omnissa/horizon/omnissa-app-volumes, score: 1.00} search: /en/search.json

{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "cannot-power-on-view-vms-after-deleting-resource-pools", "locale": "en", "labels": { "author": "dario-doerflinger", "series": "lessons-learned", "capability/modern-workplace": 1.69, "capability/virtualization": 1.42, "vendor/omnissa": 1.99, "vendor/vmware": 0.98 }, "annotations": { "source": "blog-content/posts/en/cannot-power-on-view-vms-after-deleting-resource-pools.md", "route": "/en/insights/cannot-power-on-view-vms-after-deleting-resource-pools/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/cannot-power-on-view-vms-after-deleting-resource-pools.md" } }, "spec": { "title": "Cannot power on VMs after deleting resource pools", "date": "2017-07-27", "author": "dario-doerflinger", "locale": "en", "summary": "One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected.", "capabilities": [ "modern-workplace", "virtualization" ], "vendors": [ "omnissa", "vmware" ], "series": "lessons-learned", "legacySlug": "cannot-power-on-view-vms-after-deleting-resource-pools", "migrated": "2026-08-24", "draft": false, "sections": [ { "body": "One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected. One thing he did during the cleaning up was to get rid of a number of resource pools that were only created for the purpose of putting the VMs into \"folders\" when viewed from the old C# Client.\n\nAfter fixing other errors he was ready to create new linked clones. But they could not power on. The error message said:\n\n> The available memory resources in the parent resource pool are insufficient for this operation\n\nTurns out the hosts had a file in /etc/vmware which referred to the resource pools and was not properly cleaned up. In order to solve this problem the following had to be run on each esxi host:\n\n> rm /etc/vmware/pools.xml \n> /etc/init.d/hostd restart \n> /etc/init.d/vpxa restart\n\nAfter that the VMs were able to power-on as expected and the environment was up and running again." } ] }, "status": { "corpus": 315, "alsoLike": [ { "ref": "posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus", "score": "1.00" }, { "ref": "posts/ubersicht-omnissa-horizon-fur-citrix-kunden", "score": "1.00" }, { "ref": "solutions/omnissa/horizon/omnissa-app-volumes", "score": "1.00" } ], "search": "/en/search.json" }}

apiVersion = "soultec.ch/v1"kind = "Post"[metadata]name = "cannot-power-on-view-vms-after-deleting-resource-pools"locale = "en"[metadata.labels]author = "dario-doerflinger"series = "lessons-learned""capability/modern-workplace" = 1.69"capability/virtualization" = 1.42"vendor/omnissa" = 1.99"vendor/vmware" = 0.98[metadata.annotations]source = "blog-content/posts/en/cannot-power-on-view-vms-after-deleting-resource-pools.md"route = "/en/insights/cannot-power-on-view-vms-after-deleting-resource-pools/"schema = "/nerd/schema/posts.json"markdown = "/en/insights/cannot-power-on-view-vms-after-deleting-resource-pools.md"[spec]title = "Cannot power on VMs after deleting resource pools"date = 2017-07-27author = "dario-doerflinger"locale = "en"summary = "One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected."capabilities = ["modern-workplace", "virtualization"]vendors = ["omnissa", "vmware"]series = "lessons-learned"legacySlug = "cannot-power-on-view-vms-after-deleting-resource-pools"migrated = 2026-08-24draft = false[[spec.sections]]body = '''One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected. One thing he did during the cleaning up was to get rid of a number of resource pools that were only created for the purpose of putting the VMs into "folders" when viewed from the old C# Client.After fixing other errors he was ready to create new linked clones. But they could not power on. The error message said:> The available memory resources in the parent resource pool are insufficient for this operationTurns out the hosts had a file in /etc/vmware which referred to the resource pools and was not properly cleaned up. In order to solve this problem the following had to be run on each esxi host:> rm /etc/vmware/pools.xml > /etc/init.d/hostd restart > /etc/init.d/vpxa restartAfter that the VMs were able to power-on as expected and the environment was up and running again.'''[status]corpus = 315search = "/en/search.json"[[status.alsoLike]]ref = "posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus"score = "1.00"[[status.alsoLike]]ref = "posts/ubersicht-omnissa-horizon-fur-citrix-kunden"score = "1.00"[[status.alsoLike]]ref = "solutions/omnissa/horizon/omnissa-app-volumes"score = "1.00"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Post"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>cannot-power-on-view-vms-after-deleting-resource-pools</name> <locale>en</locale> <labels> <author>dario-doerflinger</author> <series>lessons-learned</series> <entry key="capability/modern-workplace">1.69</entry> <entry key="capability/virtualization">1.42</entry> <entry key="vendor/omnissa">1.99</entry> <entry key="vendor/vmware">0.98</entry> </labels> <annotations> <source>blog-content/posts/en/cannot-power-on-view-vms-after-deleting-resource-pools.md</source> <route>/en/insights/cannot-power-on-view-vms-after-deleting-resource-pools/</route> <schema>/nerd/schema/posts.json</schema> <markdown>/en/insights/cannot-power-on-view-vms-after-deleting-resource-pools.md</markdown> </annotations> </metadata> <spec> <title>Cannot power on VMs after deleting resource pools</title> <date>2017-07-27</date> <author>dario-doerflinger</author> <locale>en</locale> <summary>One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected.</summary> <capabilities> <item>modern-workplace</item> <item>virtualization</item> </capabilities> <vendors> <item>omnissa</item> <item>vmware</item> </vendors> <series>lessons-learned</series> <legacySlug>cannot-power-on-view-vms-after-deleting-resource-pools</legacySlug> <migrated>2026-08-24</migrated> <draft>false</draft> <sections> <section> <body>One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected. One thing he did during the cleaning up was to get rid of a number of resource pools that were only created for the purpose of putting the VMs into "folders" when viewed from the old C# Client.After fixing other errors he was ready to create new linked clones. But they could not power on. The error message said:> The available memory resources in the parent resource pool are insufficient for this operationTurns out the hosts had a file in /etc/vmware which referred to the resource pools and was not properly cleaned up. In order to solve this problem the following had to be run on each esxi host:> rm /etc/vmware/pools.xml > /etc/init.d/hostd restart > /etc/init.d/vpxa restartAfter that the VMs were able to power-on as expected and the environment was up and running again. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <alsoLike> <item> <ref>posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus</ref> <score>1.00</score> </item> <item> <ref>posts/ubersicht-omnissa-horizon-fur-citrix-kunden</ref> <score>1.00</score> </item> <item> <ref>solutions/omnissa/horizon/omnissa-app-volumes</ref> <score>1.00</score> </item> </alsoLike> <search>/en/search.json</search> </status></manifest>

# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "cannot-power-on-view-vms-after-deleting-resource-pools", "locale": "en", "labels": { "author": "dario-doerflinger", "series": "lessons-learned", "capability/modern-workplace": 1.69, "capability/virtualization": 1.42, "vendor/omnissa": 1.99, "vendor/vmware": 0.98, }, "annotations": { "source": "blog-content/posts/en/cannot-power-on-view-vms-after-deleting-resource-pools.md", "route": "/en/insights/cannot-power-on-view-vms-after-deleting-resource-pools/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/cannot-power-on-view-vms-after-deleting-resource-pools.md", }, }, "spec": { "title": "Cannot power on VMs after deleting resource pools", "date": "2017-07-27", "author": "dario-doerflinger", "locale": "en", "summary": "One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected.", "capabilities": ["modern-workplace", "virtualization"], "vendors": ["omnissa", "vmware"], "series": "lessons-learned", "legacySlug": "cannot-power-on-view-vms-after-deleting-resource-pools", "migrated": "2026-08-24", "draft": False, "sections": [ { "body": ( "One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected. One thing he did during the cleaning up was to get rid of a number of resource pools that were only created for the purpose of putting the VMs into \"folders\" when viewed from the old C# Client.\n" "\n" "After fixing other errors he was ready to create new linked clones. But they could not power on. The error message said:\n" "\n" "> The available memory resources in the parent resource pool are insufficient for this operation\n" "\n" "Turns out the hosts had a file in /etc/vmware which referred to the resource pools and was not properly cleaned up. In order to solve this problem the following had to be run on each esxi host:\n" "\n" "> rm /etc/vmware/pools.xml \n" "> /etc/init.d/hostd restart \n" "> /etc/init.d/vpxa restart\n" "\n" "After that the VMs were able to power-on as expected and the environment was up and running again." ), }, ], }, "status": { "corpus": 315, "alsoLike": [ { "ref": "posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus", "score": "1.00", }, { "ref": "posts/ubersicht-omnissa-horizon-fur-citrix-kunden", "score": "1.00", }, { "ref": "solutions/omnissa/horizon/omnissa-app-volumes", "score": "1.00", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))

# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Post' metadata = [ordered]@{ name = 'cannot-power-on-view-vms-after-deleting-resource-pools' locale = 'en' labels = [ordered]@{ author = 'dario-doerflinger' series = 'lessons-learned' 'capability/modern-workplace' = 1.69 'capability/virtualization' = 1.42 'vendor/omnissa' = 1.99 'vendor/vmware' = 0.98 } annotations = [ordered]@{ source = 'blog-content/posts/en/cannot-power-on-view-vms-after-deleting-resource-pools.md' route = '/en/insights/cannot-power-on-view-vms-after-deleting-resource-pools/' schema = '/nerd/schema/posts.json' markdown = '/en/insights/cannot-power-on-view-vms-after-deleting-resource-pools.md' } } spec = [ordered]@{ title = 'Cannot power on VMs after deleting resource pools' date = '2017-07-27' author = 'dario-doerflinger' locale = 'en' summary = 'One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected.' capabilities = @('modern-workplace', 'virtualization') vendors = @('omnissa', 'vmware') series = 'lessons-learned' legacySlug = 'cannot-power-on-view-vms-after-deleting-resource-pools' migrated = '2026-08-24' draft = $false sections = @( [ordered]@{ body = @'One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected. One thing he did during the cleaning up was to get rid of a number of resource pools that were only created for the purpose of putting the VMs into "folders" when viewed from the old C# Client.After fixing other errors he was ready to create new linked clones. But they could not power on. The error message said:> The available memory resources in the parent resource pool are insufficient for this operationTurns out the hosts had a file in /etc/vmware which referred to the resource pools and was not properly cleaned up. In order to solve this problem the following had to be run on each esxi host:> rm /etc/vmware/pools.xml > /etc/init.d/hostd restart > /etc/init.d/vpxa restartAfter that the VMs were able to power-on as expected and the environment was up and running again.'@ } ) } status = [ordered]@{ corpus = 315 alsoLike = @( [ordered]@{ ref = 'posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus' score = '1.00' } [ordered]@{ ref = 'posts/ubersicht-omnissa-horizon-fur-citrix-kunden' score = '1.00' } [ordered]@{ ref = 'solutions/omnissa/horizon/omnissa-app-volumes' score = '1.00' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32

// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": map[string]any{ "name": "cannot-power-on-view-vms-after-deleting-resource-pools", "locale": "en", "labels": map[string]any{ "author": "dario-doerflinger", "series": "lessons-learned", "capability/modern-workplace": 1.69, "capability/virtualization": 1.42, "vendor/omnissa": 1.99, "vendor/vmware": 0.98, }, "annotations": map[string]any{ "source": "blog-content/posts/en/cannot-power-on-view-vms-after-deleting-resource-pools.md", "route": "/en/insights/cannot-power-on-view-vms-after-deleting-resource-pools/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/cannot-power-on-view-vms-after-deleting-resource-pools.md", }, }, "spec": map[string]any{ "title": "Cannot power on VMs after deleting resource pools", "date": "2017-07-27", "author": "dario-doerflinger", "locale": "en", "summary": "One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected.", "capabilities": []any{"modern-workplace", "virtualization"}, "vendors": []any{"omnissa", "vmware"}, "series": "lessons-learned", "legacySlug": "cannot-power-on-view-vms-after-deleting-resource-pools", "migrated": "2026-08-24", "draft": false, "sections": []any{ map[string]any{ "body": "One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected. One thing he did during the cleaning up was to get rid of a number of resource pools that were only created for the purpose of putting the VMs into \"folders\" when viewed from the old C# Client.\n" + "\n" + "After fixing other errors he was ready to create new linked clones. But they could not power on. The error message said:\n" + "\n" + "> The available memory resources in the parent resource pool are insufficient for this operation\n" + "\n" + "Turns out the hosts had a file in /etc/vmware which referred to the resource pools and was not properly cleaned up. In order to solve this problem the following had to be run on each esxi host:\n" + "\n" + "> rm /etc/vmware/pools.xml \n" + "> /etc/init.d/hostd restart \n" + "> /etc/init.d/vpxa restart\n" + "\n" + "After that the VMs were able to power-on as expected and the environment was up and running again.", }, }, }, "status": map[string]any{ "corpus": 315, "alsoLike": []any{ map[string]any{ "ref": "posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus", "score": "1.00", }, map[string]any{ "ref": "posts/ubersicht-omnissa-horizon-fur-citrix-kunden", "score": "1.00", }, map[string]any{ "ref": "solutions/omnissa/horizon/omnissa-app-volumes", "score": "1.00", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}

// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Post", metadata: { name: "cannot-power-on-view-vms-after-deleting-resource-pools", locale: "en", labels: { author: "dario-doerflinger", series: "lessons-learned", "capability/modern-workplace": 1.69, "capability/virtualization": 1.42, "vendor/omnissa": 1.99, "vendor/vmware": 0.98, }, annotations: { source: "blog-content/posts/en/cannot-power-on-view-vms-after-deleting-resource-pools.md", route: "/en/insights/cannot-power-on-view-vms-after-deleting-resource-pools/", schema: "/nerd/schema/posts.json", markdown: "/en/insights/cannot-power-on-view-vms-after-deleting-resource-pools.md", }, }, spec: { title: "Cannot power on VMs after deleting resource pools", date: "2017-07-27", author: "dario-doerflinger", locale: "en", summary: "One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected.", capabilities: ["modern-workplace", "virtualization"], vendors: ["omnissa", "vmware"], series: "lessons-learned", legacySlug: "cannot-power-on-view-vms-after-deleting-resource-pools", migrated: "2026-08-24", draft: false, sections: [ { body: "One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected. One thing he did during the cleaning up was to get rid of a number of resource pools that were only created for the purpose of putting the VMs into \"folders\" when viewed from the old C# Client.\n" + "\n" + "After fixing other errors he was ready to create new linked clones. But they could not power on. The error message said:\n" + "\n" + "> The available memory resources in the parent resource pool are insufficient for this operation\n" + "\n" + "Turns out the hosts had a file in /etc/vmware which referred to the resource pools and was not properly cleaned up. In order to solve this problem the following had to be run on each esxi host:\n" + "\n" + "> rm /etc/vmware/pools.xml \n" + "> /etc/init.d/hostd restart \n" + "> /etc/init.d/vpxa restart\n" + "\n" + "After that the VMs were able to power-on as expected and the environment was up and running again.", }, ], }, status: { corpus: 315, alsoLike: [ { ref: "posts/soultec-ag-erreicht-hochsten-omnissa-partnerstatus", score: "1.00", }, { ref: "posts/ubersicht-omnissa-horizon-fur-citrix-kunden", score: "1.00", }, { ref: "solutions/omnissa/horizon/omnissa-app-volumes", score: "1.00", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 53 lines · YAML · validated at build# 64 lines · JSON · validated at build# 66 lines · TOML · validated at build# 78 lines · XML · validated at build# 78 lines · Python · read back at build, equals the JSON record# 75 lines · PowerShell · read back at build, equals the JSON record# 88 lines · Go · read back at build, equals the JSON record# 73 lines · JavaScript · read back at build, equals the JSON record · served at /en/insights/cannot-power-on-view-vms-after-deleting-resource-pools.md

Lessons learned · 2017-07-27

Cannot power on VMs after deleting resource pools

One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected.

2017-07-27Date

Dario DörflingerAuthor

1Min read

Topics Modern Workplace 1.69 Virtualization 1.42

Vendors Omnissa 1.99 VMware 0.98

This post is from 2017. It stays online because people still look for it, but it describes the products as they were then.

One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected. One thing he did during the cleaning up was to get rid of a number of resource pools that were only created for the purpose of putting the VMs into “folders” when viewed from the old C# Client.

After fixing other errors he was ready to create new linked clones. But they could not power on. The error message said:

The available memory resources in the parent resource pool are insufficient for this operation

Turns out the hosts had a file in /etc/vmware which referred to the resource pools and was not properly cleaned up. In order to solve this problem the following had to be run on each esxi host: