Boris, this is EC2. Xen 4.2 with a default config.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
To manage notifications about this bug go to:
I don't understand what the file argument would mean. Once you write()
to a file, QEMU no longer can implement a ring buffer (it cannot discard
written data). You would need to do something like the following:
qemu -chardev memchr,max-capacity=640k,id=foo -serial chardev:foo
And then introduce
I don't understand what the file argument would mean. Once you write()
to a file, QEMU no longer can implement a ring buffer (it cannot discard
written data). You would need to do something like the following:
qemu -chardev memchr,max-capacity=640k,id=foo -serial chardev:foo
And then introduce
savevm section or instance 'hpet' 0
Error -22 while loading VM state
Regards,
Anthony Liguori
If I do, on O1,
qemu-system-x86_64 -M pc-0.14 -vnc :1 -m 512 -cdrom
debian-testing-amd64-businesscard.iso -monitor stdio -hda /mnt/x.qcow2 -net
user -net nic,model=rtl8139 -S
(qemu) loadvm /mnt
** Changed in: qemu
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/948675
Title:
QEMU is crashing when called with -vga none
To manage notifications about
We can always improve the information to the user for something like so
I've marked this as wishlist.
** Changed in: qemu
Importance: Undecided = Wishlist
** Changed in: qemu
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team,
We can always improve the information to the user for something like so
I've marked this as wishlist.
** Changed in: qemu
Importance: Undecided = Wishlist
** Changed in: qemu
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is a legacy behavior in QEMU. There are a number of legitimate use
cases where a user may only have read access to an image and as long as
that image is mounted read-only, everything will work okay.
Virtio and SCSI will expose the read-only attribute to the guest so it
should be very
This is a legacy behavior in QEMU. There are a number of legitimate use
cases where a user may only have read access to an image and as long as
that image is mounted read-only, everything will work okay.
Virtio and SCSI will expose the read-only attribute to the guest so it
should be very
Removing 'insmod gfxterm' and 'insmod vbe' let's the guest boot up.
The full output of the error message is:
error: no suitable mode found.
error: unknown command `terminal'.
out of range pointer 0x8022
Aborted: Press any key to exit.
The first error is from
** Changed in: qemu
Status: New = Confirmed
--
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/697197
Title:
Empty password allows access to VNC in libvirt
--
** Changed in: qemu
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/697197
Title:
Empty password allows access to VNC in libvirt
--
ubuntu-bugs mailing list
Please do not file bugs against upstream unless they've been explicitly
reproduced against an upstream version. Thanks.
** Changed in: qemu
Status: New = Invalid
--
KVM 9.10 crashes for suse-10 as guest
https://bugs.launchpad.net/bugs/563582
You received this bug notification because
Please do not file bugs against upstream unless they've been explicitly
reproduced against an upstream version. Thanks.
** Changed in: qemu
Status: New = Invalid
--
KVM 9.10 crashes for suse-10 as guest
https://bugs.launchpad.net/bugs/563582
You received this bug notification because
cache=writethrough and cache=none have equivalent data integrity.
FWIW, I believe most recent versions of virt-manager default to
cache=none for physical devices.
--
LVM backed drives should default to cache='none'
https://bugs.launchpad.net/bugs/568445
You received this bug notification
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu
Status: New = Invalid
--
qemu fail to parse command -net none
https://bugs.launchpad.net/bugs/599617
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu
Status: New = Invalid
--
qemu fail to parse command -net none
https://bugs.launchpad.net/bugs/599617
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The '/' character is used to create special expressions if double quotes
aren't used.
** Changed in: qemu
Status: New = Invalid
--
qemus pmemsave doesn't accept / in filename
https://bugs.launchpad.net/bugs/543478
You received this bug notification because you are a member of Ubuntu
The '/' character is used to create special expressions if double quotes
aren't used.
** Changed in: qemu
Status: New = Invalid
--
qemus pmemsave doesn't accept / in filename
https://bugs.launchpad.net/bugs/543478
You received this bug notification because you are a member of Ubuntu
Patches should go to qemu-devel, not bug reports.
** Changed in: qemu
Status: New = Invalid
--
qemu-nbd slow and missing writeback cache option
https://bugs.launchpad.net/bugs/595117
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Patches should go to qemu-devel, not bug reports.
** Changed in: qemu
Status: New = Invalid
--
qemu-nbd slow and missing writeback cache option
https://bugs.launchpad.net/bugs/595117
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: meanwhile (Ubuntu)
Status: New = Confirmed
--
Meanwhile user status detection broken
https://bugs.launchpad.net/bugs/264752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: qemu
Assignee: (unassigned) = Anthony Liguori (anthony-codemonkey)
--
virsh save is very slow
https://bugs.launchpad.net/bugs/524447
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
This actually turns out to be related to dd's default block size. By
default, dd uses a block size of 512. The effect of this is that qemu
fills the pipe buffer very quickly because dd just is submitting very
small requests (that will require a RMW).
If you set an explict block size with dd
You can disable scaling by hitting ctrl-alt-u.
What's probably happening is that the window manager is generating an
extraneous scaling event. I'm going to move this to wishlist as we
should provide better user controls of this behavior.
** Changed in: qemu
Importance: Undecided = Wishlist
I see no indication that this is actually a qemu issue. If there's any
evidence that it is, please reopen.
** Changed in: qemu
Status: New = Invalid
--
kernel NULL pointer in -virtual (-server) kernel
https://bugs.launchpad.net/bugs/546458
You received this bug notification because you
I think the preferred way to do this is just to create a /proc/cpuinfo
file within the root file system. It's impossible for qemu to know
which file is /proc/cpuinfo because you can technically mount procfs
anywhere.
** Changed in: qemu
Status: New = Invalid
--
Should emulate
kvm-84 is very old. Please try to reproduce this against the latest
qemu git or at least 0.12.4.
** Changed in: qemu
Status: New = Incomplete
--
usb_add of a Creative ZEN unrecognized in guest
https://bugs.launchpad.net/bugs/241119
You received this bug notification because you are a
*** This bug is a duplicate of bug 391879 ***
https://bugs.launchpad.net/bugs/391879
** This bug has been marked a duplicate of bug 391879
migrate exec ignores exit status
--
migrate exec hangs for several minutes if the pipe is closed before all its
data is written
The attached patch works for me with the posted test case.
** Changed in: qemu
Status: Confirmed = In Progress
** Patch added: 0001-migration-respect-exit-status-with-exec.patch
http://launchpadlibrarian.net/49572236/0001-migration-respect-exit-status-with-exec.patch
--
migrate exec
I'm marking this as Won't Fix in qemu as it doesn't seem like a good
idea for us to automatically resize the terminal for a user.
I'd suggest using a wrapper script if this is a desirable behavior for
you.
** Changed in: qemu
Status: Confirmed = Won't Fix
--
gnome-terminal should
We use SDL fullscreen mode which currently implements the behavior
you're describing.
** Changed in: qemu
Status: Confirmed = Invalid
--
ctl+alt+F does not leave full screen
https://bugs.launchpad.net/bugs/483251
You received this bug notification because you are a member of Ubuntu
** Changed in: qemu
Status: Confirmed = Invalid
--
kernel stacktrace on volume detach in kvm guest
https://bugs.launchpad.net/bugs/458201
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
** Changed in: qemu
Status: Fix Committed = Fix Released
--
dynamic block device attach/detach not functional with karmic KVM
https://bugs.launchpad.net/bugs/432154
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in
** Changed in: qemu
Assignee: (unassigned) = Anthony Liguori (anthony-codemonkey)
--
virsh save is very slow
https://bugs.launchpad.net/bugs/524447
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
This actually turns out to be related to dd's default block size. By
default, dd uses a block size of 512. The effect of this is that qemu
fills the pipe buffer very quickly because dd just is submitting very
small requests (that will require a RMW).
If you set an explict block size with dd
You can disable scaling by hitting ctrl-alt-u.
What's probably happening is that the window manager is generating an
extraneous scaling event. I'm going to move this to wishlist as we
should provide better user controls of this behavior.
** Changed in: qemu
Importance: Undecided = Wishlist
I see no indication that this is actually a qemu issue. If there's any
evidence that it is, please reopen.
** Changed in: qemu
Status: New = Invalid
--
kernel NULL pointer in -virtual (-server) kernel
https://bugs.launchpad.net/bugs/546458
You received this bug notification because you
I think the preferred way to do this is just to create a /proc/cpuinfo
file within the root file system. It's impossible for qemu to know
which file is /proc/cpuinfo because you can technically mount procfs
anywhere.
** Changed in: qemu
Status: New = Invalid
--
Should emulate
kvm-84 is very old. Please try to reproduce this against the latest
qemu git or at least 0.12.4.
** Changed in: qemu
Status: New = Incomplete
--
usb_add of a Creative ZEN unrecognized in guest
https://bugs.launchpad.net/bugs/241119
You received this bug notification because you are a
*** This bug is a duplicate of bug 391879 ***
https://bugs.launchpad.net/bugs/391879
** This bug has been marked a duplicate of bug 391879
migrate exec ignores exit status
--
migrate exec hangs for several minutes if the pipe is closed before all its
data is written
The attached patch works for me with the posted test case.
** Changed in: qemu
Status: Confirmed = In Progress
** Patch added: 0001-migration-respect-exit-status-with-exec.patch
http://launchpadlibrarian.net/49572236/0001-migration-respect-exit-status-with-exec.patch
--
migrate exec
** Changed in: qemu
Status: New = Invalid
--
does not pass pressed caps lock to client
https://bugs.launchpad.net/bugs/427612
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm marking this as Won't Fix in qemu as it doesn't seem like a good
idea for us to automatically resize the terminal for a user.
I'd suggest using a wrapper script if this is a desirable behavior for
you.
** Changed in: qemu
Status: Confirmed = Won't Fix
--
gnome-terminal should
We use SDL fullscreen mode which currently implements the behavior
you're describing.
** Changed in: qemu
Status: Confirmed = Invalid
--
ctl+alt+F does not leave full screen
https://bugs.launchpad.net/bugs/483251
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: qemu
Status: Confirmed = Invalid
--
kernel stacktrace on volume detach in kvm guest
https://bugs.launchpad.net/bugs/458201
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu
Status: New = Invalid
--
import qemu-user-static from debian
https://bugs.launchpad.net/bugs/548346
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: qemu
Status: Fix Committed = Fix Released
--
dynamic block device attach/detach not functional with karmic KVM
https://bugs.launchpad.net/bugs/432154
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
beagleboard is not in upstream QEMU. Please do not mark bugs as affects
upstream QEMU unless you've actually reproduced the problem with
upstream QEMU.
** Changed in: qemu
Status: New = Invalid
--
apt/dpkg in qemu-system-arm hangs if a big task is installed
If someone reproduces the bug against upstream qemu, feel free to refile
the bug with the appropriate information.
--
apt/dpkg in qemu-system-arm hangs if a big task is installed
https://bugs.launchpad.net/bugs/532733
You received this bug notification because you are a member of Ubuntu
Server
beagleboard is not in upstream QEMU. Please do not mark bugs as affects
upstream QEMU unless you've actually reproduced the problem with
upstream QEMU.
** Changed in: qemu
Status: New = Invalid
--
apt/dpkg in qemu-system-arm hangs if a big task is installed
If someone reproduces the bug against upstream qemu, feel free to refile
the bug with the appropriate information.
--
apt/dpkg in qemu-system-arm hangs if a big task is installed
https://bugs.launchpad.net/bugs/532733
You received this bug notification because you are a member of Ubuntu
Bugs,
I can confirm that the package in #45 fixes the problem.
--
[lucid] Blank screen with KMS on Thinkpad X201 with Arrandale (i915)
https://bugs.launchpad.net/bugs/554569
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
The use-case of virt-manager is casual desktop virtualization. Usually,
a user of desktop virtualization benefits from using the host page cache
because subsequent launches of a VM are considerably faster since the IO
is kept in memory.
You can manipulate the cache settings via libvirt XML if
http://wiki.qemu.org/Features/HelperNetworking
We plan on addressing this upstream by introducing a helper to create
the tap device. This helper would be owned by root, and would be
limited in what it did with the tap device (in terms of attaching it to
a bridge).
This allows a sysadmin to
http://wiki.qemu.org/Features/HelperNetworking
We plan on addressing this upstream by introducing a helper to create
the tap device. This helper would be owned by root, and would be
limited in what it did with the tap device (in terms of attaching it to
a bridge).
This allows a sysadmin to
You can use an ANSI sequence to resize a terminal. The following works
in gnome-terminal:
echo -en '\033[8;25;80t' qemu -curses ...
But it's somewhat impolite to resize a user's terminal automatically
though.
--
gnome-terminal should default to 80x25 for application compatibility
qemu-img snapshot and savevm are different mechanisms. I'd suggest
closing this bug and opening a separate one for savevm.
--
'qemu-img snapshot' crashed, corrupting disk image
https://bugs.launchpad.net/bugs/442598
You received this bug notification because you are a member of Ubuntu
Server
Can you please try to reproduce with an upstream qemu-kvm?
--
oosplash.bin crashed with SIGSEGV in splash_create_window() under KVM
https://bugs.launchpad.net/bugs/273930
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
*** This bug is a duplicate of bug 530077 ***
https://bugs.launchpad.net/bugs/530077
Looks like the install failed to succeed and there was not an MBR
written.
** This bug has been marked a duplicate of bug 530077
kvm: 16-bit code execution failure should be more friendly
--
running
qemu-img snapshot and savevm are different mechanisms. I'd suggest
closing this bug and opening a separate one for savevm.
--
'qemu-img snapshot' crashed, corrupting disk image
https://bugs.launchpad.net/bugs/442598
You received this bug notification because you are a member of Ubuntu
Bugs,
Can you please try to reproduce with an upstream qemu-kvm?
--
oosplash.bin crashed with SIGSEGV in splash_create_window() under KVM
https://bugs.launchpad.net/bugs/273930
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
*** This bug is a duplicate of bug 530077 ***
https://bugs.launchpad.net/bugs/530077
Looks like the install failed to succeed and there was not an MBR
written.
** This bug has been marked a duplicate of bug 530077
kvm: 16-bit code execution failure should be more friendly
--
running
If you accidentally resize the window (even by 1-pixel), then it will
stay in scaled mode even during guest geometry changes.
It sucks from a usability perspective. Clever suggestions about how we
can support scaling in a more friendly way are certainly appreciated.
--
sdl window
If you accidentally resize the window (even by 1-pixel), then it will
stay in scaled mode even during guest geometry changes.
It sucks from a usability perspective. Clever suggestions about how we
can support scaling in a more friendly way are certainly appreciated.
--
sdl window
I don't know what is meant by should emulate /proc/cpuinfo. Can you
please be more specific?
NB, the default CPU that is exposed is a generic one which allows for
maximum portability with respect to live migration. You can use the
'-cpu host' option to expose the underlying host CPU although
I don't know what is meant by should emulate /proc/cpuinfo. Can you
please be more specific?
NB, the default CPU that is exposed is a generic one which allows for
maximum portability with respect to live migration. You can use the
'-cpu host' option to expose the underlying host CPU although
This is a bug in a patch introduced by debian. The patch changes the
behavior of the caplocks key in such a way that it breaks any
application that is actually using SDL correctly. See
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=317010
This patch should be removed from the libsdl package.
This is a bug in a patch introduced by debian. The patch changes the
behavior of the caplocks key in such a way that it breaks any
application that is actually using SDL correctly. See
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=317010
This patch should be removed from the libsdl package.
I don't think we can unconditionally change the behavior as that would
introduce regressions on other platforms.
Without understanding the underlying SDL problem, I'm not convinced we
wouldn't see problems just on Ubuntu either. It could be something
weird that's linked to an SDL input driver.
I don't think we can unconditionally change the behavior as that would
introduce regressions on other platforms.
Without understanding the underlying SDL problem, I'm not convinced we
wouldn't see problems just on Ubuntu either. It could be something
weird that's linked to an SDL input driver.
** Changed in: qemu
Status: New = Fix Released
--
qemu-kvm 0.12.1.1 needed for KSM support (key KVM virtualization feature)
https://bugs.launchpad.net/bugs/500272
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
Status: New = Fix Released
--
qemu-kvm 0.12.1.1 needed for KSM support (key KVM virtualization feature)
https://bugs.launchpad.net/bugs/500272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
1. kvm-img create hda.img 4G
2. kvm -hda hda.img -cdrom jaunty-desktop-i386.iso -m 512
3. Install Ubuntu onto hda
4. Reboot, following the prompts (press enter to eject the CD)
5. System boots into installed OS.
It's the use of '-boot d' that is creating problems for you. By
default, the order=
1. kvm-img create hda.img 4G
2. kvm -hda hda.img -cdrom jaunty-desktop-i386.iso -m 512
3. Install Ubuntu onto hda
4. Reboot, following the prompts (press enter to eject the CD)
5. System boots into installed OS.
It's the use of '-boot d' that is creating problems for you. By
default, the order=
This is expected behavior.
You probably should be using -boot dc. This will cause the VM to boot
into the install OS after installation. This is precisely why
distributions eject the CD after installation (to prevent booting into
the installer again).
** Changed in: qemu
Status: New =
** Changed in: qemu
Status: Fix Committed = Fix Released
--
Block I/O crashes after migration
https://bugs.launchpad.net/bugs/341682
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
--
Ubuntu-server-bugs mailing
Can you please reproduce outside of a eucalyptus environment
** Changed in: qemu
Status: New = Incomplete
--
kernel stacktrace on volume detach in kvm guest
https://bugs.launchpad.net/bugs/458201
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: qemu
Status: Confirmed = Fix Committed
** Changed in: qemu
Milestone: None = 0.12.0
--
dynamic block device attach/detach not functional with karmic KVM
https://bugs.launchpad.net/bugs/432154
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: qemu
Status: Triaged = Incomplete
--
kvm crashed with SIGSEGV in malloc_consolidate()
https://bugs.launchpad.net/bugs/355410
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
** Changed in: qemu
Status: Triaged = Fix Committed
** Changed in: qemu
Milestone: None = 0.12.0
--
qemu mouse and keyboard grab is an accessibility problem
https://bugs.launchpad.net/bugs/237635
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: qemu
Status: Fix Committed = Fix Released
--
2.6.31 guest vm's unable to use virtio
https://bugs.launchpad.net/bugs/403215
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
--
Ubuntu-server-bugs
** Changed in: qemu
Status: Confirmed = Invalid
--
limited screen resolution
https://bugs.launchpad.net/bugs/349331
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
** Changed in: qemu
Milestone: None = 0.12.0
--
KVM crashes when -vga is set to vmware.
https://bugs.launchpad.net/bugs/414885
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
This is expected behavior.
You probably should be using -boot dc. This will cause the VM to boot
into the install OS after installation. This is precisely why
distributions eject the CD after installation (to prevent booting into
the installer again).
** Changed in: qemu
Status: New =
** Changed in: qemu
Status: Fix Committed = Fix Released
--
Block I/O crashes after migration
https://bugs.launchpad.net/bugs/341682
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Can you please reproduce outside of a eucalyptus environment
** Changed in: qemu
Status: New = Incomplete
--
kernel stacktrace on volume detach in kvm guest
https://bugs.launchpad.net/bugs/458201
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: qemu
Status: Confirmed = Fix Committed
** Changed in: qemu
Milestone: None = 0.12.0
--
dynamic block device attach/detach not functional with karmic KVM
https://bugs.launchpad.net/bugs/432154
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: qemu
Status: Triaged = Incomplete
--
kvm crashed with SIGSEGV in malloc_consolidate()
https://bugs.launchpad.net/bugs/355410
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: qemu
Status: Triaged = Fix Committed
** Changed in: qemu
Milestone: None = 0.12.0
--
qemu mouse and keyboard grab is an accessibility problem
https://bugs.launchpad.net/bugs/237635
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: qemu
Milestone: None = 0.12.0
--
KVM crashes when -vga is set to vmware.
https://bugs.launchpad.net/bugs/414885
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.ubuntu.com
** Changed in: qemu
Status: Confirmed = Invalid
--
limited screen resolution
https://bugs.launchpad.net/bugs/349331
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.ubuntu.com
** Changed in: qemu
Status: Fix Committed = Fix Released
--
2.6.31 guest vm's unable to use virtio
https://bugs.launchpad.net/bugs/403215
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: qemu
Status: New = Fix Released
--
Ubuntu 8.04 alpha 5 won't boot in qemu 0.9.1
https://bugs.launchpad.net/bugs/197230
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
http://patchwork.ozlabs.org/patch/35996/
Fixes this issue
** Changed in: qemu
Assignee: (unassigned) = Anthony Liguori (anthony-codemonkey)
** Changed in: qemu-kvm (Ubuntu)
Status: Triaged = Fix Committed
** Changed in: qemu-kvm (Ubuntu)
Assignee: (unassigned) = Anthony
http://patchwork.ozlabs.org/patch/35996/
Fixes this issue
** Changed in: qemu
Assignee: (unassigned) = Anthony Liguori (anthony-codemonkey)
** Changed in: qemu-kvm (Ubuntu)
Status: Triaged = Fix Committed
** Changed in: qemu-kvm (Ubuntu)
Assignee: (unassigned) = Anthony
No, this should not be necessary.
This typically happens for two reasons. The first is that there is
excessive load on the host and this can happen because of a race
condition in the guest. The second, and more common, is that the wrong
bios is in use.
--
Karmic cannot boot on qemu
This behavior will not be demonstrated on current qemu-kvm packages in
Karmic.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Invalid
** Changed in: qemu-kvm (Ubuntu)
Status: Invalid = Fix Released
--
Stock Ubuntu KVM ignores guest synchronous fileIO requests
This behavior will not be demonstrated on current qemu-kvm packages in
Karmic.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Invalid
** Changed in: qemu-kvm (Ubuntu)
Status: Invalid = Fix Released
--
Stock Ubuntu KVM ignores guest synchronous fileIO requests
Please enter your full qemu command line into the bug report.
--
does not pass pressed caps lock to client
https://bugs.launchpad.net/bugs/427612
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
1 - 100 of 172 matches
Mail list logo
