Bug 1031735 - Windows 2k3-64 and SLES 11 can't be installed on the Guest VM
Summary: Windows 2k3-64 and SLES 11 can't be installed on the Guest VM
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.5
Hardware: x86_64
OS: All
unspecified
high
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-18 16:27 UTC by zwei
Modified: 2013-11-20 15:35 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-20 15:35:03 UTC
Target Upstream Version:


Attachments (Terms of Use)
capture (62.98 KB, application/x-rar)
2013-11-18 16:27 UTC, zwei
no flags Details

Description zwei 2013-11-18 16:27:18 UTC
Created attachment 825737 [details]
capture

Description of problem:

1. Windows guest VM on RHEL 6.5 Beta host, can't boot up with Windows 2k3-64 iso image, always show "Booting from DVD/CD...".
2. Generi guest VM can't boot up with SLES 11 x64 image.

Version-Release number of selected component (if applicable):
2.6.32-425.el6.x86_64
RHEL6.5-20131024.1-Server-x86_64-DVD1.iso

How reproducible:


Steps to Reproduce:
1. Create guest VM on RHEL 6.5 on GUI virtual machine manager.
2. Select installing guest OS with image.
3. Select Windows server 2003 for win2k3-64, or keep default "Generic" for SLES 11 x64. 

Actual results:
1. Can't boot up with above ISO.
2. CPU utilization keep high.
3. 

Expected results:

Install guest OS successful.

Additional info:

Windows 2008 R2 image works well.
RHEL 5 and 6 work well too.

Comment 1 zwei 2013-11-18 16:29:36 UTC
Nov 18 10:59:51 lin106095 qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory
Nov 18 11:14:26 lin106095 kernel: virbr0: port 4(vnet2) entering disabled state
Nov 18 11:14:26 lin106095 kernel: device vnet2 left promiscuous mode
Nov 18 11:14:26 lin106095 kernel: virbr0: port 4(vnet2) entering disabled state
Nov 18 11:14:27 lin106095 kernel: device vnet2 entered promiscuous mode
Nov 18 11:14:27 lin106095 kernel: virbr0: topology change detected, propagating
Nov 18 11:14:27 lin106095 kernel: virbr0: port 4(vnet2) entering forwarding state
Nov 18 11:14:27 lin106095 qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory
Nov 18 11:14:42 lin106095 kernel: virbr0: port 4(vnet2) entering disabled state
Nov 18 11:14:42 lin106095 kernel: device vnet2 left promiscuous mode
Nov 18 11:14:42 lin106095 kernel: virbr0: port 4(vnet2) entering disabled state
Nov 18 11:19:07 lin106095 dnsmasq-dhcp[4425]: DHCPREQUEST(virbr0) 192.168.122.213 52:54:00:c9:7f:91
Nov 18 11:19:07 lin106095 dnsmasq-dhcp[4425]: DHCPACK(virbr0) 192.168.122.213 52:54:00:c9:7f:91 WIN-G4O8G7H2IGH
Nov 18 11:24:24 lin106095 kernel: device vnet2 entered promiscuous mode
Nov 18 11:24:24 lin106095 kernel: virbr0: topology change detected, propagating
Nov 18 11:24:24 lin106095 kernel: virbr0: port 4(vnet2) entering forwarding state
Nov 18 11:24:24 lin106095 qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory

Comment 3 Martin Kletzander 2013-11-20 13:26:07 UTC
What's the qemu-kvm version used?  Can you attach the machine log from /var/log/libvirt/qemu/<machinename>.log?  Thanks.  In the meantime, I'm transferring this to qemu-kvm as those machines are (almost) the same form virt-manager/libvirt POV.

Comment 4 zwei 2013-11-20 15:33:43 UTC
Sorry, my fault. My iso image is broken.


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