similar to: CentOS4 installer can't find a hard drive to install.

I hope someone can enlighten me. I have a quad-port Intel 82580 nic (igb driver) on my system and I''d like to dedicate each nic to a HVM via VT-d PCI passthrough. The IOMMU on my system seems to work, I can assign the PCI devices to my HVMs. The HVMs see the pci device and load their respective igb drivers, and ethtool -i eth0 works on each HVM, shows the drivers are loaded and the

Hello Rusty, A few trivial fixes on top of virtio-spec-0.8.9 (patch -p0): - grammatical errors - mark '-' in 'avail->flags' as non-breakable hyphen - add a footnote for console device to indicate queues 2 onwards are avl. if a feature was negotiated Amit --- virtio-spec-0.8.9.lyx 2010-10-05 17:26:11.318836266 +0530 +++ virtio-spec-0.8.9-mod.lyx 2010-10-05

Hello Rusty, A few trivial fixes on top of virtio-spec-0.8.9 (patch -p0): - grammatical errors - mark '-' in 'avail->flags' as non-breakable hyphen - add a footnote for console device to indicate queues 2 onwards are avl. if a feature was negotiated Amit --- virtio-spec-0.8.9.lyx 2010-10-05 17:26:11.318836266 +0530 +++ virtio-spec-0.8.9-mod.lyx 2010-10-05

The virtio-console device has recently been updated to support multiple devices and multiple ports. These ports can also function as generic serial ports. Reflect these changes in the spec. Signed-off-by: Amit Shah <amit.shah at redhat.com> --- virtio-spec/virtio-spec-0.8.3.lyx.orig 2010-01-20 19:21:02.239131766 +0530 +++ virtio-spec/virtio-spec-0.8.3.lyx 2010-01-20 19:21:02.228131971

The virtio-console device has recently been updated to support multiple devices and multiple ports. These ports can also function as generic serial ports. Reflect these changes in the spec. Signed-off-by: Amit Shah <amit.shah at redhat.com> --- virtio-spec/virtio-spec-0.8.3.lyx.orig 2010-01-20 19:21:02.239131766 +0530 +++ virtio-spec/virtio-spec-0.8.3.lyx 2010-01-20 19:21:02.228131971

How does one specify two different ports in the same host file? When lapops are hardwired versus when mobile on a totally different lan. address0 71.17.72.27 address1 192.168.2.27 port0 22755 port1 655

This is a corrected version of the patch I originally submitted on September 5th, and resubmitted on October 14th. I have removed the changes that added $(CFLAGS) to the link-only invocations of gcc. Otherwise, the patch is the same as before. My thanks to Paul (prj@po.cwru.edu) for noticing my error and kindly correcting me. ** text of original letter, with corrections ** I had to make some

I had to make some patches to rsync to get it to build on VOS. We are a POSIX-96 (but not Unix) system. Here is the subset of the patches that I think are general to all platforms. I have tested these here. I was surprised that CPPFLAGS is not available to the compilation rules in the Makefile. Most other packages (e.g. Samba) seem to allow CPPFLAGS to be set by the user. Since this is how I

** This is a resend of mail I originally sent on September 5th. I am still interested in getting these patches applied, and getting a new config.guess and config.sub. Is there anything else I need to do in order to get these changes accepted? Thanks. PG ** I had to make some patches to rsync to get it to build on VOS. We are a POSIX-96 (but not Unix) system.

The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When

The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When

Howdy, I've been trying for a while now to get this running. Can anybody please tell me what the proper configuration is for this unit ??? This is what I've got/tried so far: # cat ups.conf # Start with # # # upsdrvctl -u nut -D start MEGATEC MODE=netserver user=nut # Ultra ULT33046 2000 VA 1200 W

So a 70-persistent-net.rules like # onboard port 1 -> eth0 ACTION=="add", SUBSYSTEM=="net", BUS=="pci", ID=="0000:00:19.0", NAME="eth0" # PCIe card -> eth2 ACTION=="add", SUBSYSTEM=="net", BUS=="pci", ID=="0000:03:00.0", NAME="eth2" # onboard port 2 -> eth1 ACTION=="add",

another identical machine will have the same bus ids. that's why this works. Kahlil (Kal) Hodgson GPG: C9A02289 Head of Technology (m) +61 (0) 4 2573 0382 DealMax Pty Ltd GitHub: @tartansandal Suite 1416 401 Docklands Drive Docklands VIC 3008 Australia "All parts should go together without forcing. You must

The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When

This is an updated version of my patches to get rsync to build and run its tests on the Stratus VOS operating system. I have updated this patch to apply cleanly to the current copy of HEAD. I also ran the test suite and discovered that I needed to tweak a few spots in the Makefile to append the executable suffix (VOS is one of the few systems that has a required executable suffix). There are a

On Fri, 2018-12-14 at 10:29 +0100, Daniel Vetter wrote: > On Thu, Dec 13, 2018 at 08:25:32PM -0500, Lyude Paul wrote: > > The current way of handling refcounting in the DP MST helpers is really > > confusing and probably just plain wrong because it's been hacked up many > > times over the years without anyone actually going over the code and > > seeing if things

So I'm back to this problem. A quick run down of what the original problem was: I have a machine that I'm configuring to use kickstart to setup. It has two builtin ethernet ports (labeled ports 1 and 2) and I'm adding a third one on its PCIe bus. Originally I was using an r8169 clone a default kickstart always put it as eth0 with the builtin ones as eth1 and eth2 respectively. After

Right, I understand that part. However I believe I'm now in the realm of making this specific to this machine as I have no guarantee that another identical machine will pop up with those same bus IDs. Maybe for the internal ports, but I don't know if the same will happen for the PCIe bus. Would that be correct? On Thu, May 14, 2015 at 6:21 PM, Kahlil Hodgson < kahlil.hodgson at

Hello: I just gave 3 tries at compiling a xen kernel. I managed to get the networking in the host to work ok on the third try, unfortuately xend gives me the following errors in my xend.log and will not start. Any ideas? It fails to start with the following error ---------------------------------------------------- /usr/sbin/xend [root@localhost ~]# /usr/sbin/xend start Traceback (most recent