kernel-packages team mailing list archive

[Thiago Martins <thiagocmartinsc@xxxxxxxxx>]

Hi Serge,

 At first, yes, I was trying with VirtIO.

 Later, I disabled VirtIO for Disk, didn't solve.

 Then, I disabled VirtIO for Net, didn't solve.

 Again, I disabled VirtIO for both Disk and Net, didn't solve.

 But, thinking on it again now, I did not tested it with a Windows 2008
R2 that did not touched VirtIO drivers, I mean, in all of my tests, I
was using at least, the ballon RAM driver (and probable VirtIO Serial,
or something like that).

 Next week, I'll try it with again, without any VirtIO, from the
beginning, with KSM=1.

Best,
Thiago

-- 
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/1338277

Title:
  Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to
  crash (BSOD)

Status in “linux” package in Ubuntu:
  Confirmed
Status in “qemu” package in Ubuntu:
  Confirmed

Bug description:
  Guys,

  I'm trying to run Windows 2008 as a QEmu guest on my Ubuntu 14.04 but,
  after lots of tests, I figured out that it doesn't work, QEmu makes
  Windows 2008 to crash, and it is not a Windows fault, I'm pretty sure
  that it is a QEmu bug.

  Lab environment (5 servers):

  3 physical servers: Dell R610

  2 physycal servers: IBM x3650

  * Where Windows crash (5 servers tested) ?

  Ubuntu 14.04 + QEmu 2.0 + VirtIO 0.1-81 = Windows 2008 crash every
  hour

  - Installed with "apt-get install ubuntu-virt-server".

  * Where Windows do not crash (5 servers tested) ?

  Ubuntu 14.04 + Xen 4.4 +  gplpv_Vista2008x64_1.0.1092.9 = Windows
  working smoothly

  - Installed with "apt-get install xen-system-amd64".

  So, after removing QEmu from my environment, and using Xen instead,
  all Windows guests are now running without any crash.

  What kind of information, can I provide for you guys, to deep debug
  this QEmu problem ?

  Plus, it is interesting to note that a lot of times, all Windows
  guests (on top of QEmu / KVM) crashes at the exactly the same time!
  So, it can not be a problem within each Windows guest, but at the
  Hypervisor itself! Something happen there, that affects almost all
  Windows guests simultaneously.

  Also, it worth to mention that this problem is probably affecting
  clouds based on OpenStack IceHouse, on top of Ubuntu + QEmu 2.0...

  Screenshots:

  http://i.imgur.com/vnJSTgg.png

  http://i.imgur.com/34nADWr.png

  NOTE: I'm using KSM (Kernel Samepage Merging) with QEmu, to save RAM.
  It seems that when with Xen (+QEmu / HVM), KSM is not used :'( , but
  it is enabled ( 1 > /sys/kernel/mm/ksm/run at Dom0's kernel). I did
  not tried to disable KSM to see if Windows becomes more stable on QEmu
  2.0...

  Also, I did not run tests on this environment with Ubuntu 12.04.4 (or
  12.04.4 with Ubuntu Cloud Archives, to get newer versions of QEmu (but
  not 2.0) for old LTS).

  CURIOSITY: On older hardware, like Dell R1950, and at my old Intel
  Desktop Core i7, I'm running Windows 2008 and 7, on Ubuntu 14.04 with
  QEmu 2.0 without any crash... I really like to figure out why QEmu is
  crashing Windows guests on Dell R610 and on IBM x3650...

  Attaching the VM's configuration files on next posts...

  Best,
  Thiago
  --- 
  AlsaDevices:
   total 0
   crw-rw---- 1 root audio 116,  1 Jul 15 08:32 seq
   crw-rw---- 1 root audio 116, 33 Jul 15 08:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.2
  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 14.04
  InstallationDate: Installed on 2014-06-23 (22 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R610
  Package: qemu
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=6a76ba24-a056-468d-b620-84a49c71d873 ro
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-30-generic N/A
   linux-backports-modules-3.13.0-30-generic  N/A
   linux-firmware                             1.127.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/23/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 6.4.0
  dmi.board.name: 0DFXXD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0DFXXD:rvrA00:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R610
  dmi.sys.vendor: Dell Inc.

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