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

[Xen-devel] change cd iso image in hvm but loop not changed?


  • To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
  • Date: Sun, 26 Jul 2009 15:00:24 +0100
  • Delivery-date: Sun, 26 Jul 2009 07:00:55 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=Hq24xoqyGTALEK8tSuzlTsElIu2RK4ECBwii8O+loNhCWAoCA4DbUhmclVJtoWWFwz 9I7pWl42izyb6ncuD40Y+F4khdW/D4RiVDD9sGHIOV63lRJSOKPfGIOs1OHBJzbW3MrL iDYkoPNuhuC5nluUTb+RWGOYVCE9zKcxYKcd4=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,

I booted a windows hvm with a iso image (/root/t.iso) connected to the
cdrom, I then changed the iso image using the following technique:


I used xm block-list <domid> to find the cdrom be-path:

5632   0    0     1      -1     -1    /local/domain/0/backend/vbd/3/5632

To make absolutely sure I got the right device I used xenstore-read:

xenstore-read /local/domain/0/backend/vbd/3/5632/params

/root/t.iso


I then used xenstore-write to change the iso image:

 xenstore-write /local/domain/0/backend/vbd/3/5632/params
/home/admin/isos/sql2k8.iso


After a few seconds the new cd appears in windows, however there is
still a loop device setup for the original iso image:

losetup -a
/dev/loop/0: [0802]:1517 (/root/t.iso)


Why is this setup? if the cd can be changed without mounting the new
iso as a loop device why do it in the first place?

the hvm has gplpv drivers loaded but they do not provide cdrom, it is emulated.

Andy

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


 


Rackspace

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