similar to: CPU-Capabilties for Nested Virtualization

Hi, I?m using libvirt version 0.9.12 under Debian Squeeze with and AMD Opteron 4280. Executing the virsh capabilities command only show me the following flags: <cpu> <arch>x86_64</arch> <model>Opteron_G4</model> <vendor>AMD</vendor> <topology sockets='1' cores='8' threads='2'/> <feature name='nodeid_msr'/>

Hi, I?m using libvirt version 0.9.12 under Debian Squeeze with and AMD Opteron 4280. Executing the virsh capabilities command only show me the following flags: <cpu> <arch>x86_64</arch> <model>Opteron_G4</model> <vendor>AMD</vendor> <topology sockets='1' cores='8' threads='2'/> <feature name='nodeid_msr'/>

Hello all, I'm trying to setup a NUMA topology identical as the machine which hosts the qemu-kvm VirtualMachine. numactl -H on the host: available: 8 nodes (0-7) node 0 cpus: 0 1 2 3 4 5 node 0 size: 8189 MB node 0 free: 7581 MB node 1 cpus: 6 7 8 9 10 11 node 1 size: 8192 MB node 1 free: 7061 MB node 2 cpus: 12 13 14 15 16 17 node 2 size: 8192 MB node 2 free: 6644 MB node 3 cpus: 18 19 20

I am using libvirt 0.10.2.2 and qemu-kvm 1.2.2 (qemu-kvm 1.2.0 + qemu 1.2.2 applied on top plus a number of stability patches). Having issue where my VMs fail to start with the following message: kvm_init_vcpu failed: Cannot allocate memory Following the instructions at http://libvirt.org/formatdomain.html#elementsNUMATuning I've added the following to my VCPU configuration: <vcpu

On a gentoo server with libvirt-1.1.3 I get problems with starting VMs. When I do: # virsh start vm180 error: Failed to start domain vm180 error: Input/output error This happens with 1.1.3 and 1.1.4 (I rebuilt the packages and restarted the libvirtd.service). # journalctl -f -u libvirtd.service shows: Dec 03 17:32:56 jupiter libvirtd[24020]: Input/output error Dec 03 17:33:47 jupiter

Hello, I'm trying to get the Android Emulator to run inside a kvm vm on CentOS-6. Apparently the latest Android Emulators cannot run without hardware acceleration so I am trying to get the vm to see the svm cpu flag. Host: $ grep model\ name /proc/cpuinfo | sort -u model name : AMD Phenom(tm) II X4 965 Processor $ grep svm /proc/cpuinfo | sort -u flags : fpu vme de pse tsc msr pae mce cx8

Thank you very much for getting back to me. On 2019-03-07 04:23, Stephan Bosch via dovecot wrote: >> http payload echo (ssl): sequential .................................. : ok >> http payload echo (ssl): pipeline .................................... : ok >> http payload echo (ssl): parallel .................................... : >> FAILED: Test is hanging >> http

> On Aug 12, 2017, at 3:50 PM, Fred Smith <fredex at fcshome.stoneham.ma.us> wrote: > > I had a series of kernel hardware error reports today while I was away > from my computer: > > Message from syslogd at fcshome at Aug 12 10:12:24 ... > kernel:[Hardware Error]: MC2 Error: VB Data ECC or parity error. > > Message from syslogd at fcshome at Aug 12 10:12:24 ...

Hi, I have an fc17 server with an Opteron 6128 with a few fc17/16 guests. How can I be sure I'm best matching the guest CPU with that of the server? I've used virt-manager to create the guests, and it currently shows the processor is a "Phenom(tm) 9550 Quad-Core": processor : 1 vendor_id : AuthenticAMD cpu family : 16 model : 2 model name : AMD

Hi, I have a fedora15 box with a win7 kvm instance that has been running for some time, but lately it seems to just crash and disappear without any idea of what happened. It's never happened while I have been using it, only when the instance is idle. I usually start the instance using virt-manager, but also start it just using "virsh start mykvm" then access it using the spicec

Paolo Bonzini <pbonzini at redhat.com> wrote: > Il 29/05/2014 19:45, Chris Webb ha scritto: >> Chris Webb <chris at arachsys.com> wrote: >> >>> My CPU flags inside the crashing guest look like this: >>> >>> fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush >>> mmx fxsr sse sse2 ht syscall nx mmxext

Paolo Bonzini <pbonzini at redhat.com> wrote: > Il 29/05/2014 19:45, Chris Webb ha scritto: >> Chris Webb <chris at arachsys.com> wrote: >> >>> My CPU flags inside the crashing guest look like this: >>> >>> fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush >>> mmx fxsr sse sse2 ht syscall nx mmxext

I had a series of kernel hardware error reports today while I was away from my computer: Message from syslogd at fcshome at Aug 12 10:12:24 ... kernel:[Hardware Error]: MC2 Error: VB Data ECC or parity error. Message from syslogd at fcshome at Aug 12 10:12:24 ... kernel:[Hardware Error]: Error Status: Corrected error, no action required. Message from syslogd at fcshome at Aug 12 10:12:24 ...

I'm looking for assistance with pci-passthrough on CentOS 6.2. I've installed libvirt version: 0.9.4, package: 23.el6_2.8 from yum. I have a windows XP client setup via virt-manager which boots and runs fine until I attempt to assign a PCI device to it. The error log reads: -----------------/var/log/libvirt/qemu/SageTv.log---------------- 2012-06-02 22:55:07.801: starting up LC_ALL=C

I am using a debian 9 guest, hosted on a ESXi platform with nested virtualisation enabled. On this debian 9 guest when I run libguesfs-test-tool, it fails with an error: "qemu-system-x86_64: /build/qemu-DqynNa/qemu-2.8+dfsg/target-i386/kvm.c:1805: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed." Instead when I use a wrapper script and hook it with the env

On Sat, Aug 12, 2017 at 05:51:33PM -0400, Steven Tardy wrote: > > > On Aug 12, 2017, at 3:50 PM, Fred Smith <fredex at fcshome.stoneham.ma.us> wrote: > > > > I had a series of kernel hardware error reports today while I was away > > from my computer: > > > > Message from syslogd at fcshome at Aug 12 10:12:24 ... > > kernel:[Hardware Error]:

Hi we observed that below errors occur on AMD platform since 25de7691a0e27c29c8d783a22373cc265571f5e9 root at lkp-opteron1 /opt/rootfs/llvm_project/src/build# cmake -DCMAKE_BUILD_TYPE=release -DLLVM_ENABLE_PROJECTS=clang -G "Unix Makefiles" ../llvm -DCMAKE_INSTALL_PREFIX=/opt/cross/ -- clang project is enabled -- clang-tools-extra project is disabled -- compiler-rt project is disabled

The code was passing sizeof(char *) - not the length of the buffer - to memset. Change the function to take the length of the buffer as a parameter. Fixes the warning: argument to 'sizeof' in 'memset' call is the same expression as the destination; did you mean to provide an explicit length? Signed-off-by: Jonathan Boeing <jonathan.n.boeing at gmail.com> ---

LKP framework can guarantee that all the software environment are same on AMD and INTEL platform. INTEL platform always work well, after revert this patch, AMD works well. we tried below commit on AMD. 1) 25de7691a0e27c29c8d783a22373cc265571f5e9: bad 2) a82235843b102202766115e10003c9465a8b83ae: good the error logs(build/CMakeFiles/CMakeError.log) has no difference b/w 1) and 2) on AMD platform

Chris Webb <chris at arachsys.com> wrote: > My CPU flags inside the crashing guest look like this: > > fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush > mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb lm rep_good nopl > extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic popcnt aes xsave > avx f16c hypervisor lahf_lm