Bug#653068:

2012-06-28 Thread anatoly techtonik
The same problem trying Debian Squeeze in virt-manager with qxl on Fedora 17: unaligned pointer 0x8ef20002 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#653068: qemu-kvm: squeeze VMs don't boot on wheezy hosts

2012-03-26 Thread intrigeri
Hi, Matthias Heinz wrote: Loading Linux 2.6.32-5-amd64 ... unaligend pointer 0x93940002 Aborted. Press any key to exit. I can see this too: in a Squeeze VM in a libvirt + qemu sid environment, switching from Cirrus to QXL display triggers this bug. I tried booting the VM with the Linux 3.2

Bug#653068: qemu-kvm: squeeze VMs don't boot on wheezy hosts

2012-01-13 Thread Matthias Heinz
Hallo Michael, Am 05.01.2012 15:17, schrieb Michael Tokarev: See also LP#717445: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/717445 which is exactly the same issue but reported against grub. And I tend to think more and more it is a grub bug after all, not qemu/kvm/bios bug. I did

Bug#616487: Bug#653068: qemu-kvm: squeeze VMs don't boot on wheezy hosts

2012-01-05 Thread Michael Tokarev
See also LP#717445: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/717445 which is exactly the same issue but reported against grub. And I tend to think more and more it is a grub bug after all, not qemu/kvm/bios bug. More of the same thing: https://bugs.launchpad.net/qemu/+bug/502107

Bug#653068: qemu-kvm: squeeze VMs don't boot on wheezy hosts

2012-01-04 Thread Matthias Heinz
Hi, I'm sorry that my answer took so long. I ran a few tests today and it's getting a bit weird. But first the answers to your questions. Am 23.12.2011 16:27, schrieb Michael Tokarev: I read that one and thought about it. But I don't know if it applies. Sometimes the message states that

Bug#653068: qemu-kvm: squeeze VMs don't boot on wheezy hosts

2012-01-04 Thread Michael Tokarev
retitle 653068 squeeze-VMs fail to boot with qxl video tags 653068 - moreinfo unreproducible severity 653068 normal thanks On 04.01.2012 20:20, Matthias Heinz wrote: [] I don't have to reboot to get the problems. Using spice as graphics output (and installing the image with spice! Very

Bug#616487: Bug#653068: qemu-kvm: squeeze VMs don't boot on wheezy hosts

2012-01-04 Thread Michael Tokarev
And a followup for this and another, older bugreport. It looks like the prob happens with qxl and vmware, and it is the same problem. I looked at grub sources, that message is from grub, here it is: kern/mm.c, get_header_from_pointer(): if ((grub_addr_t) ptr (GRUB_MM_ALIGN - 1))

Bug#653068: qemu-kvm: squeeze VMs don't boot on wheezy hosts

2011-12-23 Thread Matthias Heinz
Package: qemu-kvm Version: 0.15.1+dfsg-1 Severity: important Hi, I've tried several things to get Squeeze running in a VM on a wheezy/testing system here. First I thought it was a problem with the iSCSI target, then with nested LVM volumegroups, but even with an installation on the local

Bug#653068: qemu-kvm: squeeze VMs don't boot on wheezy hosts

2011-12-23 Thread Michael Tokarev
On 23.12.2011 17:26, Matthias Heinz wrote: Package: qemu-kvm Version: 0.15.1+dfsg-1 Severity: important Hi, I've tried several things to get Squeeze running in a VM on a wheezy/testing system here. First I thought it was a problem with the iSCSI target, then with nested LVM

Bug#653068: qemu-kvm: squeeze VMs don't boot on wheezy hosts

2011-12-23 Thread Matthias Heinz
Hi, Am 23.12.2011 14:54, schrieb Michael Tokarev: Hmm. Does #586143 , for example, ring any bells? I read that one and thought about it. But I don't know if it applies. Sometimes the message states that it's already the initrd that gets loaded, before it fails. And it is reproducible, means

Bug#653068: qemu-kvm: squeeze VMs don't boot on wheezy hosts

2011-12-23 Thread Michael Tokarev
tags 653068 + moreinfo unreproducible thanks On 23.12.2011 18:48, Matthias Heinz wrote: Hi, Am 23.12.2011 14:54, schrieb Michael Tokarev: Hmm. Does #586143 , for example, ring any bells? I read that one and thought about it. But I don't know if it applies. Sometimes the message states