Re: [Qemu-devel] RAMBlock's named ""

2017-03-09 Thread Paolo Bonzini
On 07/03/2017 20:46, Dr. David Alan Gilbert wrote: > (from https://bugzilla.redhat.com/show_bug.cgi?id=1425273) > The simplest reproducer of this is: > > ./qemu-system-x86_64 -nographic -device e1000e,id=foo -m 1G -M pc,accel=kvm > my.img > > with a Linux image and after it's booted do

Re: [Qemu-devel] RAMBlock's named ""

2017-03-08 Thread Juan Quintela
"Dr. David Alan Gilbert" wrote: > * Igor Mammedov (imamm...@redhat.com) wrote: >> On Tue, 7 Mar 2017 19:46:56 + >> "Dr. David Alan Gilbert" wrote: >> >> > We seem to have a couple of weird cases where we end up with >> > RAMBlocks with no name; I think they'll badly confuse >> > the migrati

Re: [Qemu-devel] RAMBlock's named ""

2017-03-08 Thread Dr. David Alan Gilbert
* Igor Mammedov (imamm...@redhat.com) wrote: > On Tue, 7 Mar 2017 19:46:56 + > "Dr. David Alan Gilbert" wrote: > > > We seem to have a couple of weird cases where we end up with > > RAMBlocks with no name; I think they'll badly confuse > > the migration code, but I don't quite understand how

Re: [Qemu-devel] RAMBlock's named ""

2017-03-08 Thread Igor Mammedov
On Tue, 7 Mar 2017 19:46:56 + "Dr. David Alan Gilbert" wrote: > We seem to have a couple of weird cases where we end up with > RAMBlocks with no name; I think they'll badly confuse > the migration code, but I don't quite understand how they're > happening. > > 1) device_del e1000e > 2) -obj

Re: [Qemu-devel] RAMBlock's named ""

2017-03-08 Thread Dr. David Alan Gilbert
* Peter Maydell (peter.mayd...@linaro.org) wrote: > On 7 March 2017 at 20:46, Dr. David Alan Gilbert wrote: > > The real fun is that there doesn't seem to be anything that stops > > two blocks having the same name! > > The memory region API says that the name is for debugging only, > so the probl

Re: [Qemu-devel] RAMBlock's named ""

2017-03-07 Thread Peter Maydell
On 7 March 2017 at 20:46, Dr. David Alan Gilbert wrote: > The real fun is that there doesn't seem to be anything that stops > two blocks having the same name! The memory region API says that the name is for debugging only, so the problem is in code which relies on them being unique :-) thanks --

[Qemu-devel] RAMBlock's named ""

2017-03-07 Thread Dr. David Alan Gilbert
We seem to have a couple of weird cases where we end up with RAMBlocks with no name; I think they'll badly confuse the migration code, but I don't quite understand how they're happening. 1) device_del e1000e 2) -object memory-backend-file without wiring it up I added some debug into migration/r