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

[Xen-users] DomU from physical disk FC6-2911


  • From: marc+xenuser@xxxxxxxxxxxxxxxx
  • Date: Sat, 5 May 2007 15:10:52 -0500 (CDT)
  • Delivery-date: Wed, 09 May 2007 10:19:46 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I'm trying to get xen working on FC6 using
vmlinuz-2.6.19-1.2911.6.5.fc6xen as other  newer images result in the machine 
locking up.

I have 3 disks in the system - two IDE drives (master/slave - hda/hdb) and one 
SATA (sdb)

All 3 drives have a bootable FC6 setup.   One is to be the Dom0 and the other 
(hdb and sdb) are to be the 2 DomU's.   Thus the virt-manager and associated 
scripts are not helpful.    Most of the docs use the .img files.


The system seems to have allocated /dev/sda  for Xen.  (Am I making the proper 
guess here?)  


Results from     xm create -n apps
Using config file "/etc/xen/apps".
(vm
    (name apps)
    (memory 1024)
    (vcpus 1)
    (image (linux (kernel /boot/vmlinuz-2.6.19-1.2911.6.5.fc6xen) (args 4)))
    (device (vbd (uname phy:vg/AppsVG) (dev sda1) (mode w)))
    (device (vif (ip 192.168.1.8) (mac 00:16:3e:00:00:08) (bridge xenbr0)))
)

The text of /etc/xen/apps
kernel = "/boot/vmlinuz-2.6.19-1.2911.6.5.fc6xen"
memory = 1024
name = "apps"
vif = [ 'ip=192.168.1.8,mac=00:16:3e:00:00:08,bridge=xenbr0' ]
disk = [ 'phy:vg/AppsVG,sda1,w' ]
extra = "4"




The Error I get after some time is
Error: Device 2049 (vbd) could not be connected.  

Email lists talk about how Device 2049 (vdb) errors are corrected with a 
modprobe loop command - but FC6 has netloop so I'm guessing I have some other 
config problem(s).

So....what am I doing wrong with my configs?

_______________________________________________
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®.