The Saturday 30 Aug 2014 à 19:22:09 (+0200), Benoît Canet wrote :
> The Saturday 30 Aug 2014 à 17:04:12 (+0100), Richard W.M. Jones wrote :
> > BTW, what is "tcmu-runner"? The github repo you pointed to is ... opaque.
>
> Andy Groover.
My apologizes for the mispelling.
>is working on a way to i
Hello,
I see. I wasn't aware of such constraints. Thanks
Best regards,
Jaume
On Sat, Aug 30, 2014 at 12:58 AM, Richard Henderson wrote:
> On 08/28/2014 01:44 PM, Jaume Marti Farriol wrote:
> > This patch includes changes in the helper parameters, for the
> instructions involved in saving to m
Hello,
I thought that it was more readable with 2 boolean arguments, but I will
encode them into a single argument. Also, on fxsave and fxrstor helpers I
will encode the data32 and data64 parmeters into a single one.
Best regards,
Jaume
On Sat, Aug 30, 2014 at 12:57 AM, Richard Henderson wrote:
On 30.08.14 07:55, Anton Blanchard wrote:
> dtc fails on a recent QEMU snapshot:
>
> ERROR (name_properties): "name" property in /hypervisor#1 is incorrect
> ("hypervisor" instead of base node name)
>
> Looking at the device tree we have a hypervisor property:
>
> # lsprop hypervisor
> hyperv
Public bug reported:
I am using QEMU 2.1.0 on a Slackware 14.1 operating system (with Linux
3.15.8).
I run QEMU like this:
$ qemu-system-i386 slackware-14.1-install-dvd.iso
I have also tested with the "-enable-kvm" and the "-m 1000" options.
And QEMU does not work.
I mean, after 10 minutes, noth
** Attachment added: "the qemu window after 10 minutes"
https://bugs.launchpad.net/qemu/+bug/1363467/+attachment/4190981/+files/qemu.png
** Description changed:
I am using QEMU 2.1.0 on a Slackware 14.1 operating system (with Linux
3.15.8).
I run QEMU like this:
$ qemu-system-i386
The Saturday 30 Aug 2014 à 17:04:12 (+0100), Richard W.M. Jones wrote :
> BTW, what is "tcmu-runner"? The github repo you pointed to is ... opaque.
Andy Groover is working on a way to implement LIO storage backend in userspace.
tcmu-runner is a daemon able to load storage backend plugins for this
The Saturday 30 Aug 2014 à 17:02:12 (+0100), Richard W.M. Jones wrote :
> On Sat, Aug 30, 2014 at 05:53:43PM +0200, Benoît Canet wrote:
> > The Saturday 30 Aug 2014 à 15:46:41 (+0100), Richard W.M. Jones wrote :
> > > For the benefit of those who have absolutely no idea what you're
> > > talking ab
BTW, what is "tcmu-runner"? The github repo you pointed to is ... opaque.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs
On Sat, Aug 30, 2014 at 05:53:43PM +0200, Benoît Canet wrote:
> The Saturday 30 Aug 2014 à 15:46:41 (+0100), Richard W.M. Jones wrote :
> > For the benefit of those who have absolutely no idea what you're
> > talking about, could you write a simpler summary of what you're trying
> > to do?
> >
> >
The Saturday 30 Aug 2014 à 15:46:41 (+0100), Richard W.M. Jones wrote :
> For the benefit of those who have absolutely no idea what you're
> talking about, could you write a simpler summary of what you're trying
> to do?
>
> Rich.
Hello,
Most cloud providers sell virtualized instances either usi
I found out a few days ago that if you:
(1) Open a qcow2 file that has lazy_refcounts = on and a backing file, and
(2) Write lots of stuff, and
(3) Kill qemu with SIGTERM [which I believed, maybe incorrectly, is a
"nice" way to kill qemu]
.. then you can end up with a corrupt qcow2 file. In pa
For the benefit of those who have absolutely no idea what you're
talking about, could you write a simpler summary of what you're trying
to do?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress
Hello,
On Fri, Aug 29, 2014 at 04:58:20PM -0600, Cam Macdonell wrote:
> Hello,
>
> A bug was reported to me regarding mmaping of BAR0 in ivshmem. Indeed the
> mmap fails. This bug will affect those using the ivshmem server as BAR0
> contains the registers for sending and receiving interrupts.
From: Gonglei
Add a qom property with the same name 'bootindex',
when we remove it form qdev property, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-off-by: Gonglei
---
hw/net/rtl8139.c | 24
1 file
From: Gonglei
Only in this way, we can assure the new bootindex take effect
during vm rebooting.
Signed-off-by: Gonglei
---
hw/block/fdc.c | 6 +++---
hw/block/virtio-blk.c| 4 ++--
hw/i386/kvm/pci-assign.c | 4 ++--
hw/ide/qdev.c| 14 +++---
hw/misc/vfio.c
From: Gonglei
Add a qom property with the same name 'bootindex',
when we remove it form qdev property, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-off-by: Gonglei
---
hw/net/vmxnet3.c | 24
1 file
From: Gonglei
Remove bootindexA/B form qdev property to qom, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-off-by: Gonglei
---
hw/block/fdc.c | 47 +--
1 file changed, 45 insertio
From: Gonglei
Introduce del_boot_device_path() to clean up fw_cfg content when
hot-unplugging a device that refers to a bootindex.
Signed-off-by: Gonglei
Signed-off-by: Chenliang
---
include/sysemu/sysemu.h | 1 +
vl.c| 36
2 files cha
From: Gonglei
Add a qom property with the same name 'bootindex',
when we remove it form qdev property, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-off-by: Gonglei
---
hw/net/lance.c | 26 ++
hw
From: Gonglei
Add a qom property with the same name 'bootindex',
when we remove it form qdev property, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-off-by: Gonglei
---
hw/usb/dev-network.c | 24
1
From: Gonglei
We must assure that the changed bootindex can take effect
when guest is rebooted. So we introduce fw_cfg_machine_reset(),
which change the fw_cfg file's bootindex data using the new
global fw_boot_order list.
Signed-off-by: Chenliang
Signed-off-by: Gonglei
---
hw/nvram/fw_cfg.c
From: Gonglei
Add a qom property with the same name 'bootindex',
when we remove it form qdev property, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-off-by: Gonglei
---
hw/net/spapr_llan.c | 24
1 f
From: Gonglei
Remove bootindex form qdev property to qom, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-off-by: Gonglei
---
hw/i386/kvm/pci-assign.c | 25 -
1 file changed, 24 insertions(+), 1 deleti
From: Gonglei
Add a qom property with the same name 'bootindex',
when we remove it form qdev property, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-off-by: Gonglei
---
hw/net/ne2000.c | 26 ++
1 fil
From: Gonglei
Device should be removed from global boot list when
it is hot-unplugged.
Signed-off-by: Gonglei
Signed-off-by: Chenliang
---
hw/core/qdev.c | 4
1 file changed, 4 insertions(+)
diff --git a/hw/core/qdev.c b/hw/core/qdev.c
index da1ba48..70294ad 100644
--- a/hw/core/qdev.c
From: Gonglei
Remove bootindex form qdev property to qom, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-off-by: Gonglei
---
hw/usb/host-libusb.c | 26 +-
1 file changed, 25 insertions(+), 1 deletion(
From: Gonglei
Sometimes, we want to modify boot order of a guest, but no need to
shutdown it. We can call dynamic changing bootindex of a guest, which
can be assured taking effect just after the guest rebooting.
For example, in P2V scene, we boot a guest and then attach a
new system disk, for co
From: Gonglei
Add a qom property with the same name 'bootindex',
when we remove it form qdev property, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-off-by: Gonglei
---
hw/scsi/scsi-disk.c| 29 ++
From: Gonglei
Add a qom property with the same name 'bootindex',
when we remove it form qdev property, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-off-by: Gonglei
---
hw/net/virtio-net.c| 20
hw/v
From: Gonglei
Add a qom property with the same name 'bootindex',
when we remove it form qdev property, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-off-by: Gonglei
---
hw/ide/qdev.c | 28
1 fil
From: Gonglei
when we remove bootindex form qdev.property to qom.property,
we can use those functions set/get bootindex property for all
correlative devices.
Signed-off-by: Gonglei
---
include/sysemu/sysemu.h | 4
vl.c| 27 +++
2 files changed,
From: Gonglei
Remove bootindex form qdev property to qom, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-off-by: Gonglei
---
hw/misc/vfio.c | 26 +-
1 file changed, 25 insertions(+), 1 deletion(-)
di
From: Gonglei
When set a device's bootindex to -1, we remove it from global
fw_boot_order list.
Signed-off-by: Gonglei
---
vl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/vl.c b/vl.c
index 4d5a889..f2c3b2d 100644
--- a/vl.c
+++ b/vl.c
@@ -1313,6 +1313,7 @@ void add_boot_device_path(in
From: Gonglei
Add a qom property with the same name 'bootindex',
when we remove it form qdev property, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-off-by: Gonglei
---
hw/block/virtio-blk.c | 19 +++
1 file
From: Gonglei
Remove bootindex form qdev property to qom, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Meanwhile set the initial value of bootindex to -1.
Signed-off-by: Gonglei
---
hw/net/e1000.c | 1 +
hw/net/eepro100.
From: Gonglei
Remove bootindex form qdev property to qom, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Meanwhile set the initial value of bootindex to -1.
Signed-off-by: Gonglei
---
hw/block/virtio-blk.c| 1 +
hw/ide/qdev.c
From: Gonglei
Determine whether a given bootindex exists or not.
If exists, we report an error.
Signed-off-by: Gonglei
---
include/sysemu/sysemu.h | 1 +
vl.c| 15 +++
2 files changed, 16 insertions(+)
diff --git a/include/sysemu/sysemu.h b/include/sysemu/syse
From: Gonglei
Add the function of updating bootindex about fw_boot_order list
in add_boot_device_path(). We should delete the old one if a
device has existed in global fw_boot_order list.
Signed-off-by: Gonglei
---
vl.c | 21 +
1 file changed, 21 insertions(+)
diff --git a
From: Gonglei
Remove bootindex form qdev property to qom, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-off-by: Gonglei
---
hw/usb/redirect.c | 28 +++-
1 file changed, 27 insertions(+), 1 deletion(-
From: Gonglei
Add a qom property with the same name 'bootindex',
when we remove it form qdev property, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-off-by: Gonglei
---
hw/net/e1000.c | 26 ++
1 file
From: Gonglei
Add a qom property with the same name 'bootindex',
when we remove it form qdev property, things will
continue to work just fine, and we can use qom features
which are not supported by qdev property.
Signed-ooff-by: Gonglei
---
hw/net/eepro100.c | 26 +-
1
Peter Maydell wrote on 2014/08/29 20:01:12:
.
>
> What I really would like is a way for the kernel to tell the
> interpreter binary what particular mangling it's chosen to do
> of the command line arguments. Then we could have one
> binary that coped in both situations and when run via the
>
On Friday 29 August 2014 03:46 AM, Alexander Graf wrote:
>
>
> On 28.08.14 19:42, Aravinda Prasad wrote:
>>
>>
>> On Thursday 28 August 2014 02:07 PM, Alexander Graf wrote:
>>>
>>>
>>> On 28.08.14 08:38, Aravinda Prasad wrote:
On Wednesday 27 August 2014 04:07 PM, Alexander Graf
On Friday 29 August 2014 01:37 AM, Benjamin Herrenschmidt wrote:
> On Thu, 2014-08-28 at 22:47 +0530, Aravinda Prasad wrote:
>> Should we avoid having error log in 0x7000? As per above only
>> ibm,nmi-register-2 places error log in 0x7000 which will be terminated
>> in future?
>
> The question i
45 matches
Mail list logo
