Q&A with Paul Maritz
I will not be attempting to live blog the entire Q&A session, but when I find a question and reply interesting I will make a note here. The wireless is still spotty, so once again I will keep updating this post as much as possible. I am paraphrasing the answers unless I provide quotes around the statement.
Commenting on open source competition and Linux virtualization alternatives:
Open source is very important because if you do not innovate the open source community will catch you.
How do we (your company) get involved with the development of this new vision of infrastructure?
VMware is figuring out how to interface their professional people with partners and clients to help enable the adoption of the new products
Note sure of the exact question, but the answer was that vmotion between AMD and Intel processors will still not be possible even after the new Intel announcement and future processor technologies.
Why call it a Virtual Datacenter Operating System?
It is like a OS in that it handles applications loads and has parallels like APIs and Services, but it is not an OS. We expect new types of applications to be developed to fulfill the services needed in the datacenter.
Question was asked to explain more about the Cisco vSwitch announcement Paul mentioned in the Keynote.
Under obligation to wait until 11:00 am for Cisco to officially announce.
Are you looking at extending Vmotion across data centers?
Looking at it with storage partners. We would need storage replication and therefore storage vendor partnership development to pull this off. There is also application challenges associated with live migration between physical locations.
Does VMware consider including the diversification of virtualization products of other vendors?
Today we do not support other company’s hypervisors. After we get our new framework operational we are not opposed to looking at this if customers request this.
Address the time drift issue in virtual infrastructure?
Referring to the Interrupt handling in Linux problems. We have submitted patches to the Linux community for the short term. In the long term the ability of the new client alignment and advances of technology to allow the VMs direct access to the hardware will help fix this
Are you ever going to release a VC client on Linux.
I would love to. Our client needs to be OS independent. Unfortunately there are several steps necessary to get there.
I/o Virtualization improvements
VMDirectPath is our answer already. Several breakout sessions already scheduled about this topic