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

[Daniel P. Berrange]

On Thu, Apr 26, 2007 at 04:30:29PM +0530, Source wrote:
> 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.

I've no idea - that's very odd

> 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
> '

Hmm, virbr0 corresponds to the default network, so not sure why the device
would be present if it were not active. Can you show 'virsh net-list --all'
One possibility I can think of is that something else had created the virbr0
device before libvirt_qemud started & thus prevented it from starting its
own default network. A simple reboot to clear out an pre-existing network
state might just do the trick there.

> 
> 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?

That is correct XML file to have.

> 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?

A shared physical device, is any real NIC which is enslaved as part of a bridge.
If you were using Xen, then the Xen startup scripts automatically put 'eth0'
into a bridge 'xenbr0'. With non-Xen we don't try to second guess what the admin
might want for their network setup, so we don't touch the real NICs ourselves.
If you want to have a shared physical device available then you can use the
regular distro provided network scripts, eg creating a suitable config file for
the bridge device at /etc/sysconfig/network-scripts/ifcfg-br0 and then in the
ifcfg-eth0  file setting BRIDGE=br0

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=|