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_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 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'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
=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 :
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
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
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
Hi all,
I'm going to use qga follow this:
https://wiki.qemu.org/index.php/Features/GuestAgent
But I'm confused with [example usage] section, I don't know where to
install qemu-ga, so I just install on host. But then I found qemu-ga should
be installed on guest, that's why my qga socket always fa
Has anybody successfully installed Windows 10 on qemu 2.9
I upgraded to Fedora 26 (x86_64) going from qemu 2.7 to qemu 2.9, with a
Windows 10 guest. Booting this guest eventually resulted in a vga resolution-
sized screen with gray vertical bars. With no further progress, after a few
minutes
Nerijus Baliunas writes:
On Tue, 11 Jul 2017 14:19:35 -0400 Sam Varshavchik
wrote:
> Has anybody successfully installed Windows 10 on qemu 2.9
>
> I upgraded to Fedora 26 (x86_64) going from qemu 2.7 to qemu 2.9, with a
> Windows 10 guest. Booting this guest eventually resul
I first mentioned this a few weeks ago. An upgrade from Fedora 25 to 26
updated qemu 2.7 to qemu 2.9. I had two Windows 10 hosts that went this
upgrade path.
After the upgrade, the Windows 10 guests started experiencing sporadic
issues when they initiate a reboot from within the guest VM. M
Pierre Couderc writes:
onn a linux system, I know how to mount a directory such as :
-virtfs
local,path=path/to,security_model=passthrough,id=host0,mount_tag=host0
But how should do for it to be ssen as D: from a W guest ?
Sorry, cetainly basic, but I hwave not found on google...
Windo
appreciated.
Regards,
Sam
This one has stumped me for a while, before I figured out the problem. I
have two guests, on two different hosts. Both of them are qemu 4.1.1, and I
use libvirt/virt-manager.
For some reason, one of them stubbornly refused to boot off a USB thumb
drive. In both cases I had no problem adding
I'm trying to add swtpm to an existing Windows 10 guest (21H1).
I tried both TIS and CRB device type, i.e.:
Neither one seems to be recognized by Windows 10. The "Security Processor
Troubleshooting" shows "Your device does not support this feature.
I've read other reports that
26 matches
Mail list logo
