QEMU 0.12 is way outdated nowadays, so I assume this problem has been
fixed sometime in the last years... so I'm closing this ticket now. If
you still have problems with the latest version of QEMU, please feel
free to open this bug again.
** Changed in: qemu
Status: Incomplete => Won't Fix
Looks a duplicate of
https://sourceforge.net/tracker/index.php?func=detailaid=2042889group_id=180599atid=893831
Closed the SF bug, lets focus on this issue here.
Jes
** Bug watch added: SourceForge.net Tracker #2042889
http://sourceforge.net/support/tracker.php?aid=2042889
--
qemu-kvm
Looks like the SCSI driver is causing problems. QEMU's SCSI emulation is known
to be broken, please use IDE
or virtio-blk.
Jes
--
qemu-kvm 0.12.4+dfsg-1 from debian squeeze crashes BUG: unable to handle
kernel NULL pointer (sym53c8xx)
https://bugs.launchpad.net/bugs/587993
You received this
** Description changed:
I use eucalyptus software (1.6.2) on debian squeeze with kvm
0.12.4+dfsg-1 (the same happend with 0.11.1+dfsg-1 ). Kernel
2.6.32-3-amd64. After a few days machines crash. There are no logs in
host system. Guest is the same kernel and OS as host. The kvm process
** Description changed:
I use eucalyptus software (1.6.2) on debian squeeze with kvm
- 0.12.4+dfsg-1. Kernel 2.6.32-3-amd64. After a few days machines crash.
- There are no logs in host system. Guest is the same kernel and OS as
- host. The kvm process use 100% of cpu time. I can not even ping
If you can recreate the issue, please update the bug report with
information about to how recreate the problem.
** Changed in: qemu
Status: New = Incomplete
--
qemu-kvm 0.12.4+dfsg-1 from debian squeeze crashes BUG: unable to handle
kernel NULL pointer (sym53c8xx)
