← Back to team overview

kernel-packages team mailing list archive

[Bug 1071322] Re: Quantal kernel for precise: starting KVM VM causes 'vmwrite error'

 

Please note that 29282fde80d44e587f8c152b10049a56e61659f0 is in the following Ubuntu kernels:
3.16 series
3.13 series
3.8 series

As 3.5 is no longer supported please upgrade the 3.13 series kernel for Precise.
Thanks,

** Package changed: linux-meta-lts-quantal (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1071322

Title:
  Quantal kernel for precise: starting KVM VM causes 'vmwrite error'

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  Starting a KVM VM (via libvirt) on 12.04.1 running linux-image-
  generic-lts-quantal/linux-image-3.5.0-18-generic causes the following
  in dmesg:

  [   35.818137] vmwrite error: reg 401e value a050a000 (err 12)
  [   35.834818] Pid: 3714, comm: kvm Tainted: G         C   3.5.0-18-generic #29~precise1-Ubuntu
  [   35.834822] Call Trace:
  [   35.834850]  [<ffffffffa04f9c10>] vmwrite_error+0x2c/0x2e [kvm_intel]
  [   35.834855]  [<ffffffffa04ef7b0>] vmcs_writel+0x20/0x30 [kvm_intel]
  [   35.834862]  [<ffffffffa04f0d39>] vmx_cpuid_update+0x79/0x160 [kvm_intel]
  [   35.834895]  [<ffffffffa016ecf9>] kvm_vcpu_ioctl_set_cpuid2+0x99/0xb0 [kvm]
  [   35.834912]  [<ffffffffa01517ec>] kvm_arch_vcpu_ioctl+0x68c/0xcf0 [kvm]
  [   35.834919]  [<ffffffff8115b0ca>] ? lazy_max_pages+0x1a/0x30
  [   35.834924]  [<ffffffff81173f0b>] ? kfree+0x3b/0x140
  [   35.834941]  [<ffffffffa04f426e>] ? vmx_vcpu_load+0x3e/0x1c0 [kvm_intel]
  [   35.834945]  [<ffffffff8115dd14>] ? __vunmap.part.16+0x84/0xc0
  [   35.834962]  [<ffffffffa0151007>] ? kvm_arch_vcpu_load+0x57/0x1b0 [kvm]
  [   35.834974]  [<ffffffffa013d379>] kvm_vcpu_ioctl+0xb9/0x6c0 [kvm]
  [   35.834989]  [<ffffffffa0150e7e>] ? kvm_arch_dev_ioctl+0x6e/0x1a0 [kvm]
  [   35.834994]  [<ffffffff8119931a>] do_vfs_ioctl+0x8a/0x340
  [   35.834998]  [<ffffffff81199661>] sys_ioctl+0x91/0xa0
  [   35.835004]  [<ffffffff816a6a69>] system_call_fastpath+0x16/0x1b
  [   35.835966] vmwrite error: reg 401e value a050a000 (err 12)
  [   35.852638] Pid: 3715, comm: kvm Tainted: G         C   3.5.0-18-generic #29~precise1-Ubuntu
  [   35.852640] Call Trace:
  [   35.852649]  [<ffffffffa04f9c10>] vmwrite_error+0x2c/0x2e [kvm_intel]
  [   35.852655]  [<ffffffffa04ef7b0>] vmcs_writel+0x20/0x30 [kvm_intel]
  [   35.852661]  [<ffffffffa04f0d39>] vmx_cpuid_update+0x79/0x160 [kvm_intel]
  [   35.852676]  [<ffffffffa016ecf9>] kvm_vcpu_ioctl_set_cpuid2+0x99/0xb0 [kvm]
  [   35.852691]  [<ffffffffa01517ec>] kvm_arch_vcpu_ioctl+0x68c/0xcf0 [kvm]
  [   35.852695]  [<ffffffff8115b0ca>] ? lazy_max_pages+0x1a/0x30
  [   35.852699]  [<ffffffff81173f0b>] ? kfree+0x3b/0x140
  [   35.852705]  [<ffffffffa04f426e>] ? vmx_vcpu_load+0x3e/0x1c0 [kvm_intel]
  [   35.852709]  [<ffffffff8115dd14>] ? __vunmap.part.16+0x84/0xc0
  [   35.852723]  [<ffffffffa0151007>] ? kvm_arch_vcpu_load+0x57/0x1b0 [kvm]
  [   35.852735]  [<ffffffffa013d379>] kvm_vcpu_ioctl+0xb9/0x6c0 [kvm]
  [   35.852750]  [<ffffffffa0150e7e>] ? kvm_arch_dev_ioctl+0x6e/0x1a0 [kvm]
  [   35.852754]  [<ffffffff8119931a>] do_vfs_ioctl+0x8a/0x340
  [   35.852758]  [<ffffffff81199661>] sys_ioctl+0x91/0xa0
  [   35.852762]  [<ffffffff816a6a69>] system_call_fastpath+0x16/0x1b
  --- 
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 Oct 25 14:24 seq
   crw-rw---T 1 root audio 116, 33 Oct 25 14:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=f744f0b7-5b16-4935-8a91-5d085acf2cb3
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: empty empty
  Package: linux-meta (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   LC_COLLATE=C
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=d6ae63dc-e328-422d-bc41-f424a79cb28c ro console=ttyS0,38400n8
  ProcVersionSignature: Ubuntu 3.5.0-18.29~precise1-generic 3.5.7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-18-generic N/A
   linux-backports-modules-3.5.0-18-generic  N/A
   linux-firmware                            1.79.1
  RfKill: Error: [Errno 2] No such file or directory
  StagingDrivers: xgifb
  Tags:  precise staging
  Uname: Linux 3.5.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/15/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: TYAN-Tempest-i5000VS-S5372
  dmi.board.vendor: TYAN Computer Corporation
  dmi.board.version: empty
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd01/15/2007:svnempty:pnempty:pvrempty:rvnTYANComputerCorporation:rnTYAN-Tempest-i5000VS-S5372:rvrempty:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: empty
  dmi.product.version: empty
  dmi.sys.vendor: empty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071322/+subscriptions