Hi,
I after a month I updated to the current cset (12018:11b718eb22c9) for porting
the mini-os and xen did a panic.
I tracked the problem down to:
- I did not initializing SHARED_INFO_VA (see early_xen_setup() for linux)
- the next access to the shared info area leads to a
alternate data tlb
Hi Alex,
I also met the GPT issue, if I didn't use the GPT partitioned disk image file.
But I can do installation successfully in VTI with ioemu(Qemu) disk. And
installing again, the GPT issue is gone.
But I did not understand how to install VTI Linux in a VBD disk. I just have
the
Hi Zhang,
We were looking forward to your patches.
We have a question and a comment.
Question:
How can we inject the INIT interrupt into domVTi?
We made xm os-init command, and tested your patch.
But INIT handler of domVTi was not executed, we think.
We attach two files.
-
I still have a question:
How windows OS_INIT handler do? How can I confirm whether PAL_INIT executed
successful in windows? ( in Linux , I can see a lot of dump info on screen)
Good good study,day day up ! ^_^
-Wing(zhang xin)
OTC,Intel Corporation
-Original Message-
From: Masaki
From: Jan Beulich
Sent: 2006年11月6日 21:17
What is the purpose of this member? Neither does it seem to get set
(e.g.
xc_get_pfn_list), nor does it seem to get read.
Thanks, Jan
Xen/ia64 is the only user on this member, with some historical
requirement to query a specific frame list starting
1 / 2
# HG changeset patch
# User [EMAIL PROTECTED]
# Date 1162819834 -32400
# Node ID 3eef92a12f219d048a45a54014d67bab0652734f
# Parent 11b718eb22c996868bed5b18dcc08081ad27d0be
preliminary clean up ia64 mm.c for blktap dom0 mount support.
PATCHNAME: clean_up_for_blktap_dom0_mount
2 / 2
# HG changeset patch
# User [EMAIL PROTECTED]
# Date 1162819837 -32400
# Node ID 2ea5b636612322b6659ecc3481cdbf17e0eb0559
# Parent 3eef92a12f219d048a45a54014d67bab0652734f
Support Xen/IA64 self-grant-table-page-mapping.
Before the changeset 10677:2937703f0ed0 of xen-unstable.hg,
it is
Hi Keir,
Is something keeping Isaku's blktap/ia64 patches from xen-unstable?
We need these in RHEL5 but I'd like to see them merged into
xen-unstable before patching the distro.
Thanks,
Aron
___
Xen-ia64-devel mailing list
On 6/11/06 9:21 pm, Aron Griffis [EMAIL PROTECTED] wrote:
Is something keeping Isaku's blktap/ia64 patches from xen-unstable?
I'm not really blktap maintainer. Andy or Julian should probably look at the
patches.
-- Keir
___
Xen-ia64-devel mailing
On Mon, Nov 06, 2006 at 03:15:22PM +0900, [EMAIL PROTECTED] wrote:
However during shadow_teardown_xxx() in your patch
other domain might access the p2m table and struct page_info.
Page reference convension must be kept right during them.
Yes, it might access them. In past, I thought
Thank you for your suggestion.
We'll study it.
Thanks,
- Tsunehisa Doi
You (yamahata) said:
However during shadow_teardown_xxx() in your patch
other domain might access the p2m table and struct page_info.
Page reference convension must be kept right during them.
Yes, it might
Hi all,
This patch fixes the vmx fault handler to set the fault vector number
in r19. The r19 is used to display a fault message in
dispatch_to_fault_handler().
Signed-off-by: Akio Takebe [EMAIL PROTECTED]
Signed-off-by: Kazuhiro Suzuki [EMAIL PROTECTED]
Thanks,
KAZ
diff -r 11b718eb22c9
Hi, Wing
I'm sorry.
Our patch modify codes of hypervisor and dom0 kernel.
So after installing xen.gz and dom0 kernel, please reboot system with them.
Best Regards,
Akio Takebe
Oh, I forgot restart xend last time.
But this time I get another error info. See attachment
Good good study,day day
13 matches
Mail list logo
