*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Same problem
I using kernel 3.16.0-55-generic, Ubuntu 14.04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Same problem
I using kernel 3.16.0-55-generic, Ubuntu 14.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Hi,
could you please file a new bug with debugging information as per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1346917/comments/11
?
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Hi,
could you please file a new bug with debugging information as per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1346917/comments/11
?
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Same issue there. 2 VMs with 2008 sp2 x86, and 2008 R2 sp1 x64 hanging
simultaneously with BSOD stop 0x005c (0x010b 0x0003 0x)
Issue arrised after upgrading kernel from 3.12 to 3.13.
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Same issue there. 2 VMs with 2008 sp2 x86, and 2008 R2 sp1 x64 hanging
simultaneously with BSOD stop 0x005c (0x010b 0x0003 0x)
Issue arrised after upgrading kernel from 3.12 to 3.13.
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
I have same problem after crash not help restarting virtual pc on next
boot bsod with c5 code persist. I must force off machine and pover on.
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
I have same problem after crash not help restarting virtual pc on next
boot bsod with c5 code persist. I must force off machine and pover on.
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Same bluescreen again on day 9 after the kernel upgrade.
So upgrading Kernel from 3.13 to 3.16 did not help.
Still looking for a fix.
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Same bluescreen again on day 9 after the kernel upgrade.
So upgrading Kernel from 3.13 to 3.16 did not help.
Still looking for a fix.
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Just wanted to add that upgrading my kernel to a newer version fixed the
problem for me, too.
Host: 2x E5-2620V2, Ubuntu 14.04 LTS
Guest: 24 virtual cores, Windows Server 2008 R2
Before fix:
sudo uname -a
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Just wanted to add that upgrading my kernel to a newer version fixed the
problem for me, too.
Host: 2x E5-2620V2, Ubuntu 14.04 LTS
Guest: 24 virtual cores, Windows Server 2008 R2
Before fix:
sudo uname -a
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
** This bug is no longer a duplicate of bug 1307473
guest hang due to missing clock interrupt
** This bug has been marked a duplicate of bug 1346917
Using KSM on NUMA capable machines can cause KVM
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
** This bug is no longer a duplicate of bug 1307473
guest hang due to missing clock interrupt
** This bug has been marked a duplicate of bug 1346917
Using KSM on NUMA capable machines can cause KVM
*** This bug is a duplicate of bug 1307473 ***
https://bugs.launchpad.net/bugs/1307473
** This bug has been marked a duplicate of bug 1307473
guest hang due to missing clock interrupt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
*** This bug is a duplicate of bug 1307473 ***
https://bugs.launchpad.net/bugs/1307473
** This bug has been marked a duplicate of bug 1307473
guest hang due to missing clock interrupt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Re-installing 14.04 fixed my problem. Running with the same virtual
machine configurations on the same hardware without any problems. No
hyperv feature needed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Could it be DUP of
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1307473 ?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1308341
Title:
Multiple CPUs causes blue screen on
I agree. This seems to me like a duplicate of bug 1307473.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1308341
Title:
Multiple CPUs causes blue screen on Windows guest (14.04
Re-installing 14.04 fixed my problem. Running with the same virtual
machine configurations on the same hardware without any problems. No
hyperv feature needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Could it be DUP of
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1307473 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308341
Title:
Multiple CPUs causes blue screen on Windows guest
I agree. This seems to me like a duplicate of bug 1307473.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308341
Title:
Multiple CPUs causes blue screen on Windows guest (14.04 regression)
To
marking as confirmed, see bug 1332409 with the apport-collect
information.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
marking as confirmed, see bug 1332409 with the apport-collect
information.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308341
I was able to work around this by downgrading the kernel on a Ubuntu 14
box to 3.12.20-031220-generic #201405160935 (and of course wasn't seeing
this with Ubuntu 12).
I've periodically tried booting back to the standard Ubuntu 14 3.13
kernel to see if it's been fixed (and also tried
Thanks, given that info it seems clear to be a kernel and not a qemu
bug.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: virt-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
(Removed the task against virt-manager since hyperv is apparently *not*
a safe workaround in all cases)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1308341
Title:
Multiple CPUs
I was able to work around this by downgrading the kernel on a Ubuntu 14
box to 3.12.20-031220-generic #201405160935 (and of course wasn't seeing
this with Ubuntu 12).
I've periodically tried booting back to the standard Ubuntu 14 3.13
kernel to see if it's been fixed (and also tried
Thanks, given that info it seems clear to be a kernel and not a qemu
bug.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: virt-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
(Removed the task against virt-manager since hyperv is apparently *not*
a safe workaround in all cases)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308341
Title:
Multiple CPUs causes blue screen
Tried to reproduce this overnight with a windows 8 instance run by hand
with 4 cores, but no hang. I'll keep trying with some more options
added from your command line.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
-smp 4 -realtime mlock=off -rtc base=localtime does not seem to help me
reproduce this.
Does the system have to be under stress?
Can you reproduce this without virtio?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Tried to reproduce this overnight with a windows 8 instance run by hand
with 4 cores, but no hang. I'll keep trying with some more options
added from your command line.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-smp 4 -realtime mlock=off -rtc base=localtime does not seem to help me
reproduce this.
Does the system have to be under stress?
Can you reproduce this without virtio?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have done clean install of the server and yes, Windows VM freezes with hyperv
before as well as after reinstall. I'm have reverted my servers to 12.04.4
until this is solved.
Krzysiek
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I have done clean install of the server and yes, Windows VM freezes with hyperv
before as well as after reinstall. I'm have reverted my servers to 12.04.4
until this is solved.
Krzysiek
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hallo to all, this is my first post here.
I have exactly the same problem occurred after Distribution Update
Ubuntu Server x64 from 12.04.4 to 14.04.
1. I have Windows 7 32/64-Bit and Windows 2008 Server 64-Bit VMs, all
show the same error with two dedicated cores (no pinning). In
combination
Hallo to all, this is my first post here.
I have exactly the same problem occurred after Distribution Update
Ubuntu Server x64 from 12.04.4 to 14.04.
1. I have Windows 7 32/64-Bit and Windows 2008 Server 64-Bit VMs, all
show the same error with two dedicated cores (no pinning). In
combination
After adding hyperv feature, the guest freezes regularly. This happens
on both and Windows 7 64-bit and Windows 2012 R2 guests. When removing
the hyperv feature the guest acts normally, but fails with a blue
screen as before. This may be a completely different issue, but this
renders the
After adding hyperv feature, the guest freezes regularly. This happens
on both and Windows 7 64-bit and Windows 2012 R2 guests. When removing
the hyperv feature the guest acts normally, but fails with a blue
screen as before. This may be a completely different issue, but this
renders the
Thanks, it sounds like at least we should have that enabled by default
when, in virt-manager, a windows guest is selected.
** Also affects: virt-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Importance: Undecided = High
** Changed in: qemu (Ubuntu)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: virt-manager (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Thanks, it sounds like at least we should have that enabled by default
when, in virt-manager, a windows guest is selected.
** Also affects: virt-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Importance: Undecided = High
** Changed in: qemu (Ubuntu)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: virt-manager (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308341
Title:
Adding hyperv seemed to work for me too.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1308341
Title:
Multiple CPUs causes blue screen on Windows guest
To manage notifications about
Adding hyperv seemed to work for me too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308341
Title:
Multiple CPUs causes blue screen on Windows guest
To manage notifications about this bug go
It look like adding hyperv in features section to guest definition
helps, my Win7 VM now is running for ~12h, when without hyperv it was
like 3-4 hour. I will test it for few days and will post here again.
features
acpi/
apic/
pae/
hyperv
relaxed state='on'/
/hyperv
It look like adding hyperv in features section to guest definition
helps, my Win7 VM now is running for ~12h, when without hyperv it was
like 3-4 hour. I will test it for few days and will post here again.
features
acpi/
apic/
pae/
hyperv
relaxed state='on'/
/hyperv
My instalation was upgraded from 12.04 to 14.04, as well. My machine
have 2 CPU, so I set Windows 7 VM to be the only guest using CPU2
(1,3,5,7,9,11,13,15) , the error still persists.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
My instalation was upgraded from 12.04 to 14.04, as well. My machine
have 2 CPU, so I set Windows 7 VM to be the only guest using CPU2
(1,3,5,7,9,11,13,15) , the error still persists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308341
BTW, my installation was an upgrade from Ubuntu 10.04 to 12.04.
Motherboard is a dual socket Xeon fra ASUS with two E5-2630 v2 CPUs.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Sorry, I meant from 12.04 to 14.04. 12.04 was a fresh installation.
Hyper-threading is enabled.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1308341
Title:
Multiple CPUs causes
BTW, my installation was an upgrade from Ubuntu 10.04 to 12.04.
Motherboard is a dual socket Xeon fra ASUS with two E5-2630 v2 CPUs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308341
Title:
Sorry, I meant from 12.04 to 14.04. 12.04 was a fresh installation.
Hyper-threading is enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308341
Title:
Multiple CPUs causes blue screen on
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
I have Windows 7 32bit, and Windows 2008 R2 both expirence this problem, info
from Windows 7 BSOD
Host system for this VM is Dell R510,
qemu-kvm_2.0.0~rc1+dfsg-0ubuntu3_amd64.deb
VM command line:
qemu-system-x86_64 -enable-kvm -name win7_kc -S -machine
pc-1.0,accel=kvm,usb=off -cpu
libvirt xml
** Attachment added: win7_kc.xml
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1308341/+attachment/4107146/+files/win7_kc.xml
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308341
Title:
I have Windows 7 32bit, and Windows 2008 R2 both expirence this problem, info
from Windows 7 BSOD
Host system for this VM is Dell R510,
qemu-kvm_2.0.0~rc1+dfsg-0ubuntu3_amd64.deb
VM command line:
qemu-system-x86_64 -enable-kvm -name win7_kc -S -machine
pc-1.0,accel=kvm,usb=off -cpu
libvirt xml
** Attachment added: win7_kc.xml
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1308341/+attachment/4107146/+files/win7_kc.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Guest configuration XML from libvirt
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1308341/+attachment/4085104/+files/win7-test.xml
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
** Attachment added: Blue screen
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1308341/+attachment/4085103/+files/BSOD.png
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
The command line used to start the guest (from log file):
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name win7-test -S -machine
pc-i440fx-trusty,accel=kvm,usb=off -m 4096 -realtime mlock=off -smp
** Description changed:
- Configuring a Windows 7 guest using more than one CPU cases the guest to
fail. This happens after a few hours after guest boot. This is the error on the
blue screen:
+ Configuring a Windows 7 guest using more than one CPU cases the guest to
fail. This happens after a
** Attachment added: Blue screen
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1308341/+attachment/4085103/+files/BSOD.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308341
Title:
** Attachment added: Guest configuration XML from libvirt
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1308341/+attachment/4085104/+files/win7-test.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The command line used to start the guest (from log file):
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name win7-test -S -machine
pc-i440fx-trusty,accel=kvm,usb=off -m 4096 -realtime mlock=off -smp
** Description changed:
- Configuring a Windows 7 guest using more than one CPU cases the guest to
fail. This happens after a few hours after guest boot. This is the error on the
blue screen:
+ Configuring a Windows 7 guest using more than one CPU cases the guest to
fail. This happens after a
70 matches
Mail list logo
