Found that my qcow2 disk had corrupted regions before running kvm-img.
Invalidating for now unless I find that the corruption resulted from
qemu-img snapshot creating/removal.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are
Public bug reported:
qemu-utils:
Installed: 1.0+noroms-0ubuntu14.7
This has happened 5 times on my Ubuntu 12.04 VM host so far. This time I got
the stack trace:
Program terminated with signal 11, Segmentation fault.
#0 0x7f82189745f6 in alloc_refcount_block
Public bug reported:
STR:
1. Install 13.04 current in 12.04 LTS kvm machine
2. Change resolution to 800x600 in the guest
3. Log out
4. Log in
Expected results:
Unity desktop is displayed
Actual results:
Virtual machine hangs, restarts (with no kernel panic). Sometimes general
protection fault
So, it looks like not only custom libvirt network is affected but the
standard default too effectively rendering libvirt machines in a desktop
session without any kind of network.
** Summary changed:
- [raring] No ip assigned to bridge and no routes added for routed network
+ [raring] No ip
python-webob:
Installed: 1.1.1-1
HEAD http://.../v1.0/9830818c942e40bbabaad02454524597/public/index.html
200 OK
Date: Fri, 10 Aug 2012 07:36:16 GMT
Accept-Ranges: bytes
ETag: 5b72f5fe49849d509cbb4be3b733e002
Content-Length: 13
Content-Type: text/plain
Last-Modified: Fri, 18 May 2012 14:25:36
** Also affects: python-novaclient (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-novaclient in Ubuntu.
https://bugs.launchpad.net/bugs/939766
Title:
python-novaclient
Since I am being bit by this every time libvirt update is issued I have
put the libvirt binary with the patch attached to my ppa:rye/ppa
archive.
** Patch added: 9905-fix-apparmor-serial-permissions.patch
As I can see on my installation the following happens:
requested_mask=r:: denied_mask=r::
but
virt-aa-helper.c:
865 for (i = 0; i ctl-def-nserials; i++)
866 if (ctl-def-serials[i]
ctl-def-serials[i]-data.file.path)
867 if (vah_add_file(buf,
868
Yes, it looks like my case is vmmouse driver.
I have uninstalled it and virtual machine is usable again.
I updated my bug report to be the duplicate of LP:553081.
Thanks, Marc!
--
[lucid] Stuttering/skipping mouse with Lucid guest
https://bugs.launchpad.net/bugs/560377
You received this bug
Incorrectly reassigned. Just reproduced with vncviewer. Mouse location
is not updated properly.
** Package changed: virt-manager (Ubuntu) = qemu-kvm (Ubuntu)
** Summary changed:
- [lucid] Stuttering mouse in VNC
+ [lucid] Stuttering/skipping mouse with Lucid guest
--
[lucid]
I have just checked alpha1 LiveCD and mouse moves perfectly there, however it
does not leave the virtual screen boundaries.
How is that implemented in later versions?
--
[lucid] Stuttering/skipping mouse with Lucid guest
https://bugs.launchpad.net/bugs/560377
You received this bug notification
Also this isn't the normal VM mouse lagging with the host, this is a plain
stops and doesn't go anywhere for a few seconds.
Confirming that as well, this is not a mouse-only problem.
With alpha1 the mouse move does not trigger any lags. With current
install the following is experienced:
$
virt-manager VNC is affected only, other vnc connections are ok.
** Package changed: qemu-kvm (Ubuntu) = virt-manager (Ubuntu)
** Summary changed:
- [lucid] Stuttering mouse
+ [lucid] Stuttering mouse in VNC
** Changed in: virt-manager (Ubuntu)
Status: New = Confirmed
--
[lucid]
** Changed in: apache2 (Ubuntu)
Status: New = Confirmed
--
apache 2.2.14-5ubuntu4 fails to start with mod_dav_fs enabled
https://bugs.launchpad.net/bugs/551276
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
--
Public bug reported:
Binary package hint: qemu-kvm
As of 2010-03-04 I am unable to boot any linux guests using KVM.
This is an a part of the logs where Oops happens, full guest boot log is
attached:
[1.781721] Freeing unused kernel memory: 660k freed
[1.809907] Write protecting the
** Attachment added: guest kernel boot serial output
http://launchpadlibrarian.net/40142006/kvm-guest-oops-serial-output.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/40141861/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
** Summary changed:
- [lucid] All linux guests oops during boot (9.04, 9.10, 10.04)
+ [lucid] All linux guests oops in kvm_leave_lazy_mmu during boot (9.04, 9.10,
10.04)
--
[lucid] All linux guests oops in kvm_leave_lazy_mmu during boot (9.04, 9.10,
10.04)
Hello,
I am experiencing this issue with:
qemu-kvm 0.12.3-0ubuntu4
Linux buzz 2.6.32-15-generic #22-Ubuntu SMP Tue Mar 2 02:24:17 UTC 2010 i686
GNU/Linux
I was able to start the vms by rebooting into
Linux buzz 2.6.32-14-generic #20-Ubuntu SMP Sat Feb 20 05:38:50 UTC 2010 i686
GNU/Linux
So
Dustin,
That happens even when I'm just trying to start ubuntu cd off an ide
emulation. The guest kernel finds out that it runs in kvm and commits
suicide.
--
[lucid] All linux guests oops in kvm_leave_lazy_mmu during boot (9.04, 9.10,
10.04)
https://bugs.launchpad.net/bugs/531823
You received
@Stefan,
I can confirm that guests no longer die with the host kernel version you placed.
Linux buzz 2.6.32-15-generic #22+kvmfix1 SMP Thu Mar 4 22:13:32 UTC 2010 i686
GNU/Linux
P.S. The correct link is http://people.canonical.com/~smb/bug531823.
--
[lucid] All linux guests oops in
This bug may be closed since Ubuntu Karmic comes with qemu-kvm-0.11.0 released
way after KVM-80 which fixed the original problem.
The bug report for libvirt not supporting domain reboots is filed under Bug
#368962
--
kvm - guest freebsd 7 - reboot problems
Reproducible on 8.04, no longer reproducible on 8.10a6.
--
dhcp3-client warns about nonexisting pid
https://bugs.launchpad.net/bugs/219929
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
Ubuntu-server-bugs mailing
Frankly speaking, I could not find the code that can creates the empty
file, but here are the steps to reproduce:
1. Find interface that is not connected (to simplify tests), in my case
it is eth0.
2. Run and interrupt the client:
sudo dhclient eth0
[sudo] password for rtg:
Internet Systems
Public bug reported:
Binary package hint: dhcp3-client
In case pid file does not contain any pid, the message
There is already a pid file /var/run/dhclient.pid with pid 134519120
is printed with random unbelievable pids.
This bugs comes from dhclient.c.stale-pids.dpatch
...
@@ -251,11 +251,17
24 matches
Mail list logo
