search for: breth0

...6705e..a0a66e9 100644 --- a/src/test/functional/managed_node_configuration_test.rb +++ b/src/test/functional/managed_node_configuration_test.rb @@ -48,7 +48,7 @@ class ManagedNodeConfigurationTest < Test::Unit::TestCase expected = <<-HERE # THIS FILE IS GENERATED! -ifcfg=#{nic.mac}|breth0|BOOTPROTO=#{nic.boot_protocol}|TYPE=bridge|PEERDNS=no|ONBOOT=yes +ifcfg=#{nic.mac}|breth0|BOOTPROTO=#{nic.boot_protocol}|TYPE=Bridge|PEERDNS=no|ONBOOT=yes ifcfg=#{nic.mac}|eth0|BRIDGE=breth0|ONBOOT=yes HERE @@ -67,7 +67,7 @@ ifcfg=#{nic.mac}|eth0|BRIDGE=breth0|ONBOOT=yes expected = &...

I will try to explain 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...

Since create-ovirt-network script has been deprecated (was part of ovirt-appliance repo) we can't default to bridge on the host of ovirtbr0 for doing fake node testing. So default to network:default and allow manual override to something like bridge:breth0 Signed-off-by: Perry Myers <pmyers at redhat.com> --- create-ovirt-iso-nodes | 11 +++++++---- 1 files changed, 7 insertions(+), 4 deletions(-) diff --git a/create-ovirt-iso-nodes b/create-ovirt-iso-nodes index d74dc4d..fe2e7ab 100755 --- a/create-ovirt-iso-nodes +++ b/create-ovirt-iso-n...

Hello , i am trying to install a virtual machine and i get this error in tasks in 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...

...n_poweroff>destroy</on_poweroff><on_reboot>restart</on_reboot><on_crash>destroy</on_crash><devices><emulator>/usr/bin/qemu-kvm</emulator><interface type='bridge'><mac address='00:16:3e:1f:b6:eb'/><source bridge='breth0'/></interface><input bus='ps2' type='mouse'/><graphics type='vnc' port='-1' listen='0.0.0.0'/><serial type='pty'><target port='0'/></serial></devices><features><acpi/><apic/>...

...irt/management.ovirt.priv at OVIRT.PRIV for qpidd/management.ovirt.priv at OVIRT.PRIV I can monitor the booting of my node via serial console and here are the relevant error messages : First : Bringing up interface eth0: RTNETLINK answers: No such file or directory [ OK ] Bringing up interface breth0: Determining IP information for breth0... failed. [FAILED] This one is I assume because there is no DHCP server on the guest network. It shouldn't be a problem since the hardware node should not be reachable by the guest network ? I plan to configure the IP of my guests statically. Second :...

...devices"] << interface } diff --git a/src/task-omatic/taskomatic.rb b/src/task-omatic/taskomatic.rb index 31c38e3..5c6a673 100755 --- a/src/task-omatic/taskomatic.rb +++ b/src/task-omatic/taskomatic.rb @@ -409,12 +409,12 @@ class TaskOmatic else net_device = "breth0" # FIXME remove this default at some point end - net_interfaces.push({ :mac => nic.mac, :interface => net_device }) + net_interfaces.push({ :mac => nic.mac, :interface => net_device, :virtio => nic.virtio }) } xml = create_vm_xml(db_vm.description...

...weroff>destroy</on_poweroff><on_reboot>restart</ on_reboot><on_crash>destroy</on_crash><devices><emulator>/usr/bin/qemu- kvm</emulator><interface type='bridge'><mac address='00:16:3e:03:de: 23'/><source bridge='breth0'/></interface><input bus='ps2' type='mouse'/><graphics type='vnc' port='-1' listen='0.0.0.0'/><serial type='pty'><target port='0'/></serial></devices><features><acpi/><apic/...

...t;devices"] << interface } diff --git a/src/task-omatic/taskomatic.rb b/src/task-omatic/taskomatic.rb index 83849ad..9c2a162 100755 --- a/src/task-omatic/taskomatic.rb +++ b/src/task-omatic/taskomatic.rb @@ -430,7 +430,7 @@ class TaskOmatic else net_device = "breth0" # FIXME remove this default at some point end - net_interfaces.push({ :mac => nic.mac, :interface => net_device, :virtio => nic.virtio }) + net_interfaces.push({ :mac => nic.mac, :interface => net_device, :model => nic.model }) } # network_alway...

...o 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 part doesn't seem to make a difference)

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

redux patchset permitting a vm to be associated with multiple networks and vice-versa. updated patchset so as to be applicable against current oVirt server HEAD these patches may be applied in any order, they all need to be pushed together

This patchset contains changes to the ovirt server frontend, backend, and tests components, permitting vms to be associated with multiple networks and vice versa. Also included are two patches which are required for the frontend bits; a patch adding collapsable sections to the vm form, which in itself depends on the second patch that provides default values for the cpu and memory vm table fields

...to find a nic or bonding here, given - # a specified host and network, we should try earlier on to find a host - # that has a nic / bonding on the specified network + # loop through each nic/network assigned to vm, + # finding necessary host devices to bridge - net_device = "breth0" # FIXME remove this default value at some point, tho net_device can't be nil - unless db_vm.network.nil? - if db_vm.network.class == PhysicalNetwork - device = Nic.find(:first, - :conditions => ["host_id = ? AND physical_network_id = ?&qu...