qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Monitor file path length limitation


From: Simon
Subject: [Qemu-devel] Monitor file path length limitation
Date: Wed, 24 May 2017 17:16:58 +0200
User-agent: Roundcube Webmail/1.1.2

Hello,

It seems that the monitor file path length is limited to about 100 characters (107 to be precise).

Currently I'm using the '-monitor' parameter to create the monitor file in a directory which gather all the files related to a given VM (monitor file, PID file, disk image, etc.):

-monitor 'unix:/home/user/vmtools/test/out/foobar.iso/foobar.iso_A/foobar.iso_B/foobar.iso_C/foobar.iso_D/foobar.iso_E/monitor.sock,server,nowait'

With this command Qemu does not produce any warning or error message but create the socket file "mon" instead of the expected "monitor.sock".

Things go even worse if I add a further nesting:

-monitor 'unix:/home/user/vmtools/test/out/foobar.iso/foobar.iso_A/foobar.iso_B/foobar.iso_C/foobar.iso_D/foobar.iso_E/foobar.iso_F/monitor.sock,server,nowait'

Now, still without any warning, Qemu creates a file named "foo" in the parent directory ('foobar.iso_E/') instead of the expected directory ('foobar.iso_E/').

Is there a clean way to work around this limitation? For instance, is there an alternative option I can use to generate this monitor file? Or should I just assume that absolute paths are not supported in the '-monitor' option and change the working directory before launching Qemu so I can pass "./monitor.sock" as monitor file path (I really prefer to use absolute path whenever possible though).

As a side-note, is there any technical reason for such a limitation?

Regards,
Simon.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]