WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] "device model failure" when launching Windows SBS 2003 H

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] "device model failure" when launching Windows SBS 2003 HVM
From: Frans Lawaetz <frans@xxxxxxxxxxxx>
Date: Fri, 1 May 2009 11:35:13 -0500
Accept-language: en-US
Acceptlanguage: en-US
Delivery-date: Fri, 01 May 2009 09:38:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7207d96f0904302018laf91ba8q6e240b00d033ff83@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1241125148.7413.66.camel@xxxxxxxxxxxxxxxxxxxxx> <7207d96f0904302018laf91ba8q6e240b00d033ff83@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcnKC4yZgGodu/s4Q6eQN6cxcJDdsAAX5azQ
Thread-topic: [Xen-users] "device model failure" when launching Windows SBS 2003 HVM
>>
>> I am trying to install Windows SBS 2003 32-bit in a HVM on a CentOS 5.1
>> x86_64 system running Xen 3.3.1 from the gitco repositories.
>>
>> The domU config is below.  I have tried a variety of different settings to
>> no avail.
>>

>> disk = [ 'phy:/dev/VolGroup00/win2k3,xvda,w', ',hdc:cdrom,r' ]
>> cdrom = '/dev/cdrom'

>This seems wrong. Try

>disk = [ 'phy:/dev/VolGroup00/win2k3,hda,w', 'phy:/dev/cdrom,hdc:cdrom,r' ]
>and remove the "cdrom=" line completely

Unfortunately that made no difference.

My updated domU config file is as follows:


import os, re
arch = os.uname()[4]
if re.search('64', arch):
    arch_libdir = 'lib64'
else:
    arch_libdir = 'lib'
kernel = '/usr/lib/xen/boot/hvmloader'
builder = 'hvm'
memory = '1024'
disk = [ 'phy:/dev/VolGroup00/win2k3,hda,w', 'phy:/dev/cdrom,hdc:cdrom,r' ]
#disk = [ 'phy:/dev/VolGroup00/win2k3,xvda,w', ',hdc:cdrom,r' ]
#cdrom = '/dev/cdrom'
boot = 'dc'
name = 'windows'
acpi = 1
apic = 1
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
vnc=1
vncdisplay=1
sdl=0


The error remains the same:

[2009-05-01 16:42:54 20070] INFO (XendDomain:1174) Domain windows (63) unpaused.
[2009-05-01 16:42:58 20070] INFO (XendDomainInfo:1634) Domain has shutdown: 
name=windows id=63 reason=poweroff.
[2009-05-01 16:42:58 20070] DEBUG (XendDomainInfo:2402) XendDomainInfo.destroy: 
domid=63
[2009-05-01 16:42:58 20070] DEBUG (XendDomainInfo:1939) Destroying device model
[2009-05-01 16:42:58 20070] WARNING (image:472) domain windows: device model 
failure: no longer running; see /var/log/xen/qemu-dm-windows.log

On occasion when I get vnc connected in time I see a brief "unrecognized" 
message appear on the screen before everything disappears.

Thanks,
Frans

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>