- 26 Mar, 2015 1 commit
-
-
Gonglei authored
Add a space after comma. Signed-off-by:
Gonglei <arei.gonglei@huawei.com> Message-Id: <1427374663-10168-1-git-send-email-arei.gonglei@huawei.com> Reviewed-by:
Eric Blake <eblake@redhat.com> Signed-off-by:
Paolo Bonzini <pbonzini@redhat.com>
-
- 03 Mar, 2015 1 commit
-
-
Gonglei authored
qemu_boot_set() can't fail in restore_boot_order(), then simply assert it doesn't fail, by passing &error_abort if boot_set_handler set. Suggested-by:
Markus Armbruster <armbru@redhat.com> Signed-off-by:
-
- 27 Feb, 2015 1 commit
-
-
Gonglei authored
Reproducer: $./qemu-system-x86_64 --enable-kvm -kernel /home/vmlinuz-2.6.32.12-0.7-default \ -initrd /home/initrd-2.6.32.12-0.7-default -append \ "root=/dev/ram rw console=ttyS0,115200" -dtb guest.dtb -vnc :10 --monitor stdio -smp 2 QEMU 2.2.50 monitor - type 'help' for more information (qemu) Segmentation fault (core dumped) Reported-by:
Edivaldo de Araujo Pereira <edivaldoapereira@yahoo.com.br> Signed-off-by:
-
- 11 Feb, 2015 1 commit
-
-
Gonglei authored
commit 6b1566cb (qdev: Introduce FWPathProvider interface) did a good job for supproting to get firmware path on some different architectures. Moreover further more, we can use the interface to get firmware path name for a device which isn't attached a specific bus, such as virtio-bus, scsi-bus etc. When the device (such as vhost-scsi) realize the TYPE_FW_PATH_PROVIDER interface, we should introduce a new function to get the correct firmware path name for it. Signed-off-by:
-
- 22 Dec, 2014 5 commits
-
-
Gonglei authored
It will be useful for checking when we change traditional boot order dynamically and propagate error message to the monitor. For x86 architecture, we pass &local_err to set_boot_dev() when vm startup in pc_coms_init(). Cc: Michael S. Tsirkin <mst@redhat.com> Cc: Alexander Graf <agraf@suse.de> Cc: Blue Swirl <blauwirbel@gmail.com> Cc: qemu-ppc@nongnu.org Signed-off-by:
-
Gonglei authored
Signed-off-by:
-
Gonglei authored
It will be useful for checking when we change traditional boot order dynamically and propagate error message to the monitor. Signed-off-by:
-
Gonglei authored
It will be useful for checking when we change traditional boot order dynamically and propagate error message to the monitor. Signed-off-by:
-
Gonglei authored
First, we can downsize vl.c, make it simpler by little and little. Second, I can maintain those code and make some improvement. Cc: Jan Kiszka <jan.kiszka@siemens.com> Signed-off-by:
-
- 15 Oct, 2014 9 commits
-
-
Gonglei authored
The function may be called by qmp command, we should report error message to the caller. Signed-off-by:
Gerd Hoffmann <kraxel@redhat.com>
-
Gonglei authored
Device should be removed from global boot list when it is hot-unplugged. Signed-off-by:
-
Gonglei authored
On this way, we can assure the new bootindex take effect during vm rebooting. Signed-off-by:
-
Gonglei authored
when we remove bootindex form qdev.property to qom.property, we can use those functions set/get bootindex property for all correlative devices. Meanwhile set the initial value of bootindex to -1. Signed-off-by:
-
Gonglei authored
When set a device's bootindex to -1, we remove it from global fw_boot_order list. Signed-off-by:
-
Gonglei authored
Add the function of updating bootindex about fw_boot_order list in add_boot_device_path(). We should delete the old one if a device has existed in global fw_boot_order list. Signed-off-by:
-
Gonglei authored
Introduce del_boot_device_path() to clean up fw_cfg content when hot-unplugging a device that refers to a bootindex or update a existent devcie's bootindex. Signed-off-by:
Chenliang <chenliang88@huawei.com> Reviewed-by:
-
Gonglei authored
Determine whether a given bootindex exists or not. If exists, we report an error. Signed-off-by:
-
Gonglei authored
Signed-off-by:
-
