search for: exception_handling

Hi, have permanent failure when try to create VDI on local SR type=file or type=ext. On both types it failed with the same error: SR_BACKEND_FAILURE_78 VDI Creation failed [opterr=error 127] I am on Debian box with kernel 3.3.0-rc7, Xen version 4.1.2 (Debian 4.1.2-2.1), Xen-API Version: 1.3.2-4 (Kronos) Is it a bug, or am I missing something? Anybody managed to workaround this problem? Here is

The log snippet doesn''t have the detail in it - have a look in /var/log/SMlog - you might find something more useful in there. Jon On 5 Apr 2012, at 10:23, Dimitar Kazakov wrote: > Hi, > have permanent failure when try to create VDI on local SR type=file or > type=ext. On both types it failed with the same error: > SR_BACKEND_FAILURE_78 > VDI Creation failed

On Thu, Mar 19, 2020 at 10:13:15AM +0100, Joerg Roedel wrote: > diff --git a/arch/x86/boot/compressed/idt_handlers_64.S b/arch/x86/boot/compressed/idt_handlers_64.S > index bfb3fc5aa144..67ddafab2943 100644 > --- a/arch/x86/boot/compressed/idt_handlers_64.S > +++ b/arch/x86/boot/compressed/idt_handlers_64.S > @@ -75,3 +75,7 @@ SYM_FUNC_END(\name) > .code64 > >

Hi John, I'll read your email with greater care along the week, but I have added a page on the wiki to help us organise our thoughts. http://wiki.llvm.org/Exception_Handling I'll change it as I go reading your email, but for now, I've separated into each of the requirements you said. New ones could be added, existing ones merged, but the most important is to add more complete rationale to each, so every one agrees on the same thing when reading them. I think...

Hi all, today i tried to enable HA on xcp 1.6 but when i enable it through xencenter I received the following error in xensource.log: Dec 5 17:56:26 xcp1 xapi: [ info|xcp1|490661|Async.pool.enable_ha R:9119ce88ffcb|xapi_ha] Using statefile: /etc/xensource/static-vdis/0/disk Dec 5 17:56:26 xcp1 xapi: [debug|xcp1|490661|Async.pool.enable_ha R:9119ce88ffcb|xapi_ha]

From: Joerg Roedel <jroedel at suse.de> Install an exception handler for #VC exception that uses a GHCB. Also add the infrastructure for handling different exit-codes by decoding the instruction that caused the exception and error handling. Signed-off-by: Joerg Roedel <jroedel at suse.de> --- arch/x86/Kconfig | 1 + arch/x86/boot/compressed/Makefile

Thanks! I found the problem in SMlog. /usr/sbin/td-util create vhd 1024 /var/run/sr-mount/4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2/247b64e4-6b7f-4b2f-bd73-50e848c78d71.vhd /usr/sbin/td-util: error while loading shared libraries: libxenctrl.so.4.0: cannot open shared object file: No such file or directory td-util from blktap-utils 2.0.90-3 (testing) is looking for libxenctrl.so.4.0, but the package

From: Joerg Roedel <jroedel at suse.de> Install an exception handler for #VC exception that uses a GHCB. Also add the infrastructure for handling different exit-codes by decoding the instruction that caused the exception and error handling. Signed-off-by: Joerg Roedel <jroedel at suse.de> --- arch/x86/Kconfig | 1 + arch/x86/boot/compressed/idt_64.c

Hi there, I am trying to set up XCP on Ubuntu 12.04. I went through the procedure given in the README file of the xcp-xapi package and reached the point where the hypervisor seems to be running fine. I set up a VM using the Debian Squeeze (64bit) template and started it, giving a Debian mirror URL as install-repository. Running "xe vm-list" reports that the machine is running, but when

From: Joerg Roedel <jroedel at suse.de> Add the first handler for #VC exceptions. At stage 1 there is no GHCB yet becaue we might still be on the EFI page table and thus can't map memory unencrypted. The stage 1 handler is limited to the MSR based protocol to talk to the hypervisor and can only support CPUID exit-codes, but that is enough to get to stage 2. Signed-off-by: Joerg Roedel

From: Joerg Roedel <jroedel at suse.de> Add the first handler for #VC exceptions. At stage 1 there is no GHCB yet becaue we might still be on the EFI page table and thus can't map memory unencrypted. The stage 1 handler is limited to the MSR based protocol to talk to the hypervisor and can only support CPUID exit-codes, but that is enough to get to stage 2. Signed-off-by: Joerg Roedel

From: Joerg Roedel <jroedel at suse.de> Add the first handler for #VC exceptions. At stage 1 there is no GHCB yet becaue the kernel might still be running on the EFI page table. The stage 1 handler is limited to the MSR based protocol to talk to the hypervisor and can only support CPUID exit-codes, but that is enough to get to stage 2. Signed-off-by: Joerg Roedel <jroedel at

On Tue, Feb 11, 2020 at 5:53 AM Joerg Roedel <joro at 8bytes.org> wrote: > > From: Joerg Roedel <jroedel at suse.de> > > Add the first handler for #VC exceptions. At stage 1 there is no GHCB > yet becaue we might still be on the EFI page table and thus can't map > memory unencrypted. > > The stage 1 handler is limited to the MSR based protocol to talk to

On Tue, Feb 11, 2020 at 5:53 AM Joerg Roedel <joro at 8bytes.org> wrote: > > From: Joerg Roedel <jroedel at suse.de> > > Add the first handler for #VC exceptions. At stage 1 there is no GHCB > yet becaue we might still be on the EFI page table and thus can't map > memory unencrypted. > > The stage 1 handler is limited to the MSR based protocol to talk to

Hi, In my project I need to customize the output of translate/t method when there is no translation found. I''ve follow the rails guide about I18n API section 6.2 and made a custom exception handler in an initializer file. module I18n def custom_handler(exception, key, locale, options) case exception when I18n::MissingTranslationData I18n.normalize_keys(locale, key,

...r R which a neophyte can follow? Ostensibly, seh provides better performance[1], [2], and if a 4.9.2 toolchain is being developed, it may be worth considering using seh. Thank you, Avi [1] <http://sourceforge.net/p/mingw-w64/mailman/message/30532139/> [2] <http://wiki.qt.io/MinGW-64-bit#Exception_handling:_SJLJ.2C_DWARF.2C_and_SEH>

From: Joerg Roedel <jroedel at suse.de> Install a page-fault handler to add an identity mapping to addresses not yet mapped. Also do some checking whether the error code is sane. This makes non SEV-ES machines use the exception handling infrastructure in the pre-decompressions boot code too, making it less likely to break in the future. Signed-off-by: Joerg Roedel <jroedel at

On Thu, Mar 19, 2020 at 10:13:11AM +0100, Joerg Roedel wrote: > From: Joerg Roedel <jroedel at suse.de> > > Install a page-fault handler to add an identity mapping to addresses > not yet mapped. Also do some checking whether the error code is sane. > > This makes non SEV-ES machines use the exception handling > infrastructure in the pre-decompressions boot code too,

On Apr 13, 2011, at 2:06 AM, Renato Golin wrote: > I'll read your email with greater care along the week, but I have > added a page on the wiki to help us organise our thoughts. > > http://wiki.llvm.org/Exception_Handling If you want to volunteer to keep track of the discussion on the wiki, I think that would be great. I don't think we're going to hold the discussion on the wiki, though. Also, what you've listed as "Areas to Consider" are explicitly things I *don't* want to consider imme...

Since it looks like we're going to start discussing changing the EH representation again, I think it would be a very good idea to first review the core requirements we have of the exceptions IR. Mostly, here, I'm taking the major exceptions implementations I have direct knowledge of --- zero-cost DWARF-based libUnwind with the default GCC personalities, builtin_sjlj-based libUnwind with