Bug#696877: installation-reports: Wheezy DI-b4-amd64-netboot-mini.iso from an usb stick fails trying to install grub
On 23/01/13 21:42, Steven Chamberlain wrote: Hi, It looks like some code is already there to avoid cdrom or USB install media being used as the grub-install target. In the grub-installer script: 552 # [...] if /cdrom seems 553 # to be a USB stick then (hd0) may not be safe. If we hit either of those 554 # checks, then try the disk containing /boot instead. 555 # The same goes for /hd-media, so avoid installing there as well. 556 cdsrc=$(mount | grep "on /cdrom " | cut -d' ' -f1) 557 cdfs=$(mount | grep "on /cdrom " | cut -d' ' -f5) 558 hdsrc=$(mount | grep "on /hd-media " | cut -d' ' -f1) For hybrid media on USB it seems that /cdrom will be iso9660, so the next thing preventing an install to (hd0) is if cdrom-detect/hybrid is set to true. This seems a bit of a long shot, but in cdrom-detect it looks like this might go wrong if `list-devices cd; list-devices maybe-usb-floppy` finds the install media before `list-devices usb-partition` does. If someone who has hardware that can reproduce this, could please do the following, it could really help explain this: 1. boot a USB install up to the 'Configure the network' step, 2. drop to the Alt-F2 shell, 3. run these commands and note the output from them: # mount | grep cdrom # list-devices cd # list-devices maybe-usb-floppy # list-devices usb-partition # list-devices disk Thanks! Regards, Hi, Here's the output on a (laptop) machine of mine ... # mount | grep cdrom # list-devices cd # list-devices maybe-usb-floppy # list-devices usb-partition /dev/sda4 # list-devices disk /dev/sda At this stage, all the installer can see is the USB stick. I let the installer run on to the partition disks section and the output is then ... # mount | grep cdrom # list-devices cd /dev/sr0 # list-devices maybe-usb-floppy # list-devices usb-partition /dev/sda4 # list-devices disk /dev/sda /dev/sdb So in grub terms the hard-drive is disk 1. After the original installation, /boot/grub/device.map read: (hd0) /dev/disk/by-id /usb-BUFFALO_ClipDrive_A320051021751-0:0 (hd1) /dev/disk/by-id/ata-Hitachi_HTS545025B9A300_100411PBN2061SFS47GT and /boot/grub/grub.cfg had several set root='(hd1,msdos?)' statements. This stuck me as not quite right so I deleted device map and ran update-grub. To avoid confusion, I don't think I'm using a 'hybid media on USB'. I threw together a USB image with both 32- and 64-bit mini.iso and a syslinux menu to choose between them. I didn't go anything specific to create a USB/CD hybird. I hope this helps. I'm willing supply more information if asked. Regards, -- Paul Bryan Roberts pbronline-deb...@yahoo.co.uk -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5101278f.6050...@yahoo.co.uk
Re: #698707 installation-report: Installation Report using USB stick
On Wednesday 23 January 2013, Vincent McIntyre wrote: > Hi Paul, > you said > > > Grub install failed: > > - proposes to install on first hard drive (as always) > > - but first hard drive was the USB stick > > - install failed, USB stick not damaged (whew) > > - post installation: > > - regenerated device map and reinstalled grub bootloader [..] I wish to point to another use case where gub installation fails miserably. In installing an HP DL360G7 I had to use an USB stick as the installation media (the server has not installed a CD reader) AND another usb stick as supplementary media for installing the firmware files for the broadcom ethernets. so i had: /dev/sda1 install media /dev/sdb1 supplementary media /dev/sdc1 target media (smartarray 410 logical volume) The installer installed grub on /dev/sda with root at /dev/sdc using UUID so when I rebooted in the installed system, i had to remove the supplementary media and the devices list was /dev/sda1 install media (now with grub that points to the installed system) /dev/sdb1 installed system root to correct the situation i had to boot the system as described, but removing the install media stick (with grub) while the kernel was at initial loading stage, so the device scan was only /dev/sda1 installed system and wen fully booted, running grub-install and the update-grub and the problem was resolved. ( Please note that another thing (not for this bug) that created havoc in device list is the fact that to load the non-free firmware when it is requested by the installer my auxiliary stick was not autodetected, so i needed to switch console, mount manually the stick under /media and then tell the installer to retry. This however leaved the aux sick mounted since it was absolutely not clear if the installer needed it mounted or not during the other stages of the installation, with the effect of complicating the device map for grub. Maybe an help screen in debian installer at the prompt of aux media that explain how this media must be prepared for the automounting and autounmounting would be very welcome. ) what i think is needed to do is that the grub installation part in debian installer must do two things to catch by default the majority of use cases with minimum user intervention: 1. necessarly present a list of devices where grub can be installed. And maybe automagically removing from taht list the installation media device? 2. set the default drive for grub installation to the drive that contains the root partition selected during disk partitioning. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201301241342.28871.and...@z80.it
Bug#696877: installation-reports: Wheezy DI-b4-amd64-netboot-mini.iso from an usb stick fails trying to install grub
Thanks Paul, On 24/01/13 12:22, Paul Bryan Roberts wrote: > # mount | grep cdrom Ah of course, this is netboot... > # list-devices cd > /dev/sr0 > # list-devices maybe-usb-floppy > # list-devices usb-partition > /dev/sda4 What exactly is sda4; is that where the mini.iso files are? Is it formatted as vfat? > After the original installation, /boot/grub/device.map read: > (hd0) /dev/disk/by-id /usb-BUFFALO_ClipDrive_A320051021751-0:0 As a result, default_bootdev gets set to this. GRUB will install there unless either: * the device is mounted on /cdrom * the device is mounted on /hd-media * the install media was detected as hybrid iso9660 on USB * the device has no partition, and yet it isn't a whole-drive filesystem recognised by grub-probe We need some novel way to detect that the installer is running from the USB stick, but this isn't obvious from /proc/mounts or /proc/cmdline. I suspect that if /dev/sda4 contained a directory ".disk/" containing an empty file named "info", that might result in it being mounted on /cdrom; then grub-installer would decide know not to install there. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51012f8c.9000...@pyro.eu.org
Bug#696877: installation-reports: Wheezy DI-b4-amd64-netboot-mini.iso from an usb stick fails trying to install grub
[quoting from #698707] On 24/01/13 12:42, Andrea Borghi wrote: > 2. set the default drive for grub installation to the drive that contains the > root > partition selected during disk partitioning. That's a good thing to ask, it seems like a more obvious place to start. Currently (hd0) is preferred unless we're able to detect that it is install media. That's the problem currently. *Only* if we'd detected it as install media, we would fall back to: > 575 bootfs=$(findfs /boot) > 576 [ "$bootfs" ] || bootfs="$(findfs /)" (That does a grub probe of /boot or / in the target, or otherwise whatever seems mounted on /target/boot or /target) But wouldn't that be a better default_bootdev, for any grub-legacy/pc/sparc/ieee1275 install? Could we try to determine default_bootdev that way to begin with? It would just require a shuffle round of the code that is already there. I'm picturing something like: > case $ARCH:$grub_package in > *:grub|*:grub-pc|sparc:grub-ieee1275) > # For GRUB installs this should be a better starting point > bootfs=$(findfs /boot) > [ "$bootfs" ] || bootfs="$(findfs /)" > default_bootdev=$(device_to_disk "$bootfs") > ;; > *) > # This was the original default > default_bootdev_os="$($chroot $ROOT grub-mkdevicemap --no-floppy -m > - | head -n1 | cut -f2)" > if [ "$default_bootdev_os" ]; then > default_bootdev="$($chroot $ROOT readlink -f > "$default_bootdev_os")" > else > default_bootdev="(hd0)" > fi > ;; > esac Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51013544.1050...@pyro.eu.org
Bug#696615: Another use-case for this bug
I wish to point to another use case where gub installation fails miserably. In installing an HP DL360G7 I had to use an USB stick as the installation media (the server has not installed a CD reader) AND another usb stick as supplementary media for installing the firmware files for the broadcom ethernets. so i had: /dev/sda1 install media /dev/sdb1 supplementary media /dev/sdc1 target media (smartarray 410 logical volume) The installer installed grub on /dev/sda with root at /dev/sdc using UUID so when I rebooted in the installed system, i had to remove the supplementary media and the devices list was /dev/sda1 install media (now with grub that points to the installed system) /dev/sdb1 installed system root to correct the situation i had to boot the system as described, but removing the install media stick (with grub) while the kernel was at initial loading stage, so the device scan was only /dev/sda1 installed system and when fully booted, running grub-install and the update-grub and the problem was resolved. ( Please note another thing (not for this bug) that created havoc in device list is the fact that to load the non-free firmware when it is requested by the installer my auxiliary stick was not autodetected, so i needed to switch console, mount manually the stick under /media and then tell the installer to retry. This however leaved the aux sick mounted since it was absolutely not clear if the installer needed it mounted or not during the other stages of the installation, with the effect of complicating the device map for grub. Maybe an help screen in debian installer at the prompt of aux media that explain how this media must be prepared for the automounting and autounmounting would be very welcome. ) what i think is needed to do is that the grub installation part in debian installer must do two things to catch by default the majority of use cases with minimum user intervention: 1. necessarily present a list of devices where grub can be installed. (And maybe automagically removing from that list the installation media device?) 2. set the default drive for grub installation to the drive that contains the root partition selected during disk partitioning. and (but this is more an RFE that a bug) in the same menu make the devices multi-selectable for when we are installing to a raid-1 volume. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201301241353.36010.and...@z80.it
Bug#696877: installation-reports: Wheezy DI-b4-amd64-netboot-mini.iso from an usb stick fails trying to install grub
On 24/01/13 12:56, Steven Chamberlain wrote: Thanks Paul, On 24/01/13 12:22, Paul Bryan Roberts wrote: # mount | grep cdrom Ah of course, this is netboot... # list-devices cd /dev/sr0 # list-devices maybe-usb-floppy # list-devices usb-partition /dev/sda4 What exactly is sda4; is that where the mini.iso files are? Yes, sda4 is where the mini.iso files. It's sda4, not sda1, 'cos I formatted the USB stick to have the USB-ZIP geometry according to the notes on http://www.syslinux.org/doc/usbkey.txt. Is it formatted as vfat? No. ext2. That was a mistake because the Debian Installer won't read firmware blobs for wireless network devices from ext2 formatted partitions. Seems you need vfat. After the original installation, /boot/grub/device.map read: (hd0) /dev/disk/by-id /usb-BUFFALO_ClipDrive_A320051021751-0:0 As a result, default_bootdev gets set to this. GRUB will install there unless either: * the device is mounted on /cdrom * the device is mounted on /hd-media * the install media was detected as hybrid iso9660 on USB * the device has no partition, and yet it isn't a whole-drive filesystem recognised by grub-probe We need some novel way to detect that the installer is running from the USB stick, but this isn't obvious from /proc/mounts or /proc/cmdline. I suspect that if /dev/sda4 contained a directory ".disk/" containing an empty file named "info", that might result in it being mounted on /cdrom; then grub-installer would decide know not to install there. Regards, Umm, empty files under .disk/info sounds rather heuristic to me. In that vein, as a first pass, I'd look for the file syslinux (or extlinux usw.) in the root directory. I think it unlikely such boot loaders would be used to boot off a pukka hard-drive. I do like the idea that the grub install in most cases will be to the device with the root partition for the installation just made BUT that would not work with my RAIDed machines. Regards, -- Paul Bryan Roberts pbronline-deb...@yahoo.co.uk -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51015bc2.7090...@yahoo.co.uk
Bug#698877: installation-reports: Install as VM guest - boot from virtual USB stick
Package: installation-reports Severity: normal Tags: d-i Dear Maintainer, Apart from the grub bit, the installation was fine. Well done. See Comments/Problems below. -- Package-specific info: Boot method: USB image Image version: 16-Nov-2012 http://ftp.nl.debian.org/debian/dists/testing/main installer-amd64/current/images/netboot/mini.iso Date: 13-Jan-2013 Machine: kvm-qemu VM Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on rootfs rootfs 575500 188820357448 35% / udevdevtmpfs 10240 0 10240 0% /dev tmpfs tmpfs50896 696 50200 2% /run /dev/disk/by-uuid/... ext4575500 188820357448 35% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 101780 76101704 1% /run/shm /dev/sda6 ext4 1056264 61460994804 6% /home /dev/sda7 ext4 4035648 2762836 1272812 69% /usr /dev/sda8 ext4 1537024 366164 1092780 26% /var /dev/sda9 ext4 1046168 34072 1012096 4% /opt 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: [ ] 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:[E] Overall install:[O] Comments/Problems: To get qemu-kvm to boot the virtual USB stick, it had to be disk 0. The grub installer proposed to install its bootloader on disk 0, which is not what was wanted. However, post-installation device.map reads: (hd0) /dev/disk/by-id/ata-QEMU_HARDDISK_QM1 (hd1) /dev/disk/by-id/ata-QEMU_HARDDISK_QM2 This would make it hard for any heuristic that didn't consider disk contents to tell which 'disk' was installed from and which was installed to. -- 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="7.0 (wheezy) - installer build 20121114" X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: Linux wheezy 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010] lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: Kernel driver in use: ata_piix lspci -knn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03) lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 [1013:00b8] lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: 00:03.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 20) lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: Kernel driver in use: 8139cp lsmod: Module Size Used by lsmod: hfsplus71571 0 lsmod: hfs45877 0 lsmod: minix 27580 0 lsmod: msdos 17077 0 lsmod: fuse 61981 0 lsmod: ufs58774 0 lsmod: qnx4 13184 0 lsmod: ntfs 163839 0 lsmod: reiserfs 192077 0 lsmod: usblp 17343 0 lsmod: usbcore 128640 1 usblp lsmod: usb_common 12354 1 usbcore lsmod: battery13109 0 lsmod: power_supply 13475 1 battery lsmod: efivars17780 0 lsmod: dm_mod 63645 0 lsmod: md_mod 87742 0 lsmod: xfs 594991 0 lsmod: jfs 137196 0 lsmod: ext4 350601 5 lsmod: crc16 12343 1 ext4 lsmod: jbd2 62015 1 ext4 lsmod: ext3 161867 0 lsmod:
Bug#698878: installation-reports: Boot from USB stick 1 - install to USB stick 2
Package: installation-reports Severity: normal Tags: d-i Dear Maintainer, I think the Debian Installer does an excellent job but I have quibbles with: the partitioner's handling of swap the grub installer's handing of USB sticks. See Comments/Problems below. Also my first attempt failed at the Install tasks step. The /var partition was 'only' 1 Gb and that is not enough to netinstall KDE. Put that in your minimum system requirements. -- Package-specific info: Boot method: USB stick Image version: 16-Nov-2012 http://ftp.nl.debian.org/debian/dists/testing/main installer-amd64/current/images/netboot/mini.iso Date: 14-Jan-2013 Machine: i5 Laptop Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on rootfs rootfs 472036 173823273842 39% / udevdevtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 3848361012383824 1% /run /dev/disk/by-uuid/... ext4472036 173823273842 39% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 116 80 1159920 1% /run/shm /dev/sdb6 ext4960504 208324752180 22% /home /dev/sdb7 ext4 3844152 3412248431904 89% /usr /dev/sdb8 ext4 1441280 921828446236 68% /var /dev/sdb9 ext4984696 17628967068 2% /opt $ sudo swapon -s FilenameTypeSizeUsedPriority /dev/sda1 partition 1951740 0 -1 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: [ ] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [F] Install base system:[O] Install tasks: [O] Install boot loader:[F] Overall install:[O] Comments/Problems: The quibble with the partitioner's handling of swap: - by default, the partitioner will use all existing swap partitions - usually this is what is wanted - by default, it will reformat swap partition, changing their UUID - usually no one cares about the UUID - you can't set a label for the swap partition - seems you can for most other partitions Suppose I have a dual boot (or even multi boot) machine. Do I need a distinct swap partition for each bootable installation ? I think not. If I accept the installer's default action and if the other installations have fstabs using *%@^%@^ UUIDs, those fstabs are broken. This may not be noticed for some time. Workaround is to define no swap during installation and do it by hand afterwards. In my case, I want the USB to use the swap partition on the hard-drive. The hard-drive of whatever machine I plug the USB stick into. I don't want an fstab full of UUIDs. I label my swap partitions - swapa (swapb usw). I can't do this during the installation. I do it by hand after for each machine. What would be nice is an option in the installer to use existing swap, either without reformatting or, where compatible, with the old UUID and label. The quibbles with the grub install. There are two. Here's the post-install grub device.map. (hd0) /dev/disk/by-id/usb-Verbatim_STORE_N_GO_TT018706-0:0 (hd1) /dev/disk/by-id/usb-BUFFALO_ClipDrive_A320051021751-0:0 (hd2) /dev/disk/by-id/ata-Hitachi_HTS545025B9A300_100411PBN2061SFS47GT In this case, the proposal to install the grub bootloader to disk 0 was the right guess: the installation was to the Verbatim USB and the Buffalo USB was the installation medium. However, the grub boot menu was not right. Under normal circumstances, the Hitachi hard-drive is hd0 and the Verbatim USB is hd1. I suspect I ended up with a bootable installation only because the Linux kernel images on hd0 and hd1 are the same. I did not want a boot menu that gives me the option of booting the hard drive. The second quibble is the installer did not offer me a choice. -- 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="7.0 (wheezy) - installer build 20121114" X_INSTALLATION_MEDIUM=netboot ==
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * FAILED BUILD: amd64 Jan 22 22:57 debian-cd@pettersson sidamd64 http://cdbuilder.debian.org/cdimage-log/sidamd64 * FAILED BUILD: amd64 Jan 22 22:57 debian-cd@pettersson Asidamd64 http://cdbuilder.debian.org/cdimage-log/Asidamd64 * FAILED BUILD: amd64 Jan 22 22:57 debian-cd@pettersson 5sidamd64 http://cdbuilder.debian.org/cdimage-log/5sidamd64 * FAILED BUILD: amd64 Jan 22 22:57 debian-cd@pettersson 4sidamd64 http://cdbuilder.debian.org/cdimage-log/4sidamd64 Totals: 102 builds (4 failed, 0 old) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1tyxeg-0001y8...@ravel.debian.org
Bug#698909: installation-reports: successful install in GNOME Boxes using kFreeBSD
Package: installation-reports Severity: normal I did a successful install of Debian GNU/kFreeBSD in a GNOME Boxes virtual machine running on a Debian GNU/Linux (wheezy) system. -- Package-specific info: Boot method: GNOME Boxes booted the ISO for me Image version: debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso Date: 2013-01-25 12:02 Machine: GNOME Boxes - virtual machine based on KVM Partitions: see hardware report below 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: During the partitioning section of the installer, I got this message twice, ignoring it worked fine: Could not get identity of device /dev/ada0 - Inappropriate ioctl for device The timezone selection section did not have a GeoIP option, instead I had to manually select my timezone. The mirror selection did not default to http.debian.net nor to cdn.debian.net, instead I had to either manually navigate the long list of countries and mirrors or manually enter a server. When I manually entered http.debian.net, it decided that the mirror was bad and forced me to enter another mirror. The installer logs indicate it couldn't find Suite|Codename in the Release file, trying the wget command it used manually worked fine though. This is the command that GNOME Boxes ran for the installer: /usr/bin/kvm -S -M pc-1.1 -enable-kvm -m 500 -smp 1,sockets=1,cores=1,threads=1 -name debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso 2 -uuid 021d00ef-beaa-a48b-ce53-f11f3e6256c0 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/home/pabs/.libvirt/qemu/lib/debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso 2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-reboot -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/home/pabs/.local/share/gnome-boxes/images/debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso 2,if=none,id=drive-ide0-0-0,format=qcow2,cache=none -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 -drive file=/home/pabs/tmp/debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev user,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:59:c7:b5,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing -vga qxl -global qxl-vga.vram_size=67108864 -device AC97,id=sound0,bus=pci.0,addr=0x4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 This is the command that GNOME Boxes ran for the installed system: /usr/bin/kvm -S -M pc-1.1 -enable-kvm -m 500 -smp 1,sockets=1,cores=1,threads=1 -name debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso 2 -uuid 021d00ef-beaa-a48b-ce53-f11f3e6256c0 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/home/pabs/.libvirt/qemu/lib/debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso 2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/home/pabs/.local/share/gnome-boxes/images/debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso 2,if=none,id=drive-ide0-0-0,format=qcow2,cache=none -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive file=/home/pabs/tmp/debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev user,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:59:c7:b5,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing -vga qxl -global qxl-vga.vram_size=67108864 -device AC97,id=sound0,bus=pci.0,addr=0x4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 I note that the automatic reports listed below contai
Bug#698909: marked as done (installation-reports: successful install in GNOME Boxes using kFreeBSD)
Your message dated Fri, 25 Jan 2013 06:58:30 +0100 with message-id <20130125055830.gk5...@mykerinos.kheops.frmug.org> and subject line Re: Bug#698909: installation-reports: successful install in GNOME Boxes using kFreeBSD has caused the Debian Bug report #698909, regarding installation-reports: successful install in GNOME Boxes using kFreeBSD 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.) -- 698909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal I did a successful install of Debian GNU/kFreeBSD in a GNOME Boxes virtual machine running on a Debian GNU/Linux (wheezy) system. -- Package-specific info: Boot method: GNOME Boxes booted the ISO for me Image version: debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso Date: 2013-01-25 12:02 Machine: GNOME Boxes - virtual machine based on KVM Partitions: see hardware report below 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: During the partitioning section of the installer, I got this message twice, ignoring it worked fine: Could not get identity of device /dev/ada0 - Inappropriate ioctl for device The timezone selection section did not have a GeoIP option, instead I had to manually select my timezone. The mirror selection did not default to http.debian.net nor to cdn.debian.net, instead I had to either manually navigate the long list of countries and mirrors or manually enter a server. When I manually entered http.debian.net, it decided that the mirror was bad and forced me to enter another mirror. The installer logs indicate it couldn't find Suite|Codename in the Release file, trying the wget command it used manually worked fine though. This is the command that GNOME Boxes ran for the installer: /usr/bin/kvm -S -M pc-1.1 -enable-kvm -m 500 -smp 1,sockets=1,cores=1,threads=1 -name debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso 2 -uuid 021d00ef-beaa-a48b-ce53-f11f3e6256c0 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/home/pabs/.libvirt/qemu/lib/debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso 2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-reboot -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/home/pabs/.local/share/gnome-boxes/images/debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso 2,if=none,id=drive-ide0-0-0,format=qcow2,cache=none -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 -drive file=/home/pabs/tmp/debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev user,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:59:c7:b5,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing -vga qxl -global qxl-vga.vram_size=67108864 -device AC97,id=sound0,bus=pci.0,addr=0x4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 This is the command that GNOME Boxes ran for the installed system: /usr/bin/kvm -S -M pc-1.1 -enable-kvm -m 500 -smp 1,sockets=1,cores=1,threads=1 -name debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso 2 -uuid 021d00ef-beaa-a48b-ce53-f11f3e6256c0 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/home/pabs/.libvirt/qemu/lib/debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso 2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/home/pabs/.local/share/gnome-boxes/images/debian-wheezy-DI-b4-kfreebsd-amd64-netinst.iso 2,if=non
Bug#698909: installation-reports: successful install in GNOME Boxes using kFreeBSD
On Fri, 2013-01-25 at 06:58 +0100, Christian PERRIER wrote: > Given that your installation was a complete success, I do as > usual with reports for successful installations: I close the bug..:-) It wasn't a complete success, my report contained a few issues that could/should be polished up, I guess you missed that bit? -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
