TPM emulation for Win 10

2021-09-11 Thread Sam Varshavchik
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

Controller type "USB 3" doesn't boot.

2020-02-03 Thread Sam Varshavchik
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

[Qemu-discuss] QEMU fault injection

2018-06-04 Thread sam atac
appreciated. Regards, Sam

[Qemu-discuss] How to use qga correctly? some key point !

2017-09-05 Thread Sam
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

Re: [Qemu-discuss] How do I mount a virtfs directory so that it be D: on guest ?

2017-09-01 Thread Sam Varshavchik
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...

Re: [Qemu-discuss] [Qemu-devel] [QGA] Bug of qga?

2017-08-30 Thread Sam
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 <sam...@daynix.com>: > Hi Sam, > > Thanks for reporting this, in order to debug this efficiently I need y

Re: [Qemu-discuss] [Qemu-devel] [QGA] Bug of qga?

2017-08-30 Thread Sam
Qemu-2.6.0 2017-08-30 14:20 GMT+08:00 Sam <batmanu...@gmail.com>: > 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

Re: [Qemu-discuss] [QGA] Bug of qga?

2017-08-29 Thread Sam
So how to fix this bug? And where should I to report bug? 2017-08-29 13:52 GMT+08:00 Sam <batmanu...@gmail.com>: > 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 <batmanu...@gmail.com>: > >&g

Re: [Qemu-discuss] Why I got "timeout" while using qga socket to connect VM?

2017-08-22 Thread Sam
=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 <batmanu...@gmail.com&

[Qemu-discuss] How to get qemu log?

2017-08-14 Thread Sam
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 *

[Qemu-discuss] How to detect qga socket available?

2017-08-10 Thread Sam
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~

Re: [Qemu-discuss] [Qemu-devel] For unix domain socket, will only one client could connect to this socket?

2017-07-27 Thread Sam
Thank you, I think another process connect this socket, so I hanged here. 2017-07-27 18:47 GMT+08:00 Daniel P. Berrange <berra...@redhat.com>: > 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

[Qemu-discuss] For unix domain socket, will only one client could connect to this socket?

2017-07-27 Thread Sam
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 >

[Qemu-discuss] qemu 2.9 Windows 10 VM restart issues follow-up

2017-07-26 Thread Sam Varshavchik
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.

[Qemu-discuss] [qemu-trace] how to add trace easily?

2017-07-19 Thread Sam
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(_mem_rom, NULL, _mem_ops, NULL, > NULL, UINT64_MAX); >

[Qemu-discuss] How to stop `qemu-system-x86_64 ...` instead of `kill -9`?

2017-07-12 Thread Sam
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

Re: [Qemu-discuss] Windows 10 guest on qemu 2.9

2017-07-11 Thread Sam Varshavchik
Nerijus Baliunas writes: On Tue, 11 Jul 2017 14:19:35 -0400 Sam Varshavchik <mr...@courier-mta.com> 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.

[Qemu-discuss] Windows 10 guest on qemu 2.9

2017-07-11 Thread Sam Varshavchik
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

Re: [Qemu-discuss] [dpdk-dev] Will huge page have negative effect on guest vm in qemu enviroment?

2017-06-21 Thread Sam
, as there is no log to report this. 2017-06-21 14:15 GMT+08:00 Pavel Shirshov <pavel.shirs...@gmail.com>: > 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 > perfomance on the

[Qemu-discuss] Will huge page have negative effect on guest vm in qemu enviroment?

2017-06-20 Thread Sam
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

Re: [Qemu-discuss] [Qemu-devel] Fwd: [DPDK-memory] how qemu waste such long time under dpdk huge page envriment?

2017-06-19 Thread Sam
tion 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 <berra...@redhat.com>: > On Mon, Jun 19, 2017 at 05:30:59PM +0800, Sam wrote: > > Hi all, > > > > I'm r

[Qemu-discuss] Fwd: [DPDK-memory] how qemu waste such long time under dpdk huge page envriment?

2017-06-19 Thread Sam
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-discuss] how qemu waste such long time?

2017-06-14 Thread Sam
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