Bug#841747: installation-reports: Installation Report: Successful installation of testing Stretch via netinstall

2016-10-22 Thread Aaron 
Package: installation-reports
Severity: normal

Dear Maintainer,

Just reporting successful installation, as requested at:
https://www.debian.org/releases/testing/amd64/apas04.html.en



-- Package-specific info:

Boot method: USB
Image version: 
http://cdimage.debian.org/cdimage/stretch_di_alpha7/amd64/iso-cd/debian-stretch-DI-alpha7-amd64-netinst.iso
Date: 

Machine: Compaq laptop BIOS/MBR
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:




-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20160630"
X_INSTALLATION_MEDIUM=hd-media

==
Installer hardware-summary:
==
uname -a: Linux tesla 4.6.0-1-amd64 #1 SMP Debian 4.6.2-2 (2016-06-25) x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series 
Chipset Memory Controller Hub [8086:2a40] (rev 07)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1605]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
lspci -knn: DeviceName: Mobile Intel(R) 4 Series Express Chipset Family
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1605]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 
Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1605]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #4 [8086:2937] (rev 03)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1605]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #5 [8086:2938] (rev 03)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1605]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB2 EHCI Controller #2 [8086:293c] (rev 03)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1605]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) 
HD Audio Controller [8086:293e] (rev 03)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1605]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) 
PCI Express Port 1 [8086:2940] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) 
PCI Express Port 2 [8086:2942] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #1 [8086:2934] (rev 03)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1605]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #2 [8086:2935] (rev 03)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1605]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #3 [8086:2936] (rev 03)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1605]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.3 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #6 [8086:2939] (rev 03)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1605]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB2 EHCI Controller #1 [8086:293a] (rev

Bug#548880: closed by Julien Cristau <jcris...@debian.org> (Bug#548880: fixed in debootstrap 1.0.85)

2016-10-22 Thread Sascha Silbe 
Dear Ansgar, dear Julien,

Debian Bug Tracking System  writes:

[...]
>  debootstrap (1.0.85) unstable; urgency=medium
[...]
>[ Ansgar Burchardt ]
[...]
>* Error out when seeing short options. (Closes: #548880)

Kudos!

Sascha
-- 
Softwareentwicklung Sascha Silbe, Niederhofenstraße 5/1, 71229 Leonberg
https://se-silbe.de/
USt-IdNr.: DE281696641


signature.asc
Description: PGP signature

Re: grub2 menuentry

2016-10-22 Thread Richard Owlett 

On 10/21/2016 10:46 PM, Hussein partovi ghamichi wrote:

hi
i like to know if you can help me
my quesion is
boot and install debian 8.3 iso with grub2 menuentry from hard.
i want a working example


Welcome to Debian.
This question would be more appropriate at 
debian-u...@lists.debian.org .


You need to give a more precise description than "8.3 iso" as 
there are several _significantly_ different files that match.


Where & How did you obtain it?

I predict that you will also be asked why that version?
Debian 8.6 is the current version.

Bug#840720: marked as done (installation-report: stretch/testing setup inside qemu/kvm with virt-manager)

2016-10-22 Thread Debian Bug Tracking System 
Your message dated Sat, 22 Oct 2016 09:06:21 +0200
with message-id <20161022090621.2316e3da@a68n.lokal>
and subject line not waiting for anything
has caused the Debian Bug report #840720,
regarding installation-report: stretch/testing setup inside qemu/kvm with 
virt-manager
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
840720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: installation-reports
Version: 2.62
Severity: wishlist

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


- -- Package-specific info:

Boot method: iso-img
Image version:
http://gensho.acc.umu.se/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: 2016-10-13

Machine: kvm vm, see attachment
Partitions:
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs500520   0500520   0% /dev
tmpfs  tmpfs   1020283420 98608   4% /run
/dev/vda1  xfs   11523072 3138444   8384628  28% /
tmpfs  tmpfs   510132  68510064   1% /dev/shm
tmpfs  tmpfs 5120   4  5116   1% /run/lock
tmpfs  tmpfs   510132   0510132   0% /sys/fs/cgroup
tmpfs  tmpfs   102024  12102012   1% /run/user/1000
tmpfs  tmpfs   102024   4102020   1% /run/user/109



Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o]
Detect network card:[o]
Configure network:  [o]
Detect CD:  [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives:  [o]
Install base system:[o]
Install tasks:  [o]
Install boot loader:[o]
Overall install:[o]

Comments/Problems:

This is actually not an installer-problem, but one with libvirt or virt-manager
respectively, there is fix necessary in order to be able to start up existing 
virtual
machines:
This is the problem:
> Error starting domain: Requested operation is not valid: network 'default' is 
> not active
> 
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in 
> cb_wrapper
> callback(asyncjob, *args, **kwargs)
>   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 127, in tmpcb
> callback(*args, **kwargs)
>   File "/usr/share/virt-manager/virtManager/domain.py", line 1355, in startup
> self._backend.create()
>   File "/usr/lib/python2.7/dist-packages/libvirt.py", line 999, in create
> if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> libvirtError: Requested operation is not valid: network 'default' is not 
> active

This is the fix:

> root@dop58:/home/remosrv# cd /etc/libvirt/qemu/networks/autostart
> root@dop58:/etc/libvirt/qemu/networks/autostart# ln -s ../default.xml 
> default.xml
> root@dop58:/etc/libvirt/qemu/networks/autostart# ls -la
> total 4
> drwxr-xr-x 1 root root 22 Oct 10 13:48 .
> drwxr-xr-x 1 root root 40 Oct 10 13:45 ..
> lrwxrwxrwx 1 root root 14 Oct 10 13:48 default.xml -> ../default.xml
> root@dop58:/etc/libvirt/qemu/networks/autostart# cat default.xml 
> 
>   default
>   
>   
>   
> 
>   
> 
>   
> 
> 
> root@dop58:/etc/libvirt/qemu/networks/autostart# service libvirtd restart

I also disabled the bridge-netfilter, now I am able to log in to the host with 
SSH,
see: 

> $$ man sysctl.d

VM-configuration attached, also kernel-bootup messages [dmesg-output]

There is a message at bootup. saying that hardware-support for kvm is missing 
inside the
guest, so this would most probably require nested virtualisation, the other 
issue is,
that there is a 90 seconds grace-period at startup while systemd waits for
Network-Manager, which ist not really required inside a VM.

- -- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer