Re: [Qemu-devel] [questions] about KVM as aMicrosoft-compatiblehypervisor

[Vadim Rozenfeld]

Hi Zhang,

No I haven't seen such problem
Which kernel version are you running?
Does it include the latest lazy eli changes?

Btw, hv_spinlocks=0xfffffff is a pretty huge value.

Best regards,
Vadim.



----- Original Message -----
From: "Zhang Haoyu" <address@hidden>
To: "Vadim Rozenfeld" <address@hidden>
Cc: "Jidong Xiao" <address@hidden>, "qemu-devel" <address@hidden>, "kvm" 
<address@hidden>
Sent: Monday, August 4, 2014 12:17:41 PM
Subject: Re: Re: [Qemu-devel] [questions] about KVM as 
aMicrosoft-compatiblehypervisor

Hi, Vadim

I start a vm(windows server 2008 64bit) with below qemu command, get stuck with 
black screen during boot stage, 
no error report by qemu and kvm hypervisor, but if I remove the item 
"hv_vapic", then start and run the VM successfully.

/var/run/qemu-server/5195516385344.pid -daemonize -name win2008_iotest -smp 
sockets=1,cores=1 -cpu core2duo,hv_spinlocks=0xfffffff,hv_relaxed,hv_vapic 
-nodefaults -vga cirrus -no-hpet -k en-us -boot menu=on,splash-time=8000 -m 
2048 -usb -drive if=none,id=drive-ide0,media=cdrom,aio=native,forecast=disable 
-device ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=200 -drive 
file=/sf/data/3600605b006c126da1b0cde571ba48d0d_00e0ed2d202e/images/host-00e0ed2d202e/win2008_iotest.vm/vm-disk-1.qcow2,if=none,id=drive-virtio1,cache=writethrough,aio=native,forecast=disable
 -device virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb 
-drive 
file=/sf/data/local/images/host-00e0ed2d202e/win2008_iotest.vm/vm-disk-1.qcow2,if=none,id=drive-virtio2,cache=writethrough,aio=native,forecast=disable
 -device 
virtio-blk-pci,drive=drive-virtio2,id=virtio2,bus=pci.0,addr=0xc,bootindex=101 
-netdev 
type=tap,id=net0,ifname=519551638534400,script=/sf/etc/kvm/vtp-bridge,vhost=on,vhostforc
 e=on -device 
virtio-net-pci,mac=FE:FC:FE:58:E0:81,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300
 -rtc driftfix=slew,clock=rt,base=localtime -global 
kvm-pit.lost_tick_policy=discard -global PIIX4_PM.disable_s3=1 -global 
PIIX4_PM.disable_s4=1 -post win2008_iotest -enable-kvm -L /boot/pc-bios

Seen similar problem before?
Any ideas?

Thanks,
Zhang Haoyu

>> >> Hi, Vadim
>> >> I read the kvm-2012-forum paper < KVM as a Microsoft-compatible 
>> >> hypervisor>, 
>> >> Any update and other references, please?
>> >> 
>> >> Thanks,
>> >> Zhang Haoyu
>> >> 
>> >> 
>> >
>> >Unfortunately, not too much.
>> >From the the most recent, we have lazy eoi implemented by 
>> >MST and reference time counter.
>> >
>> How to get the source of windows pv-eoi?
>I'll be referencing to git://git.kernel.org/pub/scm/virt/kvm/kvm.git
>
>for lazy eoi please take a look at commit:
>b63cf42fd1d8c18fab71222321aaf356f63089c9
>
>> And what is "reference time counter", could you provide some references or 
>> code, please?
>Take a look at commit:
>e984097b553ed2d6551c805223e4057421370f00
>
>I also suggest reading Hypervisor Functional Specification 3.0a provided
>by Microsoft and available for downloading
>from  http://www.microsoft.com/en-au/download/details.aspx?id=39289
>
>Best regards,
>Vadim.

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to address@hidden
More majordomo info at  http://vger.kernel.org/majordomo-info.html