Blog posts tagged with 'xen'

It was late in the afternoon, on a typically harsh Canadian winter day, as Rob McEwen, the CEO of Goldcorp Inc., stood at the head of the boardroom table confronting a room full of senior geologists. The news he was about to deliver was not good. In fact it was disastrous, and McEwen was having a hard time shielding his frustration.

The small Toronto-based gold-mining firm was struggling, besieged by strikes, lingering debts, and an exceedingly high cost of production, which had caused them to cease mining operations. Conditions in the marketplace were hardly favorable. The gold market was contracting, and most analysts assumed that the company's fifty-year-old mine in Red Lake, Ontario, was dying. Without evidence of substantial new gold deposits, the mine seemed destined for closure, and Goldcorp was likely to go down with it. Tensions were running at fever pitch. McEwen had no real experience in the extractive industries, let alone in gold mining. Nevertheless, as an adventurous young mutual fund manager he had gotten involved in a takeover battle and emerged as Goldcorp, Inc.'s majority owner. Few people in the room had much confidence that McEwen was the right person to rescue the company. But McEwen just shrugged off his critics.

He turned to his geologists and said, "We're going to find more gold on this property, and we won't leave this room tonight until we have a plan to find it." At the conclusion of the meeting he handed his geologists $10 million for further exploration and sent them packing for Northern Ontario. Most of his staff thought he was crazy but they carried out his instructions, drilling in the deepest and most remote parts of the mine. Amazingly, 2 few weeks later they arrived back at Goldcorp headquarters beaming with pride and bearing a remarkable discovery: Test drilling suggested rich deposits of new gold, as much as thirty times the amount Goldcorp was currently mining!

The discovery was surprising, and could hardly have been better timed. But after years of further exploration, and to McEwen's deep frustration, the company's geologists struggled to provide an accurate estimate of the gold's value and exact location. He desperately needed to inject the urgency of the market into the glacial processes of an old-economy industry.

In 1999, with the future still uncertain, McEwen took some time out for personal development. He wound up at an MIT conference for young presidents when coincidentally the subject of Linux came up. Perched in the lecture hall, McEwen listened intently to the remarkable story of how Linus Torvalds and a loose volunteer brigade of software developers had assembled the world-class computer operating system over the Internet. The lecturer explained how Torvalds revealed his code to the world, allowing thousands of anonymous programmers to vet it and make contributions of their own.

McEwen had an epiphany and sat back in his chair to contemplate. If Goldcorp employees couldn't find the Red Lake gold, maybe someone else could. And maybe the key to finding those people was to open up the exploration process in the same way Torvalds "open sourced" Linux.

McEwen raced back to Toronto to present the idea to his head geologist. "I'd like to take all of our geology, all the data we have that goes back to 1948, and put it into a file and share it with the world," he said. "Then we'll ask the world to tell us where we're going to find the next six million ounces of gold." McEwen saw this as an opportunity to harness some of the best minds in the industry. Perhaps understandably, the in-house geologists were just a little skeptical.

Mining is an intensely secretive industry, and apart from the minerals themselves, geological data is the most precious and carefully guarded resource. It's like the Cadbury secret-it's just not something companies go around sharing. Goldcorp employees wondered whether the global community of geologists would respond to Goldcorp's call in the same way that software developers rallied around Linus Torvalds. Moreover, they worried about how the contest would reflect on them and their inability to find the illusive gold deposits.

McEwen acknowledges in retrospect that the strategy was controversial and risky. "We were attacking a fundamental assumption; you simply don't give away proprietary data," he said. "It's so fundamental," he adds, "that no one had ever questioned it." Once again, McEwen was determined to soldier on.

In March 2000, the "Goldcorp Challenge" was launched with a total of $575,000 in prize money available to participants with the best methods and estimates. Every scrap of information (some four hundred megabytes worth) about the 55,000-acre property was revealed on Goldcorp's Web site. News of the contest spread quickly around the Internet, as more than one thousand virtual prospectors from fifty countries got busy crunching the data.

Within weeks, submissions from around the world came flooding in to Goldcorp headquarters. As expected, geologists got involved. But entries came from surprising sources, including graduate students, consultants, mathematicians, and military officers, all seeking a piece of the action. "We had applied math, advanced physics, intelligent systems, computer graphics, and organic solutions to inorganic problems. There were capabilities I had never seen before in the industry," says McEwen. "When I saw the computer graphics I almost fell out of my chair." The contestants had identified 110 targets on the Red Lake property, 50 percent of which had not been previously identified by the company. Over 80 percent of the new targets yielded substantial quantities of gold. In fact, since the challenge was initiated an astounding eight million ounces of gold have been found. McEwen estimates the collaborative process shaved two to three years off their exploration time.

Today Goldcorp is reaping the fruits of its open source approach to exploration. Not only did the contest yield copious quantities of gold, it catapulted his under-performing $ 100 million company into a $9 billion juggernaut while transforming a backward mining site in Northern Ontario into one of the most innovative and profitable properties in the industry. Needless to say McEwen is one happy camper. As are his shareholders. One hundred dollars invested in the company in 1993 is worth over $3,000 today.

Perhaps the most lasting legacy of the Goldcorp Challenge is the validation of an ingenious approach to exploration in what remains a conservative and highly secretive industry. Rob McEwen bucked an industry trend by sharing the company's proprietary data and simultaneously transformed 2 lumbering exploration process into a modem distributed gold discovery engine that harnessed some of the most talented minds in the field.

McEwen saw things differently. He realized that the uniquely qualified minds to make new discoveries were probably outside the boundaries of his organization, and by sharing some intellectual property he could harness the power of collective genius and capability. In doing so he stumbled successfully into the future of innovation, business, and how wealth and just about everything else will be created. Welcome to the new world of wikinomics where collaboration on a mass scale is set to change every institution in society.

Last time, XenSource was not yet acquired by Citrix. What were the reasons to consider this sale?

I think we were doing pretty well as XenSource, but one of the challenges we faced is that it takes time to build a 'sales channel' to distribute software. Citrix already have a great sales channel, so the acquisition provided a great opportunity to take Xen to the mass-market.

What kind of open-source commitment do you expect from Citrix?

Citrix have been great in supporting the open source side of things, funding folk to work full-time on open source Xen, and also funding a full time Xen programme manager. The management understand the importance of a strong Xen community and the need for the project's independence from Citrix's own Xen products.

The change was always going to make some members of the community nervous (just like when we originally formed XenSource), but it's the same group of people and we intend to carry on just as before. One difference is that we now have 'xen.org' to provide a clear independent identity for the Xen project, and also the Xen Advisory Board to help govern the project.

How does Xen's future look on Windows platforms?

Lots of people use Xen to run Windows VMs -- after all, Windows arguably needs virtualization more than Unix OSes. I reckon that something like over 80% of the VMs running on XenServer are Windows.

We began using Xen in Fall 2003 soon after reading the paper "Xen and the Art of Virtualization" published in the Symposium on Operating Systems Principles (SOSP). After attending SOSP and talking to some of the authors, Jeanna Matthews returned excited about Xen. She and her graduate operating systems course at Clarkson University decided to repeat and extend the results reported in that paper. That class included two of the co-authors for this book, Eli Dow (currently at IBM) and Todd Deshane (currently completing his Ph.D.), who were both studying for their Master's degrees at the time. In the process of repeating the results from the 2003 Xen paper, we learned a lot about running Xen - much of it the hard way! Our goal for this book was to write exactly the material we wished was available when we first started using Xen.

In July 2004, we published the paper "Xen and the Art of Repeated Research" describing our experience with Xen and presenting the results we obtained repeating and extending the results. All the authors, in addition to being a part of the Fall 2003 graduate operating systems course, were also members of the Applied Computing Laboratories at Clarkson University specifically the Clarkson Open Source Institute (COSI) and the Clarkson Internet Teaching Laboratory (ITL). These labs were founded to provide students with hands-on experience with cutting-edge computing technologies and to form a community in which everyone both learns and teaches. Other students in the labs - both graduate and undergraduate - began to use Xen as the basis for both production systems and for research projects. Through the years, we have used Xen as the basis for a number of academic papers as well as the basis of award winning team projects. In the process, we have learned a lot about running Xen. It is our goal in this book to share this knowledge with you and to make your experience running Xen as smooth and simple as possible.

• Chapter 1 - Xen: Background and Virtualization Basics
• Chapter 2 - A Quick Tour with the Xen LiveCD
• Chapter 3 - The Xen Hypervisor
• Chapter 4 - Hardware Requirements and Installation of Xen Dom0
• Chapter 5 - Using Prebuilt Guest Images
• Chapter 6 - Managing Unprivileged Domains
• Chapter 7 - Populating Guest Images
• Chapter 8 - Storing Guest Images
• Chapter 9 - Device Virtualization and Management
• Chapter 10 - Network Configuration
• Chapter 11 - Securing a Xen System
• Chapter 12 - Managing Guest Resources
• Chapter 13 - Guest Save, Restore, and Migration
• Chapter 14 - Xen in the Enterprise: A Brief Survey
• Appendix A - Resources
• Appendix B - The xm command
• Appendix C - Xend Configuration Parameters
• Appendix D - Guest Configuration Parameters
• Appendix E - Xen Performance Evaluation

It was late in the afternoon, on a typically harsh Canadian winter day, as Rob McEwen, the CEO of Goldcorp Inc., stood at the head of the boardroom table confronting a room full of senior geologists. The news he was about to deliver was not good. In fact it was disastrous, and McEwen was having a hard time shielding his frustration.

The small Toronto-based gold-mining firm was struggling, besieged by strikes, lingering debts, and an exceedingly high cost of production, which had caused them to cease mining operations. Conditions in the marketplace were hardly favorable. The gold market was contracting, and most analysts assumed that the company's fifty-year-old mine in Red Lake, Ontario, was dying. Without evidence of substantial new gold deposits, the mine seemed destined for closure, and Goldcorp was likely to go down with it. Tensions were running at fever pitch. McEwen had no real experience in the extractive industries, let alone in gold mining. Nevertheless, as an adventurous young mutual fund manager he had gotten involved in a takeover battle and emerged as Goldcorp, Inc.'s majority owner. Few people in the room had much confidence that McEwen was the right person to rescue the company. But McEwen just shrugged off his critics.

He turned to his geologists and said, "We're going to find more gold on this property, and we won't leave this room tonight until we have a plan to find it." At the conclusion of the meeting he handed his geologists $10 million for further exploration and sent them packing for Northern Ontario. Most of his staff thought he was crazy but they carried out his instructions, drilling in the deepest and most remote parts of the mine. Amazingly, 2 few weeks later they arrived back at Goldcorp headquarters beaming with pride and bearing a remarkable discovery: Test drilling suggested rich deposits of new gold, as much as thirty times the amount Goldcorp was currently mining!

The discovery was surprising, and could hardly have been better timed. But after years of further exploration, and to McEwen's deep frustration, the company's geologists struggled to provide an accurate estimate of the gold's value and exact location. He desperately needed to inject the urgency of the market into the glacial processes of an old-economy industry.

In 1999, with the future still uncertain, McEwen took some time out for personal development. He wound up at an MIT conference for young presidents when coincidentally the subject of Linux came up. Perched in the lecture hall, McEwen listened intently to the remarkable story of how Linus Torvalds and a loose volunteer brigade of software developers had assembled the world-class computer operating system over the Internet. The lecturer explained how Torvalds revealed his code to the world, allowing thousands of anonymous programmers to vet it and make contributions of their own.

McEwen had an epiphany and sat back in his chair to contemplate. If Goldcorp employees couldn't find the Red Lake gold, maybe someone else could. And maybe the key to finding those people was to open up the exploration process in the same way Torvalds "open sourced" Linux.

McEwen raced back to Toronto to present the idea to his head geologist. "I'd like to take all of our geology, all the data we have that goes back to 1948, and put it into a file and share it with the world," he said. "Then we'll ask the world to tell us where we're going to find the next six million ounces of gold." McEwen saw this as an opportunity to harness some of the best minds in the industry. Perhaps understandably, the in-house geologists were just a little skeptical.

Mining is an intensely secretive industry, and apart from the minerals themselves, geological data is the most precious and carefully guarded resource. It's like the Cadbury secret-it's just not something companies go around sharing. Goldcorp employees wondered whether the global community of geologists would respond to Goldcorp's call in the same way that software developers rallied around Linus Torvalds. Moreover, they worried about how the contest would reflect on them and their inability to find the illusive gold deposits.

McEwen acknowledges in retrospect that the strategy was controversial and risky. "We were attacking a fundamental assumption; you simply don't give away proprietary data," he said. "It's so fundamental," he adds, "that no one had ever questioned it." Once again, McEwen was determined to soldier on.

In March 2000, the "Goldcorp Challenge" was launched with a total of $575,000 in prize money available to participants with the best methods and estimates. Every scrap of information (some four hundred megabytes worth) about the 55,000-acre property was revealed on Goldcorp's Web site. News of the contest spread quickly around the Internet, as more than one thousand virtual prospectors from fifty countries got busy crunching the data.

Within weeks, submissions from around the world came flooding in to Goldcorp headquarters. As expected, geologists got involved. But entries came from surprising sources, including graduate students, consultants, mathematicians, and military officers, all seeking a piece of the action. "We had applied math, advanced physics, intelligent systems, computer graphics, and organic solutions to inorganic problems. There were capabilities I had never seen before in the industry," says McEwen. "When I saw the computer graphics I almost fell out of my chair." The contestants had identified 110 targets on the Red Lake property, 50 percent of which had not been previously identified by the company. Over 80 percent of the new targets yielded substantial quantities of gold. In fact, since the challenge was initiated an astounding eight million ounces of gold have been found. McEwen estimates the collaborative process shaved two to three years off their exploration time.

Today Goldcorp is reaping the fruits of its open source approach to exploration. Not only did the contest yield copious quantities of gold, it catapulted his under-performing $ 100 million company into a $9 billion juggernaut while transforming a backward mining site in Northern Ontario into one of the most innovative and profitable properties in the industry. Needless to say McEwen is one happy camper. As are his shareholders. One hundred dollars invested in the company in 1993 is worth over $3,000 today.

Perhaps the most lasting legacy of the Goldcorp Challenge is the validation of an ingenious approach to exploration in what remains a conservative and highly secretive industry. Rob McEwen bucked an industry trend by sharing the company's proprietary data and simultaneously transformed 2 lumbering exploration process into a modem distributed gold discovery engine that harnessed some of the most talented minds in the field.

McEwen saw things differently. He realized that the uniquely qualified minds to make new discoveries were probably outside the boundaries of his organization, and by sharing some intellectual property he could harness the power of collective genius and capability. In doing so he stumbled successfully into the future of innovation, business, and how wealth and just about everything else will be created. Welcome to the new world of wikinomics where collaboration on a mass scale is set to change every institution in society.

Ian Pratt is the leader and chief architect of the Xen project, which he founded in 2001 with the aim of making virtualization ubiquitous on scale-out hardware, and was a founder of XenSource. Ian has played a key role in both the architecture of Xen and formation of industry partnerships that led to the emergence of Xen as the open source virtualization technology. Ian is a member of Senior faculty at the Computer Laboratory of Cambridge University, UK, where he has led Systems Research for 7 years. He holds a PhD in Computer Science, and was elected a Fellow of Kings College in 1996. Ian was a founder of Nemesys Research, acquired by FORE Systems, and has consulted widely in the technology industry.

Creation of the new Xen Project Avisory Board and Xen.org

Members of the Xen Advisory Board include the following

• Citrix
• IBM
• Intel
• HP
• Novell
• Red Hat
• Sun

The Xen Project Mission Statement is -

Build the industry standard open source hypervisor
- Core "engine" that is incorporated into multiple vendors' products
• Maintain our industry-leading performance
- Be first to exploit new hardware acceleration features
- Help OS vendors paravirtualize their OSes
• Maintain our reputation for stability and quality
- Security must now be paramount
• Support multiple CPU types; big and small systems
- From server to client to mobile
• Foster innovation
- Be a great platform for research and experimentation
• Drive interoperability
- Between Xen-based products
- With other virtualization products

there is wide industry participation in the Xen hypervisor open source project. In this Xen Summit alone there were six presentations from Intel, three presentations from Sun and Red Hat, and two from HP and three from Citrix. In the Spring 2007 Xen Summit, there were eight presentations by IBM, three presentations by HP, two presentations by AMD, three by Red Hat, and seven by XenSource/Citrix. The Xen Open Source hypervisor is pulling in the creativity, innovation, knowledge and experience of a wide range of industry heavyweights. This effort is completely focused on building a highly scalable, stable and a powerful 64 bit virtualization engine.

 Xen's true hypervisor architecture enables
excellent security and scalability
• Lightweight service domains
- I/O driver domains and utility domains
- Device emulation domains
- Domain building / measurement domains
• Allows efficient large SMP scalability
• Minimum privilege, small TCB
- De-privilege and disaggregate domain 0
True hypervisor design
- Small privileged component, principle of least privilege
• Secure compartmentalization
- Grant tables allow controlled sharing
• Optimized as a hypervisor
• Cross-platform: x86, ia64, Power and ARM
• OS agnostic: Windows, Linux, Solaris, *BSD
• Flexible to enable domain0 disaggregation
- Control-plane OS (e.g. OpenBSD or MiniOS)
- Driver domains
- Service domains (e.g. virus scanners, firewalls etc)

Server
- Performance and scalability optimizations
- Enable Smart IO devices
- SCSI pass-through

• Security
- Domain0 disaggregation; XSM Xen Security Modules
- Secure boot, TPM, certification, multi-level secure systems

• Client
- Power management
  Suspend and hibernate; Clock management
- 3D video
   direct h/w access; high-performance guest virtualization
- USB device pass-through

after attending a summary of the recent Citrix iForum it became clear that XenServer will pose a significant challenge in all areas to the VMware offering asthe resources of Citrix are integrated to the XenServer platform as the products mature.    

it may be a good idea to determine the differences from the management side between VMware ESX and Citrix XenServer Enterprise edition. There are some differences, and as the next release of XenServer that has had the Citrix touch on the whole build, there should be some exciting new features that will surely give VMware a challenge for the best enterprise virtualization product. Regardless, we all win, as a better suite of products will be made available to the enterprise