networking
James Bardin wrote:
> Hello, > > I'm having trouble digging up some documentation on libvirt's network > config. > > I'm not sure where to set this up, but I have a bridged device br0 that > I would like to have available in virt-manager/virsh. > > Right now, I can edit the VM's xml interface element manually to use > br0. Virt-manager has an option for shared physical device, but it's > empty, and I can't figure out how to see it from virsh. > > cc-ing et-mgmt-tools which is the virt-manager list The bridge should be showing up in shared physical device drop down automatically, there shouldn't be anything you need to teach libvirt. What virt-manager version are you using? Distro? Is there anything showing up in the shared device drop down (even if you can't select it?) Also if you could attach ~/.virt-manager/virt-manager.log it might help. Thanks, Cole _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@redhat.com https://www.redhat.com/mailman/listinfo/et-mgmt-tools |
networking
James Bardin wrote:
> Cole Robinson wrote: >> What virt-manager version are you using? >> Distro? > > libvirt: 0.4.0-2ubuntu8 > virt-manager: 0.5.3-0ubuntu10 > > Distro: Ubuntu 8.04.1 server x86_64 > >> Is there anything showing up in the shared device drop >> down (even if you can't select it?) >> > > The drop-down activates, but is empty. > >> Also if you could attach ~/.virt-manager/virt-manager.log >> it might help. >> > > This group popped up a lot yesterday: > > [Tue, 19 Aug 2008 14:55:19 virt-manager 5811] WARNING (connection:494) > Unable to list active networks > [Tue, 19 Aug 2008 14:55:19 virt-manager 5811] WARNING (connection:498) > Unable to list inactive networks > [Tue, 19 Aug 2008 14:55:19 virt-manager 5811] ERROR (engine:158) Could > not refresh connection qemu:///system > <class 'libvirt.libvirtError'> virConnectListDomainsID() failed Broken pipe > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/engine.py", line 152, in _tick > self.connections[uri]["connection"].tick() > File "/usr/share/virt-manager/virtManager/connection.py", line 550, in > tick > newActiveIDs = self.vmm.listDomainsID() > File "/usr/lib/python2.5/site-packages/libvirt.py", line 795, in > listDomainsID > if ret is None: raise libvirtError ('virConnectListDomainsID() > failed', conn=self) > libvirtError: virConnectListDomainsID() failed Broken pipe > This is probably from a libvirtd restart while virt-manager was running. If so, nothing to worry about. > > Here's the output when I try to add a new network device: > > [Wed, 20 Aug 2008 10:57:39 virt-manager 6673] ERROR (connection:158) > Unable to connect to HAL to list network devices: '%s'<class > 'dbus.exceptions.DBusException'> > org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Hal > was not provided by any .service files > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/connection.py", line 144, in > detect_network_devices > hal_object = self.bus.get_object('org.freedesktop.Hal', > '/org/freedesktop/Hal/Manager') > File "/var/lib/python-support/python2.5/dbus/bus.py", line 244, in > get_object > follow_name_owner_changes=follow_name_owner_change s) > File "/var/lib/python-support/python2.5/dbus/proxies.py", line 241, in > __init__ > self._named_service = conn.activate_name_owner(bus_name) > File "/var/lib/python-support/python2.5/dbus/bus.py", line 183, in > activate_name_owner > self.start_service_by_name(bus_name) > File "/var/lib/python-support/python2.5/dbus/bus.py", line 281, in > start_service_by_name > 'su', (bus_name, flags))) > File "/var/lib/python-support/python2.5/dbus/connection.py", line 607, > in call_blocking > message, timeout) > DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name > org.freedesktop.Hal was not provided by any .service files > [Wed, 20 Aug 2008 10:57:47 virt-manager 6673] ERROR (console:106) Cannot > initialize notification > systemorg.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute > dbus-launch to autolaunch D-Bus session > > This is the problem: we use dbus to contact hal to list physical net devices on the system, then we probe their /sys path to determine if they are in a bridge, among other things. Make sure hald (or some equivalently named service) is running. Bar that, you'll probably have to ask the ubuntu folks. Thanks, Cole _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@redhat.com https://www.redhat.com/mailman/listinfo/et-mgmt-tools |
networking
James Bardin wrote:
> > Cole Robinson wrote: >> Make sure hald (or some equivalently named service) is >> running. Bar that, you'll probably have to ask the >> ubuntu folks. >> > > It's running. I'll see if I can figure out where this went wrong. > > Does this apply to virsh as well? > > Thanks > -jim No virsh/libvirt doesn't use hal. If you want to try manually adding the bridge device to the domain, try the following. 'virsh dumpxml vmname > tmpxml' edit 'tmpxml', add to the <devices> section: <interface type='bridge'> <source bridge='br0'/> </interface> 'virsh define tmpxml' Hope that helps, Cole _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@redhat.com https://www.redhat.com/mailman/listinfo/et-mgmt-tools |
Networking
Hello,
I have upgraded Ubuntu 8.04.1 to 8.10 beta on an Advent 4211 (MSI Wind clone). The LAN has dhcp and I have a network connection. However, the taskbar icon of the Network Manager has an orange exclamation mark and says "No network connection". If I click on "Edit connections" and go to the wired connection and try to change something, I get the message "Updating connection failed: nm-ifupdown-connection.c.c82-connection update not supported (read-only).. I suppose as long as the connection actually does work, that's the main thing. I don't understand how to use this new "Network Manager" though. Anyone else working with this? Paolo -- ubuntu-users mailing list ubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
Networking
Paolo wrote:
> Hello, > > I have upgraded Ubuntu 8.04.1 to 8.10 beta on an Advent 4211 (MSI > Wind clone). The LAN has dhcp and I have a network connection. > > However, the taskbar icon of the Network Manager has an orange > exclamation mark and says "No network connection". > > If I click on "Edit connections" and go to the wired connection and > try to change something, I get the message "Updating connection > failed: nm-ifupdown-connection.c.c82-connection update not > supported (read-only).. > > I suppose as long as the connection actually does work, that's the > main thing. I don't understand how to use this new "Network > Manager" though. > > Anyone else working with this? > > Paolo On Monday I unfortunately d/l upgrades to the Intrepid Beta, which had previously been the Intrepid Alpha 6 upgraded online from Hardy. I had exactly what you describe (same error messages & issues). However, in addition I could not get online or access any repositories (lost my DNS and routing references). However I could access all the machines on my LAN. After screwing around with it for several hours I decided to do a clean install off my Intrepid Beta 1 live disk. Which has had one set of upgrades applied today. It seems to have fixed things by itself. Which is good in one way, but aggravating in another, since I really wanted to fix it myself in case it happens again. -- Cheers, SDM -- a 21st Century Schizoid Man Systems Theory internet music project: <www.systemstheory.net> on MySpace: <www.myspace.com/systemstheory> on Last FM: <www.last.fm/music/Systems+Theory> get "Codetalkers" *free* at <www.mikedickson.org.uk/codetalkers> NP: nothing -- ubuntu-users mailing list ubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
Networking
Steven Davies-Morris wrote:
> On Monday I unfortunately d/l upgrades to the Intrepid Beta, which had > previously been the Intrepid Alpha 6 upgraded online from Hardy. I had > exactly what you describe (same error messages & issues). It seems a lot of people have been having problems: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/279262 The bug has been "confirmed". -- ubuntu-users mailing list ubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
Networking
Paolo wrote:
> Steven Davies-Morris wrote: > >> On Monday I unfortunately d/l upgrades to the Intrepid Beta, >> which had previously been the Intrepid Alpha 6 upgraded online >> from Hardy. I had exactly what you describe (same error messages >> & issues). > > It seems a lot of people have been having problems: > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/279262 > > > The bug has been "confirmed". It also won't let me change my network setup back to it's static IP assignment. Or at least it won't "hold" the static assignment, reverting back to the DHCP IP on reboot. I guess I'll sit tight and wait for the patch to come along. -- Cheers, SDM -- a 21st Century Schizoid Man Systems Theory internet music project: <www.systemstheory.net> on MySpace: <www.myspace.com/systemstheory> on Last FM: <www.last.fm/music/Systems+Theory> get "Codetalkers" *free* at <www.mikedickson.org.uk/codetalkers> NP: nothing -- ubuntu-users mailing list ubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
networking
so, i've got some debian boxes in a virtualbox environment. most work
fine, but one is annoying me. after i boot it, the first interface comes up fine, but not the second. if i run '/etc/init.d/networking restart' they both go down. here is my ifconfig and interfaces file (which both look pretty normal to me): swilson-mbp-vdebian:~# ifconfig -a eth0 Link encap:Ethernet HWaddr 08:00:27:8d:ce:55 inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0 inet6 addr: fe80::a00:27ff:fe8d:ce55/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:11 errors:0 dropped:0 overruns:0 frame:0 TX packets:24 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2881 (2.8 KiB) TX bytes:3131 (3.0 KiB) eth1 Link encap:Ethernet HWaddr 08:00:27:f6:03:08 inet addr:192.168.56.102 Bcast:192.168.56.255 Mask:255.255.255.0 inet6 addr: fe80::a00:27ff:fef6:308/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:902 errors:0 dropped:0 overruns:0 frame:0 TX packets:133 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:65559 (64.0 KiB) TX bytes:20082 (19.6 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) swilson-mbp-vdebian:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp allow hotplug eth1 iface eth1 inet dhcp -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: AANLkTikMdg274rTGO2KKkXYj+G702EnJYOKv+aUjLRQ_@mail .gmail.com">http://lists.debian.org/AANLkTikMdg274rTGO2KKkXYj+G702EnJYOKv+aUjLRQ_@mail .gmail.com |
networking
On 01/14/2011 12:34 PM, shawn wilson wrote:
# The primary network interface allow-hotplug eth0 iface eth0 inet dhcp allow hotplug eth1 iface eth1 inet dhcp replace 'allow hotplug' with 'auto' auto eth0 auto eth1 Mihira. -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 4D2FF644.7010108@gmail.com">http://lists.debian.org/4D2FF644.7010108@gmail.com |
networking
On Fri, Jan 14, 2011 at 2:04 AM, shawn wilson <ag4ve.us@gmail.com> wrote:
> > allow-hotplug eth0 > iface eth0 inet dhcp > allow hotplug eth1 > iface eth1 inet dhcp How about with "allow-hotplug eth1" rather than "allow hotplug eth1"? -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: AANLkTi=8f+MmNaw7QJfSLKVBMfg3+LkC+bsCZX2Ftu8k@mail .gmail.com">http://lists.debian.org/AANLkTi=8f+MmNaw7QJfSLKVBMfg3+LkC+bsCZX2Ftu8k@mail .gmail.com |
| All times are GMT. The time now is 05:05 AM. |
VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.