On Tue, Aug 19, 2008 at 11:25:21AM +0900, Jun Koi wrote:
> Yes, that was a mistake. I changed -c to --connect, and get the error
> "Unsupported virtualization type" now. How can I fix it?
I've been bitten by this very same error message in virt-install.
Took me absolutely ages to work out that I had to use the '--hvm'
option. It's a usability bug in virt-install, plain and simple.
Attached is a patch which clarifies the error message.
Rich.
--
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
Read my OCaml programming blog: http://camltastic.blogspot.com/
Fedora now supports 60 OCaml packages (the OPEN alternative to F#)
http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora
diff -r de5bcee1e78f virtinst/ImageManager.py
--- a/virtinst/ImageManager.py Mon Aug 18 16:33:57 2008 -0400
+++ b/virtinst/ImageManager.py Wed Aug 20 14:08:00 2008 +0100
@@ -46,7 +46,7 @@
self._guest = self._capabilities.guestForOSType(self._boot_caps.type, self._boot_caps.arch)
if self._guest is None:
- raise PlatformMatchException(_("Unsupported virtualization type"))
+ raise PlatformMatchException(_("Unsupported virtualization type. If the host only supports full virtualization, try adding the --hvm option."))
self._domain = self._guest.bestDomainType()
self.type = self._domain.hypervisor_type
--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list