Thanks all for replying. We want to stick on to the Xen Hypervisor for some reason.
1. Does the community plan to support this feature? 2. Could I submit this request to the blueprint? My team would like to contribute on it if necessary. 3. or some good reasons to migrate from Xen to KVM? Regards 在 2012-6-22 上午2:52，"Nathanael Burton" <nathanael.i.bur...@gmail.com>写道： > Seems like an attribute that could be added to instance types / flavors > that could be passed on to the scheduler and virt layers. > > Nate > On Jun 21, 2012 2:12 PM, "Daniel P. Berrange" <berra...@redhat.com> wrote: > >> On Fri, Jun 22, 2012 at 12:17:11AM +0800, Huang Zhiteng wrote: >> > Of course it is possible. What kind of issue did you run into? >> > >> > On Thu, Jun 21, 2012 at 5:52 PM, Wang Li <fox...@gmail.com> wrote: >> > > hi,all >> > > >> > > I need to run virtual machines on Xen Hypervisor in HVM mode, >> > > is it possible when using libvirt? >> >> Actually, this is not currently possible. For reasons I don't >> know, the libvirt driver currently hardcodes use of paravirtualized >> guests when connected to Xen hosts. It does not allow use of HVM >> guests. There's no particularly good technical reason why it can't >> be made to work. There'd need to be a way to tag instance types >> with HVM vs paravirt, in addition to their architecture. The >> libvirt driver would have to expose whether each host supports >> paravirt or HVM or both. The schedular would then have to take >> this into account when placing guests. >> >> Until this is done, if you really need to run HVM guests, then >> you'll have to use KVM instead of Xen. >> >> Regards, >> Daniel >> -- >> |: http://berrange.com -o- >> http://www.flickr.com/photos/dberrange/ :| >> |: http://libvirt.org -o- >> http://virt-manager.org :| >> |: http://autobuild.org -o- >> http://search.cpan.org/~danberr/ :| >> |: http://entangle-photo.org -o- >> http://live.gnome.org/gtk-vnc :| >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
