Can't mount kvm image file on new kernel of 16.04(linux 4.4.0-119)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned | ||
Xenial |
Expired
|
Medium
|
Unassigned |
Bug Description
When I use 4.4.0-62-generic kernel, I can mount kvm image file.
But when I use 4.4.0-116-generic or 119 kernel, I can't mount the kvm image file.
Is there some way to mount the kvm image file on 4.4.0-116-generic later kernel?
- release
root@ofaci1:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.4 LTS
Release: 16.04
Codename: xenial
root@ofaci1:~#
- packages
root@ofaci1:~# dpkg -l | egrep "qemu|mount|
ii cgroupfs-mount 1.2 all Light-weight package to set up cgroupfs mounts
ii ipxe-qemu 1.0.0+git-
ii libmount1:amd64 2.27.1-6ubuntu3.4 amd64 device mounting library
ii linux-image-
ii linux-image-
ii mount 2.27.1-6ubuntu3.4 amd64 tools for mounting and manipulating filesystems
ii qemu-block-
ii qemu-kvm 1:2.5+dfsg-
ii qemu-system-common 1:2.5+dfsg-
ii qemu-system-x86 1:2.5+dfsg-
ii qemu-utils 1:2.5+dfsg-
root@ofaci1:~#
- Use 4.4.0-62-generic
root@ofaci1:~# uname -a
Linux ofaci1 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
root@ofaci1:~# qemu-nbd --connect /dev/nbd1 /opt/ci-
root@ofaci1:~# fdisk /dev/nbd1
Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/nbd1: 40 GiB, 42949672960 bytes, 83886080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000dfd65
Device Boot Start End Sectors Size Id Type
/dev/nbd1p1 2048 3905535 3903488 1.9G 82 Linux swap / Solaris
/dev/nbd1p2 * 3905536 83884031 79978496 38.1G 83 Linux
Command (m for help): q
root@ofaci1:~# mount /dev/nbd1p2 /mnt/d1
root@ofaci1:~# ls /mnt/d1
bin etc initrd.img.old lost+found opt run sys var
boot home lib media proc sbin tmp vmlinuz
dev initrd.img lib64 mnt root srv usr vmlinuz.old
root@ofaci1:~# umount /mnt/d1
- Use 4.4.0-119-generic
root@ofaci1:~# uname -a
Linux ofaci1 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
root@ofaci1:~# qemu-nbd --connect /dev/nbd1 /opt/ci-
root@ofaci1:~# echo $?
0
root@ofaci1:~# fdisk /dev/nbd1
Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/nbd1: 40 GiB, 42949672960 bytes, 83886080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000dfd65
Device Boot Start End Sectors Size Id Type
/dev/nbd1p1 2048 3905535 3903488 1.9G 82 Linux swap / Solaris
/dev/nbd1p2 * 3905536 83884031 79978496 38.1G 83 Linux
Command (m for help): q
root@ofaci1:~# mount /dev/nbd1p2 /mnt/d1
mount: special device /dev/nbd1p2 does not exist
root@ofaci1:~# ls /dev/nbd1*
/dev/nbd1 /dev/nbd11 /dev/nbd13 /dev/nbd15
/dev/nbd10 /dev/nbd12 /dev/nbd14
root@ofaci1:~#
affects: | ubuntu → linux (Ubuntu) |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1761646/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]