Hide Forgot
Description of problem: Boot up a win8 guest on RHEL7 (or even RHEL6.5) host with "-M rhel6.4.0" machine type, guest will hit the following problems: (1) guest could boot up, however the screen resolution changes to 640x480 and the desktop has no colour (2) guest fails to boot up. Screenshot will be uploaded. Version-Release number of selected component (if applicable): kernel-3.10.0-57.el7.x86_64 qemu-kvm-1.5.3-21.el7.x86_64 seabios-bin-1.7.2.2-4.el7.noarch How reproducible: Always Steps to Reproduce: 1. Boot up a win8 guest with "-M rhel6.4.0" machine type. eg: /usr/libexec/qemu-kvm -cpu SandyBridge -M rhel6.4.0 -enable-kvm -m 4096 -smp 2,sockets=2,cores=1,threads=1 -name rhel7.0-64 -uuid 9a0e67ec-f286-d8e7-0548-0c1c9ec93009 -nodefconfig -nodefaults -monitor stdio -rtc base=utc,clock=host,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -drive file=/home/win8-32-virtio-el6.qcow2,if=none,id=drive-disk0,format=qcow2,cache=none,id=disk0 -device virtio-blk-pci,bus=pci.0,addr=0x8,drive=drive-disk0,id=disk-0 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,drive=drive-ide0-1-0,bus=ide.0,unit=1,id=scsi-cdrom -netdev tap,id=hostnet0,vhost=on,fd=4 4<>/dev/tap4 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=ee:e7:9c:92:1e:f5,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=channel1,path=/tmp/helloworld1,server,nowait -device virtserialport,chardev=channel1,name=port1,bus=virtio-serial0.0,id=port1 -chardev socket,id=channel2,path=/tmp/helloworld2,server,nowait -device virtserialport,chardev=channel2,name=port2,bus=virtio-serial0.0,id=port2 -device usb-tablet,id=input0 -vnc :10 -vga std -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -drive if=none,id=drive-fdc0-0-0,format=raw,cache=none -global isa-fdc.driveA=drive-fdc0-0-0 -qmp tcp:0:5555,server,nowait -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 2. 3. Actual results: Guest (1) fails to boot up or (2) screen resolution has problem. Expected results: Guest could boot up with correct screen view. Additional info: Host info: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz stepping : 7 microcode : 0x29 cpu MHz : 2793.148 cache size : 6144 KB physical id : 0 siblings : 4 core id : 3 cpu cores : 4 apicid : 6 initial apicid : 6 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid bogomips : 6186.35 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management:
Created attachment 835167 [details] fail to boot up
Created attachment 835168 [details] screen resolution changes to very small
Maybe I should add "+sep" to the command line. After append "+sep" to "-cpu SandyBridge", guest could boot up successfully. Close it now.