We have been trying to build a multicore NoC emulator, which can runs a full
system. We plan to run the full system in qemu and get information from
traces to feed noxim,which is a NoC emulator. Noxim needs to read a taskList
to start emulating. Each task include the following data fields:
#Exe
I see,
Thanks
> On 2 May 2019, at 17:21, Eric Blake wrote:
>
> On 5/2/19 8:58 AM, Sam Eiderman wrote:
>> This patch series aims to improve the speed of qemu-img rebase.
>>
>> 1. Mainly by removing unnecessary reads when rebasing on the same
>> chain.
>&g
mit my fix (which is very similar to what Max did) without the
original change?
Sam
> On 3 May 2019, at 17:32, Max Reitz wrote:
>
> On 03.05.19 13:34, Thomas Huth wrote:
>> Hi Sam,
>>
>> On 02/05/2019 15.08, Sam Eiderman wrote:
>>> Commit b69864e ("v
Gentle ping on "[PATCH 2/2] vmdk: Add read-only support for seSparse snapshots”.
Yuchenlin reviewed "[PATCH 1/2] vmdk: Fix comment regarding max l1_size
coverage”.
Thanks, Sam
> On 24 Apr 2019, at 10:48, Sam Eiderman wrote:
>
> VMware introduced a new snapshot format
Hi all,
I'm running `QEMU_CMD ...` to create a vm. And I enable all events.
For qemu and ovs-dpdk(ovs-2.4.9 with dpdk-2.2.0) environment, when I add
'-chardev
socket,id=char-n-ddc979cd,path=/usr/local/var/run/openvswitch/n-ddc979cd,server'
option, I got a very long time to start vm, detail log is
Hi all,
I'm running `QEMU_CMD ...` to create a vm under dpdk huge page envriment
(which set huge page 1G). And I enable all events in qemu.
For qemu and ovs-dpdk(ovs-2.4.9 with dpdk-2.2.0) environment, detail log is:
> 30012@1497443246.678304:object_dynamic_cast_assert
qemu:memory-region->qemu:m
that's the question I can't figure
out.
And qemu long time start up only happened in huge page enviroment, I don't
know why.
2017-06-19 17:45 GMT+08:00 Daniel P. Berrange :
> On Mon, Jun 19, 2017 at 05:30:59PM +0800, Sam wrote:
> > Hi all,
> >
> > I
Hi all,
We plan to use DPDK on HP host machine with several core and big memory. We
plan to use qemu-kvm enviroment. The host will carry 4 or more guest vm and
1 ovs.
Ovs-dpdk is much faster then normal ovs, but to use ovs-dpdk, we have to
enable huge page globally.
My question is, will huge pag
BTW, we also think about use ovs-dpdk in docker enviroment, but test result
said it's not good idea, we don't know why.
2017-06-21 11:32 GMT+08:00 Sam :
> Hi all,
>
> We plan to use DPDK on HP host machine with several core and big memory.
> We plan to use qemu-kvm env
For qemu, I don't know why, as there is no log to
report this.
2017-06-21 14:15 GMT+08:00 Pavel Shirshov :
> Hi Sam,
>
> Below I'm saying about KVM. I don't have experience with vbox and others.
> 1. I'd suggest don't use dpdk inside of VM if you want to see best
hi all，
I'm debuging ovs-2.6.0, dpdk-2.2.0 and qemu-2.6.0. And I run such command:
QEMU_CMD -D qemu-log.log -trace events=qemu-events ...
I want to trace vhost-user protocol process between QEMU and ovs-dpdk.
Ovs-dpdk's log shows lots of infomations of vhost-user protocol, but QEMU's
log shows o
hi all,
I'm running `qemu-system-x86_64 ...` to start a guest vm. Now I want to
stop and destroy this vm, I found there is no `qemu-stop` related command,
so I have to `kill -9` this process.
How could I stop `qemu-system-x86_64` instead of `kill -9`? Use `virsh`
command or something?
Thank you~
Hi all,
I start VM using command like this:
-chardev socket,path=/home/gangyewei-3/kvm/qga.sock,server,nowait,id=qga0
> -device virtio-serial -device
> virtserialport,chardev=qga0,name=org.qemu.guest_agent.0
But When I use socat to send command (
https://wiki.qemu.org/Features/GuestAgent), it b
rdev
> socket,path=/home/gangyewei-3/kvm/qga.sock,server,nowait,id=qga0 -device
> virtio-serial -device
> virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 -incoming tcp:0:4444
2017-08-22 17:54 GMT+08:00 Sam :
> Hi all,
>
> I start VM using command like this:
>
> -chardev s
=on -numa
> node,memdev=mem -mem-prealloc -chardev socket,path=/home/gangyewei-3/
> kvm/qga.sock,server,nowait,id=qga0 -device virtio-serial -device
> virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 -incoming
> tcp:0:
2017-08-22 18:00 GMT+08:00 Sam :
> whole command is :
Hi all,
I'm using qga to send `route -n` and `ping` command to guest. But I found
SOMETIMES, the second `ping` command's result is the same as `route -n`
command.
So I guess is there some cache mechanism of qga command result? So when I
send the second command, and receive from qga socket, I rece
10:11 GMT+08:00 Sam :
> Hi all,
>
> I'm using qga to send `route -n` and `ping` command to guest. But I found
> SOMETIMES, the second `ping` command's result is the same as `route -n`
> command.
>
> So I guess is there some cache mechanism of qga command result? So w
Hi all,
I'm starting vm using:
kvm]$ sudo /usr/local/bin/qemu-system-x86_64 -m 256 -hda test.qcow2 -cdrom
> CentOS-7-x86_64-DVD-1503-01.iso -boot d
> VNC server running on '127.0.0.1:5900'
then I start vnc client in another PC to connect 10.253.23.24:11800 and
10.253.23.24:5900, I got time out,
I follow this:
https://en.wikibooks.org/wiki/QEMU/QEMU_Hello_World:_Installing_QEMU_and_getting_it_up_and_running
2017-08-25 14:31 GMT+08:00 Sam :
> Hi all,
>
> I'm starting vm using:
>
> kvm]$ sudo /usr/local/bin/qemu-system-x86_64 -m 256 -hda test.qcow2
>> -cdrom C
Actually, I just want to install OS and use it, but I found I can't go into
guest OS (as vnc time out), so what should I do?
2017-08-25 14:45 GMT+08:00 Sam :
> I follow this:
> https://en.wikibooks.org/wiki/QEMU/QEMU_Hello_World:_
> Installing_QEMU_and_getting_it_up_and_running
>
I use ssh to the host PC, so I think I could not use two screen.
2017-08-25 15:38 GMT+08:00 Sam :
> Actually, I just want to install OS and use it, but I found I can't go
> into guest OS (as vnc time out), so what should I do?
>
> 2017-08-25 14:45 GMT+08:00 Sam :
>
>&g
,nowait,id=qga0 \
-device virtio-serial \
-device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 \
-incoming tcp:0:80818
2017-08-25 16:21 GMT+08:00 Thomas Huth :
> On 25.08.2017 08:31, Sam wrote:
> > Hi all,
> >
> > I'm starting vm using:
> >
> >
I could repeat this several times, I think it's mis-order of qmp in qga
socket.
2017-08-25 11:09 GMT+08:00 Sam :
> Also I found:
>
> when I use `socat` to take a qga socket, then I use `socat` to communicate
> it will got error.
> But also SOMETIMES, I will not got error and
So how to fix this bug? And where should I to report bug?
2017-08-29 13:52 GMT+08:00 Sam :
> I could repeat this several times, I think it's mis-order of qmp in qga
> socket.
>
> 2017-08-25 11:09 GMT+08:00 Sam :
>
>> Also I found:
>>
>> when I use `socat` t
Hi all,
I'm debugging qemu start up process, I want to add a log in 'io_mem_init'
function in exce.c as bellow:
> static void io_mem_init(void)
> {
> ADD_LOG_HERE_TO_RECORD_TIME();
> memory_region_init_io(&io_mem_rom, NULL, &unassigned_mem_ops, NULL,
> NULL, UINT64_MAX);
> memory_regi
Hi all,
I want to add new trace-event and log it, so I add into $QEMU/trace-event
like this:
io_mem_init(void) ""
>
and after configure, $QEMU/build/trace-events-all also have this.
then I add code like this into $QEMU/exec.c
trace_io_mem_init();
>
then I `make` and `make install`.
But when I
Hi all,
I'm working on qemu-qga, and I want to send qmp command from this unix
socket, but it hanged there(no response), I don't know if it's connect
failed or something?
[root@yf-mos-test-net09 ~]# socat
> /opt/cloud/workspace/servers/f6fdd093-383b-444e-9bcf-dfa81794d465/qga.sock
> readline
> {"
Thank you, I think another process connect this socket, so I hanged here.
2017-07-27 18:47 GMT+08:00 Daniel P. Berrange :
> On Thu, Jul 27, 2017 at 06:37:32PM +0800, Sam wrote:
> > Hi all,
> >
> > I'm working on qemu-qga, and I want to send qmp command from this unix
Hi all,
I want to send command through qga socket, but sometimes it will hanged
there. So I want to test qga socket available first, then send qga command.
So my question is how to test qga socket available, which is not taken by
others? By timeout?
Thank you~
Hi all,
I add some log like this in QEMU_SRC/hw/i386/pc.c
+++ b/hw/i386/pc.c
>
> @@ -1364,6 +1364,13 @@ void pc_memory_init(PCMachineState *pcms,
>
>
>> linux_boot = (machine->kernel_filename != NULL);
>
>
>> +/* add for qemu start speed */
>
> +time_t rawtime;
>
> +struct tm * t
Hi all,
I'm using qemu to start vm in huge page enviroment, I use CMD1 and CMD2 to
test the time of start of a vm, CMD1 contains option '-mem-prealloc', CMD2
does not contain this.
I found while using CMD1, the time to run this command is longer then CMD2.
For words, I know this option is to wait
So if I remove '-mem-prealloc' option, the qemu will not mmap while
starting guest vm? Or will mmap after some thing? Or will mmap when admin
to trigger it by qemu command?
2017-10-25 18:44 GMT+08:00 Dr. David Alan Gilbert :
> * Sam (batmanu...@gmail.com) wrote:
> > Hi all
Waiting time is different in different server, and different with memory
and cpu usage in one server.
For HP PowerEdge R720 with 15+ VM running, it's 10+ second.
But If I remove '-mem-prealloc', it's 1 second.
2017-10-25 20:06 GMT+08:00 Dr. David Alan Gilbert :
> * Sa
For qemu-2.6.0, in huge page (1G) environment, after kill the qemu process,
memory which is alloc for the vm could not be released. Detail is bellow.
Or should I use some specific command to stop vm? I want to know if there
someone has the same problem?
The start up command is:
CMD1="$QEMU_CMD -D
BTW, I start VM by this command, and then stop it, then memory leak happens.
To compare, I start another VM, and wait for about 10 minutes, and then
kill it as I does above, then no memory leak happens.
So is this a bug of KVM or qemu ?
2017-10-26 11:09 GMT+08:00 Sam :
> For qemu-2.6.0,
I don't know if this process is:
1. qemu call kernel API to alloc 40G memory.
2. qemu process is killed by hand.
3. kernel alloc 40G memory, but qemu process is down, then this 40G is left
in kernel.
2017-10-26 11:54 GMT+08:00 Sam :
> BTW, I start VM by this command, and then stop
'-mem-prealloc' is to reduce the start time of
VM, but now it seems I have to do more test.
2017-10-26 22:02 GMT+08:00 Daniel P. Berrange :
> On Thu, Oct 26, 2017 at 11:09:49AM +0800, Sam wrote:
> > For qemu-2.6.0, in huge page (1G) environment, after kill the qemu
> process,
pt it immediately(use
`ctrl+c`).
3. then use that script to send command2(do not send command1) again, then
you could get the result of command1.
2017-08-29 17:04 GMT+08:00 Sameeh Jubran :
> Hi Sam,
>
> Thanks for reporting this, in order to debug this efficiently I need you
> to provide
Qemu-2.6.0
2017-08-30 14:20 GMT+08:00 Sam :
> Hi all,
>
> I could repeat it, host os and guest os is Centos-7, qemu-ga is alive in
> guest. the step to repeat it is:
>
> 1. run python script just like the first email.
> 2. send qmp command1(cmd in the python script, like
Hi all,
I'm using python socket to connect VM's monitor socket like this:
[root@yf-mos-test-net09 tests]# python
> Python 2.7.5 (default, Jun 24 2015, 00:41:19)
> [GCC 4.8.3 20140911 (Red Hat 4.8.3-9)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> from s
/path/qemu.sock'), is it the
same socket of qga socket?
Thank you~
2017-09-04 17:36 GMT+08:00 Daniel P. Berrange :
> On Mon, Sep 04, 2017 at 02:17:39PM +0800, Sam wrote:
> > Hi all,
> >
> > I'm using python socket to connect VM's monitor socket like this:
&g
quot;query-status"}
> {"execute":"query-status"}
> unknown command: '{"execute":"query-status"}'
And I send QMP json format command, it report error as above. So where is
the monitor socket? Why I got error while using QMP comman
There are two docs:
https://wiki.qemu.org/index.php/Documentation/QMP
https://en.wikibooks.org/wiki/QEMU/Monitor
I don't know which one is right...?
2017-09-04 20:31 GMT+08:00 Sam :
> Thank you, but I have to ask last question. My qemu is 2.6.0, and there is
> no -qmp option :
&
Hi all,
I'm using HMP socket to send command to add netdev, my command like this:
[gangyewei-3@yf-mos-test-net07 tests]$ sudo python monitor.py 55919
> (qemu):
> Connected to qemu monitor ...
> on_monitor_open
> ds
> (qemu):
> {'return': ["unknown command: 'ds'"]}
> chardev-add
> socket,id=char
BTW, same result while using `telnet 127.0.0.1 55919`, which means also
have the two problem in the email before.
2017-09-08 11:23 GMT+08:00 Sam :
> Hi all,
>
> I'm using HMP socket to send command to add netdev, my command like this:
>
> [gangyewei-3@yf-mos-test-net07
_intf1,vhostforce=on
Connection closed by foreign host.
2017-09-08 11:32 GMT+08:00 Sam :
> BTW, same result while using `telnet 127.0.0.1 55919`, which means also
> have the two problem in the email before.
>
> 2017-09-08 11:23 GMT+08:00 Sam :
>
>> Hi all,
>>
>> I
Why could I not find in ovs-dpdk maillist? could some one give the bug
number?
2017-10-27 15:08 GMT+08:00 Daniel P. Berrange :
> On Fri, Oct 27, 2017 at 11:28:33AM +0800, Sam wrote:
> > After restart ovs-dpdk(which is openvswitch with dpdk lib), memory is
> > released.
> >
Hi all,
I'm debugging a mis-unmap bug in ovs-dpdk, process is this:
1. start ovs-dpdk with 10G socket memory, then use `top`, ovs-vswitchd take
10G memory. command is bellow.
2. start qemu vm1 with vhost device as server to connect port on ovs-dpdk,
command is bellow. qemu share 40G memory with o
Add support for the UUID parameter to the emulated RTAS call
ibm,get-system-parameter.
Return the guest's UUID as the value for the RTAS UUID system
parameter, or null (a zero length result) if it is not set.
Signed-off-by: Sam Bobroff
---
hw/ppc/spapr_rtas.c | 6 ++
1 file chang
This is corrected by using the rtas_st_buffer() function to write to
the buffer.
The function return value code is also slightly simplified.
Signed-off-by: Sam Bobroff
---
hw/ppc/spapr_rtas.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/hw/ppc/spapr_rtas.c b
s Run Mode" parameter.
It also improves the surrounding code a little to support the addition of
additional system parameters.
Sam Bobroff (4):
spapr: Add rtas_st_buffer utility function
spapr: Add RTAS sysparm UUID
spapr: Fix RTAS sysparm DIAGNOSTICS_RUN_MODE
spapr: Add RTAS sysparm
roduce the following kernel
message: arch/powerpc/platforms/pseries/lparcfg.c \
parse_system_parameter_string Error calling get-system-parameter \
(0xfffd)
Signed-off-by: Sam Bobroff
---
hw/ppc/spapr_rtas.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/hw/ppc/spapr_rtas.
.
Signed-off-by: Sam Bobroff
---
include/hw/ppc/spapr.h | 17 +
1 file changed, 17 insertions(+)
diff --git a/include/hw/ppc/spapr.h b/include/hw/ppc/spapr.h
index 08c301f..39a7764 100644
--- a/include/hw/ppc/spapr.h
+++ b/include/hw/ppc/spapr.h
@@ -373,6 +373,23 @@ static inline
On 24/06/14 22:06, Alexander Graf wrote:
>
> On 24.06.14 02:22, Sam Bobroff wrote:
>> This series of patches improves QEMU's emulation of the RTAS call
>> "ibm,get-system-parameter" by adding support for the "UUID" and "SPLPAR
>> Characterist
.
Signed-off-by: Sam Bobroff
---
include/hw/ppc/spapr.h | 13 +
1 file changed, 13 insertions(+)
diff --git a/include/hw/ppc/spapr.h b/include/hw/ppc/spapr.h
index 08c301f..088baba 100644
--- a/include/hw/ppc/spapr.h
+++ b/include/hw/ppc/spapr.h
@@ -373,6 +373,19 @@ static inline void
Add support for the UUID parameter to the emulated RTAS call
ibm,get-system-parameter.
Return the guest's UUID as the value for the RTAS UUID system
parameter, or null (a zero length result) if it is not set.
Signed-off-by: Sam Bobroff
---
hw/ppc/spapr_rtas.c| 4
include/h
of
them moved out into spapr.h.
* Use g_strdup_printf()/g_free() rather than snprintf() to a stack array.
* Use cpu_physical_memory_write() instead of looping over each
byte.
Sam Bobroff (4):
spapr: Add rtas_st_buffer utility function
spapr: Fix RTAS sysparm DIAGNOSTICS_RUN_MODE
s
This is corrected by using the rtas_st_buffer() function to write to
the buffer.
The RTAS constants are also moved out into a header file, some new
constants added and the surrounding code slightly simplified.
Signed-off-by: Sam Bobroff
---
hw/ppc/spapr_rtas.c| 18 +-
include
roduce the following kernel
message: arch/powerpc/platforms/pseries/lparcfg.c \
parse_system_parameter_string Error calling get-system-parameter \
(0xfffd)
Signed-off-by: Sam Bobroff
---
hw/ppc/spapr_rtas.c| 8
include/hw/ppc/spapr.h | 1 +
2 files changed, 9 insertions(+)
diff
Lol weird it's not marked as duplicate anymore anyway, guess it was not
you then. Don't know what happened.
Can this bug be fixed in KVM or is it really to Windows specific? Else I
may have a look at it, never did any KVM development though, should be
fun.
@Serge: Did you get the license already
This is also affecting Windows Server 2008 and happens with all usb
storage devices I tested.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/685096
Title:
USB Passthrough not working for Windows 7 g
7;/usr/local/bin/fsdev/virtfs-proxy-helper': No such file make:
> *** [install] Error 1
I am affected by this issue as well. It seems simple enough so I'll try sending
a patch for it :-)
Sam.
Allow "make install" to handle tool binaries that reside in
sub-directories.
Without this patch "make install" will fail if it needs to strip
a tool binary (e.g. debugging is not enabled) that is installed
from a subdirectory. An example is fsdev/virtfs-proxy-helper.
Signed
Public bug reported:
Using the latest stable (2.4.0.1) and earlier releases (at least down to
2.2.1), I am unable to run a qemu-system-arm virtualization on a Mac OS
X Yosemite machine. QEMU was compiled with --enable-sdl.
Command line:
qemu-system-arm -device virtio-net,netdev=user.0 -drive
fil
Oh right, stupid mistake then! Never mind. Thanks for pointing this out.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1500175
Title:
unable to init msix vectors
Status in QEMU:
New
Bug descrip
As a sidenote: may I ask why the given command does not work? The IMG
should contain a kernel that should be bootable, so there should be no
need to specify an extra kernel.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs
Got it, thanks!
> Op 29-sep.-2015, om 03:51 heeft Peter Maydell het
> volgende geschreven:
>
> None of QEMU's ARM boards automatically boot a bios image shipped with
> QEMU. You must provide one explicitly, or else use the 'built in
> bootloader" with -kernel. (I'm not aware of any rom image th
quot;.
The cause is that the has_port field is not set in the address, so
later it is not copied by qapi_copy_SocketAddress(). This patch simply
adds the missing "has_port = true".
Signed-off-by: Sam Bobroff
---
qemu-char.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/qemu-char
On Thu, Oct 29, 2015 at 07:26:14AM +0100, Markus Armbruster wrote:
> Sam Bobroff writes:
>
> > Currently when constructing an inet socket monitor (e.g. via "-monitor
> > telent:localhost:12345,server,nowait") the port is ignored and a
> > random one is used inst
implemented, we display a warning message.
Signed-off-by: Sam Bobroff
---
This is somewhat of an RFC as the issue probably hasn't been noticed
very often (ever?) and there are several approaches to addressing it.
The discussion was a while ago, here:
http://lists.nongnu.org/archive/html/qe
ng being set on stderr?
(Unfortunately I don't have a replication for this using an unmodified QEMU but
I suspect I could find one if necessary.)
Cheers,
Sam.
On Fri, Dec 04, 2015 at 02:33:01PM +0800, Stefan Hajnoczi wrote:
> On Mon, Nov 30, 2015 at 04:34:47PM +1100, Sam Bobroff wrote:
> > Hi QEMU programmers,
> >
> > While doing some experimental work on QEMU that has involved adding a lot of
> > new log messages (u
NE,
> -.class_init= spapr_machine_2_1_class_init,
> -.instance_init = spapr_machine_2_1_instance_init,
> -};
> +DEFINE_SPAPR_MACHINE(2_1, "2.1");
>
> static void spapr_machine_register_types(void)
> {
> type_register_static(&spapr_machine_info);
> -type_register_static(&spapr_machine_2_1_info);
> -type_register_static(&spapr_machine_2_2_info);
> -type_register_static(&spapr_machine_2_3_info);
> -type_register_static(&spapr_machine_2_4_info);
> -type_register_static(&spapr_machine_2_5_info);
> }
>
> type_init(spapr_machine_register_types)
> --
> 2.5.0
Looks good to me. Just one nit: I couldn't help noticing that the suffix and
verstr parameters to the macro were both encoding the same information.
Did you consider a macro with the major and minor version as the parameters?
e.g.
#define DEFINE_SPAPR_MACHINE(major, minor)
So usage would be:
DEFINE_SPAPR_MACHINE(2, 1);
Reviewed-by: Sam Bobroff
On Thu, Dec 10, 2015 at 04:37:22PM +0800, Stefan Hajnoczi wrote:
> On Mon, Dec 07, 2015 at 02:22:18PM +1100, Sam Bobroff wrote:
> > On Fri, Dec 04, 2015 at 02:33:01PM +0800, Stefan Hajnoczi wrote:
> > > On Mon, Nov 30, 2015 at 04:34:47PM +1100, Sam Bobroff wrote:
> >
On Mon, Dec 14, 2015 at 03:29:49PM +0800, Stefan Hajnoczi wrote:
> On Mon, Dec 14, 2015 at 04:19:50PM +1100, Sam Bobroff wrote:
> > On Thu, Dec 10, 2015 at 04:37:22PM +0800, Stefan Hajnoczi wrote:
> > > On Mon, Dec 07, 2015 at 02:22:18PM +1100, Sam Bobroff wrote:
> > > &
This patch set contains several small fixes to make QEMU more PAPR
compliant.
Sam Bobroff (4):
spapr: Add /ibm,partition-name
spapr: Add /rtas/ibm,change-msix-capable
spapr: Make ibm,change-msi respect 3 return values
spapr: SPLPAR Characteristics
hw/ppc/spapr.c | 9
QEMU has a notion of the guest name, so if it's present we might as
well put that into the device tree as /ibm,partition-name.
This is specificed by PAPR.
Signed-off-by: Sam Bobroff
---
hw/ppc/spapr.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/hw/ppc/spapr.c b/hw/ppc/sp
Currently, rtas_ibm_change_msi() always returns four values even if
less are specified.
Correct this by only returning the fourth parameter if it was
requested.
This is specified by PAPR.
Signed-off-by: Sam Bobroff
---
hw/ppc/spapr_pci.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion
and values are specified by PAPR.
Signed-off-by: Sam Bobroff
---
hw/ppc/spapr_rtas.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/hw/ppc/spapr_rtas.c b/hw/ppc/spapr_rtas.c
index 0f1ae55..a08254b 100644
--- a/hw/ppc/spapr_rtas.c
+++ b/hw/ppc/spapr_rtas.c
@@ -33,6
QEMU is MSI-X capable and makes it available via ibm,change-msi, so
we should indicate this by adding /rtas/ibm,change-msix-capable to the
device tree.
This is specificed by PAPR.
Signed-off-by: Sam Bobroff
---
hw/ppc/spapr.c | 4
1 file changed, 4 insertions(+)
diff --git a/hw/ppc
*** This bug is a duplicate of bug 1033727 ***
https://bugs.launchpad.net/bugs/1033727
This maybe not a duplicate as we're using 1.3.1 and Windows 7 isn't
working there either. All other Operating systems are working though.
@Wessel: I believe the bug you pointed out as duplicate is saying th
Public bug reported:
I'm trying to use the option: -snapshot write to temporary files
instead of disk image files
How to reproduce? See following log:
2013-06-20 02:13:18.532+: starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU_AUDIO_DRV=none /u
reasonable restriction? Should we add a
property (where?) to allow the new machine version to run without the new
kernel feature? Could that property default to "on" or "on if supported by the
kernel" without it becoming too complicated or causing trouble during
migration?
Thanks,
Sam.
t
snapshot with the name "bar" on hd2 which is the one with ID 2. That is not
the snapshot that matches the vm state (which is the one with ID 3) and
presumably can lead to filesystem corruption on hd2.
Do these seem like bugs? Should I try to find a way to fix some or all of them?
(Note: I checked the launchpad bug list but didn't see these listed.)
Cheers,
Sam.
On Mon, Oct 19, 2015 at 02:50:17PM +0200, Kevin Wolf wrote:
> [ CC: qemu-block ]
>
> Am 19.10.2015 um 07:27 hat Sam Bobroff geschrieben:
> > Hi all,
> >
> > While working through the QEMU code that saves and loads snapshots, I've
> > noticed some confusing b
ot; blob to install, and it wouldn't really
actually be BIOS but it seems like it would work easily. Since we need a
second, different, trampoline for System Reset, I would then need to add yet
another blob for that... Still, this doesn't seem so bad. I suppose we could
add some structure to the blob (e.g. a table of contents at the start) and fit
both trampolines in, but that's inventing yet another file format... ugh.
(b) As above but assemble the trampoline code into an ELF dynamic library
rather than stripping it down to a raw binary: we could use known symbols to
find the trampolines, even the patch locations, so at least we wouldn't be
inventing our own format (using dlopen()/dlsym()... I wonder if this would be
OK for all platforms...).
(c) Assemble it (as above) but include it directly in the QEMU binary by
objcopying it in or hexdumping into a C string or something similar. This seems
fairly neat but I'm not sure how people would feel about including "binaries"
into QEMU this way. Although it would take some work in the build system, it
seems like a fairly neat solution to me.
Cheers,
Sam.
On Sun, Aug 09, 2015 at 03:53:02PM +0200, Alexander Graf wrote:
>
>
> On 07.08.15 05:37, Sam Bobroff wrote:
> > Hello Aravinda and all,
> >
> > On Wed, Jul 08, 2015 at 01:58:13PM +0530, Aravinda Prasad wrote:
> >> On Friday 03 July 2015 11:31 AM, David Gibs
e
if it was used or not.
What if we set up another backend that just enables the hcall in KVM?
This would answer the question about what to do if both are available as well:
just do only what the user has asked for. (But I'm not sure what the default
behaviour should be if the user doesn't specify anything.)
(Oh also: I have tested the in-kernel hcall using a QEMU modified to enable it
and it seems to work :-)
Cheers,
Sam.
On Tue, Sep 08, 2015 at 07:38:12AM +0200, Thomas Huth wrote:
> On 08/09/15 07:03, Sam Bobroff wrote:
> > On Tue, Sep 01, 2015 at 12:53:26PM +0200, Thomas Huth wrote:
> >> On 01/09/15 02:38, David Gibson wrote:
> >>> On Mon, Aug 31, 2015 at 08:46:01PM +0200, Thomas Hu
On Tue, Sep 01, 2015 at 04:37:51PM +0530, Aravinda Prasad wrote:
>
>
> On Monday 10 August 2015 09:35 AM, Sam Bobroff wrote:
> > On Sun, Aug 09, 2015 at 03:53:02PM +0200, Alexander Graf wrote:
> >>
> >>
> >> On 07.08.15 05:37, Sam Bobroff wrote:
> &
On Thu, Sep 03, 2015 at 09:53:20AM +1000, David Gibson wrote:
> On Wed, Sep 02, 2015 at 04:34:01PM +1000, Sam Bobroff wrote:
> > On Tue, Sep 01, 2015 at 04:37:51PM +0530, Aravinda Prasad wrote:
> > >
> > >
> > > On Monday 10 August 2015 09:35 AM, Sam Bobroff
here are existing guests
> that assume a kexec() will magically wipe the fwnmi vectors away.
Yes, but I think we could handle this separately if necessary: even if we don't
need to write anything to the vector, we could still insert a magic value and
check for it later. If it's been clobbered by a kexec, go back to the old
method.
Sam.
On Tue, Jul 07, 2015 at 05:26:49PM +1000, David Gibson wrote:
> On Fri, Jul 03, 2015 at 01:42:16PM +1000, Sam Bobroff wrote:
> >
> > This patch set contains several small fixes to make QEMU more PAPR
> > compliant.
>
> Applied to spapr-next, thanks.
>
> In fut
On 25/06/14 21:12, Alexander Graf wrote:
>
> On 25.06.14 05:54, Sam Bobroff wrote:
>> This series of patches improves QEMU's emulation of the RTAS call
>> "ibm,get-system-parameter" by adding support for the "UUID" and "SPLPAR
>> Characterist
I am having this same problem. Looking at the configure script it looks like it
prefers to use:
pkg-config sdl —static
to get the static linker flags, rather than:
sdl-config —static-libs
The former returns an empty string; the latter returns the correct library
list. If it had used the
it is an SDL package distribution problem; in this case it is
coming
from delian-jessie.
Thank you,
Sam McKelvie
> On May 11, 2016, at 11:30 AM, Peter Maydell wrote:
>
> On 11 May 2016 at 19:12, Sam McKelvie wrote:
>> I am having this same problem. Looking at the configure scr
FWIW:
While trying to restore (apply) a snapshot on a Windows VM (ie: qemu-img
snapshot -a snapshotname windows.qcow2 where the image file is 150gb in
size,) I got the above error:
qemu-img: /build/buildd/qemu-2.0.0+dfsg/block/qcow2-refcount.c:467:
update_refcount_discard: Assertion `d->bytes + l
_intr(env)) {
//return -1;
}
intno = pic_read_irq(isa_pic);
return intno;
}
Then the issue manifests as a spurious interrupt and the software
ignores it, avoiding the GPF. Does anyone have any ideas as to what is
going wrong here? Should I look more closely at the Qemu emulation code
or my software? Any help is appreciated.
Thanks!
--Sam
LINT1, but this fixed the incorrect GPF I was getting.
--Sam
On 9/28/10 10:15 AM, Sam King wrote:
Hello,
I am seeing a weird crash in my system and I am trying to figure out
if it is a software bug or a qemu emulation bug. From the software
perspective I am getting a GP fault at a time where
/
next_tb = 0;
+ }
+
#if !defined(CONFIG_USER_ONLY)
} else if ((interrupt_request &
CPU_INTERRUPT_VIRQ) &&
(env->eflags & IF_MASK) &&
On 9/29/
1 - 100 of 900 matches
Mail list logo
