On 06.02.2012 19:58, Felix Blanke wrote: > Hello, > > I have a problem with virt-install. I want to use it to create my vm and > manage them. But whenever I execute the virt-install cmd I get the error > msg mentioned in the subject. > > Here are some more informations: > > hp ~ # virt-install --virt-type kvm --arch x86_64 --debug > Mon, 06 Feb 2012 19:57:29 DEBUG Launched with command line: > /usr/bin/virt-install --virt-type kvm --arch x86_64 --debug > Mon, 06 Feb 2012 19:57:29 DEBUG Requesting libvirt URI default > Mon, 06 Feb 2012 19:57:29 DEBUG Received libvirt URI qemu:///system > Mon, 06 Feb 2012 19:57:29 DEBUG Requesting virt method 'default', hv > type 'kvm'. > Mon, 06 Feb 2012 19:57:29 ERROR Host does not support any > virtualization options for arch 'x86_64' > Mon, 06 Feb 2012 19:57:29 DEBUG Traceback (most recent call last): > File "/usr/bin/virt-install-2.7", line 272, in get_virt_type > machine=options.machine) > File > "/usr/lib64/python2.7/site-packages/virtinst/CapabilitiesParser.py", > line 732, in guest_lookup > {'virttype' : osstr, 'arch' : archstr}) > ValueError: Host does not support any virtualization options for arch > 'x86_64' > > > hp ~ # virsh --connect qemu:///system > Welcome to virsh, the virtualization interactive terminal. > > Type: 'help' for help with commands > 'quit' to quit > > virsh # capabilities > <capabilities> > > <host> > <uuid>604c8a12-cb5b-d911-985d-5404a67ef15d</uuid> > <cpu> > <arch>x86_64</arch> > <model>Westmere</model> > <vendor>Intel</vendor> > <topology sockets='1' cores='4' threads='2'/> > <feature name='rdtscp'/> > <feature name='x2apic'/> > <feature name='xtpr'/> > <feature name='tm2'/> > <feature name='est'/> > <feature name='vmx'/> > <feature name='ds_cpl'/> > <feature name='monitor'/> > <feature name='pbe'/> > <feature name='tm'/> > <feature name='ht'/> > <feature name='ss'/> > <feature name='acpi'/> > <feature name='ds'/> > <feature name='vme'/> > </cpu> > <migration_features> > <live/> > <uri_transports> > <uri_transport>tcp</uri_transport> > </uri_transports> > </migration_features> > </host> > > </capabilities> > > > > I have no clue what is going on. I have kvm compiled into my kernel. > Normal "kvm" commands are working. Intel VT is enabled in the bios. > > > Any thoughts on this one? > Do you have qemu installed? Under what paths? Libvirt tries to find qemu-kvm under PATH or /usr/libexec/; then kvm and qemu-system-* under PATH; What about /dev/kvm - is it accessible? Please, provide libvirt logs as well. Michal

Hello, sounds you are using gentoo-linux, right? Here on 1.0-r2 No Problems. You need to unmask some other depends to run 1.0-r2 marko Am 07.02.2012 12:23, schrieb Felix Blanke: > On 2/7/12 11:06 AM, Michal Privoznik wrote: >> On 06.02.2012 19:58, Felix Blanke wrote: >>> Hello, >>> >>> I have a problem with virt-install. I want to use it to create my vm >>> and >>> manage them. But whenever I execute the virt-install cmd I get the >>> error >>> msg mentioned in the subject. >>> >>> Here are some more informations: >>> >>> hp ~ # virt-install --virt-type kvm --arch x86_64 --debug >>> Mon, 06 Feb 2012 19:57:29 DEBUG Launched with command line: >>> /usr/bin/virt-install --virt-type kvm --arch x86_64 --debug >>> Mon, 06 Feb 2012 19:57:29 DEBUG Requesting libvirt URI default >>> Mon, 06 Feb 2012 19:57:29 DEBUG Received libvirt URI qemu:///system >>> Mon, 06 Feb 2012 19:57:29 DEBUG Requesting virt method 'default', hv >>> type 'kvm'. >>> Mon, 06 Feb 2012 19:57:29 ERROR Host does not support any >>> virtualization options for arch 'x86_64' >>> Mon, 06 Feb 2012 19:57:29 DEBUG Traceback (most recent call last): >>> File "/usr/bin/virt-install-2.7", line 272, in get_virt_type >>> machine=options.machine) >>> File >>> >>> "/usr/lib64/python2.7/site-packages/virtinst/CapabilitiesParser.py", >>> line 732, in guest_lookup >>> {'virttype' : osstr, 'arch' : archstr}) >>> ValueError: Host does not support any virtualization options for arch >>> 'x86_64' >>> >>> >>> hp ~ # virsh --connect qemu:///system >>> Welcome to virsh, the virtualization interactive terminal. >>> >>> Type: 'help' for help with commands >>> 'quit' to quit >>> >>> virsh # capabilities >>> <capabilities> >>> >>> <host> >>> <uuid>604c8a12-cb5b-d911-985d-5404a67ef15d</uuid> >>> <cpu> >>> <arch>x86_64</arch> >>> <model>Westmere</model> >>> <vendor>Intel</vendor> >>> <topology sockets='1' cores='4' threads='2'/> >>> <feature name='rdtscp'/> >>> <feature name='x2apic'/> >>> <feature name='xtpr'/> >>> <feature name='tm2'/> >>> <feature name='est'/> >>> <feature name='vmx'/> >>> <feature name='ds_cpl'/> >>> <feature name='monitor'/> >>> <feature name='pbe'/> >>> <feature name='tm'/> >>> <feature name='ht'/> >>> <feature name='ss'/> >>> <feature name='acpi'/> >>> <feature name='ds'/> >>> <feature name='vme'/> >>> </cpu> >>> <migration_features> >>> <live/> >>> <uri_transports> >>> <uri_transport>tcp</uri_transport> >>> </uri_transports> >>> </migration_features> >>> </host> >>> >>> </capabilities> >>> >>> >>> >>> I have no clue what is going on. I have kvm compiled into my kernel. >>> Normal "kvm" commands are working. Intel VT is enabled in the bios. >>> >>> >>> Any thoughts on this one? >>> >> >> Do you have qemu installed? Under what paths? >> Libvirt tries to find qemu-kvm under PATH or /usr/libexec/; >> then kvm and qemu-system-* under PATH; >> >> What about /dev/kvm - is it accessible? >> >> Please, provide libvirt logs as well. >> >> Michal > > > Hello, > > first of all thank you very much for your reply. > > The hint with the libvirt log pointed me into the right direction. > While executing the virt-install cmd there was an error in the > libvirt.log: > > 12:03:11.938: 3137: error : qemuCapsParseHelpStr:1165 : internal > error cannot parse /usr/bin/qemu-system-x86_64 version number in 'QEMU > emulator version 1.0 (qemu-kvm-1.0), Copyright (c) 2003-2008 Fabrice > Bellard' > > > Google for that error pointed me to a bug report. This bug still > seems to be in the qemu-kvm version I was using (1.0-r2). Upgrading to > version 9999 seemed to solve my issue. I don't get the error anymore > and will now try to setup a virtual machine. > > > Kind regards, > Felix Blanke > > _______________________________________________ > libvirt-users mailing list > libvirt-users(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users _______________________________________________ libvirt-users mailing list libvirt-users(a)redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users

I do bridged network here. Then i told via virsh to use the bridge. "virt-manager" is doing the rest. i use these useflags: app-emulation/libvirt: debug elibc_glibc json libvirtd lxc macvtap nfs nls numa pcap policykit python qemu sasl udev virt-network virt-manager: policykit app-emulation/qemu-kvm: aio alsa jpeg ncurses opengl png qemu_softmmu_targets_i386 qemu_softmmu_targets_x86_64 qemu_user_targets_i386 qemu_user_targets_x86_64 sdl spice ssl threads vde vhost-net Michal helped with the useflags on libvirt. Maybe these works for you. marko Am 07.02.2012 13:28, schrieb Felix Blanke: > Hi, > > you're right, gentoo here :) > > Well, qemu-kvm emerged without problems, therefore my masking should > be correct. > Maybe it's a combination of versions which doesn't work, I don't know. > > Right now the virt-install command works. I have some trouble setting > up a vm using vde. I don't know what to tell --network to use vde. If > someone has a hint (like an example cmdline for virt-install using > vde) and would share it with me would be great. > > Kind regards, > Felix Blanke > > On 2/7/12 1:20 PM, Marko Weber wrote: >> >> Hello, >> sounds you are using gentoo-linux, right? >> Here on 1.0-r2 No Problems. >> You need to unmask some other depends to run 1.0-r2 >> >> marko >> >> >> >> Am 07.02.2012 12:23, schrieb Felix Blanke: >>> On 2/7/12 11:06 AM, Michal Privoznik wrote: >>>> On 06.02.2012 19:58, Felix Blanke wrote: >>>>> Hello, >>>>> >>>>> I have a problem with virt-install. I want to use it to create my vm >>>>> and >>>>> manage them. But whenever I execute the virt-install cmd I get the >>>>> error >>>>> msg mentioned in the subject. >>>>> >>>>> Here are some more informations: >>>>> >>>>> hp ~ # virt-install --virt-type kvm --arch x86_64 --debug >>>>> Mon, 06 Feb 2012 19:57:29 DEBUG Launched with command line: >>>>> /usr/bin/virt-install --virt-type kvm --arch x86_64 --debug >>>>> Mon, 06 Feb 2012 19:57:29 DEBUG Requesting libvirt URI default >>>>> Mon, 06 Feb 2012 19:57:29 DEBUG Received libvirt URI qemu:///system >>>>> Mon, 06 Feb 2012 19:57:29 DEBUG Requesting virt method 'default', hv >>>>> type 'kvm'. >>>>> Mon, 06 Feb 2012 19:57:29 ERROR Host does not support any >>>>> virtualization options for arch 'x86_64' >>>>> Mon, 06 Feb 2012 19:57:29 DEBUG Traceback (most recent call last): >>>>> File "/usr/bin/virt-install-2.7", line 272, in get_virt_type >>>>> machine=options.machine) >>>>> File >>>>> >>>>> >>>>> "/usr/lib64/python2.7/site-packages/virtinst/CapabilitiesParser.py", >>>>> line 732, in guest_lookup >>>>> {'virttype' : osstr, 'arch' : archstr}) >>>>> ValueError: Host does not support any virtualization options for arch >>>>> 'x86_64' >>>>> >>>>> >>>>> hp ~ # virsh --connect qemu:///system >>>>> Welcome to virsh, the virtualization interactive terminal. >>>>> >>>>> Type: 'help' for help with commands >>>>> 'quit' to quit >>>>> >>>>> virsh # capabilities >>>>> <capabilities> >>>>> >>>>> <host> >>>>> <uuid>604c8a12-cb5b-d911-985d-5404a67ef15d</uuid> >>>>> <cpu> >>>>> <arch>x86_64</arch> >>>>> <model>Westmere</model> >>>>> <vendor>Intel</vendor> >>>>> <topology sockets='1' cores='4' threads='2'/> >>>>> <feature name='rdtscp'/> >>>>> <feature name='x2apic'/> >>>>> <feature name='xtpr'/> >>>>> <feature name='tm2'/> >>>>> <feature name='est'/> >>>>> <feature name='vmx'/> >>>>> <feature name='ds_cpl'/> >>>>> <feature name='monitor'/> >>>>> <feature name='pbe'/> >>>>> <feature name='tm'/> >>>>> <feature name='ht'/> >>>>> <feature name='ss'/> >>>>> <feature name='acpi'/> >>>>> <feature name='ds'/> >>>>> <feature name='vme'/> >>>>> </cpu> >>>>> <migration_features> >>>>> <live/> >>>>> <uri_transports> >>>>> <uri_transport>tcp</uri_transport> >>>>> </uri_transports> >>>>> </migration_features> >>>>> </host> >>>>> >>>>> </capabilities> >>>>> >>>>> >>>>> >>>>> I have no clue what is going on. I have kvm compiled into my kernel. >>>>> Normal "kvm" commands are working. Intel VT is enabled in the bios. >>>>> >>>>> >>>>> Any thoughts on this one? >>>>> >>>> >>>> Do you have qemu installed? Under what paths? >>>> Libvirt tries to find qemu-kvm under PATH or /usr/libexec/; >>>> then kvm and qemu-system-* under PATH; >>>> >>>> What about /dev/kvm - is it accessible? >>>> >>>> Please, provide libvirt logs as well. >>>> >>>> Michal >>> >>> >>> Hello, >>> >>> first of all thank you very much for your reply. >>> >>> The hint with the libvirt log pointed me into the right direction. >>> While executing the virt-install cmd there was an error in the >>> libvirt.log: >>> >>> 12:03:11.938: 3137: error : qemuCapsParseHelpStr:1165 : internal >>> error cannot parse /usr/bin/qemu-system-x86_64 version number in 'QEMU >>> emulator version 1.0 (qemu-kvm-1.0), Copyright (c) 2003-2008 Fabrice >>> Bellard' >>> >>> >>> Google for that error pointed me to a bug report. This bug still >>> seems to be in the qemu-kvm version I was using (1.0-r2). Upgrading to >>> version 9999 seemed to solve my issue. I don't get the error anymore >>> and will now try to setup a virtual machine. >>> >>> >>> Kind regards, >>> Felix Blanke >>> >>> _______________________________________________ >>> libvirt-users mailing list >>> libvirt-users(a)redhat.com >>> https://www.redhat.com/mailman/listinfo/libvirt-users >> >> >> _______________________________________________ >> libvirt-users mailing list >> libvirt-users(a)redhat.com >> https://www.redhat.com/mailman/listinfo/libvirt-users > > _______________________________________________ > libvirt-users mailing list > libvirt-users(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users _______________________________________________ libvirt-users mailing list libvirt-users(a)redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users

On 02/07/2012 08:11 AM, Felix Blanke wrote: > Hi, > > I tried (most) of your use flags without any change. > > Maybe it's because my CPU is very new and qemu-kvm-1.0-r2 has problem with > that. Whatever, I'm fine with the 9999 version. > > Still needs to get a tutorial how to use vde with virt-install. Can't find > anything in the net :( > The root cause is that older libvirt failed at parsing the qemu 1.0 version string. Please file a bug with your distro and ask them to backport this fix so other users won't hit the same problem: http://libvirt.org/git/?p=libvirt.git;a=commit;h=dd8e8956060f38b084d581ed... - Cole

On 08.02.2012 09:33, Felix Blanke wrote: > On 2/8/12 12:52 AM, Cole Robinson wrote: >> On 02/07/2012 08:11 AM, Felix Blanke wrote: >>> Hi, >>> >>> I tried (most) of your use flags without any change. >>> >>> Maybe it's because my CPU is very new and qemu-kvm-1.0-r2 has problem >>> with >>> that. Whatever, I'm fine with the 9999 version. >>> >>> Still needs to get a tutorial how to use vde with virt-install. Can't >>> find >>> anything in the net :( >>> >> >> The root cause is that older libvirt failed at parsing the qemu 1.0 >> version >> string. Please file a bug with your distro and ask them to backport >> this fix >> so other users won't hit the same problem: >> >> http://libvirt.org/git/?p=libvirt.git;a=commit;h=dd8e8956060f38b084d581ed... >> >> >> - Cole > > Hi Cole, > > you're right. I installed libvirt-0.9.8 (instead of 0.9.6) and it works > fine with qemu-1.0-r2. > > Gentoo doesn't have to backport it. There is 0.9.8 allready in portage, > but masked (means not 100% stable). But qemu-kvm-1.0-r2 is also marked > as masked. Therefore it is only a combination of one masked > (qemu-kvm-1.0-r2) and one unmasked (libvirt-0.9.6) package, which isn't > anything I could complain about :) > Maybe I should fill in a "bug" report that if qemu-kvm is unmasked they > need to unmask libvirt, too. I'll thing about it. > > Thank you for clearing things up. > > Kind regards, > Felix Blanke > I've started Troubleshooting wiki page on libvirt and added your case as it was showing up frequently: http://wiki.libvirt.org/page/Troubleshooting Michal

On 02/08/2012 04:01 AM, Michal Privoznik wrote: > On 08.02.2012 09:33, Felix Blanke wrote: >> On 2/8/12 12:52 AM, Cole Robinson wrote: >>> On 02/07/2012 08:11 AM, Felix Blanke wrote:

> > I've started Troubleshooting wiki page on libvirt and added your case as > it was showing up frequently: > > http://wiki.libvirt.org/page/Troubleshooting > > Michal Hi Michal, there's already a similar section in the FAQ: http://wiki.libvirt.org/page/FAQ maybe we should find a way to merge the two?