http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1522
Summary: Empty CD-ROM does not work with stubdom
Product: Xen
Version: unstable
Platform: Other
OS/Version: Windows
Status: NEW
Severity: normal
Priority: P2
Component: Tools
AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
ReportedBy: jw@xxxxxxxxxxxxxxxxxx
I am testing with the same configuration I listed in bug # 1372:
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1372, but with one
change -- the disk line is instead:
disk = [ 'file:/servers/customers/testvds.img,hda,w', ',hdc:cdrom,r' ]
When I try to start this domain, it shows no error, but "xm list" tells a
different story:
# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 15290 16 r----- 34804.1
testvds 49 512 1 ------ 0.0
.. with no stubdom shown at all. Looking at the auto-generated stubdom
configuration file, I can see the culprit is an extraneous colon:
# cat /etc/xen/stubdoms/testvds-dm
#This file is autogenerated, edit testvds instead!
kernel = '/usr/lib/xen/boot/ioemu-stubdom.gz'
vfb = ['sdl=0, opengl=1, xauthority=/root/.Xauthority, vnc=1, vncdisplay=29,
vnclisten=0.0.0.0, vncunused=0, vncpasswd=test']
disk = [ 'file:/servers/customers/testvds.img,hda:disk,w',':,hdc:cdrom,r' ]
vif = [ 'mac=52:54:00:D6:BA:64,bridge=xenbr0' ]
I edited the stubdom-dm script to leave out the colon, and this allowed the
domain and stubdom to "start"; however, they then immediately freeze, showing
no CPU usage, just as though an invalid boot device were specified -- giving a
second component to this bug.
This bug should be very easy to reproduce, and hopefully easy to fix. I'm just
not sure where to look, beyond the stubdom-dm script.
--
Configure bugmail:
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs
|
Home