--- Begin Message ---
I think I have wrongly dropped nbd with unix socket in my last patch
series, but previously it was:
+} elsif ($path =~ m/^nbd:(\S+):(\d+):exportname=(\S+)$/) {
+ my $server = { type => 'inet', host => $1, port => $2 };
+ $blockdev = { driver => 'nbd', serve
--- Begin Message ---
>>The 'snapshot' option, for QEMU's snapshot mode, i.e. writes are only
>>temporary, is not yet supported.
from qemu manpage:
"
-snapshot
Write to temporary files instead of disk image files. In
this case, the raw disk image you use is not written back.
--- Begin Message ---
>>With '-blockdev', it is necessary to activate the volumes to generate
>>the command line, because it can be necessary to check whether the
>>volume is a block device or a regular file.
I was thinking about that, but do we have storage with activate_volume
need to be done fo
Am 16.06.25 um 13:31 schrieb DERUMIER, Alexandre via pve-devel:
>>> With '-blockdev', it is necessary to activate the volumes to generate
>>> the command line, because it can be necessary to check whether the
>>> volume is a block device or a regular file.
>
> I was thinking about that, but do we
Thanks for the review. Will send another updated patch.
On Fri Jun 13, 2025 at 1:19 PM CEST, Michael Köppl wrote:
> Quickly tested this in my Android emulator by following the steps
> described in the commit message (comment on that below). Was able to
> reproduce the issue before the patch. Goo
--- Begin Message ---
>>+ # QEMU recursively auto-removes the file children, i.e. file
>>and format node below the top
From my tests, it's not removing backing nodes when snapshots are used,
at least when then are defined with nodename. Don't have tested with
autogenerated backing nodes, I'll
> Fiona Ebner hat am 16.06.2025 12:34 CEST geschrieben:
>
>
> Am 13.06.25 um 12:00 schrieb Fabian Grünbichler:
> > On June 12, 2025 4:02 pm, Fiona Ebner wrote:
> >> @@ -5649,54 +5647,20 @@ sub vm_start_nolock {
> >>$nodename, $migrate_opts->{network});
> >> }
> >>
> >> +my $
Am 13.06.25 um 12:05 schrieb Fabian Grünbichler:
> On June 12, 2025 4:02 pm, Fiona Ebner wrote:
>> @@ -5654,16 +5642,28 @@ sub vm_start_nolock {
>> ($state_cmdline, $res->{migrate}, $statefile_is_a_volume) =
>> PVE::QemuServer::StateFile::statefile_cmdline_option(
>> $sto
Am 16.06.25 um 12:54 schrieb Fabian Grünbichler:
>> Fiona Ebner hat am 16.06.2025 12:34 CEST geschrieben:
>> Am 13.06.25 um 12:00 schrieb Fabian Grünbichler:
>>> On June 12, 2025 4:02 pm, Fiona Ebner wrote:
@@ -5649,54 +5647,20 @@ sub vm_start_nolock {
$nodename, $migrate_opts->{n
Am 13.06.25 um 12:25 schrieb joao.sousa:
> On 12/06/25 10:12, Fiona Ebner wrote:
>> The tests in qemu-server were updated since then. You can check out an
>> earlier commit and apply on top of that. For pve-storage, I'd guess it
>> was the code style changes, so same story:
>
> I reverted qemu-ser
On 2025-05-19 15:09, Maximiliano Sandoval wrote:
Signed-off-by: Maximiliano Sandoval
---
src/watchdog-mux.c | 26 ++
1 file changed, 26 insertions(+)
diff --git a/src/watchdog-mux.c b/src/watchdog-mux.c
index a9017b3..e14c768 100644
--- a/src/watchdog-mux.c
+++ b
tested it by applying this series to a node with HA guests and then
disabling the corosync network completely or, to test the "averted" log,
sleeping for 45 seconds before bringing the corosync network back up.
So far, it seems that the "about to expire" warning did make it into the
journal in
Hi Alexandre,
Am 16.06.25 um 08:22 schrieb DERUMIER, Alexandre via pve-devel:
> Hi Fiona,
> I'm going to test your patch serie this week
>
>>> While the last patch actually does the switch, many operations are
>>> not
>>> yet supported. It is included to show what changes I made there. It
>> shou
Am 13.06.25 um 11:18 schrieb Fabian Grünbichler:
> On June 12, 2025 4:02 pm, Fiona Ebner wrote:
>> The minimum supported binary version for Proxmox VE 9 is QEMU 10.0, so
>> there still is more than enough room for eventual regression testing
>> with older binaries.
>
> given that PVE 8.0 released
Am 13.06.25 um 11:30 schrieb Fabian Grünbichler:
> On June 12, 2025 4:02 pm, Fiona Ebner wrote:
>> For backwards-compat, to allow dropping some drive properties that are
>> long gone from QEMU.
>>
>> Signed-off-by: Fiona Ebner
>> ---
>> PVE/QemuServer.pm | 2 +-
>> 1 file changed, 1 insertion(+),
Am 19.05.25 um 15:09 schrieb Maximiliano Sandoval:
> Signed-off-by: Maximiliano Sandoval
> ---
> src/watchdog-mux.c | 26 ++
> 1 file changed, 26 insertions(+)
>
> diff --git a/src/watchdog-mux.c b/src/watchdog-mux.c
> index a9017b3..e14c768 100644
> --- a/src/watchdog-mu
On Mon, 02 Jun 2025 12:22:25 +0200, Fiona Ebner wrote:
> Only minor changes this time:
>
> Adapt to changed include paths:
> 32cad1ffb8 ("include: Rename sysemu/ -> system/")
> 407bc4bf90 ("qapi: Move include/qapi/qmp/ to include/qobject/")
>
> Adapt to a function signature change:
> 4822128693 (
Am 13.06.25 um 12:00 schrieb Fabian Grünbichler:
> On June 12, 2025 4:02 pm, Fiona Ebner wrote:
>> @@ -5649,54 +5647,20 @@ sub vm_start_nolock {
>> $nodename, $migrate_opts->{network});
>> }
>>
>> +my $res = {};
>> +my $statefile_is_a_volume;
>> +my $state_cmdline = [];
Am 13.06.25 um 09:54 schrieb Lukas Wagner:
> The proxmox-notify crate now uses tracing for logging, hence we have to
> set up some tracing logging infrastructure if we want to see any
> messages in the journal. Therefore we switch from the syslog crate to
> proxmox-log, which configures the appropr
Superseeded By v2:
https://lore.proxmox.com/pve-devel/20250616125844.52117-1-s.sh...@proxmox.com/T/#u
On Mon Jun 16, 2025 at 2:04 PM CEST, Shan Shaji wrote:
>
> Thanks for the review. Will send another updated patch.
>
> On Fri Jun 13, 2025 at 1:19 PM CEST, Michael Köppl wrote:
> > Quickly teste
Am 16.06.25 um 15:15 schrieb Fabian Grünbichler:
>> Fiona Ebner hat am 16.06.2025 14:57 CEST geschrieben:
>> Am 16.06.25 um 14:46 schrieb Fabian Grünbichler:
>>> variant B:
>>>
>>> move decision which driver to use to plugin via qemu_blockdev_options
>>
>> Yes.
>>
>>> how would the default/fallbac
> Fiona Ebner hat am 16.06.2025 14:57 CEST geschrieben:
>
>
> Am 16.06.25 um 14:46 schrieb Fabian Grünbichler:
> >> Fiona Ebner hat am 16.06.2025 13:51 CEST geschrieben:
> >> Am 16.06.25 um 13:31 schrieb DERUMIER, Alexandre via pve-devel:
> > With '-blockdev', it is necessary to activate
When the pending chip appears after enabling an option from the options
page, Flutter throws an overflow error, causing the chip to render
on top of the Switch widget due to insufficient space between
the title and the switch toggle.
To resolve this, modify the layout so that the pending chip widg
> Fiona Ebner hat am 16.06.2025 13:51 CEST geschrieben:
>
>
> Am 16.06.25 um 13:31 schrieb DERUMIER, Alexandre via pve-devel:
> >>> With '-blockdev', it is necessary to activate the volumes to generate
> >>> the command line, because it can be necessary to check whether the
> >>> volume is a
Am 16.06.25 um 14:46 schrieb Fabian Grünbichler:
>> Fiona Ebner hat am 16.06.2025 13:51 CEST geschrieben:
>> Am 16.06.25 um 13:31 schrieb DERUMIER, Alexandre via pve-devel:
> With '-blockdev', it is necessary to activate the volumes to generate
> the command line, because it can be necessa
--- Begin Message ---
> > With '-blockdev', it is necessary to activate the volumes to
> > generate
> > the command line, because it can be necessary to check whether the
> > volume is a block device or a regular file.
>>I was thinking about that, but do we have storage with
>>activate_volume
>>n
Am 19.05.25 um 15:09 schrieb Maximiliano Sandoval:
> One sync comes after warning that the watchdog is about to expire, and a
> second right after the watchdog expires.
>
> To maximize the chances the log will contain entries relevant to a fence
> event. This would be extremely useful for detectin
27 matches
Mail list logo
