Marking this Fix Released per Scott's comment. If you still see it in
Lucid, please comment here or mark this as affecting lucid.
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: initramfs-tools (Ubuntu)
Status: New = Fix Released
** Changed in:
I believe this is fix-released in maverick. I use -curses when booting
the uec images under kvm. At most, to make it work you have to
blacklist vga16fb.
That path *does* append to /etc/modprobe.d/blacklist.conf before upstart runs.
It adds the following:
blacklist vga16fb
--
Can't use kvm
Still present in Lucid final
--
Can't use kvm -curses with virtual or ec2 kernels
https://bugs.launchpad.net/bugs/569394
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
Michael-
I would absolutely *love* this. I begged for this at Lucid UDS in
Dallas. What would it take to make this happen? I think it would
need to be provided by the Kernel/Foundations team. Can you help
guide this through?
--
Can't use kvm -curses with virtual or ec2 kernels
I ran into this as well and we should really have a common nofb like
switch that is honored by kernel/plymouth etc.
--
Can't use kvm -curses with virtual or ec2 kernels
https://bugs.launchpad.net/bugs/569394
You received this bug notification because you are a member of Ubuntu
Server Team, which
I have encountered the same problem. My workaround is to simply prevent
the vga16fb kernel module from loading in the guest as explained in
http://blog.zorinaq.com/?e=7
--
Can't use kvm -curses with virtual or ec2 kernels
https://bugs.launchpad.net/bugs/569394
You received this bug notification
fb=false is specific to debian-installer (and, as I have mentioned
before to Dustin, fb=0 is out of spec and only works by luck - we won't
hesitate to break that if it results in cleaner code elsewhere); it is
meaningless outside the context of the installer.
--
Can't use kvm -curses with
Dustin, could you try with the -ec2 kernel as well? It's for that
testcase that I added a qemu-kvm task; perhaps this should be a separate
bug though.
--
Can't use kvm -curses with virtual or ec2 kernels
https://bugs.launchpad.net/bugs/569394
You received this bug notification because you are a
What are fb=0 and vga-off supposed to do? Avoid loading any fb modules?
Are these documented/standardized somewhere?
** Package changed: plymouth (Ubuntu) = initramfs-tools (Ubuntu)
--
Can't use kvm -curses with virtual or ec2 kernels
https://bugs.launchpad.net/bugs/569394
You received this
Host is up-to-date lucid RC + updates.
--
Can't use kvm -curses with virtual or ec2 kernels
https://bugs.launchpad.net/bugs/569394
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
Loic-
Try adding fb=0 on your kernel line (or it might be fb=false).
I used to be able to hack the ISO itself with:
* sed -i s/initrd.gz quiet --/initrd.gz fb=0 -- / hardy.iso
I just tried it with current Lucid ISOs and this doesn't work any more
since we've moved to the world of Plymouth on
I also just tried:
kvm -kernel lucid-server-uec-amd64-vmlinuz-virtual -hda lucid-server-
uec-amd64.img -curses -append root=/dev/sda fb=0
This, too, works, until we go into graphic mode. Plymouth, I suppose?
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
** Changed in:
I'll mark confirmed, as I can reproduce this.
However, this bug isn't in qemu-kvm itself. It's in Ubuntu's userspace,
with whatever is not detecting and respecting the fb=0 and vga-off
parameters. Scott, do you know what this would be, and how to disable
it properly?
--
Can't use kvm -curses
13 matches
Mail list logo
