problems with using parallel port

Bug #609055 reported by Wolfgang Lubowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Fix Released
Undecided
Jamie Strandboge

Bug Description

Binary package hint: virt-manager

1)
Description: Ubuntu 10.04 LTS
Release: 10.04

2)
  Installiert: 0.8.2-2ubuntu8
  Kandidat: 0.8.2-2ubuntu8
  Versions-Tabelle:
 *** 0.8.2-2ubuntu8 0
        500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

3) I expected to can use a old parallel dongle (on parallel port) in my guest system (Win XP)

4) When I add my parallel port (I'm not sure if it is /dev/lp0 or /dev/parport0) I can't boot the guest system and get the following output:
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 588, in run_domain
    vm.startup()
  File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup
    self._backend.create()
  File "/usr/lib/python2.6/dist-packages/libvirt.py", line 300, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: monitor socket did not show up.: Connection refused

The dongle is connected to the parallel port and libvirt-qemu has the permission to use this port. I've looked this issue up in google for hours, but didn't find much.

I'm not sure if this is a real bug, but to my mind it's at least a "strange behavior" of virt mangater/qemu/kvm.

regards wolfgang

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: virt-manager 0.8.2-2ubuntu8
ProcVersionSignature: Ubuntu 2.6.32-21.32-server 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-server x86_64
Architecture: amd64
Date: Fri Jul 23 10:02:59 2010
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
PackageArchitecture: all
ProcEnviron:
 LANG=de_AT.utf8
 SHELL=/bin/bash
SourcePackage: virt-manager

Revision history for this message
Wolfgang Lubowski (w-lub) wrote :
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks for reporting this issue.

Could you please attach the output of "dmesg" once you've tried starting your virtual machine?

Changed in virt-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Wolfgang Lubowski (w-lub) wrote :
Download full text (33.0 KiB)

this is the output after starting and before getting the error-message (I fear this isn't the complete output of dmseg, but my terminal doesn't want to give me more :( ):

[ 0.363348] system 00:06: iomem range 0xfed20000-0xfed3ffff has been reserved
[ 0.363350] system 00:06: iomem range 0xfed40000-0xfed8ffff has been reserved
[ 0.363354] system 00:09: iomem range 0xffc00000-0xffefffff has been reserved
[ 0.363358] system 00:0a: iomem range 0xfec00000-0xfec00fff could not be reserved
[ 0.363360] system 00:0a: iomem range 0xfee00000-0xfee00fff has been reserved
[ 0.363364] system 00:0c: ioport range 0xa00-0xadf has been reserved
[ 0.363365] system 00:0c: ioport range 0xae0-0xaef has been reserved
[ 0.363371] system 00:0d: iomem range 0xe0000000-0xefffffff has been reserved
[ 0.363375] system 00:0e: iomem range 0x0-0x9ffff could not be reserved
[ 0.363376] system 00:0e: iomem range 0xc0000-0xcffff has been reserved
[ 0.363378] system 00:0e: iomem range 0xe0000-0xfffff could not be reserved
[ 0.363380] system 00:0e: iomem range 0x100000-0xbddfffff could not be reserved
[ 0.363382] system 00:0e: iomem range 0xfed90000-0xffffffff could not be reserved
[ 0.368054] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:01
[ 0.368057] pci 0000:00:1c.0: IO window: 0xb000-0xbfff
[ 0.368060] pci 0000:00:1c.0: MEM window: 0xc0000000-0xc01fffff
[ 0.368064] pci 0000:00:1c.0: PREFETCH window: 0x000000c0200000-0x000000c03fffff
[ 0.368068] pci 0000:00:1c.1: PCI bridge, secondary bus 0000:02
[ 0.368070] pci 0000:00:1c.1: IO window: 0x1000-0x1fff
[ 0.368074] pci 0000:00:1c.1: MEM window: 0xfe900000-0xfe9fffff
[ 0.368077] pci 0000:00:1c.1: PREFETCH window: 0x000000c0400000-0x000000c05fffff
[ 0.368081] pci 0000:00:1c.3: PCI bridge, secondary bus 0000:03
[ 0.368083] pci 0000:00:1c.3: IO window: 0xc000-0xcfff
[ 0.368087] pci 0000:00:1c.3: MEM window: 0xfea00000-0xfeafffff
[ 0.368090] pci 0000:00:1c.3: PREFETCH window: 0x000000c0600000-0x000000c07fffff
[ 0.368094] pci 0000:00:1c.5: PCI bridge, secondary bus 0000:04
[ 0.368096] pci 0000:00:1c.5: IO window: 0xd000-0xdfff
[ 0.368100] pci 0000:00:1c.5: MEM window: 0xfeb00000-0xfebfffff
[ 0.368103] pci 0000:00:1c.5: PREFETCH window: 0x000000fdf00000-0x000000fdffffff
[ 0.368107] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:05
[ 0.368109] pci 0000:00:1e.0: IO window: 0xe000-0xefff
[ 0.368113] pci 0000:00:1e.0: MEM window: disabled
[ 0.368115] pci 0000:00:1e.0: PREFETCH window: disabled
[ 0.368124] pci 0000:00:1c.0: enabling device (0105 -> 0107)
[ 0.368128] alloc irq_desc for 17 on node -1
[ 0.368130] alloc kstat_irqs on node -1
[ 0.368134] pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 0.368138] pci 0000:00:1c.0: setting latency timer to 64
[ 0.368144] pci 0000:00:1c.1: enabling device (0106 -> 0107)
[ 0.368146] alloc irq_desc for 16 on node -1
[ 0.368147] alloc kstat_irqs on node -1
[ 0.368149] pci 0000:00:1c.1: PCI INT B -> GSI 16 (level, low) -> IRQ 16
[ 0.368152] pci 0000:00:1c.1: setting latency timer to 64
[ 0.368157] alloc irq_desc f...

Revision history for this message
Wolfgang Lubowski (w-lub) wrote :

oops, I'm sorry, at the moment the vm doesn't want to boot at all, although I've removed the serial port from it
but this may be also a bug or strange behavior ;)

P.S.: now I get the following output:
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 588, in run_domain
    vm.startup()
  File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup
    self._backend.create()
  File "/usr/lib/python2.6/dist-packages/libvirt.py", line 300, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: monitor socket did not show up.: Connection refused

regards wolfgang

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

This appears to be related to the apparmor profile in libvirt.

affects: virt-manager (Ubuntu) → libvirt (Ubuntu)
tags: added: apparmor
Changed in libvirt (Ubuntu):
assignee: nobody → Jamie Strandboge (jdstrand)
status: Incomplete → Confirmed
Revision history for this message
Wolfgang Lubowski (w-lub) wrote :

What do you mean with "confirmed"?
Maybe the problem with the parallel port is configuration problem, but that I can't boot the vm (as I've written in post #4) is at least quite strange. :(
Can you help me, please? ;)

Revision history for this message
Wolfgang Lubowski (w-lub) wrote :

now I've changed the rights for /dev/parport0 with chmod to 777 and run qemu out of the terminal, and now it works fine

Changed in libvirt (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (4.7 KiB)

This bug was fixed in the package libvirt - 0.8.3-1ubuntu1

---------------
libvirt (0.8.3-1ubuntu1) maverick; urgency=low

  * Merge from debian unstable with security fixes
  * Fixes:
    - LP: #588369
    - LP: #585964
  * Remaining changes:
    - debian/control:
      + Build-Depends on qemu-kvm, not qemu
      + Build-Depends on open-iscsi-utils, not open-iscsi
      + Build-Depends on libxml2-utils
      + Build-Depends on libapparmor-dev and Suggests apparmor
      + Bump bridge-utils, dnsmasq-base, netcat-openbsd, and iptables
        to Depends of libvirt-bin
      + Drop lvm2, qemu-kvm and qemu to Suggests
      + We call libxen-dev libxen3-dev, so change all references
      + Rename Vcs-* to XS-Debian-Vcs-*
    - debian/libvirt-bin.postinst:
      + rename the libvirt group to libvirtd
      + add each admin user to the libvirtd group
      + reload apparmor profiles
    - debian/libvirt-bin.postrm:
      + rename the libvirt group to libvirtd
      + remove apparmor symlinks on purge
    - debian/README.Debian: add AppArmor section based on the upstream
      documentation
    - debian/rules:
      + update DEB_DH_INSTALLINIT_ARGS for upstart
      + add DEB_MAKE_CHECK_TARGET := check
      + use --with-apparmor
      + copy apparmor and apport hook to debian/tmp
    - add debian/libvirt-bin.upstart
    - debian/libvirt-bin.dirs: add /etc/apparmor.d/abstractions,
      /etc/apparmor.d/disable, /etc/apparmor.d/force-complain,
      /etc/apparmor.d/libvirt, /etc/cron.daily and
      /usr/share/apport/package-hooks
    - add debian/libvirt-bin.cron.daily
    - add debian/libvirt-bin.apport
    - debian/libvirt-bin.install: install apparmor profiles, abstractions
      and apport hook
    - debian/apparmor:
      - add TEMPLATE
      - add libvirt-qemu abstraction
      - add usr.lib.libvirt.virt-aa-helper
      - add usr.sbin.libvirtd
    - debian/patches/series:
      + don't apply 0002-qemu-disable-network.diff.patch
      + don't apply 0005-Terminate-nc-on-EOF.patch. Use
        9009-autodetect-nc-params.patch instead
      + 9000-delayed_iff_up_bridge.patch (refreshed)
      + 9001-dont_clobber_existing_bridges.patch
      + 9002-better_default_uri_virsh.patch (refreshed)
      + 9003-better-default-arch.patch (refreshsed)
      + 9004-libvirtd-group-name.patch
      + 9005-increase-unix-socket-timeout.patch (refreshed)
      + 9006-default-config-test-case.patch
      + 9007-fix-daemon-conf-ftbfs.patch (updated)
      + 9008-run-as-root-by-default.patch (refreshed)
      + 9009-autodetect-nc-params.patch (refreshed)
      + 9010-dont-disable-ipv6.patch (refreshsed)
      + 9011-move-ebtables-script.patch (refreshed)
  * Dropped the following patches included/fixed upstream:
    - 9012-fix-nodeinfotest-ftbfs.patch
    - 9013-apparmor-lp457716.patch
  * Disable virtualbox support since virtualbox-ose is not in main
    - debian/control: remove virtualbox-ose build dependency
    - debian/rules: use --without-vbox
  * debian/patches/9012-apparmor-dont-ignore-open.patch: fix logic when
    using virDomainDiskDefForeachPath() and add tests. This can be removed
    in 0.8.4.
  * debian/apparmor/usr.sbin.libvirtd: add capability fseti...

Read more...

Changed in libvirt (Ubuntu):
status: In Progress → 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.