On Tue, Dec 02, Ian Campbell wrote:
On Tue, 2014-12-02 at 16:17 +0100, Olaf Hering wrote:
On Tue, Dec 02, Ian Campbell wrote:
On Mon, 2014-12-01 at 23:41 +, Mark Pryor wrote:
list,
Thanks. If you've identified a buggy changeset then it is fine to post
to the devel lists
I tried to attach a PCI device (IGB Virtual Function) to a HVM guest.
To actually get it assigned its required to run
pci-attach/pci-detach/pci-attach because it does not show up right away.
Did anyone noticed this bug already, is there a fix? There is no error
reported in dom0 dmesg, xl dmesg
On Mon, Dec 01, Olaf Hering wrote:
# xl pci-assignable-add 01:10.0
# xl pci-assignable-list
:01:10.0
# xl create -f domU.cfg
# xl console domU
## lspci gives just emulated PCI devices
ttyS0:Rescue:~ # lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02
On Mon, Dec 01, Ian Campbell wrote:
On Mon, 2014-12-01 at 15:34 +0100, Olaf Hering wrote:
On Mon, Dec 01, Sander Eikelenboom wrote:
Hmm the wiki also still mentions it:
http://wiki.xen.org/wiki/Xen_PCI_Passthrough
It was the ability with xend + qemu-trad to be able to specify
Xen does a shutdown of the emulated PCI network device in
pci_unplug_nics. But this just disables the PCI device. The tap device
for a given emulated card remains active because nothing closes the
file descriptor.
The cmdline for qemu contains something like -device
On Tue, Nov 25, Andrew Cooper wrote:
The purpose of this email is to plan how to progress the migrationv2
series through to being merged. I believe I have CC'd everyone with a
specific interest in this area, but apologies if I have missed anyone.
While you mow that lawn, did you guys think
On Wed, Nov 26, Andrew Cooper wrote:
It is certainly my hope going forward that different knobs can be
exposed. One thing I think would be interesting is some proper
calculations of the delta in the dirty set, and offering a threshold
which chooses between pause and complete or abort the
On Tue, Nov 25, Konrad Rzeszutek Wilk wrote:
On Tue, Nov 25, 2014 at 05:04:09PM +0100, Olaf Hering wrote:
+Using additional CFLAGS to build tools running in dom0 is required when
Why the mention of 'buld tools running in dom0'? It sounds like it is
required to use dom0 to build tools?
Does
The already documented configure patch was not applied.
Adjust documentation to describe existing behaviour.
Signed-off-by: Olaf Hering o...@aepfle.de
---
INSTALL | 19 +--
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/INSTALL b/INSTALL
index 6bb9d23..656c90a
and XEN_BUILD_HOST
which the build environment can set to fixed strings to get a
reproducible build.
Signed-off-by: Olaf Hering o...@aepfle.de
Cc: Ian Campbell ian.campb...@citrix.com
Cc: Ian Jackson ian.jack...@eu.citrix.com
Cc: Jan Beulich jbeul...@suse.com
Cc: Keir Fraser k...@xen.org
Cc: Tim Deegan t
and
XEN_BUILD_HOST to specify fixed strings during build.
Signed-off-by: Olaf Hering o...@aepfle.de
Cc: Ian Campbell ian.campb...@citrix.com
Cc: Ian Jackson ian.jack...@eu.citrix.com
Cc: Jan Beulich jbeul...@suse.com
Cc: Keir Fraser k...@xen.org
Cc: Tim Deegan t...@xen.org
---
xen/Makefile | 9
On Tue, Nov 18, Ian Jackson wrote:
How about
It should be possible to repeatedly build identical sources
and get identical binaries, even on different hosts at different
build times. This fails [etc. etc. ...]
Provide variables XEN_BUILD_DATE, XEN_BUILD_TIME and
801 - 812 of 812 matches
Mail list logo
