search for: nic0

i am hoping this attachment gets through. It deals with bug in ping that made it very difficult to set up a system with two gateways. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20091009/ddfc8176/attachment-0004.html> -------------- next part -------------- An HTML attachment was scrubbed... URL:

...any errors from core_udp_sendto > anymore. But you still see the "My IP is 0.0.0.0"? The firmware version change is definitely useful. Without this, I would have considered the stalling messages as expected. > Hardware used: HP ProLiant DL380 Gen9 > NIC being used: NIC1 (not NIC0, since that's connected to a different > network) This is definitely useful and I suspect the major reason for the issue. > On Mon, Jun 22, 2015 at 8:54 AM, S. Schauenburg <s.schauenburg at gmail.com> > wrote: >> >> Hello Gene, >> >> thanks a lot for yo...

...iably for me, no matter what I tried. In the end I had to use different names instead of eth0 and eth1, like: SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="11:22:33:aa:bb:cc", ATTR{type}=="1", KERNEL=="eth*", NAME="nic0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="44:55:66:dd:ee:ff", ATTR{type}=="1", KERNEL=="eth*", NAME="nic1" And also rename /etc/sysconfig/network-scripts/ifcfg-ethX to ifcfg-nicX and modify them acco...

...#39; More specifically I made this change: diff ../syslinux_ppatpat_orig/efi/main.c efi/main.c 13a14 > #include <byteswap.h> 178c179 < BSWAP_64(*(uint64_t*)&bguid->Data4), --- > This build of syslinux works on my HP ProLiant DL380 Gen9 server while netbooting from nic1 (not nic0) :-) == output booting pxe == Don't know if it is useful, but I saw this output when booting from pxe over IPv4: ... NBP file downloaded successfully. Booting from: Acpi(PNP0A3,0)/Pci(1C|4)/Pci(0|1)/Mac(XXXXXXXXXXXX)/IPv4(not-done) Getting cached packet ... == output page-fault == Sometim...

Hello, I thinking about using PCI passthrough to dedicated a domU as firewall. I understand PCI passthrough concept. When done, my domU will see network card and the dom0 won''t any more. So I''ll be able to filter all trafic from outside, since it will go through network domU. Then, how will I be able to connect other domU (and maybe dom0) to the network domU ? In a normal way,

Hello Gene, thanks a lot for your patch! It doesn't work yet, but I have some more information. Before the patch, the boot sequence ended with the following: NBP file download successfully. Getting cached packet My IP is 0.0.0.0 After the patch it ended with the following (note that the IP is the same as the Station IP address): NBP file download successfully. LibLocateHandle returned

...sue (the part that's generating the handle->Configure() messages). I'm trying to read through pieces of the EFI spec, gnu-efi API, and a few other sources.? I'm pretty certain you'll see that the previous patch/binaries are sending packets that _should_ be sent on NIC1 out NIC0.-- -Gene <<< Hi Gene have you seen this thread? http://www.syslinux.org/archives/2015-April/023436.html continued here http://www.syslinux.org/archives/2015-May/023443.html Cao's patch try to solve the same multi-NIC issue you are dealing with; Your approach detect's the right...

...   SLsl 10:00   0:09 /usr/lib/xen/bin/qemu-system-i386 -xen-domid 6 -chardev socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-6,server,nowait -mon chardev=libxl-cmd,mode=control -name InitialName -vnc 0.0.0.0:0,password -serial pty -vga cirrus -boot order=cda -smp 2,maxcpus=2 -device rtl8139,id=nic0,netdev=net0,mac=00:16:3e:e9:96:a8 -netdev type=tap,id=net0,ifname=vif6.0-emu,script=no,downscript=no -M xenfv -m 3064 -drive file=/root/test.qcow2,if=ide,index=0,media=disk,format=qcow2,cache=writeback root@ubuntu:~# xl rename 6 NewName root@ubuntu:~# xl list Name                              ...

...ling on configure with no mapping core_udp_sendto: stalling on configure with no mapping core_udp_sendto: stalling on configure with no mapping With BIOS P89 v1.40 (05/06/2015) I don't see any errors from core_udp_sendto anymore. Hardware used: HP ProLiant DL380 Gen9 NIC being used: NIC1 (not NIC0, since that's connected to a different network) Greetings, Sebastian On Mon, Jun 22, 2015 at 8:54 AM, S. Schauenburg <s.schauenburg at gmail.com> wrote: > Hello Gene, > > thanks a lot for your patch! It doesn't work yet, but I have some more > information. > >...

...the issue (the part that's generating the handle->Configure() messages). I'm trying to read through pieces of the EFI spec, gnu-efi API, and a few other sources. I'm pretty certain you'll see that the previous patch/binaries are sending packets that _should_ be sent on NIC1 out NIC0. -- -Gene

hi, at home I have setup a kvm virtualization lab. I have a layer 3 switch, a host with 3 nics and centos 6.3. In the layer 3 switch I have setup a couple of vlans: vlan 1 (default), 5 (quarantaine) and 10 (out-of-band-management). nic0 is configured in the switch as a trunk interface that sees all vlans. nic2 is an access port on vlan 5 and nic1 is not yet in the picture ;-) eth0 is bridged to br0. It also has the host default gateway. I have also created eth0.5, br0.5, eth0.10 and br0.10 interfaces to add vm's to vlan 5 and...

...iably for me, no matter what I tried. In the end I had to use different names instead of eth0 and eth1, like: SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="11:22:33:aa:bb:cc", ATTR{type}=="1", KERNEL=="eth*", NAME="nic0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="44:55:66:dd:ee:ff", ATTR{type}=="1", KERNEL=="eth*", NAME="nic1" And also rename /etc/sysconfig/network-scripts/ifcfg-ethX to ifcfg-nicX and modify them acco...

...the > handle->Configure() messages). > I'm trying to read through pieces of the EFI spec, gnu-efi API, > and a few other sources. I'm pretty > certain you'll see that the previous > patch/binaries are sending packets that > _should_ be sent on NIC1 out > NIC0.-- > -Gene > <<< > > Hi Gene > have you seen this thread? > http://www.syslinux.org/archives/2015-April/023436.html > continued here > http://www.syslinux.org/archives/2015-May/023443.html Apparently I tagged it in my email but never got around to reading it yet....

...gt; qemu-system-i386 -xen-domid 837 -chardev > > socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-837,server,nowait -mon > > chardev=libxl-cmd,mode=control -name suse11 -vnc 0.0.0.0:1 -serial pty -boot > > order=c -usb -usbdevice tablet -smp 2,maxcpus=2 -device > > rtl8139,id=nic0,netdev=net0,mac=00:16:3e:13:d3:72 -netdev > > type=tap,id=net0,ifname=tap837.0,downscript=no -M xenfv -m 2040 -drive > > file=/mnt/sdd/image/suse.image,if=ide,index=0,media=disk,format=raw,cache > > =none > > > > > > errno 14 shows Bad Address. And I find QEMU_AI...

Hi Michael, On 11/27/18 5:53 PM, Michael S. Tsirkin wrote: > On Thu, Nov 22, 2018 at 07:37:54PM +0000, Jean-Philippe Brucker wrote: >> Implement the virtio-iommu driver, following specification v0.9 [1]. >> >> Since v4 [2] I fixed the issues reported by Eric, and added Reviewed-by >> from Eric and Rob. Thanks! >> >> I changed the specification to fix one

Hi Michael, On 11/27/18 5:53 PM, Michael S. Tsirkin wrote: > On Thu, Nov 22, 2018 at 07:37:54PM +0000, Jean-Philippe Brucker wrote: >> Implement the virtio-iommu driver, following specification v0.9 [1]. >> >> Since v4 [2] I fixed the issues reported by Eric, and added Reviewed-by >> from Eric and Rob. Thanks! >> >> I changed the specification to fix one

...libxl_dm.c:1144:libxl__spawn_local_dm: tablet libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: -smp libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: 2,maxcpus=2 libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: -device libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: e1000,id=nic0,netdev=net0,mac=00:16:3e:14:b1:1d libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: -netdev libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: type=tap,id=net0,ifname=vif10.0-emu,script=no,downscript=no libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm: -M libxl: debug: libxl_dm.c:1144:l...

...n/qemu-system-i386 -xen-domid 3 -chardev socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-3,server,nowait -mon chardev=libxl-cmd,mode=control -nodefaults -name nathanwin--incoming -vnc 127.0.0.1:0,to=99 -device cirrus-vga -global vga.vram_size_mb=8 -boot order=cda -smp 2,maxcpus=2 -device rtl8139,id=nic0,netdev=net0,mac=00:16:3d:01:03:e0 -netdev type=tap,id=net0,ifname=vif3.0-emu,script=no,downscript=no -incoming fd:13 -machine xenfv -m 4088 -drive file=/dev/xen/blktap-2/tapdev2,if=ide,index=0,media=disk,format=raw,cache=writeback gtc-vana-005 ~ # lsof -p 32520 | grep blktap-2 tapdisk 32520 ro...

>>> > It does contain a Net but there are 2 issues with SNP: > 1) The interface is different than UDPv4/TCPv4 protocols; this imply lot of code. Not as much as you may think.? We already have lwIP implemented into lpxelinux.0.? It's more a matter of using more glue. > 2) SNP has its non-blocking transmit issues ; see "Flaws in the design" at >

Package: xen-utils-common Version: 4.4.1-6 Severity: normal Dear Maintainer, (There appear to be several reports on the BTS with concerns relating to this report. Some unarchiving/merging may be necessary. Reassignment may be needed as well since I'm not sure which package this problem would fall under. Ultimately decided to file with xen-utils-common with 'xl' being the frontend