** No longer affects: subiquity (Ubuntu)
** No longer affects: subiquity (Ubuntu Focal)
** No longer affects: subiquity (Ubuntu Groovy)
** Changed in: ubuntu-z-systems
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: subiquity
Importance: Undecided
Status: New
** Changed in: subiquity
Status: New => In Progress
** Changed in: subiquity
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "virt-install_with_legacy d-i-image.txt"
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893775/+attachment/5427706/+files/virt-install_with_legacy%20d-i-image.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Since there are some discussions about this ticket on other
communication channels, I want to clarify and sum up the situation here:
An installation on a DASD disk that is virtio-attached, like:
virt-install --name focal --memory 2048 --disk
path=/dev/disk/by-path/ccw-0.0.1234 --cdrom
** Tags added: fr-662
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893775
Title:
[UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on
DASD
To manage notifications about this bug
It seems from a quick look that parted just embeds a (ancient) copy of
fdasd to do the identification, so I don't think there's any real
benefit to using parted over fdasd directly.
It would really be more in keeping with how we expect things to work to
have a udev rule that would run fdasd on
So the history of this msdos/dasd partitioning table stuff in the old
installer were as follows:
LTC-135429
https://bugs.launchpad.net/ubuntu/+source/partman-partitioning/+bug/1534629
LTC-136054
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1527328
On Mon, Sep 7, 2020 at 4:50 PM Dimitri John Ledkov
<1893...@bugs.launchpad.net> wrote:
>
> I thought that one must use vfio-ccw to passthrough dasd drives, not
> virtio-scsi.
Yes - You can provide any block device (even image files) as
virtio-blk/virtio-scsi the same as on any other platform.
But
Request to always force ms-dos partition table in KVM was requested
before.
However, surely it is virtualization/layering violation, when a physical
host device which is not virtio-scsi compatible is passed through to
qemu which emulates it as scsi, despite the underlying device on the
host not
I thought that one must use vfio-ccw to passthrough dasd drives, not
virtio-scsi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893775
Title:
[UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as
'parted' with either '-l' or 'print' for example points to that fact that a
dasd is used (here a pristine DASD w/o partitions after using 'virt-install
--name groovy --memory 2048 --disk path=/dev/disk/by-path/ccw-0.0.1601 --cdrom
./groovy-live-server-s390x.iso'):
"
$ parted /dev/vda print
Here's the udev data for /dev/vda:
P: /devices/css0/0.0.0002/0.0./virtio2/block/vda
N: vda
L: 0
S: disk/by-path/ccw-0.0.
E: DEVPATH=/devices/css0/0.0.0002/0.0./virtio2/block/vda
E: SUBSYSTEM=block
E: DEVNAME=/dev/vda
E: DEVTYPE=disk
E: MAJOR=252
E: MINOR=0
E:
I just retried (just to be sure) with having done an explicit fdasd and
dasdfmt upfront (even if my DASD was already prepared before, but it may
have had some LVM leftovers), but don't see a different - same
situation.
** Attachment added: "04092020.tgz"
** Tags added: installer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893775
Title:
[UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on
DASD
To manage notifications about this
I think if you use an already formatted dasd in the KVM this should
work. If you use a completely blank one, I don't know that there's a way
for the guest to tell that it's backed by a dasd vs some other block
device?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I could recreate and can confirm the same for groovy.
If the installation was started with:
sudo virt-install --name groovy --memory 2048 --disk
path=/dev/disk/by-path/ccw-0.0.1601 --cdrom ./groovy-live-server-s390x.iso
the installer uses /dev/vda that is usually an indicator for virtio device
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin20041
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893775
Title:
[UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as
** Package changed: linux (Ubuntu) => subiquity (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893775
Title:
18 matches
Mail list logo
