xen-users
[Xen-users] no SDL window during Windows install (XEN-3.0.3-testing)
Hi All,
I tried to create a Windows guest on xen-3.0.3-testing but didn't get the SDL window to continue installation. I have dev86, SDL and SDL-devel rpms installed. I run xm log and saw an exception, exception looking up device number for hdc: [Errno 2] No such file or directory: \047/dev/hdc\047. Is that the reason why the SDL window does not appear? Although xm li shows the domain is running. What am I missing here?
Thanks in advance.
-Anirban
Relevant portions of my hvm file looks like: vif = [ 'type=ioemu, bridge=xenbr0' ] disk = [ 'phy:/dev/guestos/w2k3,ioemu:hda,w','file:/tmp/EN_WS03.ISO,hdc:cdrom,r' ]
boot="cda" sdl=1 vnc=0
I do not know why qemu could not find device hdc. I do see that the cdrom device is /dev/hdc (when I load a cd into the drive and do df, it shows the cdrom is /dev/hdc).
Detail messsages from xm log given below:
[2006-11-09 10:43:10 xend 5204] DEBUG (image:409) hvm shutdown watch registered [2006-11-09 10:43:10 xend 5204] DEBUG (DevController:110) DevController: writing {\047backend-id\047: \0470\047, \047virtual-device\047: \047768\047, \047device-type\047: \047disk\047, \047state\047: \0471\047, \047backend\047: \047/local/domain/0/backend/vbd/11/768\047} to /local/domain/11/device/vbd/768.
[2006-11-09 10:43:10 xend 5204] DEBUG (DevController:112) DevController: writing {\047domain\047: \047win\047, \047frontend\047: \047/local/domain/11/device/vbd/768\047, \047dev\047: \047hda\047, \047state\047: \0471\047, \047params\047: \047/dev/guestos/w2k3\047, \047mode\047: \047w\047, \047online\047: \0471\047, \047frontend-id\047: \04711\047, \047type\047: \047phy\047} to /local/domain/0/backend/vbd/11/768.
[2006-11-09 10:43:10 xend 5204] DEBUG (blkif:24) exception looking up device number for hdc: [Errno 2] No such file or directory: \047/dev/hdc\047 [2006-11-09 10:43:10 xend 5204] DEBUG (DevController:110) DevController: writing {\047backend-id\047: \0470\047, \047virtual-device\047: \0475632\047, \047device-type\047: \047cdrom\047, \047state\047: \0471\047, \047backend\047: \047/local/domain/0/backend/vbd/11/5632\047} to /local/domain/11/device/vbd/5632.
<snip> [2006-11-09 10:35:07 xend 5204] DEBUG (image:432) hvm_shutdown fired, shutdown reason=None [2006-11-09 10:35:07 xend.XendDomainInfo 5204] DEBUG (XendDomainInfo:933) XendDomainInfo.handleShutdownWatch
[2006-11-09 10:35:08 xend 5204] DEBUG (DevController:143) Waiting for devices vif. [2006-11-09 10:35:08 xend 5204] DEBUG (DevController:149) Waiting for 0. [2006-11-09 10:35:08 xend 5204] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vif/10/0/hotplug-status.
[2006-11-09 10:35:08 xend 5204] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vif/10/0/hotplug-status. [2006-11-09 10:35:08 xend 5204] DEBUG (DevController:478) hotplugStatusCallback 1.
[2006-11-09 10:35:08 xend 5204] DEBUG (DevController:143) Waiting for devices usb. [2006-11-09 10:35:08 xend 5204] DEBUG (DevController:143) Waiting for devices vbd. [2006-11-09 10:35:08 xend 5204] DEBUG (DevController:149) Waiting for 768.
[2006-11-09 10:35:08 xend 5204] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vbd/10/768/hotplug-status. [2006-11-09 10:35:08 xend 5204] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vbd/10/768/hotplug-status.
[2006-11-09 10:35:08 xend 5204] DEBUG (DevController:478) hotplugStatusCallback 1. [2006-11-09 10:35:08 xend 5204] DEBUG (DevController:149) Waiting for 832. [2006-11-09 10:35:08 xend 5204] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vbd/10/832/hotplug-status.
[2006-11-09 10:35:08 xend 5204] DEBUG (DevController:478) hotplugStatusCallback 1. [2006-11-09 10:35:08 xend 5204] DEBUG (DevController:143) Waiting for devices irq. [2006-11-09 10:35:08 xend 5204] DEBUG (DevController:143) Waiting for devices pci.
[2006-11-09 10:35:08 xend 5204] DEBUG (DevController:143) Waiting for devices ioports. [2006-11-09 10:35:08 xend 5204] DEBUG (DevController:143) Waiting for devices tap. [2006-11-09 10:35:08 xend 5204] DEBUG (DevController:143) Waiting for devices vtpm.
[2006-11-09 10:35:08 xend 5204] INFO (XendDomain:370) Domain win (10) unpaused.
I run xm dmesg and get following (no error):
(XEN) (GUEST: 2) Start BIOS ... (XEN) (GUEST: 2) Starting emulated 16-bit real-mode: ip=F000:FFF0
(XEN) (GUEST: 2) rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $ (XEN) (GUEST: 2) Remapping master: ICW2 0x8 -> 0x20 (XEN) (GUEST: 2) Remapping slave: ICW2 0x70 -> 0x28 (XEN) (GUEST: 2) VGABios $Id:
vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert Exp $ (XEN) (GUEST: 2) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $ (XEN) (GUEST: 2) (XEN) (GUEST: 2) ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
(XEN) (GUEST: 2) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (10212 MBytes) (XEN) (GUEST: 2) ata0 slave: Unknown device (XEN) (GUEST: 2) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom (XEN) (GUEST: 2) ata1 slave: Unknown device
(XEN) (GUEST: 2) (XEN) (GUEST: 2) Boot from Hard Disk 0 failed (XEN) (GUEST: 2) Booting from CD-Rom...
xm li does show that the win guest is running. ps -ef | grep qemu shows it is running: root 6403 5204 0 10:14 ? 00:00:01 /usr/lib/xen/bin/qemu-dm -d 2 -m 512 -boot cda -serial pty -vcpus 1 -domain-name win -net nic,vlan=1,macaddr=00:16:3e:08:3d:7f,model=rtl8139 -net tap,vlan=1,bridge=xenbr0
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-users] no SDL window during Windows install (XEN-3.0.3-testing),
Anirban Chakraborty <=
|
|
|