[Qemu-devel] [Bug 1587065] Re: btrfs qemu-ga - multiple mounts block fsfreeze

2016-08-28 Thread Tim Rose
I have a related Problem with a libvirt Guest running some Docker- Containers. root@docker1:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 7.9G 2.9G 4.6G 39% / udev 10M 0 10M 0% /dev tmpfs 794M 8.6M 785M 2% /run tmpfs 2.0G

[Qemu-devel] [RFC] target-i386: present virtual L3 cache info for vcpus

2016-08-28 Thread Longpeng (Mike)
This patch presents virtual L3 cache info for virtual cpus. Some software algorithms are based on the hardware's cache info, for example, for x86 linux kernel, when cpu1 want to wakeup a task on cpu2, cpu1 will trigger a resched IPI and told cpu2 to do the wakeup if they don't share low level cach

Re: [Qemu-devel] [PATCH v2 2/5] 9p: disallow the NUL character in all strings

2016-08-28 Thread Greg Kurz
On Fri, 26 Aug 2016 17:07:08 +0200 Greg Kurz wrote: > According to the 9P spec at http://man.cat-v.org/plan_9/5/intro : > > Data items of larger or variable lengths are represented by a > two-byte field specifying a count, n, followed by n bytes of > data. Text strings are represented this way,

Re: [Qemu-devel] [PATCH] ipmi: chassis poweroff should use qemu_system_shutdown_request()

2016-08-28 Thread Greg Kurz
On Fri, 26 Aug 2016 18:05:31 +0200 Cédric Le Goater wrote: > When issuing a chassis 'powerdown' control command, the routine > qemu_system_shutdown_request() should be used to exit the guest. > qemu_system_powerdown_request() will initiate a soft shutdown which is > not what is required by the IP

Re: [Qemu-devel] [Qemu-ppc] eTSEC device on ppce500

2016-08-28 Thread Alexander Graf
> On 26 Aug 2016, at 11:19, Alin Rauta wrote: > > Hi, > I am interested in using the eTSEC for ppce500, but looking through the code > tree it seems the “etsec_create” function is never called. > Perhaps I’m not using the right command when starting QEMU, do we have an > example for eTSEC ? >

Re: [Qemu-devel] [PATCH v2 5/5] 9p: forbid empty extension string

2016-08-28 Thread Peter Maydell
On 28 August 2016 at 13:21, Greg Kurz wrote: > Peter, > > Since you suggested to do explicit error checking on empty file names, do > you have an opinion on the case of symlinks with an empty target ? I have no strong opinion here. I was just aiming for the general principles of consistency and p

Re: [Qemu-devel] [PATCH v2 5/5] 9p: forbid empty extension string

2016-08-28 Thread Greg Kurz
On Sun, 28 Aug 2016 19:21:25 +0200 Greg Kurz wrote: > On Fri, 26 Aug 2016 14:00:37 -0500 > Eric Blake wrote: > > > On 08/26/2016 10:07 AM, Greg Kurz wrote: > > > A buggy guest using the 9p2000.u protocol can issue a create request and > > > pass an empty string as the extension argument. This

Re: [Qemu-devel] [PATCH v2 5/5] 9p: forbid empty extension string

2016-08-28 Thread Greg Kurz
On Fri, 26 Aug 2016 14:00:37 -0500 Eric Blake wrote: > On 08/26/2016 10:07 AM, Greg Kurz wrote: > > A buggy guest using the 9p2000.u protocol can issue a create request and > > pass an empty string as the extension argument. This causes QEMU to crash > > in the case of a hard link or a special fi

Re: [Qemu-devel] [PATCH v2 3/5] 9p: forbid . and .. in file names

2016-08-28 Thread Greg Kurz
On Fri, 26 Aug 2016 13:49:00 -0500 Eric Blake wrote: > On 08/26/2016 10:07 AM, Greg Kurz wrote: > > According to the 9P spec http://man.cat-v.org/plan_9/5/open about the > > create request: > > > > The names . and .. are special; it is illegal to create files with these > > names. > > > > This

Re: [Qemu-devel] [PATCH v2 2/5] 9p: disallow the NUL character in all strings

2016-08-28 Thread Greg Kurz
On Fri, 26 Aug 2016 13:41:23 -0500 Eric Blake wrote: > On 08/26/2016 10:07 AM, Greg Kurz wrote: > > According to the 9P spec at http://man.cat-v.org/plan_9/5/intro : > > > > Data items of larger or variable lengths are represented by a > > two-byte field specifying a count, n, followed by n byte

Re: [Qemu-devel] [PATCH v2 1/5] 9p: forbid illegal path names

2016-08-28 Thread Greg Kurz
On Fri, 26 Aug 2016 13:33:28 -0500 Eric Blake wrote: > On 08/26/2016 10:07 AM, Greg Kurz wrote: > > Empty path components don't make sense and may cause undefined behavior, > > depending on the backend. > > > > Also, the walk request described in the 9P spec [1] clearly shows that > > the client