search for: nomsi

I have a grub.conf (below) with pci=nomsi, also /proc/cmdline and dmesg | more do not show the pci=nomsi. How can this be? there are no strange characters after quiet and before pci=nomsi. It was edited with vi. What can I do to get this parameter in my kernel boot line. Jerry ----------------- default=0 timeout=5 splashimage=(hd0,0...

...40. assign two nics(pci and pcie) to one UP Linux guest with vtd. FAIL 41. assign two nics(pci and pcie) to one SMP Linux guest with vtd. FAIL 42. scp a big file in Linux guest via two nics(pci and pcie) assigned with vt-d. FAIL 43. assign two nics(pci and pcie) to one UP Linux guest with vtd(nomsi). PASS 44. assign two nics(pci and pcie) to one SMP Linux guest with vtd(nomsi). PASS 45. assign two nics(pci and pcie) to one UP WinXP guest with vtd(nomsi). PASS 46. assign two nics(pci and pcie) to one SMP WinXP guest with vtd(nomsi). PASS 47. scp a big file in Linux gue...

...Boot up SMP Win2008 VMX guest PASS 37. Boot up nevada VMX guest PASS 38. Boot up indiana VMX guest PASS 39. Assign 2 NICs to one UP Linux guest with VT-d(nomsi) PASS 40. Assign 2 NICs to one SMP Linux guest with VT-d(nomsi) PASS 41. Assign 2 NICs to one UP winxp guest with VT-d(nomsi) PASS 42. Assign 2 NICs to one SMP winxp guest with VT-d(nomsi) PASS 43. Scp a big file w...

...40. assign two nics(pci and pcie) to one UP Linux guest with vtd. PASS 41. assign two nics(pci and pcie) to one SMP Linux guest with vtd. PASS 42. scp a big file in Linux guest via two nics(pci and pcie) assigned with vt-d. PASS 43. assign two nics(pci and pcie) to one UP Linux guest with vtd(nomsi). PASS 44. assign two nics(pci and pcie) to one SMP Linux guest with vtd(nomsi). PASS 45. assign two nics(pci and pcie) to one UP WinXP guest with vtd(nomsi). PASS 46. assign two nics(pci and pcie) to one SMP WinXP guest with vtd(nomsi). PASS 47. scp a big file in Linux gue...

On 01/30/2017 03:18 AM, Jinesh Choksi wrote: >>Are there other kernel options that might be useful to try? > > pci=nomsi > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/comments/13 Incidentally, already found that one and I'm trying it currently on one of the boxes. So far there's been no issues, but it's only been since Friday. Also, I found this: https://xen.crc.id.au/support...

I am submitting the patch which supports more Capability Structures and Device Specific Registers for passthrough device. In Xen 3.3 unstable, qemu-dm supports Configuration Header, MSI Capability Structure, and MSI-X Capability Structure. But qemu-dm does not support PCI Express Capability Structure, Device Specific Registers, etc (writing them is ignored). To support various I/O devices, I

Hi, I am having some difficulties installing centos 5.3 on the gigabyte GA-MA790FX-UD5P motherboard. Has anyone got centos booting on this motherboard? so far I have tried the following. + disabled the jmicron controller as this caused errors on booting JMB363 bad irq(0): will probe later error (this error caused the installation to stop at this point) + tested all components in another

Anyone know how to get the realtek 8211CL network driver working on an ASUS M3N78 motherboard? I was able to get the SATA disks to work with using the pci=nomsi boot option. Jerry

Hello All. I have a dell optiplex 320 that I can install centos5 on using pci=nomsi. That seems to be the only way. After the install grub loads but thats about as far as it gets. It looks like a BIOS bug to me, but I just don't know. I left it sit for a few minutes and it just had the echoed boot params on the screen. I've tried booting with noapic nolapic apm=off acp...

...r so >> real-world VMs up on them. > > There "appears" to be some sort of load-dependent pattern here too, but > it's impossible to confirm it. > The only stability improvement I was able to use "dom0_max_vcpus=1 > dom0_vcpus_pin". Haven't tried pci=nomsi yet. So far the one hypervisor with pci=nomsi has been quiet but that doesn't mean it's fixed. I need to give it 6 weeks or so. :) Thanks for your input on the issue! -- Kevin Stange Chief Technology Officer Steadfast | Managed Infrastructure, Datacenter and Cloud Services 800 S Wells,...

...a >> bit more difficult than Intel ones. > > We've purchased a number of servers with Broadcom BCM957810A1008G, sold > by Dell as QLogic 57810 dual 10Gb Base-T adapters, none of them going up > & down like a yo-yo so far. > >> So far the one hypervisor with pci=nomsi has been quiet but that doesn't >> mean it's fixed. I need to give it 6 weeks or so. :) > > It'd be more like 6-9 months for us, making it terrible to debug it :-/ I had a bunch of these on relatively light VM load for 3 months for "burn in" with no issues but t...

I''ve installed Xen Hypervisor 3.0.3 (CentOS 5.7, i386) inside Virtualbox 4.1.16 (Mageia 1, i686) and have noticed that Dom0 is consuming 85% of the memory allocated to the VM (1GB) so I''d like to reduce this as much as possible in order to make more room for one or two VM''s. Is there a minimum amount of vRAM that can/should be allocated to Dom0 (using the dom0_mem boot

On 01/27/2017 06:08 AM, Karel Hendrych wrote: > Have you tried to eliminate all power management features all over? I've been trying to find and disable all power management features but having relatively little luck with that solving the problems. Stabbing the the dark I've tried different ACPI settings, including completely disabling it, disabling CPU frequency scaling, and setting

This might be a silly question for most, but since Xen is ever so changing with regular changesets and updates, what is the "best practice" way to upgrade / update or even downgrade Xen? 1.) Is it by booting into regular Linux Kernel without Xen, do a complete uninstall of the old Xen, than install the newly compiled Xen? 2.) Is it by booting into regular Linux Kernel without Xen,

...ling with this akward error: -> xen-pciback.hide=(X:XX.X) pci=resource_alignment=XX:XX.X <- works for me! ---- title Xen 3.4.2 / 2.6.31.12-xen4 root (hd0,6) kernel /boot/xen-3.4.2.gz module /boot/vmlinuz-2.6.31.12-xen4 root=/dev/sda7 ro console=tty0 pci=nomsi noreboot xen-pciback.hide=(01:07.0) pci=resource_alignment=01:07.0 module /boot/initrd.img-2.6.31.12-xen4 ---- Now I get: ----- chieftec:~# xm create vdr1.cfg Using config file "/etc/xen/vdr1.cfg". Started domain vdr1 (id=1) chieftec:~# ----- Have a great weekend Christian --...

...that probably won't help then. I tried it on one >> box which hasn't had the issue again yet, but that doesn't guarantee >> anything. > > I was able to discover something new, which might not conclusively prove > anything, but it at least seems to rule out the pci=nomsi kernel option > from being effective. > > I had one server booted with that option as well as MTU 1500. It was > stable for quite a long time, so I decided to try turning the MTU back > to 9000 and within 12 hours, the interface on the expansion NIC with the > jumbo MTU failed....

Hello, my dom0 is an alpinelinux installed with kernel 3.10.14-1-grsec and xen 4.2.2. My domU is an opensuse 12.3 with all patches installed. The system works great, but when I do only switch xen from 4.2.2 to 4.3.0 (packages from http://nl.alpinelinux.org/alpine/edge/main/x86_64/) then my kernel in the domU does an Oops and the drivers for my dvb card aren''t loaded successfully. When I

Hi, I''ve recently setup a few machines with 3.2 64bit without any unresolvable problem. These machines all run pv domU''s and a view "basic" hvm domUs. As I''ve got one machine left for internal use and testing, I would like to take a look at pciback with VT-d support (bios screen shows a VT-d [enable|disable]). My question is, do I need to add patches, or use

Hi, I''ve recently setup a few machines with 3.2 64bit without any unresolvable problem. These machines all run pv domU''s and a view "basic" hvm domUs. As I''ve got one machine left for internal use and testing, I would like to take a look at pciback with VT-d support (bios screen shows a VT-d [enable|disable]). My question is, do I need to add patches, or use

On 01/30/2017 12:59 PM, Kevin Stange wrote: > On 01/30/2017 03:18 AM, Jinesh Choksi wrote: >>> Are there other kernel options that might be useful to try? >> >> pci=nomsi >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/comments/13 > > Incidentally, already found that one and I'm trying it currently on one > of the boxes. So far there's been no issues, but it's only been since > Friday. > > Also, I found...