similar to: x86info: dump kvm cpuid's

The following makes 'x86info -r' dump hypervisor leaf cpu ids (for kvm this is signature+features) when running in a vm. On the guest we see the signature and the features: eax in: 0x40000000, eax = 00000000 ebx = 4b4d564b ecx = 564b4d56 edx = 0000004d eax in: 0x40000001, eax = 0100007b ebx = 00000000 ecx = 00000000 edx = 00000000 Hypervisor flag is checked to avoid output changes when

The following makes 'x86info -r' dump hypervisor leaf cpu ids (for kvm this is signature+features) when running in a vm. On the guest we see the signature and the features: eax in: 0x40000000, eax = 00000000 ebx = 4b4d564b ecx = 564b4d56 edx = 0000004d eax in: 0x40000001, eax = 0100007b ebx = 00000000 ecx = 00000000 edx = 00000000 Hypervisor flag is checked to avoid output changes when

Hi Could anybody explain me how to check how many L1/L2 cache my cpu have. I'm using CentOS 5.6 *cat /proc/cpuinfo |grep CPU * model name : Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz model name : Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz Diagram of a generic dual-core processor, with CPU-local level 1 caches, and a shared, on-die level 2 cache.

Based on cmake/modules/LLVMLibDeps.cmake, I produced a graphviz dot file and then manually removed components and edges until the graph was small enough to be presentable. I don't know if I can actually use LLVM due to its humongousness, but I hope the graph will be helpful to others attempting to comprehend LLVM. PNG attached; dot file follows. digraph G { ipo

Hi, I'm trying to build clang under MingW, but I'm getting a number of errors. Could anyone provide some hints as to what you had to do? I got some tips from http://blogs.tedneward.com/2008/02/24/Building+LLVM+On+Windows+Using+MinGW32.aspx, but using the newer packages, as it's a bit old. The ./configure seems to run without errors. The first run of make aborts with errors like:

On Mon, Jan 27, 2014 at 10:27:20AM +0100, Pino Toscano wrote: > On Monday 27 January 2014 11:06:14 Kashyap Chamarthy wrote: > > Running virt-builder in a guest Fedora-20 guest hypervisor w/ Rawhide > > Kernel, throws the below: > > > > $ virt-builder fedora-20 --format qcow2 --size 20G > > virt-builder: symbol lookup error: /lib64/libgnutls.so.28: undefined

Kashyap, just to be sure - it happens to you during the v2v conversion? on L2? While L1 and L0 works fine afterwords, right? Thanks On Fri, Jan 17, 2014 at 4:45 PM, Kashyap Chamarthy <kchamart@redhat.com> wrote: > On 01/17/2014 03:38 PM, Richard W.M. Jones wrote: >> On Fri, Jan 17, 2014 at 04:14:03PM +0200, Rom Freiman wrote: >>> How do you know that the problem is with

On Apr 8, 2013, at 2:55 PM, "Robinson, Paul" <Paul_Robinson at playstation.sony.com> wrote: I keep seeing "this is a layering violation" comments on the lists. > While there are a few llvm.org pages that mention layers in passing, > there is nothing (that I've found) actually specifying the layers. > Trying to infer the layering from the code is tedious and

Thanks Richard for a fast reply. Yes, indeed, im working on a nested environment. I try to run v2v inside a VM (L1) and to create an L2 by the conversion process. And on Intel. As I wrote, it fails once in few times, mainly when there is a memory pressure on L0. Kashyap, can you please share your experience? Why should it crash during nested conversion. I'm not too familiar with libguestfs

Is anyone building dragon-egg on darwin? I am trying to build against the fink gcc45 package that I have prepared for darwin and a updated fink llvm 2.7 package that is built as... ../llvm-2.7/configure --prefix=/sw --prefix=/sw/lib/llvm --mandir=/sw/share/man --infodir=/sw/share/info --with-gmp=/sw --with-libiconv-prefix=/usr --with-system-zlib --with-as=/Developer/usr/bin/as

I keep seeing "this is a layering violation" comments on the lists. While there are a few llvm.org pages that mention layers in passing, there is nothing (that I've found) actually specifying the layers. Trying to infer the layering from the code is tedious and error-prone (or we wouldn't see so many violations in code reviews, eh?). Now, I understand that Google has some sort

Hey everybody, Richard, you were right. I managed to reproduce the same crash without dealing with v2v (and libguestfs). Actually - it's reproducible really ease - I write a big file to /tmp on L0 (till it 100% full) and then run a L2 VM. Almost every time it crushes with double fault. Debugging, debugging and more debugging. Marcelo/Paolo, if you have any clue, I would like to hear from you.

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

Hello all, I've been digging around on this for a few days and I have not come up with a solution. I have a Compaq ProLiant DL580 (G1, the old tan Compaq) with 4 x 700MHz P-III CPUs and 11GB of memory. I've loaded CentOS 5.5 with Virtualization (Xen) + KVM and patched up to current (full KS packages file list at the end). When it boots, Xen only detects a single CPU as shown in the xm

I''m tinkering with some code to be able to talk to the hypervisor from Windows, with the ultimate aim to get a usable xenbus. So far I''ve created a driver for the Xen PCI ''device'', and (hopefully) mapped the hypercall space given by the CPUID call... What is the simplest hypercall I can make to get an answer from the hypervisor to tell me that it''s

Hello (again) all! After successfully joining my Debian Jessie box to my Server 2012R2-based domain as a domain member, I've run into another snag. The installation worked successful for a couple days as a file server, and then after a while I stopped being able to access the file server. After trying various trouble-shooting steps (including nuking the samba and winbind installations and

Hi, Please find below the proposal for the generic use of cpuid space allotted for hypervisors. Apart from this cpuid space another thing worth noting would be that, Intel & AMD reserve the MSRs from 0x40000000 - 0x400000FF for software use. Though the proposal doesn't talk about MSR's right now, we should be aware of these reservations as we may want to extend the way we use CPUID to

Hi, Please find below the proposal for the generic use of cpuid space allotted for hypervisors. Apart from this cpuid space another thing worth noting would be that, Intel & AMD reserve the MSRs from 0x40000000 - 0x400000FF for software use. Though the proposal doesn't talk about MSR's right now, we should be aware of these reservations as we may want to extend the way we use CPUID to

I am trying to a install Centos 5.1 32-bit Xen HVM DomU onto a Centos 5.1 64bit DomU with the default xen installed and the kickstart hangs at random points during the install process. Sometimes retrieving the image, sometimes formatting the filesystem, sometimes installing the packages,etc. I tried upgrading to xen 3.2 and encounter the same problem before rebuilding back to stock Centos 5.1

I'm not sure what you mean by "this mechanism?" Are you suggesting that each hypervisor put "CrossHVPara\0" somewhere in the 0x40000000 - 0x400fffff CPUID range, and an OS has to do a full scan of this CPUID range on boot to find it? That seems pretty inefficient. An OS will take 1000's of hypervisor intercepts on every boot just to search this CPUID range. I