Bug#991133: bible-kjv: Search no longer works after upgrading to Bullseye

[Regis Smith]

Package: bible-kjv
Version: 4.32
Severity: normal

Dear Maintainer,

   * What led up to the situation?

I upgraded from Buster to Bullseye

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I tried a search in bible-kjv using "??"

   * What was the outcome of this action?

It reported no results:

bible(KJV) [Gen1:1]> ??hath
  Searching for 'hath'... not found.

Searching for any term shows "not found".

   * What outcome did you expect instead?

The same behavior in the Buster package.  When doing the search in
Buster I get 1840 refs:

bible(KJV) [Gen1:1]> ??hath
  Searching for 'hath'... [1840 refs]


-- System Information:
Debian Release: 11.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bible-kjv depends on:
ii  bible-kjv-text  4.32
ii  libc6   2.31-12
ii  libreadline88.1-1

bible-kjv recommends no packages.

Versions of packages bible-kjv suggests:
pn  verse  

-- no debconf information

Bug#925899: lxc: Unprivileged containers fail to start after recent updates

[Regis Smith]

On Sun, 31 Mar 2019 14:55:52 +0200 intrigeri 
wrote:
> Hi,
> 
> Regis Smith:
> >> > lxc-start: test: lsm/apparmor.c: apparmor_prepare: 974 Cannot
use
> > generated profile: apparmor_parser not available
> 
> I've reproduced this problem and I could fix it with:
> 
>   lxc.apparmor.profile = unconfined
> 
> Regis, can you please confirm this fix works for you as well?
> 

Yes, this works.  Thanks!  This was the old solution required in Jessie
or early Stretch (w/o backports), so people may still complain after
Buster is released :)  But I'm happpy if I can reliably start
unprivileged containers again, which "unconfined" does.

Regis

Bug#925899: lxc: Unprivileged containers fail to start after recent updates

[Regis Smith]

Hi!  Thanks for replying.

On Sat, 30 Mar 2019 14:51:47 +0100 Pierre-Elliott =?utf-8?B?QsOpY3Vl?=
 wrote:
> Le mercredi 27 mars 2019 à 22:08:49-0700, Regis Smith a écrit :
> > Package: lxc
> > Version: 1:3.1.0+really3.0.3-6
> > Severity: important
> > 
> > Dear Maintainer,
> > 
> >* What led up to the situation?
> > 
> > apt update; apt upgrade
> > 
> >* What exactly did you do (or not do) that was effective (or
> >  ineffective)?
> > 
> > As a normal user:
> > $ lxc-start -n test
> > 
> >* What was the outcome of this action?
> > 
> > lxc-start: test: lxccontainer.c: wait_on_daemonized_start: 833 No
such file or directory - Failed to receive the container state
> > lxc-start: test: tools/lxc_start.c: main: 330 The container failed
to start
> > lxc-start: test: tools/lxc_start.c: main: 333 To get more details,
run the container in foreground mode
> > lxc-start: test: tools/lxc_start.c: main: 336 Additional
information can be obtained by setting the --logfile and --logpriority
options
> > 
> > If I run it in the foreground instead I get
> > 
> > $ lxc-start -n test -F
> > lxc-start: test: lsm/apparmor.c: apparmor_prepare: 974 Cannot use
generated profile: apparmor_parser not available
> > lxc-start: test: start.c: lxc_init: 899 Failed to initialize LSM
> > lxc-start: test: start.c: __lxc_start: 1917 Failed to initialize
container "test"
> > lxc-start: test: tools/lxc_start.c: main: 330 The container failed
to start
> > lxc-start: test: tools/lxc_start.c: main: 336 Additional
information can be obtained by setting the --logfile and --logpriority
options
> > 
> >* What outcome did you expect instead?
> > 
> > A running container.  These used to work up until recently.  Now I
can't stop
> > already running containers because I won't be able to restart them.
> 
> Hi,
> 
> Thanks for submitting this bug.
> 
> As you can see, it is possible to get more debug via the --logfile
and
> the --logpriority options.
> 
> That said, the first line with the -F option says it all:
> 
> > lxc-start: test: lsm/apparmor.c: apparmor_prepare: 974 Cannot use
> > generated profile: apparmor_parser not available
> 
> It means that you're lacking the apparmor_parser command, which is
> shipped by apparmor. It probably means that you refused to install
> apparmor on your host.

Actually, I do have apparmor installed, and I can run apparmor_parser
as root.  aa-status shows all the related "lxc-container-*" in enforce
mode. Priveleged containers work fine, but I can not start unprivileged
containers.  Both privileged and unpriveleged worked fine before the
updates over the past several weeks.

> 
> You have multiple choices. The first one being installing apparmor,
and
> the second one being to edit your container's configuration (or the
> /etc/lxc/default.conf file) to change the lxc.apparmor.profile
> parameter.
> 
> This bugreport raises an interesting question regarding the tradeoff

I attached the log from running

$ lxc-start -n test --logpriority DEBUG --logfile lxc.log

I commented out "apparmor.profile = generated" and it still doesn't
work.  I'd like to get this working with apparmor, since it's the
default.  However, I'd love to hear from anyone who has unprivileged
containers working on an up-to-date Buster.  The fickleness of LXC in
Stretch wore me out, so I was quite pleased when it worked reliably in
Buster, up until now.

Regis

lxc-start test 20190330180301.167 INFO confile - confile.c:set_config_idmaps:1605 - Read uid map: type u nsid 0 hostid 10 range 65536
lxc-start test 20190330180301.167 INFO confile - confile.c:set_config_idmaps:1605 - Read uid map: type g nsid 0 hostid 10 range 65536
lxc-start test 20190330180301.168 INFO lxccontainer - lxccontainer.c:do_lxcapi_start:961 - Set process title to [lxc monitor] /home/rsmith/.local/share/lxc test
lxc-start test 20190330180301.168 INFO lsm - lsm/lsm.c:lsm_init:50 - LSM security driver AppArmor
lxc-start test 20190330180301.169 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "reject_force_umount  # comment this to allow umount -f;  not recommended"
lxc-start test 20190330180301.169 INFO seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start test 20190330180301.169 INFO seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for reject_force_umount action 0(kill)
lxc-start test 20190330180301.169 INFO seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start test 20190330180301.169 INFO seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for re

Bug#925899: lxc: Unprivileged containers fail to start after recent updates

[Regis Smith]

Package: lxc
Version: 1:3.1.0+really3.0.3-6
Severity: important

Dear Maintainer,

   * What led up to the situation?

apt update; apt upgrade

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

As a normal user:
$ lxc-start -n test

   * What was the outcome of this action?

lxc-start: test: lxccontainer.c: wait_on_daemonized_start: 833 No such file or 
directory - Failed to receive the container state
lxc-start: test: tools/lxc_start.c: main: 330 The container failed to start
lxc-start: test: tools/lxc_start.c: main: 333 To get more details, run the 
container in foreground mode
lxc-start: test: tools/lxc_start.c: main: 336 Additional information can be 
obtained by setting the --logfile and --logpriority options

If I run it in the foreground instead I get

$ lxc-start -n test -F
lxc-start: test: lsm/apparmor.c: apparmor_prepare: 974 Cannot use generated 
profile: apparmor_parser not available
lxc-start: test: start.c: lxc_init: 899 Failed to initialize LSM
lxc-start: test: start.c: __lxc_start: 1917 Failed to initialize container 
"test"
lxc-start: test: tools/lxc_start.c: main: 330 The container failed to start
lxc-start: test: tools/lxc_start.c: main: 336 Additional information can be 
obtained by setting the --logfile and --logpriority options

   * What outcome did you expect instead?

A running container.  These used to work up until recently.  Now I can't stop
already running containers because I won't be able to restart them.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lxc depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  libc6  2.28-8
ii  libcap21:2.25-2
ii  libgnutls303.6.6-2
ii  liblxc11:3.1.0+really3.0.3-6
ii  libseccomp22.3.3-4
ii  libselinux12.8-1+b1
ii  lsb-base   10.2019031300

Versions of packages lxc recommends:
ii  bridge-utils 1.6-2
ii  debootstrap  1.0.114
ii  dirmngr  2.2.12-1
ii  dnsmasq-base [dnsmasq-base]  2.80-1
ii  gnupg2.2.12-1
ii  iproute2 4.20.0-2
ii  iptables 1.8.2-4
ii  libpam-cgfs  1:3.1.0+really3.0.3-6
ii  lxc-templates3.0.3-1
ii  lxcfs3.0.3-2
ii  nftables 0.9.0-2
ii  openssl  1.1.1b-1
ii  rsync3.1.3-6
ii  uidmap   1:4.5-1.1

Versions of packages lxc suggests:
ii  apparmor 2.13.2-9
ii  btrfs-progs  4.20.1-2
ii  lvm2 2.03.02-2
pn  python3-lxc  

-- Configuration Files:
/etc/lxc/default.conf changed:
lxc.net.0.type = veth
lxc.net.0.link = lxcbr0
lxc.net.0.flags = up
lxc.apparmor.profile = generated
lxc.apparmor.allow_nesting = 1


-- debconf information:
* lxc/auto_update_config: true

Bug#889679: xgammon fails to start because of font error

[Regis Smith]

Package: xgammon
Version: 0.99.1128-3+b2
Severity: important

Dear Maintainer,

When starting xgammon from the command line, I get the following error.

$ xgammon 
couldn't load doubler dice font, using default, sorry
X Error of failed request:  BadFont (invalid Font parameter)
  Major opcode of failed request:  55 (X_CreateGC)
  Resource id in failed request:  0x0
  Serial number of failed request:  132
  Current serial number in output stream:  134
$

The program works correctly if given the -doublerfont option with an
appropriate font (from, say, the list generated by xlsfonts).  But, this is
really hard to discover.

-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xgammon depends on:
ii  libc6 2.24-11+deb9u1
ii  libice6   2:1.0.9-2
ii  libsm62:1.2.2-1+b3
ii  libx11-6  2:1.6.4-3
ii  libxaw7   2:1.0.13-1+b2
ii  libxext6  2:1.3.3-1+b2
ii  libxt61:1.1.5-1

xgammon recommends no packages.

xgammon suggests no packages.

-- no debconf information

Bug#832211: RFP: wasora -- Wasora's an advanced suite for optimization and reactor analysis

[Regis Smith]

Package: wnpp
Severity: wishlist

* Package name: wasora
  Version : 0.3.111
  Upstream Author :  Jeremy Theler 
* URL : http://www.talador.com.ar/jeremy/wasora/
* License : GPLv3
  Programming Lang: C
  Description : Wasora's an advanced suite for optimization and reactor 
analysis

>From the web page: "wasora is a free computational tool designed to aid a
cognizant expert---i.e. you, whether an engineer, scientist, technician, geek,
etc.---to analyze complex systems by solving mathematical problems by means of
a high-level plain-text input file containing algebraic expressions, data for
function interpolation, differential equations and output instructions amongst
other facilities."

Wasora provides a very nice workflow for solving and visualizing numerical
problems.  An extensive list of examples can be found here:
http://www.talador.com.ar/jeremy/wasora/realbook/.  It also allows plugins,
including one called besssugo by the same author.  You can see example videos
by scrolling down the page at
http://www.talador.com.ar/jeremy/wasora/besssugo/.

It depends on the GSL and SUNDIALS libraries, which are already in
Debian.  

Bug#826363: aespipe should recommend or require sharutils

[Regis Smith]

Package: aespipe
Version: 2.4c-1
Severity: wishlist

Dear Maintainer,

The sharutils program includes uuencode, which is used in the example script
installed by aespipe at /usr/share/doc/aespipe/examples/bz2aespipe.  The
uuencode program is also used in upstream author's examples of creating random
encryption keys for aespipe and loop-aes.  I think it would make sense to at
least make sharutils a recommended package for aespipe.

-- System Information:
Debian Release: 8.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt25loop-aes (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages aespipe depends on:
ii  libc6  2.19-18+deb8u4

aespipe recommends no packages.

aespipe suggests no packages.

-- no debconf information

Bug#768073: status request

[Regis Smith]

Is the LXD package ready yet?  Pretty please? :)

Bug#770402: nautilus-dropbox on Wheezy destroys Debian's package manager

[Regis Smith]

Package: nautilus-dropbox
Version: 1.4.0-3
Followup-For: Bug #770402

Dear Maintainer,

Installing nautilus-dropbox on Wheezy leads to the hang at "Downloading
Dropbox... 100%" as reported earlier.  This leaves apt in an unrecoverable
state, as apt needs to complete the installation before doing anything else.
Please consider removing this package from Wheezy in the next update.  I think
people like myself who use oldstable don't have time to waste with stuff like
this.

Nevertheless, I'll take this as proper punishment for attempting to install
proprietary software.


-- System Information:
Debian Release: 7.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nautilus-dropbox depends on:
ii  libatk1.0-0  2.4.0-2
ii  libc62.13-38+deb7u8
ii  libcairo-gobject21.12.2-3
ii  libcairo21.12.2-3
ii  libgdk-pixbuf2.0-0   2.26.1-1+deb7u1
ii  libglib2.0-0 2.33.12+really2.32.4-5
ii  libgtk-3-0   3.4.2-7
ii  libnautilus-extension1a  3.4.2-1+build1
ii  libpango1.0-01.30.0-1
ii  policykit-1  0.105-3
ii  procps   1:3.3.3-3
ii  python   2.7.3-4+deb7u1
ii  python-gpgme 0.2-3
ii  python-gtk2  2.24.0-3+b1

nautilus-dropbox recommends no packages.

Versions of packages nautilus-dropbox suggests:
ii  nautilus  3.4.2-1+build1

-- no debconf information

Bug#781566: COPYING2 contains some armchair licensing

[Regis Smith]

On Wed, Apr 1, 2015 at 8:33 AM, Paul Tagliamonte paul...@debian.org wrote:
 On Wed, Apr 1, 2015 at 8:32 AM, Paul Tagliamonte paul...@debian.org wrote:
 
  Intersection, not set of both
 
 
 of course this should read set of both, not intersection :)

Sorry for nitpicking language, but if A and B are sets, what do you mean by the
set of both?  I assume you mean the union of A and B.  So what you say is
correct in that if A and B are distinct licenses, satisfying both licenses
requires all clauses in both licenses to be satisfied, which as a whole is the
union of A and B, not the intersection.

So the union of distinct licenses A and B is a further restriction on A (or B),
which as you note is not allowed by the GPLv2 (#6: ...You may not impose any
further restrictions on the recipients' exercise of the rights granted
herein...).

However, the example (Mon-Tue-Wed) given by the upstream author is correct.
The license A is essentially the intersection of all clauses within A itself,
and so the union of A and B is the intersection of all clauses in both sets
combined (union), hence the confusion.  The upstream author is using
intersection for clauses within the licenses, not the whole license itself.

I don't disagree with your main point--I'm hoping this is useful for upstream.
Apologies if this post seems unnecessary.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#760693: RFP: direvent -- Directory event monitoring daemon

[Regis Smith]

Package: wnpp
Severity: wishlist

* Package name: direvent
  Version : 5.0
  Upstream Author : Sergey Poznyakoff
* URL : http://www.gnu.org.ua/software/direvent/
* License : GPL
  Programming Lang: C
  Description : Directory event monitoring daemon

GNU Direvent monitors events in file system directories using a convenient
command-line interface.  The current version supports Linux, FreeBSD, NetBSD,
OpenBSD, and Darwin.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#755493: (no subject)

[Regis Smith]

Jerome BENOIT wrote:

 Hello There,

 I have just deposited my preliminary material for the Apophenia 
Statistice C library at Alioth:


 http://anonscm.debian.org/cgit/debian-science/packages/apophenia.git

 ...

Is it necessary to require GSL = 1.16?  The version in Wheezy is 1.15, 
and it's easier for
laypeople to make personal backports when the version required is not 
too high.


Regis


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#628535: GNU docs are nonfree, but vrms should think otherwise

[Regis Smith]

Package: vrms
Version: 1.15
Severity: wishlist

vrms classifies GNU documentation (gcc-doc, etc.) as non-free.  But RMS would
never do this.



-- System Information:
Debian Release: 6.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.38-bpo.2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#608005: squeeze mishandles long path strings

[Regis Smith]

Package: squeeze
Version: 0.2.3-8
Severity: normal


$ mkdir abc
$ touch abc/file.txt
$ tar -cf abc/arxiv.tar abc/file.txt
$ squeeze abc/arxiv.tar

(squeeze:4053): thunar-vfs-CRITICAL **: thunar_vfs_path_relative: assertion 
`strchr (name, '/') == NULL' failed

(squeeze:4053): thunar-vfs-CRITICAL **: thunar_vfs_path_to_string: assertion 
`buffer != NULL' failed
Segmentation fault


Using Squeeze from the command line works fine if the path is just a filename
with no parent or child directory (it also works with ~/arxiv.tar or
$HOME/arxiv.tar).  But anything more complicated gives a segfault.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.35.10-ras (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages squeeze depends on:
ii  exo-utils   0.3.107-1Utility files for libexo
ii  libatk1.0-0 1.30.0-1 The ATK accessibility toolkit
ii  libc6   2.11.2-7 Embedded GNU C Library: Shared lib
ii  libcairo2   1.8.10-6 The Cairo 2D vector graphics libra
ii  libdbus-1-3 1.2.24-4 simple interprocess messaging syst
ii  libdbus-glib-1-20.88-2.1 simple interprocess messaging syst
ii  libexo-0.3-00.3.107-1Library with extensions for Xfce
ii  libfontconfig1  2.8.0-2.1generic font configuration library
ii  libfreetype62.4.2-2.1FreeType 2 font engine, shared lib
ii  libglib2.0-02.24.2-1 The GLib library of C routines
ii  libgtk2.0-0 2.20.1-2 The GTK+ graphical user interface 
ii  libpango1.0-0   1.28.3-1 Layout and rendering of internatio
ii  libthunar-vfs-1-2   1.0.2-1+b1   VFS abstraction used in thunar
ii  libxfce4util4   4.6.2-1  Utility functions library for Xfce
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

squeeze recommends no packages.

squeeze suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#607391: qemu-kvm: /dev/kvm should have group id kvm

[Regis Smith]

Package: qemu-kvm
Version: 0.12.5+dfsg-5
Severity: normal


This is just a suggested convenience for users:  change the group ID of 
/dev/kvm to kvm when installing qemu-kvm.

-- Package-specific info:


/proc/cpuinfo:

processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 16
model   : 5
model name  : AMD Athlon(tm) II X4 640 Processor
stepping: 3
cpu MHz : 3013.786
cache size  : 512 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 4
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 5
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni 
monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs skinit wdt
bogomips: 6027.56
TLB size: 1024 4K pages
clflush size: 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

processor   : 1
vendor_id   : AuthenticAMD
cpu family  : 16
model   : 5
model name  : AMD Athlon(tm) II X4 640 Processor
stepping: 3
cpu MHz : 3013.786
cache size  : 512 KB
physical id : 0
siblings: 4
core id : 1
cpu cores   : 4
apicid  : 1
initial apicid  : 1
fpu : yes
fpu_exception   : yes
cpuid level : 5
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni 
monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs skinit wdt
bogomips: 6026.79
TLB size: 1024 4K pages
clflush size: 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

processor   : 2
vendor_id   : AuthenticAMD
cpu family  : 16
model   : 5
model name  : AMD Athlon(tm) II X4 640 Processor
stepping: 3
cpu MHz : 3013.786
cache size  : 512 KB
physical id : 0
siblings: 4
core id : 2
cpu cores   : 4
apicid  : 2
initial apicid  : 2
fpu : yes
fpu_exception   : yes
cpuid level : 5
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni 
monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs skinit wdt
bogomips: 6026.82
TLB size: 1024 4K pages
clflush size: 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

processor   : 3
vendor_id   : AuthenticAMD
cpu family  : 16
model   : 5
model name  : AMD Athlon(tm) II X4 640 Processor
stepping: 3
cpu MHz : 3013.786
cache size  : 512 KB
physical id : 0
siblings: 4
core id : 3
cpu cores   : 4
apicid  : 3
initial apicid  : 3
fpu : yes
fpu_exception   : yes
cpuid level : 5
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni 
monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs skinit wdt
bogomips: 6026.79
TLB size: 1024 4K pages
clflush size: 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate




-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages qemu-kvm depends on:
ii  adduser 3.112+nmu2   add and remove users and groups
ii  bridge-utils1.4-5Utilities for configuring the Linu
ii  iproute 20100519-3   networking and traffic control too
ii  libaio1 0.3.107-7Linux kernel AIO access library - 
ii  libasound2  1.0.23-2.1   shared library for ALSA applicatio
ii  libbluetooth3   4.66-2   Library to use the BlueZ Linux Blu
ii  libbrlapi0.54.2-6braille