Displaying 5 results from an estimated 5 matches for "verbose_request".
2008 May 27
0
VT hardware requirements
...t tm2 cx16 xtpr lahf_lm
bogomips : 4658.82
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
3) *dmesg | grep 0a:0e*
Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 rhgb quiet
pciback.hide=(0a:0e.0)(07:00.0) pciback.verbose_request=1 apic=debug
pci=routeirq)
Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet
pciback.hide=(0a:0e.0)(07:00.0) pciback.verbose_request=1 apic=debug
pci=routeirq
ACPI: PCI Interrupt 0000:0a:0e.0[A] -> GSI 18 (level, low) -> IRQ 20
pciback 0000:0a:0e.0: seizing device
ACPI: PCI Int...
2013 Nov 27
2
[BUG] domU kernel crash at igbvf module loading / __msix_mask_irq
...;']
vif = [''bridge=xenbr1'',''bridge=xenbr2'']
disk = [''phy:/dev/loop4,xvda1,w'', ''phy:/dev/loop5,xvda2,w'',
''phy:/dev/loop6,xvda3,w'']
root = "/dev/xvda1 ro rootfstype=ext4 iommu=soft
xen-pcifront.verbose_request=1"
DomU crash log:
[ 71.124852] pcifront pci-0: write dev=0000:00:00.0 - offset 72 size
2 val c00
2
[ 71.124888] BUG: unable to handle kernel paging request at
ffffc9000015400c
[ 71.124900] IP: [<ffffffff8121ea05>] __msix_mask_irq+0x21/0x24
[ 71.124911] PGD 784a0067 PUD 784a1...
2007 Nov 29
6
PCI Passthrough to HVM on xen-unstable
....18-xen-311.img
#3
title RHEL5-XEN320-UNSTABLE
root (hd0,0)
kernel /xen320-unstable/xen-3.2-unstable.gz dom0_mem=1300M
loopback.nloopbacks=16 vtd=1
module /xen320-unstable/vmlinuz-2.6.18.8-xen-1127
root=/dev/VolGroup00/LogVol01 ro showopts console=tty0 pciback.hide=(04:00.0)
pciback.verbose_request=1 apic=debug maxcpus=1
module /xen320-unstable/initrd-2.6.18.8-xen-1127.img
XEN-PEER-RHEL5 $ cat /mnt/archive/xendisks/Sles10/sles10disk.cfg
# -*- mode: python; -*-
#============================================================================
# Python configuration setup for ''xm crea...
2012 Jan 25
4
Fwd: BUG in linux+v3.2.1/drivers/xen/xen-pciback/pci_stub.c
First, maintainer''s addresses (Ryan Wilson <hap9@epoch.ncsc.mil>,
Chris Bookholt <hap10@epoch.ncsc.mil>) are wrong (users unknown to
remote mailsystem), so posting to you:
PCI bus format strings are wrong.
"%04x:%02x:%02x.%d"
should be used instead of
"%04x:%02x:%02x.%1x"
(in many places of linux+v3.2.1/drivers/xen/xen-pciback/pci_stub.c)
--
2006 Mar 07
8
PCI delegation works, access to the delegated NIC doesn''t
Hi all,
has anyone seen such a behaviour?:
I delegated successfully my NIC to a domU, but access to it from domU is not
possible. Device appears, but access to it via ''ifconfig ethX up'' doesn''t
work. Ends up in dmesg output like:
tg3: tg3_reset_hw timed out for eth1, firmware will not restart magic=00000000
Delegating my USB controllers e.g. works flawlessly.
Full