Re: bridge could not be initialized

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 06/18/2014 04:43 PM, abhishek jain wrote:
Hi

I'm trying to run VM using libvirt.xml file and getting following error...

virsh start instance-00000003

error: Failed to start domain instance-00000003
error: internal error Process exited while reading console log output: failed to launch bridge helper
kvm: -netdev bridge,br=qbr1f2191ce-38,id=hostnet0: Device 'bridge' could not be initialized

1) The qemu "bridge helper" is only used if you are running virsh as a non-privileged user (i.e. non-root). Are you sure that's what you want to do? If that really is the proper thing to do, the bridge device would need to exist in advance of starting the domain, and you would have to read up on the qemu bridge helper to learn how to setup ACLs such that the uid you are using to start the domain have permission to use the bridge helper (not using it myself, I don't have a pointer to that info handy, but Google is your friend :-)

2) it looks like this config was generated by OpenStack. Why are you starting it via virsh? I don't use OpenStack myself, but am assuming that a lot of the objects referenced in an OpenStack-generated libvirt domain config are auto-created by some piece of OpenStack code just prior to starting the domain. For example, the bridge device (there is a separate bridge device created per guest interface) and the filter that is applied to that interface (likewise). I was of the impression that OpenStack instances needed to be started from some sort of OpenStack management app, *not* from virsh.



Below is the libvirt.xml file..

domain type="kvm">
  <uuid>d9f007b9-584f-41c8-a706-e096f354575b</uuid>
  <name>instance-00000003</name>
  <memory>524288</memory>
  <vcpu>1</vcpu>
  <os>
    <type>hvm</type>
    <kernel>/opt/stack/data/nova/instances/d9f007b9-584f-41c8-a706-e096f354575b/kernel</kernel>
    <initrd>/opt/stack/data/nova/instances/d9f007b9-584f-41c8-a706-e096f354575b/ramdisk</initrd>
    <cmdline>root=/dev/vda console=tty0 console=ttyS0</cmdline>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <clock offset="utc">
    <timer name="pit" tickpolicy="delay"/>
    <timer name="rtc" tickpolicy="catchup"/>
  </clock>
  <devices>
    <disk type="file" device="disk">
      <driver name="qemu" type="qcow2" cache="none"/>
      <source file="/opt/stack/data/nova/instances/d9f007b9-584f-41c8-a706-e096f354575b/disk"/>
      <target bus="virtio" dev="vda"/>
    </disk>
    <interface type="bridge">
      <mac address="fa:16:3e:26:55:ff"/>
      <model type="virtio"/>
      <source bridge="qbr1f2191ce-38"/>
      <target dev="tap1f2191ce-38"/>
      <filterref filter="nova-instance-instance-00000003-fa163e2655ff"/>
    </interface>
    <serial type="file">
      <source path="/opt/stack/data/nova/instances/d9f007b9-584f-41c8-a706-e096f354575b/console.log"/>
    </serial>
    <serial type="pty"/>
  </devices>
</domain>


Please help regarding this.

Thanks
Abhishek Jain


_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users

_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users

[Index of Archives]     [Virt Tools]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux