similar to: [PV-onHVM][Xen][PATCH 2/3] Fix kthread_create

NOTE: An applicable subset of this patch was also submitted to upstream qemu. SUMMARY: This patch fixes several bugs in serial.c (1) A typo in serial_save() where qemu_get_8s is called (should be qemu_put_8s) (2) No support provided in serial_load() for version_id == 1 (should unmarshal a 1 byte s->divider and should provide a default value for s->fcr (3) Call serial_ioport_write() to

Migrate the last TSC values for more accurate timekeeping during live migration Signed-off-by: Dave Winchell <dwinchell@virtualiron.com> Signed-off-by: Ben Guthro <bguthro@virtualiron.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

For about the past week (perhaps a bit longer) I have been unable to use an automated script to build xen-unstable on a 32 bit machine. The build continues to ask about the following build parameter: I2O_EXT_ADAPTEC_DMA64 Choosing the default (Y) allows the build to continue to completion. After a little research, it looks like this parameter was pulled out of linux-defconfig_xen_x86_32 in

Change unsigned to unsigned long for spinlock flags. This avoids x86_64 assembly error in some distros (SLES10) Signed-off-by: Ben Guthro <bguthro@virtualiron.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

[PATCH 4/4] Add libvdisk, and vdisk_tool vdisk-support.patch provides libvdisk, and vdisk_tool, as described in [PATCH 0/4] Signed-off-by: Boris Ostrovsky <bostrovsky@virtualiron.com> Signed-off-by: Ben Guthro <bguthro@virtualiron.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

[PATCH 3/4] (Refactored) Add error checking in blktapctrl blktap-fixes.patch Add some additional error checking to blktapctrl during mkfifo Signed-off-by: Boris Ostrovsky <bostrovsky@virtualiron.com> Signed-off-by: Ben Guthro <bguthro@virtualiron.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

This implements a suggestion by Keir to remove the xenbus "ignore state transitions on shutdown" code for kernels without a shutdown callback. Signed-off-by: David Lively <dlively@virtualiron.com> Signed-off-by: Ben Guthro <bguthro@virtualrion.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Intercept guest reads of MSR_IA32_MCG_CAP and limit the number of memory banks reported to one. This prevents us from trying to read status of non-existent banks when migrated to a machine with fewer banks. Signed-off-by: Ben Guthro Signed-off-by: David Lively <dlively@virtualiron.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

After a hiatus, I have made another attempt at getting the XCI code-base up-and-running, but have run into some issues that I am hoping someone can help me with. 1. I am finding that a large hurdle in getting this building is chasing down build dependencies, of which there are many. Since the wiki recommends that this be built on a 32bit Debian lenny system - does anyone have a list of necessary

This patch provides a simple way to break out of a tight loop and bug: from the hypervisor monitor press ctrl-A, ctrl-A, ctrl-Z Signed-off-by: Robert S. Phillips (rphillips@virtualiron.com) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

The code, below, in rdmsr_hypervisor_regs (in xen/arch/x86/traps.c) looks wrong. (The same code is in wrmsr_hypervisor_regs.) int rdmsr_hypervisor_regs( uint32_t idx, uint32_t *eax, uint32_t *edx) { idx -= 0x40000000; if ( idx > 0 ) return 0; ... The intent, apparently, is that the function should return zero if the original idx exceeds 0x40000000. However because idx is

Keir, I noticed that a Shadow patch went into the 3.1.1 staging tree today. Does this mean that we should expect a 4th release candidate before the 3.1.1 release tag is official? If so - how much testing time are you going to give that release candidate before deciding whether a release tag, or another RC round is appropriate? Ben Guthro _______________________________________________

Hi, Robert, I found out another confusing code snippet: in void xi_invl_mfn(struct domain *d, unsigned long mfn) if (ext && pfn < ext->large_page_aligned_size) According to the code, it should be if (ext && (pfn>>SPT_ENTRIES_ORDER) < ext->large_page_aligned_size) If I made any mistake, please point it out.

Most likely, yes. They should have a copy of the license agreement, and you can take a look at that and see what they have to say about using them apart from the VirtualIron product. The only open source PV drivers are the ones that James has released - search the list for "GPL PV drivers" and that should turn up some threads related to those. The drivers are still very much in the

Hello Han, I am pleased you approve of the design and implementation of the XI shadow mechanism. And I appreciate the time and care you''ve taken in reviewing this substantial body of new code. You asked about performance statistics. With the current XI patch, we are seeing the following: - page faults times for XI are about 4 times faster than non-XI: 10.56 (non-XI) vs 2.43

Before I get to entrenched in the ACPI code - I thought I''d ping the community to make sure nobody else has investigated this already - Can we present cores vs sockets for guest VCPUs? Right now, the number of total processors can be specified, but can we specify cores per socket? I see this potentially being an hvmloader function, as part of its acpi build code. Could this be

Hi, When dom0 is under heavy load any Vista or Windows 2008 HVM''s that are running and have multiple cpu''s assigned often BSOD with code 0x00000101 "A clock interrupt was not recevied ona secondary processor within the allocated time interval" It only happens if the load in dom0 is high enough to make the mouse pointer lagged, once the mouse fails to track in

Hi, When dom0 is under heavy load any Vista or Windows 2008 HVM''s that are running and have multiple cpu''s assigned often BSOD with code 0x00000101 "A clock interrupt was not recevied ona secondary processor within the allocated time interval" It only happens if the load in dom0 is high enough to make the mouse pointer lagged, once the mouse fails to track in

Hi Guys, Thanks for the interest in the xen hypervisor debugger, prev known as kdb. Btw. I''m gonna rename it to xdb for xen-debugger or hdb for hypervisor debugger. KDB is confusing people with linux kdb debugger and I often get emails where people think they need to apply linux kdb patch also... Anyways, attaching patch that is cleaned up of my debug code that I accidentally left in

The existing xc_domain_dumpcore is very specific to disk/file based output. Refactor the code slightly to allow more user-specified control. This is done by adding a parallel xc_domain_dumpcore2 (naming isn''t always my strong suit), which allows the specification of a callback routine and an opaque argument block. The existing dumpcore routine is modified to use the callback for all