similar to: enabling Frame Buffer on Xen

Hi, I did not find any hints in the web where to configure/setup/manipulate the rx/tx ring buffer allocation within dom0 for xen-unstable, maybe someone here can nudge me towards the right knob. The problem: when booting a handful of domUs and connecting them (comprising a small experimental IP network with links and nodes etc.), some interfaces that have been given by the configuration files

This buffer overflow was introduced with 91e0c5f3dad47838cb2ecc1865ce789a0b7182b1 (2.6.24). Cc: Konrad Rzeszutek Wilk <konrad.wilk at oracle.com> Cc: Jeremy Fitzhardinge <jeremy at goop.org> Cc: Thomas Gleixner <tglx at linutronix.de> Cc: Ingo Molnar <mingo at redhat.com> Cc: "H. Peter Anvin" <hpa at zytor.com> Cc: x86 at kernel.org Cc: xen-devel at

This buffer overflow was introduced with 91e0c5f3dad47838cb2ecc1865ce789a0b7182b1 (2.6.24). Cc: Konrad Rzeszutek Wilk <konrad.wilk at oracle.com> Cc: Jeremy Fitzhardinge <jeremy at goop.org> Cc: Thomas Gleixner <tglx at linutronix.de> Cc: Ingo Molnar <mingo at redhat.com> Cc: "H. Peter Anvin" <hpa at zytor.com> Cc: x86 at kernel.org Cc: xen-devel at

Last month Mark Williamson sent out a patch to unconditionally enable the trace buffer. I''d like to suggest that his patch be accepted and merged. I have performed some simple benchmarks to quantify the overhead associated with the trace buffer and calls, and found a negligable performance loss due to them. The actual number was .069%, and was gotten by timing a simple cpu-intensive

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1321356497 0 # Node ID 3cfb8f2c4ce898414279d7162206be812584bd5b # Parent 955a6c07dc5e9c55316d1678b2b7cc4313f4fd57 xen: avoid crash enabling turbo mode On a system which has not had P-state information pushed down into the hypervisor running "xenpm enable-turbo-mode" will reliably crash the host. (XEN) PM

>> >> Is the nmi_sanity_check() needed? We shouldn''t lose NMIs: >> even if we take one while doing NMI processing, we sholuld >> retake the NMI as soon as the first one IRETs. >> The nmi_sanity_check() should not be needed if everything is working fine. However I suggest we should keep it for now until we are sure it is safe to remove it. I would

> On Fri, 07 Jul 2006 17:57:52 +0100, Christian Limpach wrote: > > > On 6/26/06, Markus Armbruster <armbru@redhat.com> wrote: > >> Straightforward conversion to Xenstore. > >> > >> Applies to hg repository at http://hg.codemonkey.ws/vncfb > > > > Ideally, we''d move qemu''s vnc support into a library to make it reusable.

Hi. We get the errors below in the kernel logs. WARNING: Kernel Errors Present Buffer I/O error on device nbd0, ...: 27 Time(s) Buffer I/O error on device nbd16,...: 3 Time(s) end_request: I/O error, dev nbd0, secto...: 13 Time(s) end_request: I/O error, dev nbd1, secto...: 7 Time(s) end_request: I/O error, dev nbd10, sect...: 7 Time(s) I see someone else has reported this error message. E.g.

Thanks a lot....recompiling xen-tools wih ioemu flagsolved my problem. Daniel Bojczuk On Sun, Jun 27, 2010 at 10:55 AM, Mohamed Yacoubi <myacoubi@euro-web.fr> wrote: > Hi, > Can you recompile xen-tools with USE = "ioemu" ? > That should solve the problem. > Best regards, > Le 22 juin 2010 à 22:01, Daniel Bojczuk a écrit : > > I stiil did not solve te

I have a large system with pretty voluminous boot time messages that are exceeding the capacity of the ring buffer displayed by "xm dmesg" (i.e., the early messages are lost, and I see only the last messages). With a regular, non-Xen kernel, I use "log_buf_len=size" to enlarge the printk ring buffer size, but this boot option doesn''t seem to work for Xen. Anyone have

For many months now we have been trying to create a file-backed qcow image with the qcow-create code. Each time we try to back a file with a qcow, it screams: *** buffer overflow detected ***: qcow-create terminated Below is the output from two different attempts and information about qcow-create. Any ideas/thoughts/help you can offer? Thank you for your help! -Eric [root@trogdor ~]#

This patch implements a local buffer reference type for kernel virtual address space and a remote buffer reference type for buffers up to 16 pages based on grant tables. These types are used by the USB driver for bulk data transfer. Signed-off-by: Harry Butterworth <butterwo@uk.ibm.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Running this script from within a PV guest without having an xm console attached can use all dom0 memory. while [ 1 ]; do ls -lR /usr > /dev/xvc0; done Start of script: (1% mem usage) PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10281 root 15 0 76536 14m 2448 S 2 1.0 0:00.61 qemu-dm Couple minutes later: (17% mem usage)

Hi, I have a centos 5.6 xen vps which loses network connectivity once in a while with following error. ========================================= -bash-3.2# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available

Hi, it seems as if it is not possible to have more than 3 nics per domU right now. If I specify more, I get the usual [...] xen_net: Initialising virtual ethernet driver. #### netfront can''t alloc rx grant refs vif: probe of vif-3 failed with error -12 [...] message - see bug #183. It was pointed out to me that it might be possible to adjust this manually in

This change has the effect of adding some complexity to the callback routines. The original callback passed an opaque argument which was a private item for the use of the controlling mechanism and its callback function. This change removes this and specifies only an fd. While it''s possible for the controlling mechanism to use the fd as an index to find internal data structures, this is

Package: xen-3.0 Version: 3.0.3-0-2 Severity: grave Tags: security Hi, the following CVE (Common Vulnerabilities & Exposures) id was published for xen-3.0. CVE-2007-1320[0]: | Multiple heap-based buffer overflows in the cirrus_invalidate_region | function in the Cirrus VGA extension in QEMU 0.8.2 might allow local | users to execute arbitrary code via unspecified vectors related to |

Hi, Is there any configuration setting to increase the size of the ringbuffer used for Xen dmesg ? I wanted to check the advanced features supported on my Xen systems, on my Optiplex 755 I can read the info by running "xm dmesg" and searching for VMX: (XEN) VMX: Supported advanced features: (XEN) - APIC TPR shadow (XEN) - MSR direct-access bitmap But on my Supermicro system which

I am removing the experimental feature that allows buffer sizes for transfers from TPMs larger than 2kb. This could become useful if a vTPM is located in its owns domain and needs to be serialized for suspension or migration and the packet size becomes bigger than the current limit. Partial reads were supposed to complement this feature for applications to know how many bytes to read from

I ran into this when I was reviewing what was outstanding to get NetWare to run fully virtualized. The BIOS emulator code has the segment and offset backward in the returned buffer for the int 13h, fn 48h BIOS call. BTW: This is fixed in current Bochs emulator upstream code. Signed-off-by: Bruce Rogers <brogers@novell.com> diff -r 59b8768d0d0d tools/firmware/rombios/rombios.c ---