Displaying 2 results from an estimated 2 matches for "d56df577".
2015 Jun 30
0
Windows 10 tech preview build 10130
...s:
$ ps ax | grep -i [w]10
16031 ? Sl 29:48 /usr/libexec/qemu-kvm -name KVM-W10 -S -M
rhel6.3.0 -cpu
Nehalem,+rdtscp,+pdcm,+xtpr,+tm2,+est,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme
-enable-kvm -m 4096 -realtime mlock=off -smp
4,sockets=2,cores=2,threads=2 -uuid d56df577-367f-1b6b-c6e8-eaa42a14ffc3
-nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/KVM-W10.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc
base=localtime,driftfix=slew -no-shutdown -device
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -dev...
2015 Jun 29
2
Windows 10 tech preview build 10130
On Mon, 2015-06-29 at 13:47 -0700, Greg Bailey wrote:
> I've installed it on a KVM guest on a CentOS 7 host.
I was hoping it wasn't going to come to that. That is, I hope it's not a
CentOS 6 issue.
> I've always had more success using the drivers obtained from running the
> spice guest tools vs. the virtio-win stuff. I use:
>
>