As a user, our main use case for live storage migration would be migrating
between local disk/RBD/iSCSI.
We would also use the ability to migrate storage across the network.
This could for example be used to migrate between a SAN in one datacentre to a
SAN in a remote datacentre.
Regards,
I agree.
All networking measurements are in bits/s Megabits, Kilobits
Having Proxmox's in MB/s is inconsistent with the way the rest of the
industry measures network bandwidth.
Regards,
Andrew
On 2/17/2013 8:13 PM, Stefan Priebe - Profihost AG wrote:
Right but people are u
Hi,
Any FYI more than anything. We have experienced VERY high latency when
performing IO heavy operations on our RBD volumes. We initially thought
it was due to network congestion on our uplinks, but it turns out it is
a bug.
See http://tracker.ceph.com/issues/3737
It would be great if Pro
Having a "Maintenance" mode would be
good.
Being able to mark a node as being under "Maintenance" and having
all VM's migrate off it, and it disappear from the target list in
migrations.
Also being able to select Multiple guests and migrate the
.
What is the process to submit our patch ?
Regards,
Andrew Thrift
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
my $ifacevlan = "${bridge}.$tag";
# create vlan on $iface is not already exist
if (! -d "/sys/class/net/$ifacevlan") {
On 4/2/2013 11:27 AM, Andrew Thrift wrote:
Hi,
We are wanting to submit a patch to Network.pm to be included upstream.
Our patch changes
for 64bit Windows/Linux
Regards,
Andrew Thrift
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Hi Dietmar,
We have been running this successfully for a few weeks now on the
default PVE kernel with no issues.
I searched the list archives, and the issues I could see looked like
they were related to the MTU on the parent physical interface being too
small.
Linux does not clearly differ
RDP still requires that the Terminal Server has a sound card.
It only configures a virtual sound device for the RDS client if one
exists on the server.
On 4/18/2013 3:49 PM, Dietmar Maurer wrote:
Is this feature planned ?
no, not really.
And if not, would patches be accepted to add th
Hi Dietmar,
It depends on what size frame you are trying to pass. Anything over
1504 bytes is considered "Jumbo". An MTU of 9000 would allow you to
pass a 9004byte frame. If you were doing "jumbo" frames to one of your
VM's and wanted double tagging you would set your physical interface
w
/2013 12:15 AM, Alexandre DERUMIER wrote:
seem to be possible also for win2003
http://support.dvsweb.com/app/answers/detail/a_id/263/~/enabling-audio-over-rdp-on-a-windows-server,-without-hardware-soundcard
- Mail original -
De: "Martin Maurer"
À: "Andrew Thrift" ,
Great!
Will this fix make it in to the packages for 3.0 rc2 ?
Regards,
Andrew
On 5/7/2013 10:21 PM, Dietmar Maurer wrote:
Thanks for the hint:
https://git.proxmox.com/?p=pve-qemu-kvm.git;a=commit;h=54619c4adf9014093ef09d0f28fd40e88f56a55a
-Original Message-
From: Stefan Pri
Hi,
On 3.0rc1 when I attempt to create a Linked-Clone from a VM on a pool
other than "rbd" it fails with the following error:
stopped: clone failed: rbd clone base-120-disk-1' error: rbd: error
opening pool rbd: (2) No such file or directory
Regards,
Andrew
___
Good Morning,
I have noticed that cloned VM's do not copy the cache settings of the
Template. e.g. if I have a Template with write-back enabled, then
perform a full clone it will have write-back cache disabled on the
resulting VM.
I am not sure if this is a feature, or a bug.
Regards,
Hi,
One of the features that was discussed for Proxmox 3.0 was the ability
to perform an operation on multiple VM's at the same time.
e.g. Select group of VM's or a Resource Group and Migrate them, or
start/stop them.
I was wondering if/when this feature will be implemented ?
Regards,
Hi,
We have noticed on two separate clusters that when we perform a clone,
and select a destination resource pool that the resulting cloned machine
is NOT in the pool we selected (it is in the root pool)
We also noticed that when logged in as a restricted user (that only has
access to the one
FYI we are using vlan tagging on bridges with Proxmox in production for
over a year now, initially on 2.6.32 kernel and then on 3.10. We are using
Intel gigabit and 10gigabit adapters.
We posted the patches to the list a few months back, I believe these are
very similar to Alexandre's patches.
gged 101 ?
> or is the packet vlan 201 encapsuled in vlan101 ?
>
>
>
>
>
> - Mail original -
>
> De: "Stefan Priebe - Profihost AG"
> À: "Alexandre DERUMIER" , "Andrew Thrift" <
> and...@networklabs.co.nz>
> Cc: pve-devel@pve
r0>vmbr0.201<tap interface
>>
>>
>> when the packet from tap (tagged 201) is going out through bond0.101,
>>
>> what happen ?
>>
>> is the packet vlan retagged 101 ?
>> or is the packet vlan 201 encapsuled in vlan101 ?
>>
>>
&
While this is a very neat way to load balance vlan traffic, it could be
dangerous.
You are effectively allowing users to create a loop. Unless they have their
switches and spanning tree configured correctly upstream of the host, they
could create a large broadcast storm on their network, likely kn
t does so in
> our environment).. however, it requires switches with such capability.
>
>
> On Wed, Feb 12, 2014 at 9:53 AM, Andrew Thrift
> wrote:
>
>> While this is a very neat way to load balance vlan traffic, it could be
>> dangerous.
>>
>> You are e
Will these patched packages (for qemu 1.7.1) make it in to the PVE3.2 repos
?
On Tue, May 6, 2014 at 1:00 PM, Michael Rasmussen wrote:
> On Sun, 04 May 2014 18:47:28 +0200 (CEST)
> Alexandre DERUMIER wrote:
>
> >
> > can you test them ?
> >
> Have tested with CentOS-6.5 and I can confirm that
This seems to be a trivial change, but fixes a known problem in PVE3.2
With such low risk, why would this NOT be included as an update to PVE3.2 ?
On Tue, May 6, 2014 at 5:34 PM, Dietmar Maurer wrote:
> > Will these patched packages (for qemu 1.7.1) make it in to the PVE3.2
> repos ?
>
> No,
Dietmar,
Is this not the point of pve-test ?
If the updated packages are put in to pve-test users will be able to test
this for you.
We will test this against Ceph, iSCSI to EqualLogic, RAID via PERC5, iSCSI
to Nexenta and NFS to Nexenta.
On Tue, May 6, 2014 at 8:47 PM, Dietmar Maurer wro
Hello,
We have a number of administrators using our PVE cluster, with hundreds of
VM's that are grouped by customer in to Pools. We were regularly getting
complaints from our admin users about the difficulty in finding Virtual
Machines that were for a specific customer. As our VM's were already
Exported Variable:
The particular variable referenced is the canonical list of Valid
Privileges, necessary for assessing whether any given Privilege is, in fact
on the list of valid and assignable Privileges. The change made allows the
variable to referenced outside the scope of the module that co
Hi Dietmar,
It can be literally any permission. If a user has any permission on a
pool, that pool will appear to them in the "Pool View".
Typically we will assign a user to a group for the pool, so if we have a
pool called CUSTOMER1 we will create a group called "CUSTOMER1_Admins" this
group the
Hi Dietmar,
Sorry for the delay.
Yes we have tested this on our test cluster and it appears to work as
expected.
Regards,
Andrew
On Wed, Aug 13, 2014 at 6:16 PM, Dietmar Maurer wrote:
> check_any call for valid_privs:
> This check is assessing whether the user has any permissions assi
Some feedback.
We have tested this patch and hot add/remove are both working perfectly
with at least virtio-scsi on Windows 2008, 2008r2, 2012, 2012r2 and Linux
3.2 and higher.
Thanks Guys! This is going to lower operational overheads for us as we
wont need to schedule outages to cleanly add di
This seems like a very good idea.
The web-ui could indicate the VM has pending changes, possibly by using a
different VM icon, and/or showing it on the VM summary tab.
Being able to view what changes are pending would also be a good idea in
multi-admin environments.
On Sat, Sep 6, 2014 at 2:11
Hi,
I was wondering if support for UEFI in VM's could be added to PVE.
See http://www.linux-kvm.org/page/OVMF
It looks to be an alternative firmware image that is loaded instead of the
usual bios.bin
Regards,
Andrew
___
pve-devel mailing list
pv
Hi Dietmar,
It is a replacement for the bios. You can load ovmf.fd with the -L option
for QEMU.
You can download binary copies of ovmf.fd from:
http://tianocore.github.io/ovmf/
On Wed, Oct 29, 2014 at 12:22 AM, Dietmar Maurer
wrote:
> > I was wondering if support for UEFI in VM's could be a
Hi Alexandre,
Will this potentially fix the Disk Move issues I reported a few weeks back ?
On Thu, Nov 6, 2014 at 4:09 AM, Alexandre Derumier
wrote:
> reported in drive-mirror,
>
> if we cancel the job and we try to free the rbd volume,
> it seem that rbd storage take 2-3 seconds to release th
Option 4, You could have a drop down box with a default selection of
"Distribute Evenly" then a list of all available nodes.
This would allow the user to just click through and have them distribute
evenly, OR they could select a specific node.
On Tue, Nov 11, 2014 at 12:32 PM, Michael Rasmussen
Hi,
I have noticed from at least PVE 2.3 through 3.3 that when removing a disk
from a VM that there is no "Task" created, and that no progress is shown.
This means that on storage such as Ceph where disk removal can take some
time, you are in the dark as to progress. You also cannot see from a V
e:
> Hi,
> I'm not sure, but I think a task is created only if the delete take too
> much time.
> I don't remember exactly after how much time.
>
>
> - Mail original -
> De: "Andrew Thrift"
> À: "pve-devel"
> Envoyé: Lundi 8 Décem
;
> (@cc pve-devel)
>
> - Mail transféré -
>
> De: "Andrew Thrift"
> À: "Alexandre DERUMIER"
> Envoyé: Mercredi 12 Novembre 2014 05:10:40
> Objet: Re: [pve-devel] [PATCH] rbd : free_image : retry if rbd has watchers
>
>
> Hi Alexandre,
>
t qemu-server package from pvetest repository ?(>=
> 3.3-3)
>
> It should be fixed here.
>
>
>
> - Mail original -
> De: "Andrew Thrift"
> À: "aderumier"
> Cc: "pve-devel"
> Envoyé: Lundi 8 Décembre 2014 04:42:23
> Objet
I think you may be referring to a problem I reported.
We have been having corruption of RBD volumes when live migrated from one
pool to another inside Proxmox VE.
Alexandre had spotted this bug and suggested it may be related.
On Sun, Jan 4, 2015 at 8:37 AM, Stefan Priebe wrote:
> Am 03.01.201
Hi,
Have the Promox VE team thought about using UUID's for VM's as well as
for Disks ?
The use of VMID's for disks is becoming an issue for us with Ceph. We
cannot have multiple PVE clusters sharing the same pool on Ceph as
there will be duplicate VMID's across the clusters that will result in
a
Hi Dietmar,
Using a pool per cluster will mean that you may need to split/shrink
your placement group count to stay within Ceph best-practises. With
using a fixed number of pools, you can calculate the correct number of
PG's for your estimated OSD count.
By using a UUID for the disks and having a
Hi Guys,
I work with Campbell and was involved in getting NetScaler to work on Proxmox.
The problem you are having is due to the BSD "Loader" trying to
communicate with a non-existent serial port. The solution, add a
dummy serial port.
e.g. add "serial0: socket" to the VMID.conf
It will then
Is there documentation on this feature ?
On Fri, Jan 15, 2016 at 3:15 PM, Alexandre Derumier wrote:
> This add support vlan trunks for qemu net interfaces.
>
> based on theses patches:
> http://pve.proxmox.com/pipermail/pve-devel/2014-September/012730.html
>
> This works with OVS and linux vlan-
Hi Alexandre, List
Thanks for your very informative email.
Our hosts are fairly powerful (E5-2697v2), as are our ceph hosts.
We will run some more benchmarks shortly using KRBD + iothreads and report
back.
Regards,
Andrew
On Thu, Jan 29, 2015 at 9:20 PM, Alexandre DERUMIER
wrote:
> >>Wou
Hi Stefan,
I posted a patch to do this a while back:
http://pve.proxmox.com/pipermail/pve-devel/2013-April/006995.html
It will need a few changes to work on pve-test but we have been running it
in production for a few years now.
On Thu, Feb 12, 2015 at 8:44 AM, Stefan Priebe
wrote:
>
> Am
anual
bridge_ports bond0.104
bridge_stp off
bridge_fd 0
On Sat, Feb 14, 2015 at 9:11 PM, Stefan Priebe
wrote:
> Hi,
>
> how does your interfaces file looks like?
>
> Thanks!
>
> Stefan
>
> Am 11.02.2015 um 22:28 schrieb Andrew Thrift:
>
>>
I agree.
This would be of a big benefit to us, we quite often have to fix up VM's
that users have created with sub-optimal disk and network configurations.
On Wed, Feb 18, 2015 at 1:31 AM, Alexandre DERUMIER
wrote:
> >>A fast workaround/hack would be to add such setting to datacenter.cfg
>
>
We have found you need to nest the bridges to get QinQ to work in all
scenarios.
e.g. The above patch will work for MOST scenarios, but if you attach a vlan
aware VM to the parent vmbr0 bridge it will cause traffic to the VM's to
stop, or will not be able to see the tagged frames.
The patch we use
Hi Alexandre,
This may be the cause of the crashes we have been experiencing.We
reported them here:
http://forum.proxmox.com/threads/21276-Kernel-Oops-Panic-on-3-10-5-and-3-10-7-Kernels
These only started happening since we moved to qemu-2.1.x and we get the
same output:
# info balloon
ball
oon bug, have been
> migrated from old proxmox (without stop/start ?)
> can you check in ssh if the kvm process have -machine type in the command
> line ?
>
>
> - Mail original -
> De: "aderumier"
> À: "Andrew Thrift"
> Cc: "pve-devel"
So with the ebtables patch, bridge filter rules can be configured via the
PVE API and WebUI ?
On Fri, Mar 13, 2015 at 9:10 PM, Dietmar Maurer wrote:
> > >>So it should be safe to use the vlan_filtering code?
> >
> > Maybe can we wait for rhel 7.1 kernel ? I think it should be pretty
> stable,
Did this patch make its way in to the pve-enterprise repository ?
On Mon, Mar 9, 2015 at 8:22 PM, Alexandre Derumier
wrote:
> The problem seem to come from polling interval, which is not setup
> automatically
> when -machine option exist.
>
> We already setup it manually, but not when we are do
We have been running 3.10 in production for over 2 years now. No real
problems.
On Mon, May 4, 2015 at 10:33 PM, Martin Waschbüsch
wrote:
> Hi there,
>
> I have experienced some VM crashes when trying to run 64bit FreeBSD guests.
> Apparently, if I read the posts on the forum right, the 3.10
I think it is a brilliant idea.
On Wed, May 6, 2015 at 5:24 AM, Alexandre DERUMIER
wrote:
> Hi,
>
> I wonder if we could add some kind of cloudinit support to proxmox.
>
> It's already implemented in openstack,ovirt,rhev
>
> http://www.ovirt.org/Features/Cloud-Init_Integration
>
>
> and supporte
Thanks Alexandre,
This sounds like it could fix the corruption issues we have been
experiencing when doing drive-mirror's on RBD.
On Tue, May 12, 2015 at 1:55 AM, Alexandre Derumier
wrote:
> this is candidate for proxmox 3.4 fixes && proxmox 4.0
>
>
> First patch use new "ready" flag introduce
Hi Guys,
There are a number of important fixes in the Ceph Firefly 0.80.9 release,
in particular fixes for qemu+librbd performance.
Is there any reason the PVE-Enterprise repository is still on 0.80.8 ?
Can this be updated ?
Thanks,
___
pve-devel ma
Hi Alexandre,
We also use QinQ and have submitted patches for the previous network
implementation that made use of a "bridge in bridge" design to achieve the
QinQ functionality.
The new vlan aware bridge implementation will be a lot cleaner.
When your patches are ready we will test them and prov
bridge_vlan_aware yes
> bridge_ports eth0 customer1l
> bridge_stp off
> bridge_fd 0
> post-up echo 0x88a8 > /sys/class/net/vmbr0/bridge/vlan_protocol
> post-up bridge vlan add dev customer1l vid 10 pvid untagged
>
>
> - Mail original -
AM, Andrew Thrift
wrote:
> Hi Alexandre,
>
> This looks like it should work.
>
> Something to be aware of, QinQ does not always have an outer tag with
> ethertype 0x88a8, it can also have a tag of 0x8100 or 0x9100 depending on
> the implementation.
>
> For example:
>
&g
t;
> >>auto vmbrcustomer1
> >>iface vmbrcustomer1 inet manual
> >>bridge_vlan_aware yes
> >>bridge_ports eth0.10
> >>bridge_stp off
> >>bridge_fd 0
> >>pre-up ip link add link eth0 eth0.10 type vlan proto 802.1ad
60 matches
Mail list logo
