Receive "Unsupported virtualization type" unless the -v option is used

You need to use option --hvm. Have a look to "virt-install --help" output.

marking as invalid, this was an improper usage error...

Changing back to New. Here's the command I used to create a VM:

  sudo virt-install -n web_devel -r 256 -f web_devel.img -s 4 -c ISO/jaunty-server-amd64.iso --accelerate --connect=qemu:///system --vnc --noautoconsole

From what I understand the --accelerate option makes use of hardware acceleration options:

       --accelerate
           When installing a QEMU guest, make use of the KVM or KQEMU kernel acceleration capabilities if available. Use of this option is recommended unless a guest OS is
           known to be incompatible with the accelerators. The KVM accelerator is preferred over KQEMU if both are available.

Using the -v or -hvm option does not:

       -v, --hvm This guest should be a fully virtualized guest
           Request the use of full virtualization, if both para & full virtualization are available on the host. This parameter may not be available if connecting to a Xen
           hypervisor on a machine without hardware virtualization support. This parameter is implied if connecting to a QEMU based hypervisor.

I have hardware acceleration:

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch

But the command thinks I don't. Maybe I'm mistaken and have my terms mixed up, or I wasn't clear enough in the description, but the issue is that on a system with a processor that supports the virtualization extensions I shouldn't have to use the -v option. I should be able to use paravirtualization, by either using the --accelerate or -p option.

Also, note this worked using virt-install on Hardy.

Apologies, I was confused. Soren set me straight on IRC, but mentioned he'd like to keep the bug open because virt-install "should behave better".

Thanks all.

in that case it's not "incomplete", but "confirmed", priority low

Also notice that the examples provided in the documentation found on http://doc.ubuntu.com/ubuntu/serverguide/C/virtualization.html won't work because of this bug.

Thanks for the reminder Franck, I've committed the change to revision 204 of the Jaunty branch.

I've hit the same bug. What's the workaround or confusion mentioned in #4?

Huh, for reasons I don't fully understand, I no longer get this error message. Maybe it takes two reboots for the BIOS change (enabling virtualization) to take effect.

Looks like this was fixed in the jaunty timeframe, and intrepid is now end of life. Closing this bug.