** Description changed:
Binary package hint: qemu-kvm
It seems pxe boot with kvm doesn't work in lucid. When I try to boot
with pxe I have this message :
Starting SeaBios (version 0.5.1-20100120_010601-rothera)
No bootable device.
-
- It works well in karmic, it seems the bios
for the second point (pxe rom for e1000 buggy with "No IP address"), it
seems there is the same bug on the redhat bugtracker that solves it:
https://bugzilla.redhat.com/show_bug.cgi?id=494541
and the solution (494541 is a duplicate of 507391)
https://bugzilla.redhat.com/show_bug.cgi?id=507391
*
bug 472485 seems a dupiicate of this bug (at least the point 1: wrong
directory for rom images), it is marked "fix released" while it does not
seem the case
--
pxe boot doesn't work with kvm
https://bugs.launchpad.net/bugs/570870
You received this bug notification because you are a member of Ubun
It works again, but not out of the box
It seems the kvm-pxe package install the rom in the wrong directory :
/usr/share/kvm and qemu-kvm seems to search rom images in
/usr/share/qemu
I copied /usr/share/kvm/pxe-e1000.bin to /usr/share/qemu/pxe-e1000.bin
After that, I have another error message
yes, kvm-pxe is installed, pxe boot works before the upgrade of this
server
--
pxe boot doesn't work with kvm
https://bugs.launchpad.net/bugs/570870
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
** Summary changed:
- pxe boot doesn't work
+ pxe boot doesn't work with kvm
** Description changed:
Binary package hint: qemu-kvm
- It seems pxe boot doesn't work in lucid. When I try to boot with pxe I
- have this message :
+ It seems pxe boot with kvm doesn't work in lucid. When I try to
Public bug reported:
Binary package hint: qemu-kvm
It seems pxe boot doesn't work in lucid. When I try to boot with pxe I
have this message :
Starting SeaBios (version 0.5.1-20100120_010601-rothera)
No bootable device.
It works well in karmic, it seems the bios with qemu-kvm changed, maybe
it'
We had 5 vm on this host :
- 1 debian lenny 64 bits (virtio is used for the network and the block device
with qcow2 format and 256Mo RAM is allocated)
- 2 ubuntu jaunty 64bits (virtio is used for the network and the block device
with qcow2 format and 512Mo RAM is allocated)
- 1 redhat 5 64 bits (
this upstream bug looks like the same (even if the trace doesn't match
exactly) :
http://bugzilla.kernel.org/show_bug.cgi?id=14376
It seems it's a regression between 2.6.30.6 and 2.6.31.2, unfortunately
without solution.
** Bug watch added: Linux Kernel Bug Tracker #14376
http://bugzilla.kern
** Summary changed:
- kernel crash with kvm
+ kernel crash (Oops) with kvm
--
kernel crash (Oops) with kvm
https://bugs.launchpad.net/bugs/476332
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
** Package changed: linux (Ubuntu) => qemu-kvm (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
kernel crash (Oops) with kvm
https://bugs.launchpad.net/bugs/476332
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
same crash again today, after that all vm are down, rebooting the host
is required
--
kernel crash with kvm
https://bugs.launchpad.net/bugs/476332
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
I have exactly the same logging message and same symptoms on an HP
DL360G5 with a p400i controller, but only when I create an lvm snapshot.
--
karmic cciss: error messages on working device
https://bugs.launchpad.net/bugs/413070
You received this bug notification because you are a member of Ubunt
for information, I tested with konsole and the scrollbar works fine
(with termcapinfo xterm* ti@:te@), it's a specific gnome-terminal +
screen combination bug
--
confusing scrollbar behavior in gnome-terminal when using screen-profiles
https://bugs.launchpad.net/bugs/328536
You received this bug
Is it planned to upgrade the kvm kernel module with the version in kvm-
source ?
--
kvm general protection fault on jaunty
https://bugs.launchpad.net/bugs/358836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
** Changed in: kvm (Ubuntu)
Status: New => Confirmed
--
kvm general protection fault on jaunty
https://bugs.launchpad.net/bugs/358836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
I've read bug #356152, if in addition the new scheme is buggy and
unfinished, please, please, go back, revert the gconf variable for
jaunty and rethink for karmic.
I'm really convinced it's a very critical and visible part of the
system, if it's not really clean and clear, it's not a good thing f
"a vocal minority"... that it's too much for me !
I'm not sure it's ubuntu to treat your alpha/beta/rc testers in this
way.
How many comments and how many duplicates will it take for you to
realize that you are wrong (and jaunty is not yet released)? Many people
took the time to argue to prove yo
I retried today, the panic is 100% reproduceable.
As you suggested I have tested with kvm-source and this has solved the
problem, no more panics :-)
Another problem, but it's not related, after the installation completed,
Solaris 10 didn't boot. It's a known problem, see :
http://www.linux-kvm.o
Public bug reported:
Binary package hint: kvm
Today I tried to install solaris 10 on a fresh jaunty in kvm and this has
triggered a general protection fault.
Next week I'll try to install solaris 10 again to see if this is reproduceable.
versions :
# dpkg -l | grep kvm
ii kvm
Just to be more precise, I have nothing against the new notifyosd.
But, I think, there is a problem with update-notifier implementation.
The permanent reminder for "updates available" or "reboot required" is
very important for every users (everyone doesn't want to update or
reboot immediately), t
Entirely agree with ruban, the notifier icon for updates (as implemented
in Intrepid) is simply perfect. As against, no one like unsolicited
windows. Please restore the old behavior.
--
[Jaunty] Removal of Update Notifier is WRONG
https://bugs.launchpad.net/bugs/332945
You received this bug noti
** Bug watch added: SourceForge.net Tracker #2556746
http://sourceforge.net/support/tracker.php?aid=2556746
** Also affects: kvm via
http://sourceforge.net/support/tracker.php?aid=2556746
Importance: Unknown
Status: Unknown
--
freebsd text screen corruption with kvm
https://bugs.
Public bug reported:
Binary package hint: kvm
I just try and kvm in jaunty is affected by this bug, upstream bug
report (with patch) :
http://sourceforge.net/tracker/?func=detail&atid=893831&aid=2556746&group_id=180599
FreeBSD is unusable in kvm with jaunty due to this bug, it works in
intrepid
24 matches
Mail list logo
