This seems like it is likely fixed in seabios http://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=604735 .
** Bug watch added: Debian Bug tracker #604735
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604735
--
You received this bug notification because you are a member of Ubuntu
Server
Marking qemu-kvm task Invalid, if this is not the case - please re-open
it.
Thanks.
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Hi Scott,
I was about to mark this invalid for qemu-kvm. Do you object to that?
(Does 'kvm -fda floppy.img -boot a -drive file=disk.img,if=ide -curses'
work?)
** Changed in: qemu-kvm (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of
I'm worried that this might not be worked around in eucalyptus. I've
just tried booting a uec-image with virtio outside of uec, and am seeing
the issue. (ie, i dont' think the simple work around worked).
--
eucalyptus instance reboot fails: Guest moved used index from 0 to 2639
I think that you can basically ignore my comment #5.
When I was seeing this issue, when booting with kvm, I was not booting with
'boot=on'.
After booting with boot=on, the problem goes away. boot=on is generated in the
kvm command line by eucalyptus, so I don't think this will be an issue there.
should have been more explicit. With kvm:
- works: kvm -fda floppy.img -boot a -drive file=disk.img,if=virtio,boot=on
-curses
- fails: kvm -fda floppy.img -boot a -drive file=disk.img,if=virtio -curses
--
eucalyptus instance reboot fails: Guest moved used index from 0 to 2639
This bug was fixed in the package eucalyptus - 2.0~bzr1224-0ubuntu1
---
eucalyptus (2.0~bzr1224-0ubuntu1) maverick; urgency=low
[ Dave Walker (Daviey) ]
* New upstream merge, r1224, should fix LP: #610259, #609112, #613033
* debian/patches/10-disable-iscsi.patch: Removed, we
** Branch linked: lp:ubuntu/eucalyptus
--
eucalyptus instance reboot fails: Guest moved used index from 0 to 2639
https://bugs.launchpad.net/bugs/615529
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Medium
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Medium
--
eucalyptus instance reboot fails: Guest moved used index from 0 to 2639
https://bugs.launchpad.net/bugs/615529
You received this bug notification because
** Branch linked: lp:~ubuntu-virt/ubuntu/maverick/eucalyptus/2.0
--
eucalyptus instance reboot fails: Guest moved used index from 0 to 2639
https://bugs.launchpad.net/bugs/615529
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in
** Attachment added: node controllers' var/log/libvirt/qemu/i-32AA0623.log
http://launchpadlibrarian.net/53360221/libvirt-instance.log
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/53359916/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
Heres some more information, this is a result of work done under the
kernel-upgrades spec [1]. I had originally only used the floppy disk
boot mechanism for scsi root disk, as initial boot works fine with
'-kernel grub_loader' and virtio. If I take change the eucalyptus
code to use a boot floppy
I brought this up in kvm irc and found that -kernel/-initrd booting is
commonly broken, and rharper poitned me at this thread for a recent
discussion: http://lists.gnu.org/archive/html/qemu-
devel/2010-08/msg00133.html .
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
** Branch linked: lp:~smoser/ubuntu/maverick/eucalyptus/bug-615529
--
eucalyptus instance reboot fails: Guest moved used index from 0 to 2639
https://bugs.launchpad.net/bugs/615529
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm
14 matches
Mail list logo
