[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [Bug 1723927] [NEW] Linux or windows guest boot failed
|
From: |
Laszlo Ersek \(Red Hat\) |
|
Subject: |
Re: [Qemu-devel] [Bug 1723927] [NEW] Linux or windows guest boot failed by uefi on CPU of Intel Xeon X5675 |
|
Date: |
Mon, 16 Oct 2017 12:06:20 -0000 |
On 10/16/17 13:26, chan wrote:
> Public bug reported:
>
> Hi,
>
> I started windows server 2012 DC or redhat7.0, but boot failed by UEFI, and
> start process stop on
> "TianoCore" image by looking at VNCviewer.
>
> VM using the command:(redhat7.0)
> /usr/bin/kvm -name guest=ytest,debug-threads=on -S -object
> secret,id=masterKey0,format=raw,file=/run/lib/libvirt/qemu/domain-40-ytest/master-key.aes
> -machine pc-i440fx-2.7,accel=kvm,usb=off,system=windows,dump-guest-core=off
> -bios /usr/share/qemu-kvm/OVMF_CODE.fd -m
> size=8388608k,slots=10,maxmem=34359738368k -realtime mlock=off -smp
> 1,maxcpus=24,sockets=24,cores=1,threads=1 -numa
> node,nodeid=0,cpus=0-23,mem=8192 -uuid 8cf40bd6-258a-4550-ba4e-b38230547a11
> -no-user-config -nodefaults -chardev
> socket,id=charmonitor,path=/run/lib/libvirt/qemu/domain-40-ytest/monitor.sock,server,nowait
> -mon chardev=charmonitor,id=monitor,mode=control -chardev
> socket,id=charmonitor_cas,path=/run/lib/libvirt/qemu/domain-40-ytest/monitor.sock.cas,server,nowait
> -mon chardev=charmonitor_cas,id=monitor_cas,mode=control -rtc base=utc
> -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1
> -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
> usb-ehci,id=usb1,bus=pci.0,addr=0x3 -device
> nec-usb-xhci,id=usb2,bus=pci.0,addr=0x4 -device
> virtio-scsi-pci,id=scsi1,bus=pci.0,addr=0x6 -device
> virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -device
> usb-hub,id=hub0,bus=usb.0,port=1 -drive
> file=/vms/hw235/ytest,format=qcow2,if=none,id=drive-virtio-disk0,cache=directsync,aio=native
> -device
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,pci_hotpluggable=on,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
> -drive if=none,id=drive-fdc0-0-0,readonly=on -global
> isa-fdc.driveA=drive-fdc0-0-0 -global isa-fdc.bootindexA=2 -netdev
> tap,fd=48,id=hostnet0,vhost=on,vhostfd=50 -device
> virtio-net-pci,pci_hotpluggable=on,netdev=hostnet0,id=net0,mac=0c:da:41:1d:67:6f,bus=pci.0,addr=0x5,bootindex=4
> -chardev pty,id=charserial0 -device
> isa-serial,chardev=charserial0,id=serial0 -chardev
> socket,id=charchannel0,path=/var/lib/libvirt/qemu/ytest.agent,server,nowait
> -device
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0
> -vnc 0.0.0.0:9 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9 -msg timestamp=on
>
> qemu version: 2.7.1
> edk2 version: git://git.code.sf.net/p/tianocore/edk2.git, commit:
> cc0b456a05f8dd1ebfb9be485465be37e96999e7
> server: ProLiant BL460c G7, CPU: Intel(R) Xeon(R) CPU X5675 @ 3.07GHz
>
> Another, last version of edk2(compiled by myself) start guest is failed,
> too. But r15214 of edk2 start guest is ok(Download from
> http://sourceforge.net/projects/edk2/files/OVMF/, OVMF-X64-r15214.zip)
>
> Thanks in Advance
>
> ** Affects: qemu
> Importance: Undecided
> Status: New
>
Your command line is broken;
-bios /usr/share/qemu-kvm/OVMF_CODE.fd
has never been a correct option to boot OVMF.
Your cmdline seems to have been generated by libvirt; make sure your
domain XML says
<domain type='kvm'>
<os>
<type arch='x86_64' machine='pc'>hvm</type>
<loader readonly='yes'
type='pflash'>/usr/share/qemu-kvm/OVMF_CODE.fd</loader>
</os>
</domain>
If your libvirt daemon is set up correctly, then libvirt will generate
the <nvram> element automatically for the above. (See the "nvram" stanza
in "/etc/libvirt/qemu.conf". If you modify that, don't forget to restart
libvirt.)
Also, you can capture the OVMF debug log with
<domain type='kvm'
xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ <------- don't forget
to add this too
<qemu:commandline>
<qemu:arg value='-global'/>
<qemu:arg value='isa-debugcon.iobase=0x402'/>
<qemu:arg value='-debugcon'/>
<qemu:arg value='file:/tmp/GUEST_NAME.log'/>
</qemu:commandline>
</domain>
Thanks,
Laszlo
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1723927
Title:
Linux or windows guest boot failed by uefi on CPU of Intel Xeon
X5675
Status in QEMU:
New
Bug description:
Hi,
I started windows server 2012 DC or redhat7.0, but boot failed by UEFI, and
start process stop on
"TianoCore" image by looking at VNCviewer.
VM using the command:(redhat7.0)
/usr/bin/kvm -name guest=ytest,debug-threads=on -S -object
secret,id=masterKey0,format=raw,file=/run/lib/libvirt/qemu/domain-40-ytest/master-key.aes
-machine pc-i440fx-2.7,accel=kvm,usb=off,system=windows,dump-guest-core=off
-bios /usr/share/qemu-kvm/OVMF_CODE.fd -m
size=8388608k,slots=10,maxmem=34359738368k -realtime mlock=off -smp
1,maxcpus=24,sockets=24,cores=1,threads=1 -numa
node,nodeid=0,cpus=0-23,mem=8192 -uuid 8cf40bd6-258a-4550-ba4e-b38230547a11
-no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/run/lib/libvirt/qemu/domain-40-ytest/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -chardev
socket,id=charmonitor_cas,path=/run/lib/libvirt/qemu/domain-40-ytest/monitor.sock.cas,server,nowait
-mon chardev=charmonitor_cas,id=monitor_cas,mode=control -rtc base=utc
-no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot
strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
usb-ehci,id=usb1,bus=pci.0,addr=0x3 -device
nec-usb-xhci,id=usb2,bus=pci.0,addr=0x4 -device
virtio-scsi-pci,id=scsi1,bus=pci.0,addr=0x6 -device
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -device
usb-hub,id=hub0,bus=usb.0,port=1 -drive
file=/vms/hw235/ytest,format=qcow2,if=none,id=drive-virtio-disk0,cache=directsync,aio=native
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,pci_hotpluggable=on,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-drive if=none,id=drive-fdc0-0-0,readonly=on -global
isa-fdc.driveA=drive-fdc0-0-0 -global isa-fdc.bootindexA=2 -netdev
tap,fd=48,id=hostnet0,vhost=on,vhostfd=50 -device
virtio-net-pci,pci_hotpluggable=on,netdev=hostnet0,id=net0,mac=0c:da:41:1d:67:6f,bus=pci.0,addr=0x5,bootindex=4
-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0
-chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/ytest.agent,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0
-vnc 0.0.0.0:9 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9 -msg timestamp=on
qemu version: 2.7.1
edk2 version: git://git.code.sf.net/p/tianocore/edk2.git, commit:
cc0b456a05f8dd1ebfb9be485465be37e96999e7
server: ProLiant BL460c G7, CPU: Intel(R) Xeon(R) CPU X5675 @ 3.07GHz
Another, last version of edk2(compiled by myself) start guest is
failed, too. But r15214 of edk2 start guest is ok(Download from
http://sourceforge.net/projects/edk2/files/OVMF/, OVMF-X64-r15214.zip)
Thanks in Advance
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1723927/+subscriptions