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
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/469419
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
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)
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
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
** 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
Server Team, which is subscribed to qemu-kvm in ubuntu.
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)
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
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
Your hda should be:
disk type='block' device='disk'
source dev='/dev/vm/ubuntu'/
target dev='hda' bus='ide'/
/disk
There is an example:
http://libvirt.org/drvqemu.html
--
KVM machines became corrupted after reboot
https://bugs.launchpad.net/bugs/469419
You received this bug
I've checked that and it doesn't make any difference.
I did a fresh Ubuntu 9.10 install on virtual machine and after reboot I've
installed firefox on it and the filesystem became corrupted.
Even if I don't use raw partitions I have the same issue.
Now I really thinking about giving up with
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Medium
--
KVM machines became corrupted after reboot
https://bugs.launchpad.net/bugs/469419
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
I'm afraid I have the same problem but on windows xp vm on Karmic kvm i386.
VM installs correctly and seems to work correctly however when I map physical
partition into vm and try to read files from that partition then I notice that
most of the files are corrupted however they are correct when
Upgrading a Jaunty vm to Karmic works for me, but a new Karmic install
fails with the same error.
At some point I manage to update fstab after a mkswap swapon and it
worked on reboot. But after a reboot of the host the problem was back.
--
KVM machines became corrupted after reboot
14 matches
Mail list logo
