On Tue, Aug 04, 2015 at 04:43:48PM +0200, Alexandre DERUMIER wrote:
+return 0 if $exclude_cloudinit $drive-{file} =~
m@[:/]vm-\d+-cloudinit\.$QEMU_FORMAT_RE@;
I think this will not match disks on block storage ?
file sample : 100/vm-100-cloudinit.raw
block sample :
Hi,
here a deb source package for iproute2 4.1
http://odisoweb1.odiso.net/iproute2.tar.gz
I haved added the buffer increase patch to handle all the vlans in bridge and
ip commands.
Alexandre
___
pve-devel mailing list
pve-devel@pve.proxmox.com
Hi all,
Any idea why this option '-boot menu=on' makes a VM unbootable in
nested virtualization under qemu-2.4?
Anyway to debug what goes on?
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael at rasmussen dot cc
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD3C9A00E
Since ExtJS5, when doing such a declaration,
Ext.applyIf(me, {
items: {
xtype: 'pveKVComboBox',
comboItems: data,
}
});
the comboItems property is passed in the parent class as a config object,
instead of being directly
Thanks Alexandre.
I will build something for testing this Friday.
On 5/08/2015 5:24 pm, Alexandre DERUMIER aderum...@odiso.com wrote:
BTW, can you test this method too ?
eth0.10vmbrcustomer--(vlanX)--tapX
auto vmbrcustomer1
iface vmbrcustomer1 inet manual
Hi,
while digging and comparing several kernel parameters for optimizations
i was wondering about the following changes from the RHEL7 kernel to the
PVE 4.X kernel and the reasons behind it.
Redhat uses since RHEL7 a fully tickless kernel. Options:
CONFIG_NO_HZ=y
CONFIG_NO_HZ_FULL=y
Redhat uses since RHEL7 a fully tickless kernel. Options:
CONFIG_NO_HZ=y
CONFIG_NO_HZ_FULL=y
CONFIG_RCU_FAST_NO_HZ=n
CONFIG_HZ_1000=y
CONFIG_HZ=1000
PVE now uses:
CONFIG_NO_HZ=y
CONFIG_NO_HZ_IDLE=y
CONFIG_RCU_FAST_NO_HZ=y
CONFIG_HZ_250=y
CONFIG_HZ=250
I just use the default config
On 08/05/2015 04:40 PM, Dietmar Maurer wrote:
Redhat uses since RHEL7 a fully tickless kernel. Options:
CONFIG_NO_HZ=y
CONFIG_NO_HZ_FULL=y
CONFIG_RCU_FAST_NO_HZ=n
CONFIG_HZ_1000=y
CONFIG_HZ=1000
PVE now uses:
CONFIG_NO_HZ=y
CONFIG_NO_HZ_IDLE=y
CONFIG_RCU_FAST_NO_HZ=y
CONFIG_HZ_250=y
Am 05.08.2015 um 16:48 schrieb Dietmar Maurer:
Redhat uses since RHEL7 a fully tickless kernel. Options:
CONFIG_NO_HZ=y
CONFIG_NO_HZ_FULL=y
CONFIG_RCU_FAST_NO_HZ=n
CONFIG_HZ_1000=y
CONFIG_HZ=1000
PVE now uses:
CONFIG_NO_HZ=y
CONFIG_NO_HZ_IDLE=y
CONFIG_RCU_FAST_NO_HZ=y
CONFIG_HZ_250=y
On Wed, 5 Aug 2015 18:20:43 +0200 (CEST)
Dietmar Maurer diet...@proxmox.com wrote:
Hi all,
I wonder if you should make the bios configurable, for example ship
seabios and coreboot?
Anyone with spare time to test that?
I would like to test but how and where do one specify to use coreboot
I wonder if you should make the bios configurable, for example ship
seabios and coreboot?
Anyone with spare time to test that?
I would like to test but how and where do one specify to use coreboot
instead of seabios?
This is what we need to find out (and implement) :-)
PS. Why
Why not? AFAIK this is the suggested/standard setting for mailman lists.
How often do you use 'reply-all' when you reply to an email?
Basically always for list posts.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
On Wed, 5 Aug 2015 19:23:24 +0200 (CEST)
Dietmar Maurer diet...@proxmox.com wrote:
This is what we need to find out (and implement) :-)
Adding: args: -bios /path/to/rom
And VM boots using this bios.
I am building a rom from source now:
ROMSIZE:512KB
Emulation: QEMU x86
Hi all,
Apparently mail.proxmox.com does not like large messages so this one
without the boot.rom
On Wed, 5 Aug 2015 18:20:43 +0200 (CEST)
Dietmar Maurer diet...@proxmox.com wrote:
Hi all,
I wonder if you should make the bios configurable, for example ship
seabios and coreboot?
Anyone
On Thu, 6 Aug 2015 01:37:34 +0200
Michael Rasmussen m...@datanom.net wrote:
Steps:
1) fetch coreboot-4.1.tar.xy
2) fetch coreboot-blobs-4.1.tar.xy
3) fetch seabios-1.8.2.tar.gz
4) cd coreboot-4.1 make crossgcc
5) cd seabios-1.8.2 make menuconfig (CONFIG_COREBOOT 1,
CONFIG_DEBUG_SERIAL
15 matches
Mail list logo
