search for: old_entri

This fixes a bug in changeset 22526:7a5ee3800417, where the wrong value is read when deciding whether to flush the VTd tables. The effect is minor: in situations where the p2m entry is changed but the mfn is the same, the VTd tables will be unnecessarily flushed. old_entry is left untouched in the second case, since having a present old_entry will cause the an unnecessary check to be taken at

Hello, I have been working sometime now on getting a HVM accepting a PCI card from the host. As was said in the VT-D wiki I bought an ASUS P5E VM DO motherboard (rel 0803) which has the VT-D option in the bios. I want to pass a Hauppauge PVR 500 card to a virtual machine running LinuxMCE. After first trying XEN 3.2.1 which did not enable the "VT-D virtualisation" bit in xm dmesg, i

Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as

Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as

Commit-ID: 623b03fb63f0c0473b378cf61c77258fd450b5a1 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=623b03fb63f0c0473b378cf61c77258fd450b5a1 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Fri, 28 Aug 2020 19:59:28 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 28 Aug 2020 20:22:50 +0100 [klibc] ia64: sigaction: Make

Commit-ID: 69fb0c9b936dd59a7f7c9fab40f9206b80837b5b Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=69fb0c9b936dd59a7f7c9fab40f9206b80837b5b Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Fri, 28 Aug 2020 19:59:28 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 29 Aug 2020 17:23:08 +0100 [klibc] ia64: sigaction: Make

Commit 8418552 ("[klibc] ia64: Fix shared build") missed this use of the GP register, although the code appears to have been dubious anyway, assuming the address of errno was the first thing pointed to by GP. --- usr/klibc/arch/ia64/vfork.S | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/usr/klibc/arch/ia64/vfork.S b/usr/klibc/arch/ia64/vfork.S index

Commit 8418552 ("[klibc] ia64: Fix shared build") switched to the function descriptor-less ABI. However, when passing a function pointer to the kernel for signal handling, it always expects a descriptor, and -mno-pic does not set any ELF flags that the kernel could detect. Thus to fix this regression we must construct descriptors solely for passing to/from the kernel. Despite this,

I''ve a problem with managing power consumption on Intel Nehalem CPU. I''ve installed Xen 3.4 on our Dell PowerEdge T610 system on a Ubuntu 9.04 distribution. I recompiled the kernel 2.6.30rc5. Now I can see the c-states of the CPUs but no access to P-states information and the frequency scaling does not work. By the way, if I run the kernel 2.6.28.13 which is the last one

I obtain this error when booting (xen/stable-2.6.31.x|xen/master) on Xen 3.4.2 x86_64 xen_major : 3 xen_minor : 4 xen_extra : .2 I had no errors with the same kernel, version of the day 2010-03-03 To compile the kernel i use this configuration " http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.31.6-pvops-dom0-xen-master-x86_64 "

Commit-ID: ae17951ae73ec52348c77259269637b854f0c236 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=ae17951ae73ec52348c77259269637b854f0c236 Author: Jessica Clarke <jrtc27 at jrtc27.com> AuthorDate: Fri, 28 Aug 2020 19:48:32 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 29 Aug 2020 17:23:08 +0100 [klibc] ia64: Fix sigaction

Commit-ID: 454901a0c733986bee36da111a08fe7df0ff0b98 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=454901a0c733986bee36da111a08fe7df0ff0b98 Author: Jessica Clarke <jrtc27 at jrtc27.com> AuthorDate: Fri, 28 Aug 2020 19:48:32 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 28 Aug 2020 20:22:50 +0100 [klibc] ia64: Fix sigaction struct

This patch series restores the use of superpages when restoring or migrating a VM, while retaining efficient batching of 4k pages when superpages are not appropriate or available. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This version doesn't crash or cause hung processes or stuck mountpoints, so that's an improvement. Rich.

This patch is just for review. It enables FUSE support in the API via two new calls, 'guestfs_mount_local' and 'guestfs_umount_local'. FUSE turns out to be very easy to deadlock (necessitating that the machine be rebooted). Running the test from the third patch is usually an effective way to demonstrate this. However I have not yet managed to produce a simple reproducer that

This changes the proposed API slightly. Previously 'mount-local' generating a 'mounted' event when the filesystem was ready, and from the 'mounted' event you had to effectively do a fork. Now, 'mount-local' just initializes the mountpoint and you have to call 'mount-local-run' to enter the FUSE main loop. Between these calls you can do a fork or whatever

I do not seem to be able to get any where with the power management functions. I have had a look at the xenpm Wiki page, but it hasn''t helped. Its probably something completely obvious, but I can''t see it. I running Xen 3.4.0 on Centos 5.3 x86_64 using the gitco RPMs on an Intel S5000PSL motherboard with 2 x Xeon 5410s. Dom0 is running the latest Centos 5.3 kernel. My xm

I am trying to get a pv_ops dom0 working for testing, but I am running into an elf_init error: (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_init: not an ELF binary Full output attached. >From what I have read on the mailing lists, it seems that it is usually a problem with either grub or a corrupt dom0 kernel. Attached is my kernel config (2.6.28-rc6-tip). I followed the instructions on:

Hi Team, For a XenServer (5.6 sp2) crash I have got following in the crash logs. Can somebody tell me why I can see(grant_table.c:1408:d0 dest domain 40 dying) this and how I can resolve it, if it is an issue. (XEN) *** Serial input -> Xen (type ''CTRL-a'' three times to switch input to DOM0) (XEN) Freed 128kB init memory. (XEN) __csched_vcpu_acct_start: setting dom 0

Hi all, I have searched the net and haven''t found a good answer so I hope perhaps someone here can help. I have an IBM x3850 (8863) that I am upgrading from SLES11SP1 to SLES11SP2, and at the same time XEN is being upgraded as part of the distro. The server is used as a Xen host for up to 6 guests. Anyway, the server boots fine with the SLES11SP2 default kernel, and the trace