>>sub storage_has_feature(feature) {
>>...
>>}
Yes, I think it could be fine.
add an hashtable with each features, and return 1/undef is the feature is
available.
Features when can add : snapshot,savevmstate
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER" , "Stefa
>>What performance to you get when you pre-allocate the raw file?
I don't think we can preallocated a raw file. (the file is empty but have a
size of xx giga)
some doc here from rehdat:
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualization/3.0/html/Administration_Gui
Am 14.09.2012 07:18, schrieb Dietmar Maurer:
Dietmar, can we add some property to a storage plugin and check it ? (I really
don't like theses hardcoded values)
I just added that to prevent over-motivated hackers to run untested code ;-)
The questions is how to implement that cleanly?
sub stor
> >>If so, we can do that by default, because metadata is small (128MB/TB).
> Note that the size file is the full size of the disk (no sparse file).
That is bad.
What performance to you get when you pre-allocate the raw file?
___
pve-devel mailing list
>>Above command only pre-allocates metadata, so creation is still fast?
Yes, it's creating the file in second
>>If so, we can do that by default, because metadata is small (128MB/TB).
Note that the size file is the full size of the disk (no sparse file).
- Mail origina
> Dietmar, can we add some property to a storage plugin and check it ? (I really
> don't like theses hardcoded values)
I just added that to prevent over-motivated hackers to run untested code ;-)
The questions is how to implement that cleanly?
sub storage_has_feature(feature) {
...
}
> >>If you
> 4)qemu-img create -f qcow2 -o
> size=100,preallocation=metadata,compat=1.1,lazy_refcounts=on
> file.img
> So I think it should be great to add an option for preallocatting metadatas,
> the boost is really huge.
Above command only pre-allocates metadata, so creation is still fast?
If so,
>>If you add nexenta then snapshotting works fine except you want to
>>include state.
>>
>>TASK ERROR: VM 102 qmp command 'snapshot-start' failed - Could not open
>>'iscsi://10.255.0.10/iqn.1986-03.com.sun:02:9f6ecfd8-ea21-cc24-fd90-f8a0d8edf0b6/6'
>>
I think it come from
# search share
Hi,
I'm playing with qcow2 on my new netapp pnfs cluster,some optimisations can be
done.
some benchmarks :
1).raw file : 2io/s
2).qcow2 file, sparse : 300 io/s :/
3).qcow2, preallocated metadatas (nosparse): 4000io/s
4).qcow2, with lazy counts + preallocated metadatas : 4000io/s. (lazy
>>OK first problem is the QemuServer.pm and the hardcoded cases where
>>snapshot is possible:
>>die "can't snapshot volume '$volid'\n"
>>if !(($scfg->{path} && $volname =~ m/\.qcow2$/) ||
>>($scfg->{type} eq 'rbd') ||
>>($scfg->{type} eq 'sheepdog'));
Dietmar, can we add some property to a
OK first problem is the QemuServer.pm and the hardcoded cases where
snapshot is possible:
die "can't snapshot volume '$volid'\n"
if !(($scfg->{path} && $volname =~ m/\.qcow2$/) ||
($scfg->{type} eq 'rbd') ||
($s
I really don't know if they implement an iptables filter to block dhcp query to
outside.
I'll try to look at the code more deeply tomorow
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER" , "Stefan Priebe - Profihost AG"
Cc: pve-devel@pve.proxmox.com
Envoyé: Jeudi 1
I'll try to test it tommorrow or this weekend. (I'm bit busy now)
- Mail original -
De: "Stefan Priebe - Profihost AG"
À: pve-devel@pve.proxmox.com
Envoyé: Jeudi 13 Septembre 2012 13:22:40
Objet: [pve-devel] Snapshot Tests
Hello list,
i started to test the snapshot functionality
> i started to test the snapshot functionality using nexenta storage.
>
> But when i want to take a snapshot i get:
> TASK ERROR: can't snapshot volume 'Cloud1Stor1:vm-103-disk-1'
Im currently try to get it work with 'qcow2' files. Tests with other storage
types
will follow next week.
___
Hello list,
i started to test the snapshot functionality using nexenta storage.
But when i want to take a snapshot i get:
TASK ERROR: can't snapshot volume 'Cloud1Stor1:vm-103-disk-1'
Stefan
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://
> I'm reading libvirt code, they seem to use dnsmasq on each bridge
Ins't that dangerous, because most times there is already an (external) DHCP
server listening?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailma
I'm reading libvirt code, they seem to use dnsmasq on each bridge
libvirt test sample
"
@DNSMASQ@ --strict-order --bind-interfaces --conf-file= \
--except-interface lo --txt-record=example,example value \
--listen-address 192.168.122.1 --listen-address 192.168.123.1 \
--listen-address 2001:db8:ac1
Hi,
i don't care about assigning IPs to vms BUT:
- IP should be removed from assigned pool when VM is deleted
- I want to assign hostnames to automatically to VMs based on VM id
- i want to automatically create DNS entries into our DNS system based
on hostname and IPs
So i'm not sure whether t
18 matches
Mail list logo
