search for: wrmsr

Hi, I''m doing some testing on Ubuntu 12.04 Alpha. All sounds comes out as static on the Dom0 system. (I can PCI passthrough the audio card to a DomU and that works). Native sound works fine. Linux kronos 3.2.0-8-generic-pae #15-Ubuntu SMP Wed Jan 11 15:34:57 UTC 2012 i686 i686 i386 GNU/Linux Here is the "ubuntu-bug audio" generated report:

On Wed, Oct 15, 2014 at 01:49:55PM +0000, VONDRA Alain wrote: > If I do kill -9, do I get a core dump ? I'm not sure, but ... > Killall does nothing the process is still alive... > Each time I got this hang, I find only umount -f /tmp/xxxx to force > qemu-img to stop. Are you sure this couldn't be an NFS server problem? Any message or errors in 'dmesg'? Any kernel

...461034] nfs: server 192.203.100.247 not responding, still trying These are a problem, if they are coincident with qemu-img hanging. Use 'dmesg -w' to check. > And a lot of : > [785084.263606] kvm [12719]: vcpu0 unhandled rdmsr: 0x345 > [785084.269594] kvm [12719]: vcpu0 unhandled wrmsr: 0x40 data 0 > [785084.269999] kvm [12719]: vcpu0 unhandled wrmsr: 0x60 data 0 > [785084.270406] kvm [12719]: vcpu0 unhandled wrmsr: 0x41 data 0 > [785084.270826] kvm [12719]: vcpu0 unhandled wrmsr: 0x61 data 0 > [785084.271231] kvm [12719]: vcpu0 unhandled wrmsr: 0x42 data 0 > [7850...

Package: xen-hypervisor-3.2-1-i386 Version: 3.2.1-2 Followup-For: Bug #566012 Just had another crash. I got the output from a serial console. The kernel doesn't say anything though. (XEN) traps.c:1996:d6 Domain attempted WRMSR 00000400 from 00000000:0000ffff to ffffffff:ffffffff. (XEN) traps.c:1996:d6 Domain attempted WRMSR 00000404 from 00000000:00018000 to ffffffff:ffffffff. (XEN) traps.c:1996:d6 Domain attempted WRMSR 00000408 from 00000000:00000080 to ffffffff:ffffffff. (XEN) traps.c:1996:d6 Domain attempted WRMSR 00...

...ibvirt-python-0.9.4-23.el6_2.6.x86_64 qemu-img-0.12.1.2-2.209.el6_2.4.x86_64 qemu-kvm-0.12.1.2-2.209.el6_2.4.x86_64 This message in /var/log/messages precedes every crash: [root at shackleton-eth0 log]# grep kvm /var/log/messages Mar 19 09:09:25 shackleton-eth0 kernel: kvm: 2889: cpu0 unhandled wrmsr: 0x198 data 0 Mar 19 09:15:48 shackleton-eth0 kernel: kvm: 2889: cpu0 unhandled wrmsr: 0x198 data 0 Mar 19 09:25:51 shackleton-eth0 kernel: kvm: 2889: cpu0 unhandled wrmsr: 0x198 data 0 Mar 19 11:21:27 shackleton-eth0 kernel: kvm: 2889: cpu0 unhandled wrmsr: 0x198 data 0 Mar 19 12:07:16 shackleton-...

...0.247 not responding, still trying [475748.461031] nfs: server 192.203.100.247 not responding, still trying [475748.461034] nfs: server 192.203.100.247 not responding, still trying And a lot of : [785084.263606] kvm [12719]: vcpu0 unhandled rdmsr: 0x345 [785084.269594] kvm [12719]: vcpu0 unhandled wrmsr: 0x40 data 0 [785084.269999] kvm [12719]: vcpu0 unhandled wrmsr: 0x60 data 0 [785084.270406] kvm [12719]: vcpu0 unhandled wrmsr: 0x41 data 0 [785084.270826] kvm [12719]: vcpu0 unhandled wrmsr: 0x61 data 0 [785084.271231] kvm [12719]: vcpu0 unhandled wrmsr: 0x42 data 0 [785084.271633] kvm [12719]: v...

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 used as pa...

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 used as pa...

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: if (...

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: if (...

...lease 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 TSC, the logical processor also adds (or subtracts) value X from the IA32_TSC_ADJUST MSR; 3). If an execution of WRMSR to the IA32_TSC_ADJUST MSR adds (or subtracts) value X from that MSR, the logical processor also...

...Yunhong Jiang >-----Original Message----- >From: xen-devel-bounces@lists.xensource.com >[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Tim Deegan >Sent: 2006年10月5日 23:55 >To: Li, Xin B >Cc: xen-devel@lists.xensource.com >Subject: Re: [Xen-devel] [PATCH] add RDMSR/WRMSR instruction >emulationtoVMXAssist decoder > >This bug is fixed by xen-unstable 11713:79b56c02b836 -- the >VMX code was >not tracking writes to CR4 that happen when CR0.PE=0, so the >second vcpu >was being shadowed in the wrong paging mode, and going into a PF loop. > >...

...nfs: server > 192.203.100.247 not responding, still trying These are a problem, if they are coincident with qemu-img hanging. Use 'dmesg -w' to check. > And a lot of : > [785084.263606] kvm [12719]: vcpu0 unhandled rdmsr: 0x345 > [785084.269594] kvm [12719]: vcpu0 unhandled wrmsr: 0x40 data 0 > [785084.269999] kvm [12719]: vcpu0 unhandled wrmsr: 0x60 data 0 > [785084.270406] kvm [12719]: vcpu0 unhandled wrmsr: 0x41 data 0 > [785084.270826] kvm [12719]: vcpu0 unhandled wrmsr: 0x61 data 0 > [785084.271231] kvm [12719]: vcpu0 unhandled wrmsr: 0x42 data 0 >...

Hi all, I have installed a CentOS-8 server to accomplish some tests using kvm guests ? All these guests are centos8 also. When these guests starts, I always see errors like: [ 589.687915] kvm [2133]: vcpu0, guest rIP: 0xffffffff81a5bc98 disabled perfctr wrmsr: 0xc2 data 0xffff [ 596.210773] kvm [2201]: vcpu0, guest rIP: 0xffffffffb885bc98 disabled perfctr wrmsr: 0xc2 data 0xffff Is this a bug? I am not using virt-manager to create guests configuration ? Any idea? Kernel release is: 4.18.0-80.11.2 -- Regards, C. L. Martinez

...ers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: All (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen) (XEN) Freed 100kB init memory. (XEN) traps.c:1996:d0 Domain attempted WRMSR 0000000000000277 from 00000501:00070406 to 00000501:00070106. (XEN) traps.c:1996:d0 Domain attempted WRMSR 0000000000000277 from 00000501:00070406 to 00000501:00070106. (XEN) traps.c:1996:d0 Domain attempted WRMSR 0000000000000277 from 00000501:00070406 to 00000501:00070106. (XEN) traps.c:1996:d...

...ous 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. Change rdmsr(), wrmsr(), and rdmsrl() to BUG_ON() on errors. Signed-off-by: Eduardo Habkost <ehabkost at redhat.com> --- * Build-tested using allyesconfig, with no build errors. * Tested by being able to detect the following host bug: https://bugzilla.redhat.com/show_bug.cgi?id=1025868 (#GP exception on wrms...

...ous 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. Change rdmsr(), wrmsr(), and rdmsrl() to BUG_ON() on errors. Signed-off-by: Eduardo Habkost <ehabkost at redhat.com> --- * Build-tested using allyesconfig, with no build errors. * Tested by being able to detect the following host bug: https://bugzilla.redhat.com/show_bug.cgi?id=1025868 (#GP exception on wrms...

Can''t seem to fully boot a domU on either EM64T or Opteron with x86_64 xen-unstable. Both systems'' report this from xen: (XEN) (file=traps.c, line=872) Non-priv domain attempted WRMSR(00000000c0000100. (XEN) (file=traps.c, line=872) Non-priv domain attempted WRMSR(00000000c0000102. (XEN) (file=traps.c, line=880) Non-priv domain attempted RDMSR(00000000c0000080. They boot partially, ending with: xen_mem: Initialising balloon driver. Grant table initialized IA32 emulation $Id:...

...================================================== --- 2007-08-08.orig/xen/arch/x86/traps.c 2007-08-08 11:37:08.000000000 +0200 +++ 2007-08-08/xen/arch/x86/traps.c 2007-08-08 11:40:02.000000000 +0200 @@ -1696,6 +1696,8 @@ static int emulate_privileged_op(struct break; case 0x30: /* WRMSR */ + data = regs->eax; + res = ((u64)regs->edx << 32) | data; switch ( regs->ecx ) { #ifdef CONFIG_X86_64 @@ -1704,24 +1706,21 @@ static int emulate_privileged_op(struct goto fail; if ( wrmsr_safe(MSR_FS_BASE, regs->e...

Hello, This series of patches integrates msr.h header. What it really does, is a series of steps to allow us to get rid of duplicate code between i386 and x86_64 versions With this done, achieving paravirt for x86_64 gets really easy, just a couple of extra code. The first patch was already sent a while ago, but was not yet pushed to any tree , to my knowledge. So it is sent again. Also,