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] windows 2008 x64 no cdrom.

To: 'Robbie Garrett' <rgarrett@xxxxxxxxxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] windows 2008 x64 no cdrom.
From: Tait Clarridge <Tait.Clarridge@xxxxxxxxxxxx>
Date: Fri, 14 Aug 2009 15:13:32 -0400
Accept-language: en-US
Acceptlanguage: en-US
Cc:
Delivery-date: Fri, 14 Aug 2009 12:14:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <003201ca1d12$5a49e710$fcdf0a0a@xxxxxxxxxxxxxxx>
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: <002701ca1d08$27e36bc0$fcdf0a0a@xxxxxxxxxxxxxxx> <BE3E4AD392ABD547A384D0CAFD9E77E677DA7A97@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <003201ca1d12$5a49e710$fcdf0a0a@xxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcodCCeqCzMFWVx+TyaLEoPRSvN8yQACOcJwAAA+IQAAAC4V8A==
Thread-topic: [Xen-users] windows 2008 x64 no cdrom.
> -----Original Message-----
> From: Robbie Garrett [mailto:rgarrett@xxxxxxxxxxxxxx]
> Sent: Friday, August 14, 2009 3:07 PM
> To: Tait Clarridge; xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] windows 2008 x64 no cdrom.
> 
> Hello,
> 
> I have made the changed you requested and below is my config file.
> 
> I'm using xen 3.4.1 with kernel of 2.6.18.8-xen.  The problem is still there
> for me.
> 
> import os, re
> arch = os.uname()[4]
> if re.search('64', arch):
>     arch_libdir = 'lib64'
> else:
>     arch_libdir = 'lib'
> 

The above code has sometimes caused some problems for us... remove it and 
change the device_model line to have lib64 instead of lib in the path. First 
verify that /usr/lib64/xen/bin/qemu-dm exists...

> 
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder='hvm'
> memory = '1024'
> device_model = '/usr/lib/xen/bin/qemu-dm'
> 
> # Should be at least 2KB per MB of domain memory, plus a few MB per vcpu.
> name = "windows"
> vif         = [ 'ip=204.124.181.89,mac=00:16:3E:FE:C2:02,vifname=windows' ]
> disk =
> ['file:/windows/xenwin2008.img,ioemu:hda,w','file:/windows/winxpSP2.is
> o,ioem
> u:hdc:cdrom,r']
> #---------------------------------------------------------------------------
> --
> # boot on floppy (a), hard disk (c) or CD-ROM (d)
> # default: hard disk, cd-rom, floppy
> boot="dc"
> sdl=0
> vnc=1
> vncconsole=1

Try removing both the above and below lines as well...

> vncpasswd=''
> 
> #serial='pty'
> usbdevice='tablet'
> 
> acpi=1
> apic=1
> pae=1
> usb=1

Try removing the viridian=1 line as well.

> viridian=1

Are there any log entries from qemu-dm or xend that say anything about missing 
files?


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