> I have successfully make a boot rom with coreboot using seabios as
> payload;-)
So what is the advantage if that still uses seabios?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>>In future, we can now also add additional mount entries like:
>>
>>rootfs: local:101/subvol-101-disk-1.raw,size=4
>>mount0: faststore:101/subvol-101-disk-1.raw,size=1,mp=/mnt/faststore
>>mount1: slowbigstore:101/subvol-101-disk-1.raw,size=1024,mp=/mnt/slowbigstore
>>
>>I assume that is what you r
> In future, I want to implement 'subvol' for normal directories (maps to
> simple subdirectories).
>
> So that we can remove those get_private_dir hacks...
In future, we can now also add additional mount entries like:
rootfs: local:101/subvol-101-disk-1.raw,size=4
mount0: faststore:101/subvol-1
> if ($scfg->{type} eq 'dir' || $scfg->{type} eq 'nfs') {
> + if ($size > 0) {
> + $volid = PVE::Storage::vdisk_alloc($storage_conf, $storage,
> $vmid, 'raw',
> + "vm-$vmid-rootfs.raw",
> $size);
> + } else {
> +
applied, thanks!
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>>Sure, yes. What problem do you want to solve?
no special problem, just remove a file write at each start
BTW, I have read the new code, I don't have tested it yet,
but
if ($scfg->{type} eq 'dir' || $scfg->{type} eq 'nfs') {
+ if ($size > 0) {
+ $volid = PVE::Sto
That was supposed to be [PATCH pve-container]
On Thu, Aug 06, 2015 at 03:46:47PM +0200, Wolfgang Bumiller wrote:
> veth${vmid}.${id} looks like a vlan device, with qemu we use
> tap${vmid}i${id}, so it makes sense to use an 'i' for
> containers, too.
>
> Fixed update_net to work with the new conf
veth${vmid}.${id} looks like a vlan device, with qemu we use
tap${vmid}i${id}, so it makes sense to use an 'i' for
containers, too.
Fixed update_net to work with the new configuration method,
it still expected the old configuration hash and errored
when trying to change the network interface confi
explicitly enable seccomp and add libseccomp-dev build-time
and libseccomp2 runtime dependencies
---
debian/control | 4 ++--
debian/rules | 3 ++-
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/debian/control b/debian/control
index 585efd4..c3f335e 100644
--- a/debian/control
++
> Do you still write the config file at lxc format for lxc-start ?
> (maybe on each ct start ?)
Sure, yes. What problem do you want to solve?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Do you still write the config file at lxc format for lxc-start ?
(maybe on each ct start ?)
If yes, I'm not sure, but I think it's possible to pass key=values to lxc-start
command line,
-s, --define KEY=VAL
Assign value VAL to configuration variable KEY. This overrides
any
Great !
I'll test them tomorrow.
Thanks Dietmar.
- Mail original -
De: "dietmar"
À: "pve-devel"
Envoyé: Jeudi 6 Août 2015 12:20:13
Objet: [pve-devel] use our own format for LXC containers
Hi all,
we finally use our own format for lxc containers. The patch
touch most parts of the ex
>>Sending the entire series again since I made some changes in between.
I'll try it tomorrow, I'm too busy at work today
>>(@Alexandre, since I modified most patches in the series to bring
>>them more up to date (eg. see the changelog for patch 1): if you have
>>already worked on conflicting chan
On Thu, 6 Aug 2015 01:37:34 +0200
Michael Rasmussen wrote:
>
> I have attached both configs and my boot.rom for testing (should be
> renamed to .config in the appropriate folders)
>
A set of more refined config files for coreboot and seabios-1.8.2
attached. These work excellent and boots very q
Hi all,
we finally use our own format for lxc containers. The patch
touch most parts of the existing code, so it was quite large (sorry).
To test, you need to update the following packages from git:
pve-cluster
lxc
pve-container
pve-manager
We now store LXC configuration as normal files at:
/e
From: Alexandre Derumier
- changelog:
- support any storage and not only qcow2
- cloudinit drive volume no more generated at start.
we can now enable|disable cloudinit with
qm set vmid -(ide|sata)x storeid:cloudinit
qm set vmid -delete (ide|sata)x
Signed-off-by: Alexandre Der
From: Alexandre Derumier
when we change ip address, network configuration is correctly writen in guest,
but cloud-init don't apply it and keep previous ip address.
workaround with forcing ifdown ifup
Signed-off-by: Alexandre Derumier
---
PVE/QemuServer.pm | 3 +++
1 file changed, 3 insertions
The config-disk is now generated into a qcow2 located on a
configured storage.
It is now also storage-managed and so live-migration and
live-snapshotting should work as they do for regular hard
drives.
Config drives are recognized by their storage name of the
form: VMID/vm-VMID-cloudinit.qcow2
Exam
---
PVE/API2/Qemu.pm | 2 +-
PVE/QemuServer.pm | 14 +-
2 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm
index a19ad87..4dcbb26 100644
--- a/PVE/API2/Qemu.pm
+++ b/PVE/API2/Qemu.pm
@@ -41,7 +41,7 @@ my $resolve_cdrom_alias = sub {
m
* Add ipconfigX for all netX configuration options and
using ip=CIDR, gw=IP, ip6=CIDR, gw6=IP as option names
like in 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 co
From: Alexandre Derumier
Signed-off-by: Alexandre Derumier
---
PVE/QemuServer.pm | 145 --
control.in| 2 +-
2 files changed, 143 insertions(+), 4 deletions(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index 84fc712..1bf480
Sending the entire series again since I made some changes in between.
(@Alexandre, since I modified most patches in the series to bring
them more up to date (eg. see the changelog for patch 1): if you have
already worked on conflicting changes and don't feel like dealing
with the merge conflict, j
This comes from pve-container and will be used in
qemu-server with cloudinit.
---
src/PVE/Tools.pm | 10 ++
1 file changed, 10 insertions(+)
diff --git a/src/PVE/Tools.pm b/src/PVE/Tools.pm
index a7bcd35..9b6a3e4 100644
--- a/src/PVE/Tools.pm
+++ b/src/PVE/Tools.pm
@@ -740,6 +740,16 @@ su
I test the new platform with the latest updates
On glusterfs server: no possibility to migrate contenaires :
TASK ERROR: lxc container migration not implemented.
coming soon ?
Thank's.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.pro
Again, please can you add an expamle toö show why this is required?
> there where an changing in the internal name so it is necessary to adapt the
> parser regex.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailma
25 matches
Mail list logo
