similar to: eth0 killed when adding virtual interface and multiple NICs are present

Greetings, I recently installed CentOS 5 on Dell PE 1750 server. I have noticed that the speed and duplex settings are 100 Half Duplex. I tried to change the duplex settings to full, but no success. I got the error message "Cannot get current device settings: Operation not supported". Does anyone else experience this issue?. Below is the error message and some more details about my box.

Hi all, I am trying to configure a Dom U to act as a firewall and therefore I need to pass one of the two ethernet cards to the Dom-U. I configured the Xen kernel to build pciback as a module and I am passing the hide option via boot parameters. I boot the pv machine via pygrub and I am able to see the ethernet device in Dom U as follows: Dom-U#lspci 02:00.0 Ethernet controller: Broadcom

Hi all, I have two HP DL145 G1 machines, running centos4 (2.6.9-22.0.2.ELsmp). Nics are recognized as: eth0: Tigon3 [partno(BCM95704) rev 2002 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:00:1a:19:f1:05 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap [1] eth1: Tigon3 [partno(BCM95704) rev 2002 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet

My kernel crashes every time I shut down dom0 This crash was not happening before I installed the Xen hypervisor Any ideas? (XEN) Xen version 3.2-1 (Debian 3.2.1-2) (waldi at debian.org) (gcc version 4.3.1 (Debian 4.3.1-2) ) Sat Jun 28 09:32:18 UTC 2008 (XEN) Command line: com1=9600,8n1 console=com1 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods:

Hi all! I want to assign a physical network card (e100) to a domU: I think Dom0 is ok but domU does not recognize the pci nic. into DomU I don''t know wath should I see: I have nothing in dmesg nor in messages... Into Dom0 I have this modules.conf: options pciback hide=(0000:03: 08.0) install e100 /sbin/modprobe pciback; /sbin/modprobe --ignore-install e100 This is dmesg: pciback

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello All, I have had a problem detecting the network card on my notebook when ACPI is enabled for a year. The problem still exists in 7.1-RELEASE. with ACPI: ... bge0: <Broadcom NetLink Gigabit Ethernet Controller, ASIC rev. 0xb002> irq 17 at device 0.0 on pci8 bge0: 0x10000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). bge0: couldn't

Source: xen Severity: normal Dear Maintainer, After an upgrade, my passthroughed NIC stopped working. I created a new jessie domU and tried to passthrough some PCI devices and found that both USB3 host controller and tg3 NIC generated these lines in domU dmesg: xen:events: Failed to obtain physical IRQ 31 xen:events: Failed to obtain physical IRQ 32 xen:events: Failed to obtain physical IRQ 33

Ok im trying to play Counter Strike 1.6, but it crashes when i join a server. The Video is set to OpenGL and when i set it to "Software" it started working (but the quality was really shitty so i want OpenGL). I have this video card VGA compatible controller [0300]: ATI Technologies Inc RS480 [Radeon Xpress 200G Series] And when the game crashed i got this error: Code: Allocating

Xen developers, After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed NIC stopped working. This bug was probably introduced in Debian Jessie sometime between 2015-12-30 and 2016-01-08 as 2015-12-30 as 2015-12-30 was the last time I upgraded without any problems according to my dpkg.log. This bug has also been reported to Debian Bug (https://bugs.debian.org/810379), where I got

Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro

Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro

I am unable to boot Dom0 on a machine with Reiser file systems. Reiser support is built into the xen0 kernel. I have similar setup with ext3 file systems working just fine, so I don''t think it is a setup problem. I have tried booting with and without and initrd file, booting with the original Linux distro initrd file, etc, but nothing seems to work. I recall seeing a thread about ReiserFS

On Wed, Jan 27, 2016 at 7:30 PM, Konrad Rzeszutek Wilk < konrad.wilk at oracle.com> wrote: > On Sat, Jan 23, 2016 at 05:12:04PM +0100, Tommi Airikka wrote: > > Xen developers, > > > > After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed > > NIC stopped working. > > This bug was probably introduced in Debian Jessie sometime > > between

Hello everyone, can someone please tell me if the configuration previously shown is eventually going to work? Stefano Il giorno lun 19 ott 2020 alle ore 18:56 Stefano Vargiu < vstefanoxx at gmail.com> ha scritto: > I add some additional information I didn't give in my previous email, > specifically how I tried to force DC1 and DC2 to contact each other only > with their VPN

Ok, the story is this, I''m running an Unreal Tournament 2004 server. It''s running on a system that has two external NICs that are connected to different ISPs. I would like players to be able to connect to the server from either link. My default gateway goes through NIC1. For traffic through NIC2 to work I simply added an extra routing table and rule. The extra routing table has

Hi, Thanks to everyone involved in the Xen project. I think it is great and can''t wait to get my hands dirty with it. In the meantime, I cannot boot Dom0 on an ibm x335 and I am not sure what the problem is. Any insights are welcome. Here is what my grub.conf file looks like: title Fedora Core (2.6.8-1.521) root (hd0,0) kernel /vmlinuz-2.6.8-1.521 ro root=/dev/sda9

I add some additional information I didn't give in my previous email, specifically how I tried to force DC1 and DC2 to contact each other only with their VPN IPs. I did so using dnsmasq as a DNS proxy. # DC1 configuration IP NIC1: 172.16.0.2 IP NIC2: 172.20.0.1 IP VPN: 172.19.1.173 --- /etc/resolv.conf: search domain.local domain domain.local nameserver 172.19.1.173 --- I configured dnsmasq

On 19/10/2020 12:40, Stefano Vargiu via samba wrote: > Hello everyone, > > I'm trying to add a second DC to a Samba 4 AD: they both have multiple NICs > and for this reason cannot find a way to make it work. > They communicate through VPN and both have one of the bound interfaces set > to the same IP address, 172.20.0.1, which doesn't allow me to route to the > correct

Signed-off-by: Scott Seago <sseago at redhat.com> --- src/test/functional/host_controller_test.rb | 41 -------------------- .../functional/managed_node_configuration_test.rb | 14 ++++--- src/test/functional/nic_controller_test.rb | 8 ---- src/test/functional/permission_controller_test.rb | 15 ++++--- src/test/functional/quota_controller_test.rb | 2 +-

On Mon, Oct 19, 2020 at 7:42 AM Stefano Vargiu via samba <samba at lists.samba.org> wrote: > > Hello everyone, > > I'm trying to add a second DC to a Samba 4 AD: they both have multiple NICs > and for this reason cannot find a way to make it work. > They communicate through VPN and both have one of the bound interfaces set > to the same IP address, 172.20.0.1, which