similar to: boot options for xen

I have just noticed this message in my kernel logs, reporting the possibility of an error with my memory. This would go a long way towards explaining the problems i''ve been having. This particular error is occuring when i''m not running xen so is obviously not something brought on by xen itself. The strange thing is that the NMI error is always followed by the TLAN: eth0: Adaptor

Hi everyone. I´m having this problem with Red Hat 5.4 running on a HP ProLiant BL460c G6. I have two windows 2k3 x64, but network performance is extremely bad without PV drivers, i mean, it takes a lot of time to access any location and if the path has many folders it can´t conect. Redhat provides some PV dirvers. I´ve installed them, but with no improvements. I tested another DomU, with the

''xm block-attach'' doesn''t let me assign the same backend device anymore, even if I use ''r!'' or ''w!''. I think this has changed since 3.1.1 (or maybe since 3.1.0). Is this the way it is supposed to work? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

I really need to have the ability to tie event channel port''s to interrupts for my gplpv drivers under Windows. Is anyone working on anything like this? Does MSI allow more than one interrupt per PCI device? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I''ve recently noticed that my windows crash dumps fail at around 40-50% under GPLPV. ''xm dmesg'' shows the following: (XEN) grant_table.c:350:d0 Iomem mapping not permitted ffffffffffffffff (domain 865) At first I thought that the cause was just a bug in my grant ref code but it just occurred to me that this could be happening when Windows tries to write out the

I''m just doing some testing on the gplpv drivers with different ways of handling interrupts, and I''m trying a scheme where each xen device (eg vbd/vif) driver attaches to the same IRQ as the pci driver, and each handles it in sequence. In testing though, I noticed the following when logging what each ISR is doing: 60.32381439 - evtchn event on port 5 60.32384109 - port 5

The attached patch fixes the save/restore issue seen with 32bit Windows guest VMs. The root cause is that current Xen doesn''t intercept SYSENTER-related MSRs for 32bit guest VMs. As a result, the guest_sysenter_xxx fields contain incorrect values and shouldn''t be used for save/restore. This patch checks the LMA bit of EFER register in the save/restore code path. Please apply it

The DMI checks that force the use of the bigsmp APIC driver are for systems that are no longer supported by Xen (32-bit x86). Signed-off-by: Matt Wilson <msw@amazon.com> Cc: Keir Fraser <keir@xen.org> Cc: Jan Beulich <jbeulich@suse.com> Cc: Andrew Cooper <andrew.cooper3@citrix.com> --- xen/arch/x86/genapic/bigsmp.c | 30 +----------------------------- 1 files changed, 1

I am having problems with save/restore under 3.3.1 in the GPLPV drivers. I call hvm_shutdown(xpdd, SHUTDOWN_suspend), but as soon as I lower IRQL (enabling interrupts), qemu goes to 100% CPU and the DomU load goes right up too. Xentrace is showing a whole lot of this going on: CPU0 200130258143212 (+ 770) hypercall [ rip = 0x000000008020632a, eax = 0xffffffff ] CPU0 200130258151107 (+

How should I be detecting a block-configure operation done in Dom0 in a HVM DomU? Under Debian Lenny''s Xen 3.2.1, when I execute such a command, Dom0 writes to the backend values ''params'' and ''type'', twice, but doesn''t update the ''sectors'' value to match the new device, or initiate a state change. Given that, the best I can

Does the linux-2.6.18-xen.hg go with xen-3.3-testing.hg or xen-unstable.hg? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I''m continuing to work on making a new XenCD as previously discussed here. In the course of that work, I''ve generated (actually, currently stuck on) the enclosed crash dump. Thought I''d forward it for interest. To head off questions, you''ll see references to a very large initrd (~114 Mb). The Xen dump may or not be related to this unusual usage.

I just about have my PV block device drivers booting, except just before the login screen appears I get a message that the registry couldn''t be written out. I''m pretty sure that this is because some data from the int13 interface provided by the qemu intel ide driver that has been written, hasn''t actually made it to the block device (lvm volume in my case). I''ve

I am trying to install CentOS 3.4 on a Compaq Proliant 1600, and it hangs on probing monitor type when anaconda starts. I have tried running 'linux text' and manually installing drivers from the f2 options screen. Any ideas? Forgive me if this is an unbearably simple question, but I am new to linux. Mike

On Thu, Feb 05, 2015 at 07:02:07PM +0100, Holger Baust wrote: > Hello. > > We are using pxelinux for years to boot Linux via PXE since years. > Since EFI is spreading, I changed configuration to be able to boot EFI > systems. > > The "Client": > - HP Proliant DL380Gen9 System FW: 1.21 11/03/2014, latest available > - NIC used for booting: HP Embedded LOM 331i

Hi experts, Q1:What''s the different for "dom0_max_vcpus=4 dom0_vcpus_pin" and "dom0_max_vcpus=4" ? which will get better performance Q2: dom0_max_vcpus=4 means "core0-3 will be just used by dom0" or means "4 cores(not dedicate cores) will be used by dom0, eg: core2-5 or core3-6? Q3.what does mean "nosmp" , xen, dom0,domU, will just use one

Hi experts, Q1:What''s the different for "dom0_max_vcpus=4 dom0_vcpus_pin" and "dom0_max_vcpus=4" ? which will get better performance Q2: dom0_max_vcpus=4 means "core0-3 will be just used by dom0" or means "4 cores(not dedicate cores) will be used by dom0, eg: core2-5 or core3-6? Q3.what does mean "nosmp" , xen, dom0,domU, will just use one

Hello. We are using pxelinux for years to boot Linux via PXE since years. Since EFI is spreading, I changed configuration to be able to boot EFI systems. The "Client": - HP Proliant DL380Gen9 System FW: 1.21 11/03/2014, latest available - NIC used for booting: HP Embedded LOM 331i (Broadcom BCM 5719/ tg3), FW: 5719-v1.38 The Server: - ISC-DHCP with tfpd-hpa running on Debian 6.x -

Hi, I have dovecot 2.0.20 running (its an old version, I know, it came from the stable archive at OpenCSW) with Solaris SMF integration working fine. It enables and disables okay. However, I cantt connect to it, it is allowing the connection, but spewing on permissions: Nov 24 17:34:20 proliant-1 dovecot: [ID 583609 mail.info] master: Dovecot v2.0.20 starting up Nov 24 17:34:27 proliant-1

I have been trying to track down a problem that occurs when my GPLPV drivers give Windows a packet with the NdisPacketTcpChecksumSucceeded flag set. The problem is that the machine locks hard. After some tedious work with the debugger, I have found that Windows makes a call to a routine called RtlPrefetchMemoryNonTemporal, which looks like this: 8088e579 mov eax,dword ptr