Ok, I found the problem, my fault ;)
I was the initramfs not generate after kernel install,
because I have write a temp /proxmox_install_mode file for jessie upgrade,
and forgot to remove it.
And this file skip postinstall in pve-kernel .deb install.
- Mail original -
De: dietmar
Because setting in 'netX' are hot-pluggable, but ip configuration is not.
What do you think?
I dont remember if we already managed mixing hotplugglaged updates and pending
values for the same element?
for example, we have already disk throttling which is hotpluggled with
non-hotplug disk
I also also not sure if we should store ip config inside netX, or use
a separate property like:
net0: virtio=8A:5E:75:3B:29:33,bridge=vmbr0,firewall=1
ipconfig0: ip=1.2.3.4/20,gw=...
Because setting in 'netX' are hot-pluggable, but ip configuration is not.
What do you think?
I dont remember if
Ok I'll try to do some tests to today to see what is the best way,
based on last patch from wolfgang.
- Mail original -
De: dietmar diet...@proxmox.com
À: aderumier aderum...@odiso.com
Cc: Wolfgang Bumiller w.bumil...@proxmox.com, pve-devel
pve-devel@pve.proxmox.com
Envoyé: Jeudi 18
The variable to use to check the disk type is confid,
as set in line 16 with:
var confid = me.confid || (values.controller + values.deviceid);
---
www/manager/qemu/HDEdit.js | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/www/manager/qemu/HDEdit.js b/www/manager/qemu/HDEdit.js
Hi,
I suppose that would work. But you might want to reinitialize a guest
with old settings if you screwed them up inside the guest. Maybe a
user-configurable ID or name of some sort? (The instance id needs to
change in order for cloud-init to pull the configuration. It does seem
to load some
and add a depend on libjemalloc1
Signed-off-by: Alexandre Derumier aderum...@odiso.com
---
debian/control| 4 ++--
debian/patches/series | 1 -
debian/rules | 2 +-
3 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/debian/control b/debian/control
index
Hi,
I have done a lot of benchmark with ceph these last days,
and I have had some performance problems with tcmalloc
when increasing number of disks iothread.
The main problem is that tcmalloc use a shared thread cache of 16MB
by default.
with more threads, this cache is shared, and some bad
Signed-off-by: Alexandre Derumier aderum...@odiso.com
---
PVE/QemuServer.pm | 1 +
1 file changed, 1 insertion(+)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index ab9ac74..455c473 100644
--- a/PVE/QemuServer.pm
+++ b/PVE/QemuServer.pm
@@ -4153,6 +4153,7 @@ sub vm_start {
# set
I would like to known when do you want to generate the cloudinit iso.
If user change settings (ips,hostname,...), do we want to apply them directly
to configuration ?
or do we want to put them as pending ? (for ip can be ok, for hostname that
seem strange if user want to rename his vm).
Couldn't agree more, so here is the polished version with systemctl
added also to stop the service.
diff --git a/src/PVE/Daemon.pm b/src/PVE/Daemon.pm
index e051500..fb9a923 100644
--- a/src/PVE/Daemon.pm
+++ b/src/PVE/Daemon.pm
@@ -578,6 +578,16 @@ my $read_pid = sub {
return $pid;
};
I would generate a Digest using all cloud-init related values, and
re-gererate
the iso at VM start
if the digest has changed.
Ok. Maybe can be generate the cloudinit iso file with vmid-digest.iso ?
Like this no need to store the dgest in vmid.conf ?
Also, Do we need to set theses changed
From: Alexandre Derumier aderum...@odiso.com
Signed-off-by: Alexandre Derumier aderum...@odiso.com
---
PVE/QemuServer.pm | 181 +-
control.in| 2 +-
2 files changed, 179 insertions(+), 4 deletions(-)
diff --git a/PVE/QemuServer.pm
* Changing cidr and gatway setting names to ip, ip6, gw,
gw6, as these are the names we are using for LXC.
* Adding explicit ip=dhcp and ip6=dhcp options.
* Removing the config-update code and instead generating
the ide3 commandline in config_to_command.
- Adding a conflict check to
I'm attaching a second patch to your cloud-init patch, Alexandre.
Here's the summary of the changes:
* Changing cidr and gatway setting names to ip, ip6, gw,
gw6, as these are the names we are using for LXC.
* Adding explicit ip=dhcp and ip6=dhcp options.
* Removing the config-update code
Hi,
I'm currently testing new kernel 3.19,
it's working fine on my new dell servers r630.
But I have crash in initramfs on my old test server (dell poweredge 2950,
megasas driver).
kernel panic , cannot find root / ...
with kernel 3.10, It's booting fine with
pve-kernel-3.10.0-8-pve
I just notice that I don't have
/boot/initrd.img-3.10.0-9-pve
and
#update-initramfs -k all -u
update-initramfs: Generating /boot/initrd.img-3.10.0-8-pve
update-initramfs: Generating /boot/initrd.img-3.10.0-7-pve
update-initramfs: Generating /boot/initrd.img-3.10.0-6-pve
...
(not -9-pve)
?
I
On Wed, 17 Jun 2015 17:28:28 +0200 (CEST)
Alexandre DERUMIER aderum...@odiso.com wrote:
I don't use zfs as filesystem, only ext3
So, I don't see what can be the problem here ?
Maybe some changes to the grub boot loader?
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
only change between both:
update zfs/spl 0.6.4, bump api version to 9-pve
update zfs/spl source to 0.6.4
I don't use zfs as filesystem, only ext3
So, I don't see what can be the problem here ?
And you do not load the zfs module?
___
On Wed, 17 Jun 2015 17:40:26 +0200 (CEST)
Alexandre DERUMIER aderum...@odiso.com wrote:
I just notice that I don't have
/boot/initrd.img-3.10.0-9-pve
and
#update-initramfs -k all -u
update-initramfs: Generating /boot/initrd.img-3.10.0-8-pve
update-initramfs: Generating
20 matches
Mail list logo
