Hi Gilberto
Many thanks for your reply
Unfortunately, with the message of apply pci=nocrs, i did and after of the
reboot, i get the same message of errors, so i know that this message is
useless.
Can anybody help me? :-(
Best regards
Cesar
- Original Message -
From:
+ } elsif (PVE::QemuServer::drive_is_device($drive)) {
+ $newconf-{$opt} = $value; # simply copy configuration
So where do you make a copy of the device data?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
Hi!
Wouldn't this cause issues with multiple systems attempting to control the
same device simultaneously?
Whenever you use software, you need to think. The same applies here.
It is possible to clone the VM manually by copying the conf file and the
referenced virtual disks. The advantage of
Hello Dietmar!
So where do you make a copy of the device data?
I do the same like for CDROMs. This line will copy the configuration entry in
the conf file. The device data is on the device and remains there (like it does
for CDROMs).
BR,
Jasmin
On Sun, 26 Oct 2014 11:04:40 +0100
Jasmin J. jas...@anw.at wrote:
I intended to use cloning a VM with a device to make a copy of the current
state just before I do changes in the VM (e.g: update, install new software).
And yes, it might be a problem to start the cloned VM together with the
Perhaps this is a silly question, but do you enable IPMI on BIOS???
2014-10-25 22:49 GMT-02:00 Cesar Peschiera br...@click.com.py:
Hi
I recently i installed PVE 3.3 (pve-kernel-2.6.32-33-pve: 2.6.32-138) in a
Dell PowerEdge R720, after the install i get these errors in the kern.log
file:
Does it work if you rollback to previous kernel ?
- Mail original -
De: Cesar Peschiera br...@click.com.py
À: pve-devel@pve.proxmox.com
Envoyé: Dimanche 26 Octobre 2014 02:49:19
Objet: [pve-devel] PVE 3.3 with problems of Kernel on Dell R720
Hi
I recently i installed PVE 3.3
Or perhaps, if you install pve-kernel-3.10.0-4-pve?!?
2014-10-26 9:06 GMT-02:00 Alexandre DERUMIER aderum...@odiso.com:
Does it work if you rollback to previous kernel ?
- Mail original -
De: Cesar Peschiera br...@click.com.py
À: pve-devel@pve.proxmox.com
Envoyé: Dimanche 26
pve-kernel-3.10.0-4-pve works fine for me on dell r620 and dell r815
- Mail original -
De: Gilberto Nunes gilberto.nune...@gmail.com
À: Alexandre DERUMIER aderum...@odiso.com
Cc: Cesar Peschiera br...@click.com.py, pve-devel@pve.proxmox.com
Envoyé: Dimanche 26 Octobre 2014 12:11:23
Hi!
In your case choosing Qcow2 as image format for your VMs seems
appropriate since this will give you the choice of doing snapshots of your
VMs before doing any changes and the decide after your changes whether to
rollback the changes or delete the snapshot.
a) We discuss a patch to
So where do you make a copy of the device data?
I do the same like for CDROMs. This line will copy the configuration entry in
the
conf file. The device data is on the device and remains there (like it does
for
CDROMs).
This is not a 'clone', and nothing I want to add.
This is not a 'clone', and nothing I want to add.
And virtual disks are copied to new disks as expected for a clone. Only the
disk device content isn't copied.
Imagine there is a device with 4TB mapped to a guest. There is no possibility
to copy this huge amount of data. When people do disk
Imagine there is a device with 4TB mapped to a guest. There is no possibility
to
copy this huge amount of data. When people do disk device mappings, they
know what they are doing, so indeed they know that a copy will reference the
same physical disk.
Again, this is not a 'clone'.
What
Dear,
about that pmxcfs can not handle large files, I need a little help to
create a 2nd blacklist with many
IPs for automatic blocking, so as the normal blacklist in proxmox does!
Dietmar write me in the forum, to make with ipset. I have read the man
just before but I cant understand
how to
Unfortunately I obtain the same messages of error with the previous kernel
(pve-kernel-2.6.32-32-pve: 2.6.32-136)
- Original Message -
From: Alexandre DERUMIER aderum...@odiso.com
To: Cesar Peschiera br...@click.com.py
Cc: pve-devel@pve.proxmox.com
Sent: Sunday, October 26, 2014 8:06
Do you try 3.11.X
2014-10-26 18:35 GMT-02:00 Cesar Peschiera br...@click.com.py:
Unfortunately I obtain the same messages of error with the previous kernel
(pve-kernel-2.6.32-32-pve: 2.6.32-136)
- Original Message - From: Alexandre DERUMIER
aderum...@odiso.com
To: Cesar Peschiera
Many thanks Gilberto for give me a hand, and yes, inclusive from my
workstation, i am using the virtual console on the iDRAC7 Enterprise for
manage the OS installed on the host.
Anybody have some other idea? ... i believe that i should to make some changes
in the kernel, so the help should
I have not tried the Red Hat kernel 3.x
I can see in the repository of PVE (not enterprise) these versions:
pve-kernel-3.10.0-1-pve_3.10.0-5_amd64.deb
pve-kernel-3.10.0-2-pve_3.10.0-8_amd64.deb
pve-kernel-3.10.0-2-pve_3.10.0-10_amd64.deb
pve-kernel-3.10.0-3-pve_3.10.0-11_amd64.deb
Well... I am not quite sure. but if you do not attempt to use OpenVZ and
only KVM VM's, you could even try the Debian based kernel... And not the
PVE kernel.
But, I think that Proxmox staff has more explanation about all this
stuff
2014-10-26 19:02 GMT-02:00 Cesar Peschiera
Hi Detlef
I guess that your firewall not be functioning optimally if you add the
130.00 rules in ipset, due to that for each network packet the firewall must
do 130.000 checks.
A suggestion: when i need add all ip address of a country, or several
countries, is better use a program that have a
27.10.2014 0:31, Cesar Peschiera пишет:
I guess that your firewall not be functioning optimally if you add the
130.00 rules in ipset, due to that for each network packet the firewall must
do 130.000 checks.
What? Did you mean plain list of single-address rules? Because IPSET
21 matches
Mail list logo
