[Bug 469419] Re: KVM machines became corrupted after reboot (i386 only)

2011-10-04 Thread Serge Hallyn
Per comment #12, I will mark this fix released. ** Changed in: qemu-kvm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/469419 Title: KVM machines be

[Bug 469419] Re: KVM machines became corrupted after reboot (i386 only)

2010-07-08 Thread David Ayers
I have now upgraded my production system to lucid i686 2.6.32-23-generic-pae and I was able to install a new VM again. This issue is no longer affecting me. -- KVM machines became corrupted after reboot (i386 only) https://bugs.launchpad.net/bugs/469419 You received this bug notification because

[Bug 469419] Re: KVM machines became corrupted after reboot (i386 only)

2010-05-25 Thread Anders Olsson
Actually I remember the disk being full so the host did not boot correctly until I made some space available. This is the most likely reason for the corruption of the guest, though it shouldn't happen anyway. -- KVM machines became corrupted after reboot (i386 only) https://bugs.launchpad.net/bug

[Bug 469419] Re: KVM machines became corrupted after reboot (i386 only)

2010-05-24 Thread Anders Olsson
I have also encountered what seems to be data corruption with a karmic i386 kvm host after rebooting (actually I stopped the guest, rebooted the host and now I can't start the guest again). I get a kernel panic because of a bad ELF header. The guest is also karmic i386. It has worked fine for a whi

[Bug 469419] Re: KVM machines became corrupted after reboot (i386 only)

2010-04-16 Thread David Ayers
Hello Scott, After upgrading the host to the latest packages I was now able to install Lucid-Beta2 and run it afterwards. I must admit that I'm now unsure if I remembered to upgrade after the initial Installation since I re installed a few times due to grub issues when installing on a USB drive

[Bug 469419] Re: KVM machines became corrupted after reboot (i386 only)

2010-04-15 Thread Scott Moser
David, can you please provide your kvm installation command line, and also what type of disk format you're using (ie, from qemu-create). If you're using from libvirt, virsh dumpxml output would be nice. -- KVM machines became corrupted after reboot (i386 only) https://bugs.launchpad.net/bugs/469

[Bug 469419] Re: KVM machines became corrupted after reboot (i386 only)

2010-04-15 Thread Jonathan Davies
** Changed in: qemu-kvm (Ubuntu) Status: Incomplete => Confirmed -- KVM machines became corrupted after reboot (i386 only) https://bugs.launchpad.net/bugs/469419 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mail

[Bug 469419] Re: KVM machines became corrupted after reboot (i386 only)

2010-04-11 Thread David Ayers
Yes this bug also affects Lucid beta2. I'll attempt to add a screenshot of what happens after installing Lucid B2 within Lucid B2 on i386. ** Attachment added: "post-installation-reboot.png" http://launchpadlibrarian.net/43777940/post-installation-reboot.png -- KVM machines became corrupted

[Bug 469419] Re: KVM machines became corrupted after reboot (i386 only)

2010-03-01 Thread Dustin Kirkland
Updating the title to note that this affecting 32-bit only. Can anyone reproduce this problem on Lucid kvm? I'm marking incomplete for now. Please mark confirmed if you can reproduce on Lucid. Thanks! ** Summary changed: - KVM machines became corrupted after reboot + KVM machines became corru