hallelujah praise the lord
jeje
Sorry, ok great news! The big thing to me is that because 8.04 will I
believe be LTS, it would be terrible not to have this patched. Ok, I'm a
happy little devil now.
Anthony, many thanks for your research and work yeah see you on irc
--
Gutsy Tribe 5 (KVM G
I downloaded an alternate daily build and it works just fine under KVM.
Thanks!
--
Gutsy Tribe 5 (KVM GUEST) needs -no-kvm to install
https://bugs.launchpad.net/bugs/140713
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubunt
Oh, that. It needed a new gfxboot-theme-ubuntu built against the new
gfxboot, that's all. Soren did this on 30 Nov, but it was slightly too
late to make it into the alpha-1 images. It'll be in alpha-2.
** Changed in: gfxboot (Ubuntu)
Assignee: Rick Clark (dendrobates) => Soren Hansen (shawarm
Colin,
Hardy Alpha 1 does not work with KVM. It appears that the CD was not
mastered with the proper version of gfxboot.
To confirm this, I first downloaded the source package for
gfxboot-3.3.28-0ubuntu3 and applied the patches in debian/patches by
hand. I remastered the CD with this version of
Soren believed he'd fixed this a while back, well before Hardy Alpha 1:
gfxboot (3.3.28-0ubuntu3) hardy; urgency=low
* 07_kvm_real_mode.dpatch:
- Apply patch from Steffen Winterfeldt to work around bug in kvm that
makes Ubuntu uninstallable in kvm on Intel hardware.
-- Soren Hansen
Ok, don't flame me for repeating myself here, but flagging this as
Medium is wrong in my view. Wrong for the following reasons:
1) It's easy and quick to patch, and (to me and others) SHOULD have been
done prior to the release of 7.10
2) I work as a systems administrator, and use as much as possi
** Changed in: gfxboot (Ubuntu)
Assignee: (unassigned) => Rick Clark (dendrobates)
--
Gutsy Tribe 5 (KVM GUEST) needs -no-kvm to install
https://bugs.launchpad.net/bugs/140713
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Now that gutsy's been released, can this fix get pulled in so we can at
least make sure that gutsy+1 doesn't have this problem?
--
Gutsy Tribe 5 (KVM GUEST) needs -no-kvm to install
https://bugs.launchpad.net/bugs/140713
You received this bug notification because you are a member of Ubuntu
Bugs,
The gfxboot maintainer has posted a patch that does the same thing in a
different way. I've tested the patch and it works as expected.
>From Steffen Winterfeldt:
Anyway, ss is already saved, so no need for an extra register. Here is
my version (tested and works on my machine):
--- bincode.asm (
Ok, some interesting info, and a fix / work around.
To install a guest (Tested this with Ubuntu Gutsy Beta), remaster the
ISO with the bootlogo file removed. At the boot line, use vga mode, eg:
install vga=791
Your guest installation will install fast, and perfectly.
Anthony has written a small
I can confirm this works. Here is the binary bootlogo file I used if
anyone wants to skip the build process and jump straight to the copy
Great work Anthony!!
Ben, can you get this in before final?
** Attachment added: "Binary bootlogo patched to work with KVM"
http://launchpadlibrarian.net/9
I should add that for now, it's necessary to use -std-vga on the qemu
command line until we fix the graphics updating issue in KVM.
--
Gutsy Tribe 5 (KVM GUEST) needs -no-kvm to install
https://bugs.launchpad.net/bugs/140713
You received this bug notification because you are a member of Ubuntu
Bu
Unfortunately there was a small bug in my previous patch. I should have
used a 16 bit mov instead of a 32 bit mov or else data would potentially
leak from ebx into esp. Turns out that in practice, the high bits of
ebx were zero so everything still worked.
To test out the patch, I took a gutsy-de
Hi Anthony,
Thanks for investigating this, and producing a patch, I'm so happy to
hear you have it working. You say you have a remastered Gutsy that
boots. The required changes (binary ones), is it possible you can share,
and a brief description on the remaster process please? I'd like to test
thi
Attached is a patch that fixes the problem with gfxboot. Below is a
link to the KVM bugzilla entry that has a more in-depth explaination of
the problem[1]. There's another bug in KVM that makes the install
screen black[2] but that should get fixed real soon. I have a really
bad hack in the bug e
FYI: Beta release still has same issue
I seriously hope that server release either does not have gfxboot, or
fixes this issue
--
Gutsy Tribe 5 (KVM GUEST) needs -no-kvm to install
https://bugs.launchpad.net/bugs/140713
You received this bug notification because you are a member of Ubuntu
TJ, I'd recommend building the kvm-44, for me it's preforming very well,
and stable, but as I said thats on pre-installed guests, I have not
attempted a guest installation with it.
--
Gutsy Tribe 5 (KVM GUEST) needs -no-kvm to install
https://bugs.launchpad.net/bugs/140713
You received this bug n
My issue might be another symptom, but the guest is an empty image - no
installed OS - that I'd expect to run BIOS and then report "No System
Disk" and stop, waiting. I've had that before when forgetting to aim the
CD at an installer ISO image.
It worked okay about a week ago when I installed Wind
Hi TJ,
I have no problem booting installed guests (Gutsy, XP, Vista = 100%)
when running KVM (kvm-44), from what I hear you saying, you can't boot
an installed Gutsy guest... if so, that's odd, however I am running
32-Bit host and guests.
Hopefully this gfxboot issue will be resolved, as personal
I'm seeing the same issue on Gutsy 64-bit with kvm-intel:
kernel: [ 1093.429150] emulation failed but !mmio_needed? rip a45 f4 eb
fd 89
And the bug-trace in the terminal.
To being with I had thought it was the Gutsy ISO I was trying to boot,
so I removed that.
However, I'm seeing it whenever /d
Here's a response I received from Steffen Winterfelt (the author of
gfxboot). I think this confirms that it's a KVM issue. I'm going to
open an issue on the KVM SourceForge tracker.
> Could you point to either where this check is happening, the proper place to
> ask, or the revision control syst
$ sudo /usr/local/kvm-40/bin/qemu-system-x86_64 -localtime -m 1024 -cdrom
gutsy-alternate-testing5-i386.iso -boot d
Password:
exception 13 (33)
rax 0469 rbx 0081 rcx 4300 rdx
rsi 0005961d rdi 0005961c rsp fffaa9cc rbp
FYI, SLES10 did boot correctly, as did GRML 1.0. None of the *ubuntu ISO
did :-\
OpenSUSE 10.3 beta, failed in the same way as Gutsy, with a crash dump
--
Gutsy Tribe 5 (KVM GUEST) needs -no-kvm to install
https://bugs.launchpad.net/bugs/140713
You received this bug notification because you are
Though it's not clear to me that that patch is still there. Hard to tell
- the code was refactored a lot since then.
--
Gutsy Tribe 5 (KVM GUEST) needs -no-kvm to install
https://bugs.launchpad.net/bugs/140713
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
Gutsy currently has gfxboot 3.3.28-ubuntu2. A work around was added for
Xen guests running on VT for gfxboot 3.2.35-1. The current issue we're
seeing with gfxboot under KVM is very likely a bug in KVM.
--
Gutsy Tribe 5 (KVM GUEST) needs -no-kvm to install
https://bugs.launchpad.net/bugs/140713
This is a problem because intel hw does not provide big real mode, and
expects software to handle it. Gfxboot causes the installer to stop at
the gfx boot screen. According to #kvm, suse has a patch in gfxboot that
detects kvm install and does not attempt to use big real mode, and
allows things to
26 matches
Mail list logo
