{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:39:38Z","timestamp":1750307978724,"version":"3.41.0"},"reference-count":2,"publisher":"Association for Computing Machinery (ACM)","issue":"1","license":[{"start":{"date-parts":[[2008,1,1]],"date-time":"2008-01-01T00:00:00Z","timestamp":1199145600000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["Queue"],"published-print":{"date-parts":[[2008,1]]},"abstract":"<jats:p>Virtualization can be implemented in many different ways. It can be done with and without hardware support. The virtualized operating system can be expected to be changed in preparation for virtualization, or it can be expected to work unchanged. Regardless, software developers must strive to meet the three goals of virtualization spelled out by Gerald Popek and Robert Goldberg: fidelity, performance, and safety.<\/jats:p>","DOI":"10.1145\/1348583.1348591","type":"journal-article","created":{"date-parts":[[2008,3,12]],"date-time":"2008-03-12T22:35:44Z","timestamp":1205361344000},"page":"28-35","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":32,"title":["The Cost of Virtualization"],"prefix":"10.1145","volume":"6","author":[{"given":"Ulrich","family":"Drepper","sequence":"first","affiliation":[{"name":"Red Hat"}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2008,1]]},"reference":[{"key":"e_1_2_1_1_1","doi-asserted-by":"publisher","DOI":"10.1145\/361011.361073"},{"key":"e_1_2_1_2_1","unstructured":"Drepper U. 2007. What every programmer should know about memory; http:\/\/people.redhat.com\/drepper\/cpumemory.pdf.  Drepper U. 2007. What every programmer should know about memory; http:\/\/people.redhat.com\/drepper\/cpumemory.pdf."}],"container-title":["Queue"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1348583.1348591","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/1348583.1348591","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T14:58:30Z","timestamp":1750258710000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1348583.1348591"}},"subtitle":["Software developers need to be aware of the compromises they face when using virtualization technology."],"short-title":[],"issued":{"date-parts":[[2008,1]]},"references-count":2,"journal-issue":{"issue":"1","published-print":{"date-parts":[[2008,1]]}},"alternative-id":["10.1145\/1348583.1348591"],"URL":"https:\/\/doi.org\/10.1145\/1348583.1348591","relation":{},"ISSN":["1542-7730","1542-7749"],"issn-type":[{"type":"print","value":"1542-7730"},{"type":"electronic","value":"1542-7749"}],"subject":[],"published":{"date-parts":[[2008,1]]},"assertion":[{"value":"2008-01-01","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}