** Changed in: gnome-software (Ubuntu)
Assignee: Andrew Bumbarger (andrewbumbarger) => sun lf (sunblues)
** Changed in: gnome-software (Ubuntu)
Assignee: sun lf (sunblues) => (unassigned)
** Changed in: gnome-software (Ubuntu)
Assignee: (unassigned) => sun lf
Dear Stephane
Yes I understad now.
Do you think it would be good to create a mechanism to "detach" the container
from profile with a command. this way the container will preserve its function
even after the profile was changed. (apply all profiles to the container itself
and remove dependence
Is there a mechanims to "deatch" a container from profile?
say to a container aaaContainer was created with bbbProfile. Is it possible to
"transfer" the configuration
from the profile to the container so if the bbbProfile is modified the
aaaContainer does not
change its behaviour?
--
You
Daer Stephane
I thought the device does exist in the default profile...
I can see the hardware address for eth0
Oh
The device is attached to the profile and thus affects all containers
which use the profile
so if I modify the profile all containers will be affected
to modify one container only
Public bug reported:
I am trying to create a container without network interface.
during lxd init I selected not to create a bridge (and it was not created)
so
lxc init ubuntu:16.04/amd64 gerecon --profile default
lxc config device removegerecon eth0
Device eth0 removed from gerecon
lxc
I just reinstalled a VM and, on that VM, it doesn't work.
It would be really nice to have some visibility into the inner workings
of the hv_balloon module to figure out what's going on with it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Oddly, the issue seems to have fixed itself. It's quite unclear how it
managed to do so though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584597
Title:
Hyper-V Memory Ballooning re-broken in
Public bug reported:
Regression: #1294283 fixed memory ballooning in Hyper-V in 14.04, but
the bug has returned in 16.04.
Steps to reproduce:
1. Create Gen2 Hyper-V VM
2. Install Ubuntu 16.04
3. modprobe hv_balloon
Memory usage according to Hyper-V Manager will not change
This has been
I'd like to post the output of lspci -vnvn, but it doesn't return
anything on Hyper-V.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584597
Title:
Hyper-V Memory Ballooning re-broken in 16.04
To
Simply change your translations. We from the German team do that... I know
that this does not work with every language.
2012/4/14 Hannie Dumoleyn 819...@bugs.launchpad.net
@Ask: we are talking about strings in gnome-control-center (for the
system settings), but there are also words truncated
I think so. They are already reviewed for gnome-control-center and the
relevant other packages that are directly integrated in control-center, so
have their own windows.
2012/4/14 ka_bra 819...@bugs.launchpad.net
@ 6and/\lf (eduardgotwig):
Will those changed german translations be available
I'm experiencing it now after fresh install of beta1 i386 and dist-
upgrade on an laptop Acer 5024wlmi
--
suspend/resume failure (ATI Mobility Radeon X700, kernel 2.6.31-10 Karmic Coala)
https://bugs.launchpad.net/bugs/430245
You received this bug notification because you are a member of Ubuntu
12 matches
Mail list logo
