similar to: Set PCI device latency from domU?

> They instantly got us to look at the output of zttest and we found that this was (in their words) 'extremely low', with 'best' and > 'worst' readings of 99.975586% and 99.963379% respectively. Might want to give PCI latency setting a try, it helped for me. My ZTTEST would drop occasionally to 99.95% until I set: setpci -v -s 01:01.0 latency_timer=ff

Hi all, I can''t find any good talk about this subject and would like some insights and advices on the cache side in xen. I discovered that a domO power outage can lead to a severe filesystem corruption of the domUs. The domO is a dual disk dell server with a PERC controler in writethrough cache mode, the disk cache is disabled, the scheduler in the domO/domU is NOOP, the domO is holding

Hi, > BTW: is there a tool (or pciutils patch) which can decode the virtio > capabilities? Searched for a patch today, and all google found me was this mail asking for one :-o So I went ahead and coded one up. Attached. While hacking it up I've noticed spec doesn't match reality. The "Virtio Structure PCI Capabilities" section here ...

Hi, > BTW: is there a tool (or pciutils patch) which can decode the virtio > capabilities? Searched for a patch today, and all google found me was this mail asking for one :-o So I went ahead and coded one up. Attached. While hacking it up I've noticed spec doesn't match reality. The "Virtio Structure PCI Capabilities" section here ...

On Fri, Aug 24, 2018 at 11:42 PM, Peter Wu <peter at lekensteyn.nl> wrote: > Are these systems also affected through runtime power management? For > example: > > modprobe nouveau # should enable runtime PM > sleep 6 # wait for runtime suspend to kick in > lspci -s1: # runtime resume by reading PCI config space > > On laptops from

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

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

Hello, I´m trying to map one network interface of a Dual-Port e1000 Server Adapter to a DomU (firewall). In Dom0 the adaper is seen with lspci as: 06:00.0 Ethernet controller: Intel Corporation 631xESB/632xESB DPT LAN Controller Copper (rev 01) 06:00.1 Ethernet controller: Intel Corporation 631xESB/632xESB DPT LAN Controller Copper (rev 01) My goal is to map only 06:00.1 to DomU so I used this

Hi all, I have been having an issue for over a year with several Xen installations and have not been able to find out if this is just something I am missing. Basically I am trying to configure a firewall with two ethernet cards in a domU using pci passthrough. I am hiding the Ethernet cards at boot time via the pciback.hide kernel option. Right now I am running Xen 3.3.0 and the two Ethernet

Hi, is there any possibility to get a XEN DomO and DomU running with bridget and routed mode together. The reason behind this is, to get the requests via the official IPs to the DomU''s (routed-mode) and the interworking between the DomU''s with connected with help of the (bridged-mode). I got it work, with setting everything up manually. But as I understood the

virtio uses vendor-specific capabilities to specify the location of the virtio register ranges. The specification can be found here: http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 This patch adds support for decoding these capabilities to lspci. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- Makefile | 2 +- ls-caps-vendor.c | 76

virtio uses vendor-specific capabilities to specify the location of the virtio register ranges. The specification can be found here: http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 This patch adds support for decoding these capabilities to lspci. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- Makefile | 2 +- ls-caps-vendor.c | 76

virtio uses vendor-specific capabilities to specify the location of the virtio register ranges. The specification can be found here: http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 This patch adds support for decoding these capabilities to lspci. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- Makefile | 2 +- ls-caps-vendor.c | 59

virtio uses vendor-specific capabilities to specify the location of the virtio register ranges. The specification can be found here: http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 This patch adds support for decoding these capabilities to lspci. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- Makefile | 2 +- ls-caps-vendor.c | 59

I am running a 64 bit dom0 with a stock Debian Squeeze xen hypervisor and kernel. On top of this I am running a PV 32 bit domU that is passed two PCI network cards. This set-up had been working well for over a year, however there was a recent hypervisor update so I rebooted the dom0. Unfortunately now the domU that is being passed the two NICs is no longer able to create a PPPoe connection to

Hello, I am currently trying to move my VMs from running on local host storage to a shared storage (trying out iSCSI) but I am facing a bit of a booting dilemma. The domUs are a mix of paravirtualized and fully-virtualized VMs. They all boot and run like clockwork when on local storage. The paravirtualized domUs appear not to have a problem when I relocate and boot them from the shared storage

Hi, I want to give direct access to my monitor for my linux domU so that my graphics can run smoothly inside domU which is Ubuntu 8.10 I tried doing the following, but things didn''t work out. 1. I boot my Xen on Debian ( lenny ) using kernel /boot/xen-3.2-1-i386.gz module /boot/vmlinuz-2.6.26-1-xen-686 root=/dev/sdc4 ro console=tty0 pciback.permissive pciback.hide=(00:02.0)

Fc4 domO, tyan 2462 SMP xen_changeset : Thu Sep 29 14:59:18 2005 +0100 7f732bba3ed4 domU''s will not start, they try to and hang. Regards, Ted _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I''m a newbie to Xen. I installed a DomO CentOS 5.2 and several DomU (centOS, Debian and Ubuntu). It worked very well. Yesterday I experienced a power cut. I now experienced some problems. For example, when I start a DomU with the "xm create whatever_I_want" command, I get : Using config file nnnnnnn tap tap-10-51712 : 2 getting info Started domain xxxxxx and just after,

Hello, I see the new Xen packages now really in Sid and even in Lenny on packages.debian.org: http://packages.debian.org/search?keywords=linux-image+xen+amd64&searchon=names&suite=testing&section=all http://packages.debian.org/lenny/xen-linux-system-2.6.26-1-xen-amd64 Does this mean there is now official Xen amb64 and dom0 support in Lenny? I am running it now for a while without