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 regres
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.
https://bugs
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 workar
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 abou
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 b
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.
https://bugs.launchpad.net/bugs/130
** 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
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
4,sockets=1,cores=4,threads=
** 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.
https://bugs.launchpad.net/bu
Public bug reported:
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:
"A clock interrupt was not received on a secondary processor within the
allocated time interval"
After rese
** 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.
I have a similar problem. winbindd does start, but has crashed several
times since installing 2:3.4.7~dfsg-1ubuntu3.5. Here is my gdb backtrace
from core dump:
Core was generated by `/usr/sbin/winbindd'.
Program terminated with signal 6, Aborted.
#0 0x7f4fbe8fba75 in raise () from /lib/libc.s
12 matches
Mail list logo
