[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] cd-rom access, hvm boot, unstable download from 9-7-2006


  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Eli Robinson" <Eli.Robinson@xxxxxxxxxxxxxxxx>
  • Date: Mon, 11 Sep 2006 15:29:57 -0400
  • Delivery-date: Mon, 11 Sep 2006 12:30:47 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcbV2KqpFkjLkbEbSs6w5sNGmMmqMA==
  • Thread-topic: cd-rom access, hvm boot, unstable download from 9-7-2006

I grabbed the unstable download from 9-7-2006.

 

When I go to create a hvm VM, I get a CDROM boot failure code: 0002 in xm dmesg.

 

In my configuration file, I have tried the following:

 

cdrom=/dev/had

cdrom=/root/installimages/winxpsp2.iso

 

Both without success.

 

Should I use a syntax like pointing the hard disk to an image?

 

IE:

 

cdrom = [ ‘file:/root/installimages/winxpsp2.iso’]

 

(this does not work either)

 

When I issue the xm create winxp.hvm command I get the SDL window and see a quick screen with a “Q to quit” prompt (too quick to read it all) then see the bios screen pop up, get a could not read from boot device error in that screen and it dies.

 

 

If anymore information is required please let me know.

 

The platform is an AM2 4600+ chip riding on an MSI K9N SLI Platinum with a gig of Corsair Dual channel DDR2 with a WD SATA 160 gig drive. Running CentOS 4.3 64bit.

 

Also is it best practice to give guest OS’s individual partitions or use image files for their operating system? I could see portability being a huge plus with image files but maybe better performance from partitions. Has anyone had a chance to play with this using fiber channel SANs? Is it worth the effort?

 

 

Thanks,

Eli

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.