Displaying 20 results from an estimated 1100 matches similar to: "[PATCH] vtd: fix compilation error on ia64 for 19185:1eb6afcad849."
2011 Jul 17
0
[xen-unstable test] 8091: regressions - FAIL
flight 8091 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/8091/
Regressions :-(
Tests which did not succeed and are blocking:
test-amd64-i386-rhel6hvm-intel 12 guest-localmigrate/x10 fail REGR. vs. 8071
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
test-amd64-amd64-xl-pcipt-intel 9
2011 Feb 19
0
[xen-4.0-testing test] 5856: regressions - FAIL
flight 5856 xen-4.0-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/5856/
Regressions :-(
Tests which did not succeed and are blocking:
test-amd64-xcpkern-i386-rhel6hvm-amd 5 xen-boot fail REGR. vs. 5691
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
test-amd64-amd64-win 16
2011 Jul 17
0
[xen-4.1-testing test] 8111: regressions - FAIL
flight 8111 xen-4.1-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/8111/
Regressions :-(
Tests which did not succeed and are blocking:
test-amd64-i386-rhel6hvm-amd 12 guest-localmigrate/x10 fail in 8104 REGR. vs. 8020
Tests which are failing intermittently (not blocking):
test-amd64-i386-rhel6hvm-amd 11 guest-localmigrate.2 fail pass in 8104
2012 Mar 24
0
[xen-4.0-testing test] 12413: regressions - FAIL
flight 12413 xen-4.0-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/12413/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 4 xen-build fail REGR. vs. 12202
build-amd64-pvops 4 kernel-build fail REGR. vs. 12202
build-amd64-oldkern 4
2006 Sep 05
1
[PATCH] xenmon: --ms_per_sample: check a negative value
Hi,
This patch adds the argument check of "--ms_per_sample=" option. For
"--ms_per_sample=", a negative value should be invalid.
e.g.
% xenmon.py -n --ms_per_sample=-1
usage: xenmon.py [options]
xenmon.py: error: option --ms_per_sample: invalid negative value: ''-1''
Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com>
--
KUWAMURA
2006 Jul 04
4
[PATCH] xenmon: remove magic number "31" (the idle domain)
Hi,
This patch removes the magic number "31" for readability. The number
"31" means the idle domain ID.
In detail:
- display the idle domain ID with "Idle" instead of "31"
- write to the file "log-idle.log" instead of "log-dom31.log".
Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com>
Thanks,
--
KUWAMURA
2008 Jun 30
1
[PATCH] tools/python: fix TypeError for 17903:0728459b3c8d
Hi,
If `hda'' is used in a domain config file and domain-0 has /dev/hda,
creating the domain failed by TypeError:
File "//usr/lib/python/xen/xend/server/blkif.py", line 84, in
getDeviceDetails
(device_path, devid) = blkif.blkdev_name_to_number(dev)
TypeError: unpack non-sequence
Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com>
--
KUWAMURA
2008 Nov 18
6
[PATCH] fix memory allocation from NUMA node for VT-d.
The memory relating guest domain should be allocated from NUMA node on
which the guest runs.
Because the latency of the same NUMA node is faster than that of a
different one.
This patch fixes memory allocation for Address Translation Structure
of VT-d.
VT-d uses two types of Structures for DMA address translation.
The one is Device Assignment Structure.
The other is Address Translation
2010 Jan 08
0
[PATCH] Sync Xen sysctl header for 20762:a1d0a575b4ba
Hi,
This patch fixes the following error:
File "usr/lib/python2.4/site-packages/xen/xend/XendNode.py", line 974, in xenschedinfo
sched_id = self.xc.sched_id_get()
Error: (13, ''Permission denied'')
Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com>
--
KUWAMURA Shin''ya
_______________________________________________
Xen-devel mailing
2010 Jan 21
0
[PATCH] xentrace: XC_PAGE_SIZE should be used
Hi,
20827:fad80160c001 cannot be compiled on ia64:
xentrace.c:647: error: ''PAGE_SIZE'' undeclared (first use in this function)
This patch fixes it.
Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com>
Best regards,
--
KUWAMURA Shin''ya
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
2008 Oct 08
0
[PATCH] [IOEMU] [IA64] Fix memory size calculation on VT-i over 3GB memory
Hi,
VT-i domains have two memory holes: VGA I/O (under 1MB) and MMIO
(3GB-4GB). This patch calculates the correct memory size with them.
# This is based on xen-unstable 10936:a0b3cf802d99.
Original patch by Zhang xiantao <xiantao.zhang@intel.com>
Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com>
Best regards,
--
KUWAMURA Shin''ya
2007 Apr 11
3
[PATCH][RFC] Support GPT (GUID Partition Table)
Hi,
I made a patch for GPT support.
As you see, this patch uses ad-hoc approach.
If you give me an advice, it would be appreciated
Signed-off-by: Shinya Kuwamura <kuwa@jp.fujitsu.com>
Signed-off-by: Tomohiro Takahashi <takatom@jp.fujitsu.com>
Thanks,
Tomohiro Takahashi.
diff -r 1bde28f762a6 -r 8e08fd1ffa24 tools/pygrub/src/pygrub
--- a/tools/pygrub/src/pygrub Mon Apr 09 13:40:25
2008 Mar 07
0
VTD-XML 2.3 released
Version 2.3 of VTD-XML (http://vtd-xml.sf.net), the next generation
document-centric XML processing model, is now released. To download
the latest version please visit
http://sourceforge.net/project/showfiles.php?group_id=110612&package_....
Below is a list of new features and enhancements in this version.
* VTDException is now introduced as the root class for all other VTD-
XML''s
2008 Dec 10
2
VTd not showing PCI device in VM
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
2007 Sep 30
6
[VTD][PATCH] a time out mechanism for the shared interrupt issue for vtd
Attached is a patch for shared interrupt between dom0 and HVM domain for
vtd.
Most of problem is caused by that we should inject interrupt to both
domains and the
physical interrupt deassertion then may be delayed by the device
assigned to the HVM.
The patch adds a timer, and the time out value is sufficient large to
tolerant
the delaying used to wait for the physical interrupt deassertion.
2008 Dec 12
0
[Xen-ia64-devel] [IA64] Weekly benchmark results [ww49]
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
All test cases passed.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.18.8-xen
Changeset : 18872:3acca92b9597 (ia64/xen-unstable)
753:17adc5c344fe (ia64/linux-2.6.18-xen)
131:9210bd27a551 (efi-vfirmware)
b4d410a
2008 Oct 03
0
[IA64] Weekly benchmark results [ww39]
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
All test cases passed.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.18.8-xen
Changeset : 18503:325904748847 (ia64/xen-unstable)
673:3161879fdf22 (ia64/linux-2.6.18-xen)
126:d255b2cfdd5a (efi-vfirmware)
0f3d638
2008 Oct 25
2
VTd - PCI Passthrough - VMError: fail to assign device
Dear Users,
Debian Etch 2.6.18.8-xen from xensource.com with Xen 3.3.0 on AMD64:
After i want to start the HVM i get:
VmError: fail to assign device(1:0.0): maybe it has already been
assigned to other domain, or maybe it doesn''t exist.
[2008-10-25 19:59:30 2460] DEBUG (__init__:1072)
XendDomainInfo.destroy: domid=5
[2008-10-25 19:59:30 2460] DEBUG (__init__:1072)
2014 Feb 20
0
Request for help with pci passthrough with VTd on Debian Jessie
Hi,
I am having great difficulties in getting pci passthrough with VTd to
work, surely I am doing something stupid but I cannot see what.
"tangram" (https://www.blogger.com/profile/06588030231546523539) has
been a huge help, but despite his efforts I am still stuck.
Hardware: Intel S3200SHV motherboard
BIOS : S3200X38.86B.00.00.0052
CPU : Intel Core 2
2013 Jan 15
14
[PATCH] VTD/Intremap: Disable Intremap on Chipset 5500/5520/X58 due to errata
http://www.intel.com/content/www/us/en/chipsets/5520-and-5500-chipset-ioh-specification-update.html
Stepping B-3 has two errata (#47 and #53) related to Interrupt
remapping, to which the workaround is for the BIOS to completely disable
interrupt remapping. These errata are fixed in stepping C-2.
Unfortunately this chipset is very common and many BIOSes are not
disabling remapping. We can