similar to: [PATCH] generate notification of new console ring data

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

Ben- I like the idea but I don''t understand how this patch can work: 1) You never put a name into `serial_devices[]'' for the summa port. The loop in `main'' that initializes the serial devices only calls `qemu_chr_open'' if there''s a string name in `serial_devices''. How did you get this to work? 2) Minor point, I don''t see the need

A post last week contained the design document for a shadow page table mechanism. This post contains more information, and a pointer to the code. As a recap, the "XI Shadow Mechanism" is a design for shadow page table code for fully virtualized HVM domains running on a 64-bit Xen hypervisor. This work was undertaken to address a number of goals. These are enumerated in the document

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

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

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.

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

This patch adds a parallel set of APIs to the domain builders to allow images and ramdisks to be passed via buffer, rather than via file. This allows usage of the underlying domain building routines in "file-challenged" enviroments. Specifically, xc_linux_build_mem is the buffer oriented version of the file-oriented xc_linux_build. Likewise, xc_hvm_build_mem is the buffer oriented

I have installed samba 2.0.0 on our AIX 4.1 machine. It appears to be working fine in domain security mode. Except for one thing: No matter what the read permissions in Unix are, ANY user can read EVERY file in a share. Write permission is working properly. What the heck is going on here? I have the Unix permssions set to a-rwx (000) and it STILL lets everyone read all the files in the

# This is a BitKeeper generated diff -Nru style patch. # # ChangeSet # 2005/05/01 17:01:17-07:00 kmacy@curly.lab.netapp.com # add SMP support to evtchn # Signed-off-by: Kip Macy <kmacy@netapp.com> # # freebsd-5.3-xen-sparse/i386-xen/include/xen_intr.h # 2005/05/01 17:01:15-07:00 kmacy@curly.lab.netapp.com +3 -0 # add SMP interfaces # #

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

Greetings. I''ve been asked to work on a PXE solution for booting Xen domU''s from a network, and would like some feedback and any help anyone is willing to provide. I''ve been limiting my work to HVM domU''s at the moment, because I don''t think the NBI''s (as far as I know, these are bootloaders) that I have available work in paravirtualized

We need to write the irq number to GICC_DIR on the physical cpu that previously received the interrupt, but currently we are doing it on the pcpu that received the maintenance interrupt. As a consequence if a vcpu is migrated to a different pcpu, the irq is going to be EOI''ed on the wrong pcpu. This covers the case where dom0 vcpu0 is running on pcpu1 for example (you can test this

We need to write the irq number to GICC_DIR on the physical cpu that previously received the interrupt, but currently we are doing it on the pcpu that received the maintenance interrupt. As a consequence if a vcpu is migrated to a different pcpu, the irq is going to be EOI''ed on the wrong pcpu. This covers the case where dom0 vcpu0 is running on pcpu1 for example (you can test this

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

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

First, Thank you all for this forum, as I am fairly new at both Ubuntu and Samba I have found most the answers to my issues here. Now correct me if I am wrong but Samba 4.3.2 should be able to support Domain Trusts. If so maybe you can help me, here is what I have: NT4 Domain: adc.com (Holds are production servers and user accounts for that domain) Controller = enterprise.abc.com Samba

On Fri, 13 Jan 2017 17:22:15 -0500 Bob Thomas <bthomas at cybernetics.com> wrote: > > > On 1/13/2017 4:58 PM, Rowland Penny via samba wrote: > > On Fri, 13 Jan 2017 16:43:39 -0500 > > Bob Thomas via samba <samba at lists.samba.org> wrote: > > > >> On 1/13/2017 3:30 PM, Rowland Penny wrote: > >> > >>> On Fri, 13 Jan 2017

Good Morning, Ive been trying to test Samba AD on Ubuntu 18.04 using samba version 4.8.0  The DC seems to be working fine all tests have passed.  I was able to connect Win7 RSAT, a Ubuntu workstation and a File server.  My problem is the file server will not give response to 'sudo getent passwd' with or with out username or DOMAIN\username. Everything else works as far as I can tell.

mk_pirq_info(), gsi_from_irq() and vector_from_irq() are static functions and no one is calling them. This fixed following compilation warnings : drivers/xen/events.c:134: warning: ?mk_pirq_info? defined but not used drivers/xen/events.c:180: warning: ?gsi_from_irq? defined but not used drivers/xen/events.c:190: warning: ?vector_from_irq? defined but not used Signed-off-by: Jaswinder