similar to: Config to set CPU affinity and distribute interrupts

The patch ''mem_event: use wait queue when ring is full'' I just sent out makes use of the waitqueue feature. There are two issues I get with the change applied: I think I got the logic right, and in my testing vcpu->pause_count drops to zero in p2m_mem_paging_resume(). But for some reason the vcpu does not make progress after the first wakeup. In my debugging there is one

Hi! I see these messages from the xen-kernel: (XEN) /usr/src/xen-unstable.hg/xen/include/asm/mm.h:186:d0 Error pfn 100: rd=ffff8300df05c100, od=0000000000000000, caf=00000000, taf=0000000000000000 (XEN) mm.c:636:d0 Error getting mfn 100 (pfn 5555555555555555) from L1 entry 8000000000100125 for dom32753 (XEN) /usr/src/xen-unstable.hg/xen/include/asm/mm.h:186:d0 Error pfn 100:

Hardware: Dell Poweredge R510 (32G ram, 8 CPU- Xeon) 64bit - xen 4.0.1 stable 64bit - 2.6.32.18 dom0 (.config attached) running Ubuntu 10.04 32 bit - 2.6.18.8 domU (.config attached) running ubuntu 8.04 domU has 3 tap2 disks, on lvm snapshots. domU has 2G mem, 2 VCPU workload on domU - ssh + top running, destroy domain -- This works . But, If i run a heavier workload say postgres db (just

In testing our implementation of the hypervisor copy based backend- >frontend networking changes, we see what I believe are spurious warning messages during the shutdown of the frontend domain: (XEN) /export/build/schuster/xvm-gate/xen.hg/xen/include/asm/mm.h: 189:d0 Error pfn 30e290: rd=ffff830000fcf100, od=ffff830000fcf100, caf=00000000, taf=0000000000000000 (XEN) Xen call trace:

I am currently looking at a bug report[1] which is happening when a Xen PVM guest with multiple VCPUs is running a high IO database load (a test script is available in the bug report). In experimenting it seems that this happens (or is getting more likely) when the number of VCPUs is 8 or higher (though I have not tried 6, only 2 and 4), having autogroup enabled seems to make it more likely, too

Hello, as some might have read in my previous postings, I have a Mini-OS dom0 that constructs a Mini-OS domU on x86 xen-3.0.4-testing. As the memory layout my Dom0 builds does not guarantee, that pages the DomU Mini-OS tries to use as page tables are mapped to existing memory, I changed new_pt_frame in arch/x86/mm.c in the following way: The pt_pfn is mapped R/W, then it is zeroed by a

changeset: 7353:29db5bded574 tag: tip user: kaf24@firebug.cl.cam.ac.uk date: Wed Oct 12 11:15:02 2005 +0100 summary: Fix 64-bit compile warnings in firmware. UP Dell Precision 330, Centos 4.1 dom0. Should XEN even be accessing anything from the source it was built from? Also had all the domU''s toast right after this, they where running for almost 2 days.

On 31/08/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote: > Please can you try searching for bios updates etc. I have an almost > identical pre-release Dell machine that Xen works fine on. A00 came installed and is the latest. > Please can you post the ouput of ''lspci -v''. My sata controller is a rev > 03, prog-if 8f, ''Unknown device 5656''

We have seen a series of messages when running xm-test lately on a SLES 9 SP2 32-bit box with 4GB of RAM, PAE enabled Xen build. I don''t know whether this defect of just an informational message. (XEN) (file=memory.c, line=42) Only I/O-capable domains may allocate multi-page extents. (XEN) (file=memory.c, line=42) Only I/O-capable domains may allocate multi-page extents. (XEN)

Hello, I''m trying to get PDB working in accordance with the instructions at http://www.cl.cam.ac.uk/~sos22/replay.bk/docs/misc/XenDebugger-HOWTO and a message from this list: http://lists.xensource.com/archives/html/xen-devel/2004-08/msg00017.html When I try to build pdb I first get errors because the Makefile is configured to treat warnings as errors, and there are some warnings.

All. I am running Xen on an ES7000 system with 4 procs and 4 GB memory. I am running Suse Sles-9 (32-bit) on the machine. I have compiled Xen (the tip on the unstable tree : 6552) with PAE enabled (XEN_TARGET_X86_PAE=y). The system boots fine. I started xend and when I tried to bring up a virtual machine, the system gave me the following error on the command line. On the serial port, I saw an

Hi, Does anyone know what the negative indexing of a matrix mean? I am using the RWeka and this evaluate classifier does not work on new data like this e <- evaluate_Weka_classifier(m1235,newdata=XW4, complexity = FALSE,class = FALSE) while it work with negative indexing: e <- evaluate_Weka_classifier(m1235,newdata=XW4[,-2], complexity = FALSE,class = FALSE) Although I

Hi, Does anyone know what the negative indexing of a matrix mean? I am using the RWeka and this evaluate classifier does not work on new data like this e <- evaluate_Weka_classifier(m1235,newdata=XW4, complexity = FALSE,class = FALSE) while it work with negative indexing: e <- evaluate_Weka_classifier(m1235,newdata=XW4[,-2], complexity = FALSE,class = FALSE) Although I

I''m having trouble actually seeing a PCI device in my VMs. I''ve resolved several of my issues using previous posts and using the VTdHowTo wiki page. I have both VT and VTd BIOS options enabled. I have pciback hiding the devices and xm can list and assign the devices to VMs. I don''t see the PCI devices in my VMs though. I have tried a windows and a Linux vm, without

Hello, I''ve done an update from xen 3.2 to 3.3. Since 3.3 I can not use my TV-Card anymore. The error message is "Error: pci: 0000:10:0a.0: non-page-aligned MMIO BAR found." lspci shows the card as 10:0a.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Any hints ? Thanks in advance Christoph xm dmesg: (XEN) Xen version 3.3.1-rc1-pre (root@artus.own) (gcc

Please can you do an ''lspci -nv'' to find out the exact version of your controller. I''m wandering whether it features in pci/quirks.c and whether the fixup code is borked on Xen. Also, have you tried fiddling around with any of the BIOS IDE legacy mode settings? There really is no good explanation for a) why the MMIO region is so low on native, and b) why it is

Sorry I ran ?make' command in nut-website/nut... (I still can?t understand why creating man page is so long, it is much more faster on ubuntu.) When running ?make? in nut-website, same issue then described previously, even with Arno patch > sort: stray character in field spec: invalid field specification `4.1,4.5rV > > >>>>>> and it ends with: > >

RF64 support sure would be nice, but it wouldn't really help to do this "instead of" CAF. For one thing, Logic Studio Pro does not seem to support RF64, because the manual states that WAVE and BWF are limited to 4 GB. CAF may be a format which lacks universal support, but RF64 is also very limited in usefulness. Treating either one as a substitute for the other is not

Avuton Olrich wrote: > On 7/11/05, Erik de Castro Lopo <erikd-flac@mega-nerd.com> wrote: > >>and I'm thinking of adding support for FLAC in a CAF container >>as well. Is anyone else working on this? If so please let me >>know so we can agree on how FLAC should be contained with CAF. > > > I'm sorry, but what are the advantages to the different

Hi, the CAF format is not stremable due to the way the format works. On 14 May 2020, at 4:42, webmaster at berean-biblechurch.org wrote: > Using FFmpeg, I can stream to a file on disk okay: > c:\apps\ffmpeg\bin\ffmpeg.exe -f dshow -i audio="Line In (Realtek > High Definition Audio)" -c:a libopus -ac 1 -b:a 32000 live.caf > > But, if I add Icey metadata, FFmpeg