so... I've been tinkering with KVM again. my desktop is windows, the linux server is remote, so I have a ssh X tunnel running, and XMing running locally, and launch virt-manager. opens fine, shows the VM I created some time ago. I select that VM (which is running centos 6), and 'open', a window opens for a few seconds, then blam, virt-manager exits before I can click on the 'details' lightbulb. if I run virt-manager --debug, I get the following output after clicking on 'open'... 2015-10-22 16:08:36,377 (engine:471): window counter incremented to 2 2015-10-22 16:08:36,379 (console:1150): Starting connect process for proto=vnc trans=None connhost=localhost connuser=None connport=None gaddr=127.0.0.1 gport=5900 gsocket=None 2015-10-22 16:08:36,381 (console:378): VNC connecting to localhost:5900 2015-10-22 16:08:37,009 (console:1061): Viewer connected [xcb] Extra reply data still left in queue [xcb] This is most likely caused by a broken X extension library [xcb] Aborting, sorry about that. python: xcb_io.c:576: _XReply: Assertion `!xcb_xlib_extra_reply_data_left' failed. Aborted (core dumped) -- john r pierce, recycling bits in santa cruz
Try giving the VM a Spice display, instead of VNC, see if that helps. Also, on Windows try Mobaxterm SSH client, it comes with X server built-in, perhaps it behaves less crappy. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message -----> From: "John R Pierce" <pierce at hogranch.com> > To: "CentOS mailing list" <centos at centos.org> > Sent: Friday, 23 October, 2015 00:11:15 > Subject: [CentOS] virt-manager> so... I've been tinkering with KVM again. my desktop is windows, > the linux server is remote, so I have a ssh X tunnel running, and XMing > running locally, and launch virt-manager. opens fine, shows the VM I > created some time ago. I select that VM (which is running centos 6), > and 'open', a window opens for a few seconds, then blam, virt-manager > exits before I can click on the 'details' lightbulb. > > if I run virt-manager --debug, I get the following output after clicking > on 'open'... > > 2015-10-22 16:08:36,377 (engine:471): window counter incremented to 2 > 2015-10-22 16:08:36,379 (console:1150): Starting connect process for > proto=vnc trans=None connhost=localhost connuser=None connport=None > gaddr=127.0.0.1 gport=5900 gsocket=None > 2015-10-22 16:08:36,381 (console:378): VNC connecting to localhost:5900 > 2015-10-22 16:08:37,009 (console:1061): Viewer connected > [xcb] Extra reply data still left in queue > [xcb] This is most likely caused by a broken X extension library > [xcb] Aborting, sorry about that. > python: xcb_io.c:576: _XReply: Assertion > `!xcb_xlib_extra_reply_data_left' failed. > Aborted (core dumped) > > > > > > > -- > john r pierce, recycling bits in santa cruz > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos
On 10/22/2015 4:15 PM, Nux! wrote:> Try giving the VM a Spice display, instead of VNC, see if that helps.no idea how to do this, I'm a total newb with KVM. all I actually want to do is attach a USB device to my existing and running KVM, but the instructions for doing this in virtsh are confusing (anything that requires editing XML files tends to give me a headache). specifically, I want the VM 'kfat' to 'own' Bus 005 Device 004: ID 08bb:2704 Texas Instruments Audio Codec ....... OK, I figured it out, I had to create a .xml file like... <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x08bb'/> <product id='0x2704'/> </source> </hostdev> and pass that to virsh attach-device vmname my.xml -- john r pierce, recycling bits in santa cruz