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] Xen-3.0 on Suse-10

Hi Braulio,

Heres the new file:

disk = [ 'file:/var/lib/xen/images/domain1/hda,xvda,w' ]
memory = 256
kernel = "/var/lib/xen/images/domain1/vmlinuz-2.6.13-15-xen"
ramdisk = "/var/lib/xen/images/domain1/inst-initrd"
name = "domain1"
dhcp = "dhcp"
extra = "TERM=xterm textmode=1 install=nfs://172.25.243.135/var/Suse-10"
restart= "never"
root = ""

i issue :
linux:~ # xm create -c domain1
---------------------------normal bootup
Initializing Cryptographic API
vesafb: abort, cannot ioremap video memory 0x0 @ 0x0
vesafb: probe of vesafb.0 failed with error -5
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as tty1
Event-channel device installed.
Neither TPM-BE Domain nor INIT domain!
xen_blk: Initialising virtual block device driver
Registering block device major 202
 xvda:
======================hanging up

--------------------------------------------------------------

xend.log says this:linux:~ # tail -f /var/log/xend.log
[2006-02-13 12:08:33 xend] DEBUG (image:260) ramdisk
= /var/lib/xen/images/domain1/inst-initrd
[2006-02-13 12:08:33 xend] DEBUG (image:261) flags          = 0
[2006-02-13 12:08:33 xend] DEBUG (image:262) vcpus          = 1
[2006-02-13 12:08:34 xend] INFO (xsobj:326) DBMap>introduceDomain> 1
129175 <EventChannel dom1:0:16
dom2:1:1> /domain/e2cb5734-dbdd-4f55-a771-d4f9f897ebdc
[2006-02-13 12:08:34 xend] DEBUG (XendDomainInfo:698) writing key
availability=online to path /cpu/0 in store
[2006-02-13 12:08:34 xend] WARNING (XendDomainInfo:1100) Unknown config
field boot
[2006-02-13 12:08:34 xend] WARNING (XendDomainInfo:1100) Unknown config
field display
[2006-02-13 12:08:34 xend] DEBUG (blkif:24) exception looking up device
number for xvda: [Errno 2] No such file or directory: '/dev/xvda'
[2006-02-13 12:08:35 xend] ERROR (XendDomainInfo:443) ['vif', ['mac',
'aa:00:00:1c:54:40']]
[2006-02-13 12:08:35 xend] INFO (XendRoot:141) EVENT>
xend.domain.unpause ['domain1', 1]

--------------------------------------------------------------------------
xend-debug.log says
linux:~ # tail -f /var/log/xend-debug.log
    info.cleanup()
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 755, in cleanup
    self.release_devices()
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 803, in release_devices
    for d in t.list("vif"):
  File
"/usr/lib/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line
110, in list
    ret.extend(self._list(key))
  File
"/usr/lib/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line
103, in _list
    return map(lambda x: key + "/" + x, xshandle().ls(path))
RuntimeError: (2, 'No such file or directory')

I tried googling /searching mailing lists ,but couldnt figure out much

Regards
Digz


On Fri, 2006-02-10 at 15:09 -0200, Bráulio Gergull wrote:
> Hi Digvijoy,
>
> On Feb 10, 2006 08:11 AM, Digvijoy Chatterjee
> <digvijoy_chatterjee@xxxxxxxxxxx> wrote:
>
> >
> > I am trying to start a DomU using yast2 on Suse-10 which autogenerates
> > this file and starts it up:
> >
> > disk = [ 'file:/var/lib/xen/images/domain1/hda,hda,w' ]
> > memory = 256
> > kernel = "/var/lib/xen/images/domain1/vmlinuz-2.6.13-15-xen"
> > ramdisk = "/var/lib/xen/images/domain1/inst-initrd"
> > name = "domain1"
> > dhcp = "dhcp"
> > extra = ""
> > root = ""
> 
> Edit the file above and make the following changes:
>
> disk = [ 'file:/var/lib/xen/images/domain1/hda,xvda,w' ]
>
> extra = "TERM=xterm textmode=1
> install=nfs://servername/path_to_source_dir"
>
> restart = "never"
>
> Then open an xterm and type:
>
> xm create -c domain1
>
> You should see linuxrc start inside the xterm.
>
> When the instalation finishes you should change the line
>
> ramdisk = "/var/lib/xen/images/domain1/inst-initrd"
>
> to contain the initrd for a running system instead of the installation
> one. Hopefully you can safely use "/boot/initrd-xen"
>
> Also you'll need to change the root line to:
>
> root = "/dev/xvda1"
>
> (or xvda2, depending in how partitioning was performed during install)
>
> And finaly:
>
> restart = "onreboot"
>
> Now start domain1 again from an xterm and you should be able to finish
> the installation.
>
> Another option is to use the option "Installation into directory" from
> YaST and then use that directory as the image for xen.
>
> rgrds,
> Braulio Gergull
>


**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are 
not to copy, disclose, or distribute this e-mail or its contents to any other 
person and any such actions are unlawful. This e-mail may contain viruses. 
Infosys has taken every reasonable precaution to minimize this risk, but is not 
liable for any damage you may sustain as a result of any virus in this e-mail. 
You should carry out your own virus checks before opening the e-mail or 
attachment. Infosys reserves the right to monitor and review the content of all 
messages sent to or from this e-mail address. Messages sent to or from this 
e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

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

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