sorry, i was using kvm_grp_gid as a placeholder variable for what the
gid is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850530
Title:
qemu-system-s390x permission denied in container on Eoan
To
Glad to see that it works again and that you are unblocked.
Interestingly I couldn't much info on 'kvm_grp_gid'.
However, since this now turns out to be a config change, I'm closing this
ticket as 'not a bug', hence 'Invalid'.
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete => Invalid
The host is bionic - surprisingly (as I thought it was the obvious fix),
adding kvm to the modules to be loaded didn't help
It turns out that previously, passing /dev/kvm through like this was
enough:
kvm:
path: /dev/kvm
type: unix-char
The perms for /dev/kvm on the host are:
crw-rw 1 r
Intensive testing of KVM was done with Eoan, so I'm confident that KVM works in
general (tried and used it by myself multiple times).
z/VM should be out of scope in this case - in addition KVM on top of z/VM is
not supported - and nested virtualization is not supported at all on s390x (KVM
on KV
i expect kvm module to be built in on s390x.
and the /dev/kvm should be there unless there is nexted
virtualization involved. Are you deploying these containers on top of an
LPAR, or on top of a z/VM on an LPAR.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Comparing to mine I only found one line to be different:
linux.kernel_modules: openvswitch,nbd,ip_tables,ip6_tables,kvm
So you might add "kvm" to yours there.
The dev should look like this in host and container:
crw-rw 1 root kvm 10, 232 Okt 29 22:45 /dev/kvm
Does it look the same for you
The LXD profile that you referenced looks reasonable for this use case, even if
tend to add overlay to linux.kernel_modules. But anyway, I assume that's the
profile you successfully used in the past prior to Eoan.
It might be worth to quickly check the kvm device if it's 0660 and root/kvm:
crw-rw
** Changed in: ubuntu-z-systems
Status: New => Triaged
** Also affects: lxd
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Canonical Server Team (canonical-server)
** Changed in: ubuntu-z-systems
Importance: Undecided => Mediu
This is what we're applying to the juju-default profile after
bootstrapping:
https://raw.githubusercontent.com/openstack-charmers/openstack-on-
lxd/master/lxd-profile.yaml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Tags added: s390x
** 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/1850530
Title:
qemu-system-s390x permission denied i
10 matches
Mail list logo
