[Bug 917824] Re: qemu loops/hangs on extending qcow2-diskspace
sorry, currently I'm busy and there's too much time gone, that I can check the things in a quick way. I'll try it, when I'm less busy, but this will probably take some weeks... -- 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/917824 Title: qemu loops/hangs on extending qcow2-diskspace To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/917824/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 917824] Re: qemu loops/hangs on extending qcow2-diskspace
sorry, currently I'm busy and there's too much time gone, that I can check the things in a quick way. I'll try it, when I'm less busy, but this will probably take some weeks... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/917824 Title: qemu loops/hangs on extending qcow2-diskspace To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/917824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000137] [NEW] speaker icon gone after update
Public bug reported: after the latest update the speaker icon is gone, before it was there and i had no problems with indicator-sound. the same time i updated the following packages: vim-common libunity9 gir1.2unity-5.0 libsasl2-modules vim-tiny gdb indicator-sound-gtk2 indicator-sound libsasl2-2 i'm running Xubuntu 12.04 Xfce 4.8 should i downgrade? just install the old package again? apt-cache policy indicator-sound indicator-sound: Installed: 0.8.5.0-0ubuntu2.1 Candidate: 0.8.5.0-0ubuntu2.1 [...] ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Tags: gone indicator-sound speaker update xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000137 Title: speaker icon gone after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1000137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974229] [NEW] qemu-kvm-1.0: segfault using vnc-console = not threadsafe!
Public bug reported:
after failure using qemu-kvm-0.14.1 I've tried v1.0, but there's a
problem if compiled with vnc-thread-support:
Program received signal SIGSEGV, Segmentation fault.
0x in ?? ()
(gdb) bt
#0 0x in ?? ()
#1 0x7f3ac48ca10a in qemu_iohandler_poll (readfds=0x7fff12379ac0,
writefds=0x7fff12379b40, xfds=0x7fff12379bc0, ret=3)
at iohandler.c:124
#2 0x7f3ac4964387 in main_loop_wait (nonblocking=0) at main-loop.c:463
#3 0x7f3ac4958fb1 in main_loop () at
/opt/workspace/oneiric64/qemu-kvm-1.0/vl.c:1482
#4 0x7f3ac495e1ec in main (argc=68, argv=0x7fff1237a088,
envp=0x7fff1237a2b0)
at /opt/workspace/oneiric64/qemu-kvm-1.0/vl.c:3523
(gdb) up
#1 0x7f3ac48ca10a in qemu_iohandler_poll (readfds=0x7fff12379ac0,
writefds=0x7fff12379b40, xfds=0x7fff12379bc0, ret=3)
at iohandler.c:124
124 ioh-fd_write(ioh-opaque);
(gdb) print *ioh
$4 = {fd = 29, fd_read_poll = 0, fd_read = 0x7f3ac49de158 vnc_client_read,
fd_write = 0, deleted = 0,
opaque = 0x7f3ac7978d50, next = {le_next = 0x7f3ac6add2e0, le_prev =
0x7f3ac52bde90}}
ok, how could that happen?
loooking deeper at the code and backtraces shows, that iohandler.c:124 is
called within the main-loop, while iohandler.c:77 is called within the
vnc-thread-loop
mmmh, but where the hell is the threadsafe-locking of the ioh-
structure
I didn't found anything...
the resetting in line 77 is called from vnc_client_write_plain(), where
following code can be found:
===
if (vs-output.offset == 0) {
qemu_set_fd_handler2(vs-csock, NULL, vnc_client_read, NULL, vs);
}
===
why should the function-ptrs should be zeroed?
further tracing shows, that the vnc-thread sometimes seems to exits
normally and a new one is started (I haven't verified that), but this
would be a reason for zeroing function-ptrs, which may point to code
inside the thread, which will exit...
but why should this be done? and why there's no threadsafe-modification
of the structure?
well: disabling vnc-thread at configure-state leads into a normal
running machine, but threading would be nice here...
so a quick fix could be, to drop the call above and make the vnc-thread staying
for the whole session, but I don't know all mechanisms of vnc-support within
kvm.
but a better solution would be usage of clean locking-mechanisms
** Affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974229
Title:
qemu-kvm-1.0: segfault using vnc-console = not threadsafe!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/974229/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974229] Re: qemu-kvm-1.0: segfault using vnc-console = not threadsafe!
puh, it did take a while, but meanwhile another segfault has occured, which has nothing to do with the above one. due to the long time, it took to happen, it might not be as reproducible as needed for efficient debugging, at least I've currently no further time for this. I'll now try V0.15.1 and hope, it will work well for me. some gdb-info of the current segfault, if there's someone, who want to have a look at: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fe086c46700 (LWP 30362)] 0x7fe08c0639fc in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) thread apply all bt Thread 6 (Thread 0x7fdfa2ecf700 (LWP 30793)): #0 0x7fe08c3963cb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fe08f581c79 in cond_timedwait (cond=0x7fe08fed6b20, mutex=0x7fe08fed6ae0, ts=0x7fdfa2ecee10) at posix-aio-compat.c:104 #2 0x7fe08f5823f0 in aio_thread (unused=0x0) at posix-aio-compat.c:334 #3 0x7fe08c391efc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7fe08c0cc59d in __cmsg_nxthdr () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x in ?? () Thread 5 (Thread 0x7fe087648700 (LWP 30361)): #0 0x7fe08c399a73 in pwrite64 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fe08f58201f in handle_aiocb_rw_linear (aiocb=0x7fe093c98e50, buf=0x7fe093e05600 \004\063\377\211t$\b\213\064$\213\034\272G\205\333\017\204\246) at posix-aio-compat.c:216 #2 0x7fe08f58212d in handle_aiocb_rw (aiocb=0x7fe093c98e50) at posix-aio-compat.c:251 #3 0x7fe08f582573 in aio_thread (unused=0x0) at posix-aio-compat.c:362 #4 0x7fe08c391efc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x7fe08c0cc59d in __cmsg_nxthdr () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x in ?? () Thread 4 (Thread 0x7fe086c46700 (LWP 30362)): #0 0x7fe08c0639fc in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fe08c3851c0 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7fe086c45990 in ?? () #3 0x7fe08c39bc20 in ?? () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7fe086c469c0 in ?? () #5 0x in ?? () Thread 3 (Thread 0x7fe086445700 (LWP 30363)): #0 0x7fe08c0c4747 in getmntent_r () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x in ?? () Thread 2 (Thread 0x7fdfa36d0700 (LWP 30388)): #0 0x7fe08c3963cb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fe08f581c79 in cond_timedwait (cond=0x7fe08fed6b20, mutex=0x7fe08fed6ae0, ts=0x7fdfa36cfe10) at posix-aio-compat.c:104 #2 0x7fe08f5823f0 in aio_thread (unused=0x0) at posix-aio-compat.c:334 #3 0x7fe08c391efc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7fe08c0cc59d in __cmsg_nxthdr () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x in ?? () Thread 1 (Thread 0x7fe08f3cd7a0 (LWP 30158)): #0 0x7fe08c0c5613 in getttyent () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x000f4140 in ?? () #2 0x7fff62c7e3d0 in ?? () #3 0x001d8f675e5c in ?? () #4 0x03e8 in ?? () #5 0x62c7e3c0 in ?? () #6 0x62c7e440 in ?? () #7 0x000162c7e4c0 in ?? () #8 0x3c080980 in ?? () #9 0x in ?? () (gdb) all done on a ubuntu-11.10 64bit, last configure-options were: './configure' '--target-list=x86_64-softmmu i386-softmmu x86_64-linux-user i386-linux-user' '--prefix=/usr' '--interp-prefix=/etc/qemu-binfmt/%M' '--disable-blobs' '--disable-strip' '--audio-drv-list=pa,alsa,sdl,oss' '--enable-vnc-sasl' '--enable-docs' '--enable-vhost-net' '--enable-attr' '--enable-linux-aio' '--enable-uuid' '--enable-nptl' '--enable-kvm-device-assignment' '--enable-kvm-pit' '--enable-kvm' '--enable-curses' '--enable-vnc-png' '--enable-vnc-tls' '--audio-card-list=ac97,es1370,sb16,cs4231a,adlib,gus,hda' '--enable-user' '--enable-system' '--enable-linux-user' '--enable-bsd-user' '--enable-guest-base' '--enable-darwin-user' --enable-debug the segfault occures while installing a larger app within winxp+sp3 near the possible end of setup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974229 Title: qemu-kvm-1.0: segfault using vnc-console = not threadsafe! To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/974229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 917824] Re: qemu loops/hangs on extending qcow2-diskspace
sorry, if it was not as clear as it should be...
the assignment you describe is done until old_allocs is NULL (well the
asm-test checks against zero, I've not looked at the macrodef of
QLIST_FOREACH), but in this special case old_allocs points to address
foobar *and* old_allocs-next_in_flight.le_next points to same address
foobar, too, so it will never become NULL and will endless loop...
gdb shows this:
777 QLIST_FOREACH(old_alloc, s-cluster_allocs, next_in_flight) {
779 uint64_t end_offset = offset + nb_clusters * s-cluster_size;
780 uint64_t old_offset = old_alloc-offset;
779 uint64_t end_offset = offset + nb_clusters * s-cluster_size;
784 if (end_offset old_offset || offset old_end_offset) {
782 old_alloc-nb_clusters * s-cluster_size;
781 uint64_t old_end_offset = old_alloc-offset +
784 if (end_offset old_offset || offset old_end_offset) {
777 QLIST_FOREACH(old_alloc, s-cluster_allocs, next_in_flight) {
(gdb) print old_alloc
$1 = (QCowL2Meta *) 0x34cb7a0
(gdb) print old_alloc-next_in_flight.le_next
$2 = (struct QCowL2Meta *) 0x34cb7a0
I've not analyzed, what is done within the loop, but there should be a point of
another break-possibility.
I've only understood, that there's something done to expand the allocation of
the qcow2-file, because of some needs within the guest.
because I don't know, how I created that certain disk, I've just started
another VM with a newly created disk. this is done via the
virt-manager-interface of libvirt. if this tool simply calls qemu-img or may
make some api-calls by it's own - I don't know, but if it's as important I'll
strace it.
the disk has a maximum of 32768MB with 0 pre-allocated.
qemu-img info say at the current loop (tried to install the soft again):
file format: qcow2
virtual size: 32G (34359738368 bytes)
disk size: 76M
cluster_size: 65536
if you want more output out of gdb, tell me. the VM currently hangs and
now gdb waits for commands...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917824
Title:
qemu loops/hangs on extending qcow2-diskspace
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/917824/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 917824] Re: qemu loops/hangs on extending qcow2-diskspace
sorry forgot the requested cmdline of kvm: kvm -mem-path /VM/tmp -S -M pc-0.12 -cpu qemu32 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name winxp -uuid 1c4f4992-9212-4b4c-a14d-25f2f3f28ed2 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/winxp.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=readline -rtc base=localtime -boot c -device lsi,id=scsi0,bus=pci.0,addr=0x6 -drive file=/VM/winxp/lw-c.img,if=none,id=drive-ide0-0-0,format=qcow2 -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=/VM/winxp/lw-t.img,if=none,id=drive-ide0-0-1,snapshot=on,format=qcow2 -device ide-drive,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -drive file=/VM/winxp/lw-d.img,if=none,id=drive-ide0-1-1,format=qcow2 -device ide-drive,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1 -drive file=/VM/winxp/lw-p.img,if=none,id=drive-scsi0-0-0,format=qcow2 -device scsi-disk,bus=scsi0.0,scsi-id=0,drive=drive-scsi0-0-0,id=scsi0-0-0 -netdev tap,fd=13,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:00:c1:a3:f4:45,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:3 -vga std -device AC97,id=sound0,bus=pci.0,addr=0x4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 the disk, on which the soft should be installed is that one on the emulated scsi-controller -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/917824 Title: qemu loops/hangs on extending qcow2-diskspace To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/917824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 917824] Re: qemu loops/hangs on extending qcow2-diskspace
** Also affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/917824 Title: qemu loops/hangs on extending qcow2-diskspace To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/917824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
