[et-mgmt-tools] Re: lot's of trouble using virt-manager and virt-install with qemu

[Source]

Well Well,

Little bit of surfing over internet revelaed that virt-install will have to
be given --connect option. Okay no problem.
And yeah I found the rpm for kvm and qemu which when I install give me
/usr/bin/qemu-kvm and other required stuff. Now I have this question. Why
don't I get qemu-kvm built when I compile from source code? I am getting by
installing the rpm.

Okay back to virt-manager. Now virt-manager didn't reported of not finding
/usr/bin/qemu-kvm but failed at another error stating about the network
device.

Unable to complete install 'libvirt.libvirtError virDomainCreateLinux()
failed internal error Network 'default' not active
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 677, in
do_install
    dom = guest.start_install(False, meter = meter)
  File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 649, in
start_install
    return self._do_install(consolecb, meter)
  File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 666, in
_do_install
    self.domain = self.conn.createLinux(install_xml, 0)
  File "/usr/lib/python2.4/site-packages/libvirt.py", line 480, in
createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: virDomainCreateLinux() failed internal error Network 'default'
not active
'

I found that I have virbr0 active during that time.

virbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:8486 (8.2 KiB)

And I also found it as saying <name>default</name> in
/etc/libvirt/qemu/networks/default.xml. Then why isn't virt-manager getting
it? Or is there something else to tell?

One more thing during virt-manager network select step I was not getting
showed any Shared physical device. How I can create it? I have to manually
create a device and bridge it to my real ethernet device?

Please answer my doughts.

Thansk


On 4/26/07, Source <prime.provogue at gmail.com> wrote:
>
> Hello guys,
>
> I have installed kvm-20 from source code. Loaded the kvm module and
> started the said libvirtd service. Now when I try to use virt-manager to
> create a new virtual machine it ends up saying no /usr/bin/qemu-kvm found.
> Now I found that I don't have this file. At the irc I was told to use
> kvm-19-1.src.rpm from FC7 extras development SRPMS. I used that also. I
> compiled it too. It got compiled and installed successfully but that too
> didn't provided qemu-kvm. I found that in the source tree of kvm there is a
> directory qemu/ in which I have qemu-kvm.c and qemu-kvm.h which get's
> compiled to qemu-kvm.o and get's into qemu/i386-softmmu/qemu-kvm.o but it
> doesn't makes any qemu-kvm executable in /usr/bin.
>
> Also I tried to use virt-install , first of all I would like to tell that
> it's not intelligent enough to guess which hypervisor to use if we don't
> pass --connect argument. Now when I use it with --connect=qemu:///system to
> create a new virtual machine I got the following error:
>
> libvir: QEMU error : internal error Failed to add tap interface 'vnet%d'
> to bridge 'xenbr0' : No such device
> Traceback (most recent call last):
>   File "/usr/bin/virt-install", line 630, in ?
>     main()
>   File "/usr/bin/virt-install", line 579, in main
>     dom = guest.start_install(conscb,progresscb)
>   File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 649, in
> start_install
>     return self._do_install(consolecb, meter)
>   File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 666, in
> _do_install
>     self.domain = self.conn.createLinux(install_xml, 0)
>   File "/usr/lib/python2.4/site-packages/libvirt.py", line 480, in
> createLinux
>     if ret is None:raise libvirtError('virDomainCreateLinux() failed',
> conn=self)
> libvirt.libvirtError: virDomainCreateLinux() failed internal error Failed
> to add tap interface 'vnet%d' to bridge 'xenbr0' : No such device
>
> Now it seems to follow a default xml file here. And it is trying to find
> xenbr0 which I don't have as I am not using a xen kernel so no xend running
> at the moment. It should use in that case eth0/eth1 right?
>
> Correct me if I am wrong.
>
> Thanks
> Deependra
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/et-mgmt-tools/attachments/20070426/041bc9bb/attachment.htm>