Bug 1641381

Summary: libvirt filesystem type block - not working
Product: [Community] Virtualization Tools Reporter: lejeczek <peljasz>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED EOL QA Contact: libvirt Quality Engineering <libvirt-qe>
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: jsuchane, libvirt-maint, xuzhang, yalzhang
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-09 12:42:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description lejeczek 2018-10-21 18:29:55 UTC
Description of problem:

Is current version still buggy? - https://www.redhat.com/archives/libvir-list/2013-March/msg00065.html

I have in my domain:
...
  <devices>
    <emulator>/usr/libexec/libvirt_lxc</emulator>
    <filesystem type='block' accessmode='passthrough'>
      <source dev='/dev/0nvme/ubuntu1'/>
      <target dir='/'/>
    </filesystem>


And it does not start:

$ virsh -c lxc:// console ubuntu1
Connected to domain ubuntu1
Escape character is ^]
/bin/sh: 0: can't access tty; job control turned off


Version-Release number of selected component (if applicable):

libvirtd (libvirt) 3.9.0

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Jaroslav Suchanek 2018-10-23 09:27:50 UTC
1) Can you please paste version of installed packages of libvirt?

2) Can you please try the upstream version of libvirt?

Thanks.

Comment 3 lejeczek 2018-10-23 09:55:20 UTC
$ rpm -qa \*libvirt\* | sort
libvirt-3.9.0-14.el7_5.8.x86_64
libvirt-client-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-config-network-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-config-nwfilter-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-driver-interface-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-driver-lxc-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-driver-network-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-driver-nodedev-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-driver-nwfilter-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-driver-qemu-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-driver-secret-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-driver-storage-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-driver-storage-core-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-driver-storage-disk-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-driver-storage-gluster-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-driver-storage-iscsi-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-driver-storage-logical-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-driver-storage-mpath-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-driver-storage-rbd-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-driver-storage-scsi-3.9.0-14.el7_5.8.x86_64
libvirt-daemon-kvm-3.9.0-14.el7_5.8.x86_64
libvirt-gconfig-1.0.0-1.el7.x86_64
libvirt-glib-1.0.0-1.el7.x86_64
libvirt-gobject-1.0.0-1.el7.x86_64
libvirt-libs-3.9.0-14.el7_5.8.x86_64
libvirt-python-3.9.0-1.el7.x86_64

It should be easy to reproduce the problem. I create a container:

lxc-create --template download -B lvm --vgname 0nvme --fssize 50G --name ubuntu

and libvirt fails to run it.
Libvirt does not fail if lxc was created --dir.

I'll see if I can try with upsteam's.

Many thanks, L.

Comment 4 lejeczek 2018-10-24 11:38:31 UTC
I've tried https://libvirt.org/sources/python/libvirt-python-3.10.0-1.fc26.src.rpm
Complies, installs and starts but problem still exists.

I've also tried: https://libvirt.org/sources/libvirt-4.4.0-1.fc28.src.rpm
Compiles, installs but does not start:

$ virsh -c lxc:// 
error: failed to connect to the hypervisor
error: internal error: Unexpected LXC URI path '', try lxc:///system

If anybody know if any possible patch I'd be happy to try.

Comment 5 lejeczek 2018-10-24 12:12:16 UTC
okey, seems like one change with 4.4.0
This works:

$ virsh -c lxc:/ start ubuntu1
Domain ubuntu1 started

but still:
$ virsh -c lxc:/ console ubuntu1
Connected to domain ubuntu1
Escape character is ^]
/bin/sh: 0: can't access tty; job control turned off

Comment 6 Xuesong Zhang 2023-06-09 12:42:49 UTC
I'm closing this BZ since LXC is not supported for long time, and close this BZ now. Please reopen it if I'm wrong.