qemu-system-x86_64: There is no option group 'vnc'

Bug #1589272 reported by sl1pkn07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QEMU
Fix Released
Undecided
Unassigned

Bug Description

build qemu from git (6b3532b20b787cbd697a68b383232f5c3b39bd1e)

with this options:

./configure \
    --python=/usr/bin/python2 \
    --prefix=/usr \
    --sysconfdir=/etc \
    --localstatedir=/var \
    --libexecdir=/usr/lib/qemu \
    --target-list=i386-softmmu,x86_64-softmmu,i386-linux-user,x86_64-linux-user \
    --audio-drv-list='pa alsa' \
    --enable-linux-aio \
    --enable-seccomp \
    --enable-tpm \
    --enable-modules \
    --disable-sdl \
    --disable-gtk \
    --disable-spice \
    --disable-rbd \
    --disable-libiscsi \
    --disable-libnfs \
    --disable-smartcard \
    --disable-glusterfs \
    --disable-docs \
    --disable-vnc{,-sasl,-jpeg,-png} \
    --disable-guest-agent

i get:

└───╼ qemu-system-x86_64
qemu-system-x86_64: There is no option group 'vnc'
Segment Fault (core dumped)

└───╼ coredumpctl info 12932
           PID: 12932 (qemu-system-x86)
           UID: 1000 (sl1pkn07)
           GID: 100 (users)
        Signal: 11 (SEGV)
     Timestamp: dom 2016-06-05 18:05:51 CEST (17s ago)
  Command Line: qemu-system-x86_64
    Executable: /usr/bin/qemu-system-x86_64
 Control Group: /user.slice/user-1000.slice/session-c1.scope
          Unit: session-c1.scope
         Slice: user-1000.slice
       Session: c1
     Owner UID: 1000 (sl1pkn07)
       Boot ID: 5b205159fa6b4c25946fad7087bd366f
    Machine ID: c20ee0c57658685bfedf50384b0e3ec0
      Hostname: sL1pKn07
      Coredump: /var/lib/systemd/coredump/core.qemu-system-x86.1000.5b205159fa6b4c25946fad7087bd366f.12932.1465142751000000000000.lz4
       Message: Process 12932 (qemu-system-x86) of user 1000 dumped core.

                Stack trace of thread 12932:
                #0 0x000055b269c2e245 qemu_opts_foreach (qemu-system-x86_64)
                #1 0x000055b2698fb6b5 main (qemu-system-x86_64)
                #2 0x00007fafc4e5a741 __libc_start_main (libc.so.6)
                #3 0x000055b269900eb9 _start (qemu-system-x86_64)

                Stack trace of thread 12934:
                #0 0x00007fafc51e80af pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                #1 0x000055b269c21b19 qemu_cond_wait (qemu-system-x86_64)
                #2 0x000055b26992bff4 qemu_tcg_cpu_thread_fn (qemu-system-x86_64)
                #3 0x00007fafc51e2484 start_thread (libpthread.so.0)
                #4 0x00007fafc4f216dd __clone (libc.so.6)

                Stack trace of thread 12933:
                #0 0x00007fafc51eaebc __lll_lock_wait (libpthread.so.0)
                #1 0x00007fafc51e4b45 pthread_mutex_lock (libpthread.so.0)
                #2 0x000055b269c21a39 qemu_mutex_lock (qemu-system-x86_64)
                #3 0x000055b26992bf51 qemu_mutex_lock_iothread (qemu-system-x86_64)
                #4 0x000055b269c30430 call_rcu_thread (qemu-system-x86_64)
                #5 0x00007fafc51e2484 start_thread (libpthread.so.0)
                #6 0x00007fafc4f216dd __clone (libc.so.6)

builded with GCC 6.1.1

greetings

Revision history for this message
sl1pkn07 (sl1pkn07) wrote :

any notice of this?

Revision history for this message
sl1pkn07 (sl1pkn07) wrote :

the latest commit i can works with with qemu is 70f87e0

Revision history for this message
Thomas Huth (th-huth) wrote :

Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?

Changed in qemu:
status: New → Incomplete
Revision history for this message
sl1pkn07 (sl1pkn07) wrote :

This is fixed long time ago

Greetings

Revision history for this message
Thomas Huth (th-huth) wrote :

OK, thanks, so marking this as "Fix released" now

Changed in qemu:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.