similar to: Bug#566012: xen-hypervisor-3.2-1-i386: Another crash. Is this a hypervisor-problem, or is this the kernel?

Package: xen-hypervisor-3.2-1-i386 Version: 3.2.1-2 Severity: important When starting a domU, or bringing up a network connection in a domU, this crash sometimes happens: (XEN) domain_crash_sync called from entry.S (ff188600) (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-3.2-1 x86_32p debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) EIP: 0061:[<c01013a7>] (XEN) EFLAGS:

Trying to get Xen going on Fedora 9. Xen was installed from the distro RPMs. Xen version is 3.2.0 and the linux-xen version is 2.6.25.3. Xen seems to come up fine, but the system just hangs at the point where booting of Dom0 should start. There is absolutely no output from Dom0. I configured Xen to log to a serial port and captured the output below. Any suggestions on how to continue

On Wed, Oct 15, 2014 at 03:23:39PM +0000, VONDRA Alain wrote: > I see only qemu-img consumming some CPU and MEM : > > 25897 qemu 20 0 5825976 2,429g 4368 S 5,6 32,2 603:09.34 qemu-kvm That's qemu, not qemu-img. > I have indeed, some nfs errors : > > [475747.296041] nfs: server 192.203.100.247 not responding, still trying > [475747.772022] nfs: server

On 2/11/20 5:52 AM, Joerg Roedel wrote: > Implement a handler for #VC exceptions caused by RDMSR/WRMSR > instructions. As a general comment on all of these event handlers: Why do we bother having the hypercalls in the interrupt handler as opposed to just calling them directly. What you have is: wrmsr() -> #VC exception hcall() But we could make our rd/wrmsr() wrappers just do:

On 2/11/20 5:52 AM, Joerg Roedel wrote: > Implement a handler for #VC exceptions caused by RDMSR/WRMSR > instructions. As a general comment on all of these event handlers: Why do we bother having the hypercalls in the interrupt handler as opposed to just calling them directly. What you have is: wrmsr() -> #VC exception hcall() But we could make our rd/wrmsr() wrappers just do:

The subject says it all really, I''m pretty sure the system and bios are NUMA aware but I''m not sure if it''s enabled? Is it supported in 3.2.1 stable? Thanks, Rob \ \/ /___ _ __ |___ / |___ \ / | \ // _ \ ''_ \ |_ \ __) | | | / \ __/ | | | ___) | / __/ _| | /_/\_\___|_| |_| |____(_)_____(_)_| (XEN) Xen version 3.2.1

Intel recently release a new tsc adjust feature at latest SDM 17.13.3. CPUID.7.0.EBX[1]=1 indicates TSC_ADJUST MSR 0x3b is supported. Basically it is used to simplify TSC synchronization, operation of IA32_TSC_ADJUST MSR is as follows: 1). On RESET, the value of the IA32_TSC_ADJUST MSR is 0; 2). If an execution of WRMSR to the IA32_TIME_STAMP_COUNTER MSR adds (or subtracts) value X from the

When CONFIG_PARAVIRT is enabled, the kernel is ignoring exceptions on the {rd,wr}msr instructions. This makes serious issues (either on the guest kernel, or on the host) be silently ignored, and is different from the native MSR code (which does not ignore the exceptions). As paravirt.h already includes linux/bug.h, I don't see what was the original issue preventing BUG_ON from being used.

When CONFIG_PARAVIRT is enabled, the kernel is ignoring exceptions on the {rd,wr}msr instructions. This makes serious issues (either on the guest kernel, or on the host) be silently ignored, and is different from the native MSR code (which does not ignore the exceptions). As paravirt.h already includes linux/bug.h, I don't see what was the original issue preventing BUG_ON from being used.

Hyper-V SynIC is a Hyper-V synthetic interrupt controller. The test runs on every vCPU and performs the following steps: * read from all Hyper-V SynIC MSR's * setup Hyper-V SynIC evt/msg pages * setup SINT's routing * inject SINT's into destination vCPU by 'hyperv-synic-test-device' * wait for SINT's isr's completion * clear Hyper-V SynIC evt/msg pages and destroy

Hyper-V SynIC is a Hyper-V synthetic interrupt controller. The test runs on every vCPU and performs the following steps: * read from all Hyper-V SynIC MSR's * setup Hyper-V SynIC evt/msg pages * setup SINT's routing * inject SINT's into destination vCPU by 'hyperv-synic-test-device' * wait for SINT's isr's completion * clear Hyper-V SynIC evt/msg pages and destroy

Hello to all: Recently upgraded from CentOS 6.0 to 6.2 to get USB passthrough support by performing "yum update". USB passthrough works great, but now my Windows XP sp3 guest crashes repeatedly after a few minutes. [root at shackleton-eth0 log]# rpm -qa|egrep '(kvm|kernel|libvirt-|qemu)'|sort abrt-addon-kerneloops-2.0.4-14.el6.centos.x86_64

Hi, Since a week or two I can''t create two of my three WinXP DomU''s anymore, the third one starts just fine. This is the basic error message I get: # xm create WinXPViaLilaGeert Using config file "./WinXPViaLilaGeert". Error: Creating domain failed: name=WinXPViaLilaGeert There is little information in this error message. /var/log/xen/xend.log has a little more:

> -----Original Message----- > From: Chris Murphy > Sent: Tuesday, February 17, 2015 20:48 > > On Tue, Feb 17, 2015 at 7:54 AM, Jason Pyeron wrote: > >> I'd post the entire dmesg somewhere > > > > http://client.pdinc.us/panic-341e97c30b5a4cb774942bae32d3f163.log > > At least part of the problem happens before this log starts. Feb 15 23:41:19

I can see from different post that if working with sr-iov, i should work with vlan Is this an obligation to work with vlan if working with sr-iov? If not according to which parameter will the different vf get the traffic. Let's say i declare max_vfs=7, how will the traffic be seperated between the vm? However till i get an answer i tried to work with vlan And i still don't get

Fairly straightforward code motion of MSR / TSC / PMC accessors to the sub-arch level. Note that rdmsr/wrmsr_safe functions are not moved; Linux relies on the fault behavior here in the event that certain MSRs are not supported on hardware, and combining this with a VMI wrapper is overly complicated. The instructions are virtualizable with trap and emulate, not on critical code paths, and only

Fairly straightforward code motion of MSR / TSC / PMC accessors to the sub-arch level. Note that rdmsr/wrmsr_safe functions are not moved; Linux relies on the fault behavior here in the event that certain MSRs are not supported on hardware, and combining this with a VMI wrapper is overly complicated. The instructions are virtualizable with trap and emulate, not on critical code paths, and only

I've a the following happen a couple times now, and my internet searches are failing to locate an answer to the problem. We've got a few servers that primarily house VMs using KVM. They've got E-3 cpus and 32 GB RAM, and they run stock CentOS 6.4, fully patched (not yet migrated to 6.5). The VM disk images are housed on an NFS server. None of the VMs is particularly

nic@wuwei:/usr/src/xen/xen-unstable.hg$ sudo xm create breezy -c Using config file "/etc/xen/breezy". Started domain breezy Linux version 2.6.12-xenU (nic@wuwei) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #3 SMP Thu Oct 13 14:56:20 NZDT 2005 kernel direct mapping tables upto 10000000 @ 568000-5ea000 Built 1 zonelists Kernel command line: root=/dev/sda1 ro 4 lockd.udpport=32768

Hello, I recently tried Xen 3.0.3-testing on my 2x Opteron-244 SMP machine. Everything works well exept one detail, which is not unimportant to me: the powernow-k8 driver fails to switch frequencies. A closer look on the powernow-k8 source reveals, that some MSR write operations seem to be without any effect. A rdmsr() before and after the wrmsr() call reveals that no real change on the register