Bug 663275
| Summary: | After add the second IDE disk,guest boot failed with error "not a bootable disk, No bootable device " | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | wangyimiao <yimwang> |
| Component: | qemu-kvm | Assignee: | Gleb Natapov <gleb> |
| Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.1 | CC: | alex.williamson, berrange, dyuan, eblake, gleb, gren, jyang, khong, knoel, llim, mkenneth, nzhang, virt-maint, xen-maint, yoyzhang |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-12-22 08:51:15 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 580954 | ||
Test pkgs: kernel-2..6.32-91.el6 result qemu-kvm libvirt PASS qemu-kvm-2:0.12.1.2-2.113.el6 libvirt-0.8.1-27.el6 PASS qemu-kvm-2:0.12.1.2-2.113.el6 libvirt-0.8.1-29.el6 FAIL qemu-kvm-2:0.12.1.2-2.125.el6 libvirt-0.8.1-29.el6 Please provide the /var/log/libvirt/qemu/$GUESTNAME.log file showing the command line arguments libvirt generated for the XML you used. 1. The PASS log: LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.0.0 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name rhel6 -uuid 77442b32-01e4-6d86-f5a9-fd28869ca174 -nodefconfig -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/rhel6.monitor,server,nowait -mon chardev=monitor,mode=control -rtc base=utc -boot c -drive file=/var/lib/libvirt/images/RHEL-Server-6-32-virtio.qcow2,if=none,id=drive-virtio-disk0,boot=on,format=qcow2,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -drive file=/var/lib/libvirt/images/cdrom-1.img,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=21,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:70:55:24,bus=pci.0,addr=0x3 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -vnc 127.0.0.1:0 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 2. The FAIL log: LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.0.0 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name rhel6 -uuid 77442b32-01e4-6d86-f5a9-fd28869ca174 -nodefconfig -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/rhel6.monitor,server,nowait -mon chardev=monitor,mode=control -rtc base=utc -boot c -drive file=/var/lib/libvirt/images/RHEL-Server-6-32-virtio.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -drive file=/var/lib/libvirt/images/cdrom-1.img,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=21,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:70:55:24,bus=pci.0,addr=0x3 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -vnc 127.0.0.1:0 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 sounds like a boot order problem. seabios is going to provide a better solution to set boot order very soon. Gleb has sent patches to upstream already. FYI: https://bugzilla.redhat.com/show_bug.cgi?id=643681#c7 (In reply to comment #6) > sounds like a boot order problem. seabios is going to provide a better solution > to set boot order very soon. Gleb has sent patches to upstream already. > FYI: > https://bugzilla.redhat.com/show_bug.cgi?id=643681#c7 Correct. We hope to have a good solution in rhel6.1. For rhel6.0 though from comment #5 it is not clear why libvirt decided to drop boot=on from virtio disk when ide disk was added. [root@dhcp-93-* ~]# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.126.el6.x86_64
[root@dhcp-93-* ~]# /usr/libexec/qemu-kvm -help | grep 'boot'
-boot [order=drives][,once=drives][,menu=on|off]
-no-fd-bootchk disable boot signature checking for floppy disks
[,hostname=host][,dhcpstart=addr][,dns=addr][,tftp=dir][,bootfile=f]
Linux/Multiboot boot specific:
-no-reboot exit instead of rebooting
[root@dhcp-93-* ~]# /usr/libexec/qemu-kvm -help | grep 'boot=on'
[root@dhcp-93-* ~]#
As a compraison (on my Fedora 14):
[root@Osier libvirt]# qemu-kvm -help | grep boot
[,readonly=on|off][,boot=on|off]
-boot [order=drives][,once=drives][,menu=on|off]
-no-fd-bootchk disable boot signature checking for floppy disks
[,hostname=host][,dhcpstart=addr][,dns=addr][,tftp=dir][,bootfile=f]
Linux/Multiboot boot specific:
-no-reboot exit instead of rebooting
[root@Osier libvirt]# qemu-kvm -help | grep 'boot=on'
[,readonly=on|off][,boot=on|off]
[root@Osier libvirt]#
libvirt determine if "-drive" of qemu-kvm supports "boot=on" by:
if (strstr(help, "boot=on"))
flags |= QEMUD_CMD_FLAG_DRIVE_BOOT;
Guess qemu-kvm-2:0.12.1.2-2.125.el6 behaves similar with qemu-kvm-2:0.12.1.2-2.126.el6, so IMHO that's why for qemu-kvm-2:0.12.1.2-2.125.el6, libvirt drops "boot=on" for that virtio disk.
(In reply to comment #8) > > Guess qemu-kvm-2:0.12.1.2-2.125.el6 behaves similar with > qemu-kvm-2:0.12.1.2-2.126.el6, so IMHO that's why for > qemu-kvm-2:0.12.1.2-2.125.el6, libvirt drops "boot=on" for that virtio disk. In comment #5 first command line has boot=on second doesn't. Are both command lines with the same qemu-kvm or qemu-kvm was upgraded and disk added at the same time? If the former then it looks like libvirt problem. If later then this is expected and should be taken care off in rhel6.1. (In reply to comment #9) > (In reply to comment #8) > > > > Guess qemu-kvm-2:0.12.1.2-2.125.el6 behaves similar with > > qemu-kvm-2:0.12.1.2-2.126.el6, so IMHO that's why for > > qemu-kvm-2:0.12.1.2-2.125.el6, libvirt drops "boot=on" for that virtio disk. > > In comment #5 first command line has boot=on second doesn't. Are both command > lines with the same qemu-kvm or qemu-kvm was upgraded and disk added at the > same time? If the former then it looks like libvirt problem. If later then this > is expected and should be taken care off in rhel6.1. the first command is with qemu-kvm-2:0.12.1.2-2.113.el6, the second is with qemu-kvm-2:0.12.1.2-2.125.el6, so it means qemu-kvm was upgraded, though not sure if the disk was added at the same time, dyuan, could you clarify it? (In reply to comment #10) > (In reply to comment #9) > > (In reply to comment #8) > > > > > > Guess qemu-kvm-2:0.12.1.2-2.125.el6 behaves similar with > > > qemu-kvm-2:0.12.1.2-2.126.el6, so IMHO that's why for > > > qemu-kvm-2:0.12.1.2-2.125.el6, libvirt drops "boot=on" for that virtio disk. > > > > In comment #5 first command line has boot=on second doesn't. Are both command > > lines with the same qemu-kvm or qemu-kvm was upgraded and disk added at the > > same time? If the former then it looks like libvirt problem. If later then this > > is expected and should be taken care off in rhel6.1. > > the first command is with qemu-kvm-2:0.12.1.2-2.113.el6, the second is with > qemu-kvm-2:0.12.1.2-2.125.el6, so it means qemu-kvm was upgraded, though not > sure if the disk was added at the same time, > > dyuan, could you clarify it? the disk was added at the same time, and got the different command line after qemu-kvm was upgraded from 113 to 125. *** This bug has been marked as a duplicate of bug 646895 *** |
Description of problem: After add the second IDE disk,guest boot failed with error "not a bootable disk No bootable device ". Version-Release number of selected component (if applicable): libvirt-0.8.1-29.el6.x86_64 qemu-kvm-0.12.1.2-2.125.el6.x86_64 qemu-img-0.12.1.2-2.125.el6.x86_64 kernel-2.6.32-90.el6.x86_64 How reproducible: 5/5 Steps to Reproduce: 1.#cat http.xml <domain type='kvm'> <name>http_test</name> <uuid>69dfb32a-3030-c802-e8d2-cddc9d96d7bb</uuid> <memory>524288</memory> <currentMemory>524288</currentMemory> <vcpu>1</vcpu> <os> <type arch='x86_64' machine='rhel6.0.0'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/var/lib/libvirt/images/http_test.img'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='network'> <mac address='52:54:00:3c:ba:f0'/> <source network='default'/> <target dev='vnet0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target port='0'/> </console> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/> <video> <model type='cirrus' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </memballoon> </devices> </domain> 2.Defined and started the domain # virsh define http.xml Domain http_test defined from http.xml # virsh start http_test Domain http_test started After that steps domain works fine. 3.Use qemu-img or virt-manager to create an image file named "c.img" qemu-img create /var/lib/libvirt/images/c.img 100M 4.Add the following XML into domain config xml: <disk type='file' device='disk'> <source file='/var/lib/libvirt/images/c.img'/> <target dev='hdb' bus='ide'/> <shareable/> </disk> # virsh destroy http_test Domain http_test destroyed # virsh edit http_test Domain http_test XML configuration edited. 5.Start the guest. # virsh start http_test # virt-viewer http_test Actual results: After add the second IDE disk,guest boot failed with error "not a bootable disk No bootable device " Expected results: Domain start successfully.