[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#924730: marked as done ("No kernel modules were found" using the direct online installer (virsh))

Your message dated Fri, 29 Mar 2019 12:42:25 +0100
with message-id <20190329114225.o3qm6fbli4woz5bl@mraw.org>
and subject line Re: Bug#924730: "No kernel modules were found" using the direct online installer (virsh)
has caused the Debian Bug report #924730,
regarding "No kernel modules were found" using the direct online installer (virsh)
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 owner@bugs.debian.org
immediately.)


-- 
924730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924730
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: From testing, http://httpredir.debian.org/debian/dists/buster/main/installer-amd64/

Installing Debian 10 as KVM/QEMU guest, host Debian 9.

Virsh-install command:
SCIO virt-install \
--virt-type kvm \
--name "Debian10" \
--vcpus 2 \
--memory 2048 \
--boot uefi \
--cpu host \
--os-variant debiantesting \
--features acpi=on \
--location http://httpredir.debian.org/debian/dists/buster/main/installer-amd64/ \
--disk device=cdrom,bus=scsi \--disk device=disk,path="/vm/Debian10/disk1.qcow2",format=qcow2,cache=unsafe,discard=unmap,bus=scsi \
--controller type=virtio-serial \
--controller type=scsi,model=virtio-scsi \
--network bridge=brLAN,model=virtio, \
--graphics vnc,port=5904,keymap=local,listen=0.0.0.0 \
--noautoconsole


Error, see attached screen-dump.
The installation went better using the DVD iso file.

Attachment: KernelError.jpg
Description: JPEG image


--- End Message ---
--- Begin Message --- 
Hi Brian,

Brian Wengel <m40636067@gmail.com> (2019-03-16):
> Package: debian-installer
> Version: From testing,
> http://httpredir.debian.org/debian/dists/buster/main/installer-amd64/
> 
> Installing Debian 10 as KVM/QEMU guest, host Debian 9.
> 
> Virsh-install command:
> SCIO virt-install \
> --virt-type kvm \
> --name "Debian10" \
> --vcpus 2 \
> --memory 2048 \
> --boot uefi \
> --cpu host \
> --os-variant debiantesting \
> --features acpi=on \
> --location
> http://httpredir.debian.org/debian/dists/buster/main/installer-amd64/ \
> --disk device=cdrom,bus=scsi \--disk device=disk,path="
> /vm/Debian10/disk1.qcow2",format=qcow2,cache=unsafe,discard=unmap,bus=scsi \
> --controller type=virtio-serial \
> --controller type=scsi,model=virtio-scsi \
> --network bridge=brLAN,model=virtio, \
> --graphics vnc,port=5904,keymap=local,listen=0.0.0.0 \
> --noautoconsole

Yes, there are regular kernel upgrades in unstable & testing, and we
don't rebuild d-i every time. If you're targetting testing, you likely
want to be using d-i daily builds to avoid such issues, see:
  https://d-i.debian.org/daily-images/
  https://d-i.debian.org/daily-images/daily-build-overview.html

Closing as that's an unfortunate but very well known limitation.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: