Bug 1058657 - guest fail to reboot automatically with 'reboot-timeout' value specified
Summary: guest fail to reboot automatically with 'reboot-timeout' value specified
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: seabios
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Gerd Hoffmann
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-28 09:47 UTC by Sibiao Luo
Modified: 2019-03-26 14:29 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-29 07:24:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sibiao Luo 2014-01-28 09:47:24 UTC
Description of problem:
boot guest with 'reboot-timeout=$value' specified, but guest fail to automatically reboot after $value seconds. 

Version-Release number of selected component (if applicable):
host info:
3.10.0-79.el7.x86_64
qemu-kvm-1.5.3-41.el7.x86_64
seabios-bin-1.7.2.2-10.el7.x86_64
seabios-1.7.2.2-10.el7.x86_64
guest info:
3.10.0-79.el7.x86_64

How reproducible:
3/3

Steps to Reproduce:
1.boot guest with 'reboot-timeout=$value' specified, e.g.: reboot-timeout=60000.
e.g:# /usr/libexec/qemu-kvm -M pc... -boot menu=on,reboot-timeout=60000
2.
3.

Actual results:
after step 1, guest fail to automatically reboot after 60 seconds, it was running all the time. 

Expected results:
guest can be automatically reboot in $value seconds successfully.

Additional info:
# /usr/libexec/qemu-kvm -M pc -cpu SandyBridge -enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -no-kvm-pit-reinjection -usb -device usb-tablet,id=input0 -name sluo -uuid 990ea161-6b67-47b2-b803-19fb01d30d30 -rtc base=localtime,clock=host,driftfix=slew -device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=0,bus=pci.0,addr=0x3 -chardev socket,id=channel1,path=/tmp/helloworld1,server,nowait -device virtserialport,chardev=channel1,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port1 -chardev socket,id=channel2,path=/tmp/helloworld2,server,nowait -device virtserialport,chardev=channel2,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port2 -drive file=/home/RHEL-7.0-20140116.1_Server_x86_64.qcow2bk,if=none,id=drive-system-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop -device virtio-scsi-pci,id=scsi1,bus=pci.0,addr=0x4 -device scsi-hd,drive=drive-system-disk,id=system-disk,bootindex=1 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=00:01:02:B6:40:21,bus=pci.0,addr=0x5,bootindex=2 -device virtio-balloon-pci,id=ballooning,bus=pci.0,addr=0x6 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -k en-us -boot menu=on,reboot-timeout=60000 -qmp tcp:0:4444,server,nowait -serial unix:/tmp/ttyS0,server,nowait -monitor stdio -spice disable-ticketing,port=5931 -vga qxl

Comment 1 Gerd Hoffmann 2014-01-28 12:25:21 UTC
Details please, doesn't reproduce.

Note that the option only has an effect in case seabios doesn't find a device it can boot from.  If the boot failure happens later (in the boot loader or linux kernel) seabios can't do anything about it.

Comment 2 Sibiao Luo 2014-01-29 07:24:47 UTC
(In reply to Gerd Hoffmann from comment #1)
> Details please, doesn't reproduce.
> 
> Note that the option only has an effect in case seabios doesn't find a
> device it can boot from.  If the boot failure happens later (in the boot
> loader or linux kernel) seabios can't do anything about it.

Yes, thanks for your kindly reminds. It works for me now, i not note this option should only take effect when seabios fail to boot, it will retry after $value seconds. I will let QE feature owner take a note to the case for it.

Best Regards,
sluo


Note You need to log in before you can comment on or make changes to this bug.