search for: breth1

...ay}|TYPE=bridge|PEERDNS=no|ONBOOT=yes +ifcfg=#{nic1.mac}|breth0|BOOTPROTO=#{nic1.boot_protocol}|IPADDR=#{nic1.ip_address}|NETMASK=#{nic1.netmask}|BROADCAST=#{nic1.broadcast}|GATEWAY=#{nic1.gateway}|TYPE=Bridge|PEERDNS=no|ONBOOT=yes ifcfg=#{nic1.mac}|eth0|BRIDGE=breth0|ONBOOT=yes -ifcfg=#{nic2.mac}|breth1|BOOTPROTO=#{nic2.boot_protocol}|TYPE=bridge|PEERDNS=no|ONBOOT=yes +ifcfg=#{nic2.mac}|breth1|BOOTPROTO=#{nic2.boot_protocol}|TYPE=Bridge|PEERDNS=no|ONBOOT=yes ifcfg=#{nic2.mac}|eth1|BRIDGE=breth1|ONBOOT=yes HERE @@ -116,7 +118,7 @@ ifcfg=#{nic2.mac}|eth1|BRIDGE=breth1|ONBOOT=yes # THIS FILE...

...the ovirt webinterface. Error creating virtual machine: Error: Error creating new domain (virDomainCreate). Subsystem qemu: internal error Failed to add tap interface 'vnet%d' to bridge 'breth0' : No such device in DomainWrap.cpp:ManagementMethod:115 On the node startup i only see breth1 geting started. How can i fix this? And also the node is reported in the webinterface as hypervisor QEMU, not kvm. The processor is an intel xeon with VT. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ovirt-devel/attachments...

...lain problem as good as possible. I just finished building my ovirt server from the git repo. Added a vm in cobbler. But when i install a vm it will install on breth0 on my managed node(this is my admin network(199.1.10.*)). Now it is not reachable on the quest network. Isn't this suppose to be breth1(guest network(192.168.50.*))? The management server has ip 192.168.50.200(quest) and 199.1.10.1(admin). If i boot with pxe from eth1 on the node breth0 wil get ip 192.168.50.201 but also the dns server will be 192.168.50.200. Dis is not working , because it can't resolve the name of the ovirt s...

...hutdown reason code 0 is destroy Domain 9 needs to be cleaned up: destroying the domain Done. Exiting now > Could you also post your guest cfg file please. bootloader="pygrub" memory = 1024 name = "asterisk_deb08" vcpus = 2 pvh = 1 vif = ['mac=00:16:3e:00:00:12, bridge=breth1', 'mac=00:16:3e:00:00:13, bridge=breth0'] disk = ['phy:/dev/rvg0/asterisk_deb80_rootfs,xvda,w', 'phy:/dev/rvg0/asterisk_deb80_var,xvdb,w', 'phy:/dev/rvg0/asterisk_deb80_rec,xvdc,w', 'phy:/dev/rvg0/asterisk_deb80_swap,xvdd,w'] (The pvh par...

On Fri, 2014-11-07 at 21:32 -0500, Gedalya wrote: > On 11/06/2014 09:12 AM, Ian Campbell wrote: > > I've posted a fix for this upstream: > > http://lists.xen.org/archives/html/xen-devel/2014-11/msg00542.html > > > > I've requested that it go into the next 4.4.x release. I also plan to > > backport it to the package regardless once it is accepted into the

...yes + ipv4: + - bootproto: static + address: 192.168.1.17 + netmask: 255.255.255.0 + gateway: 192.168.1.1 + dns: [192.168.1.7, 192.168.1.8] + + eth1: + hwaddress: 11:22:33:44:55:66 + onboot: yes + bridge: breth1 + + breth1: + onboot: yes + ipv4: + - bootproto: dhcp""") + + return HttpResponse(base64.encodestring(yaml.dump(yaml_data))) + +def ready(request): + """ + The config view. Accepts the configuration information from the client. +...