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] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)
From: Julien Reveillet <j.reveillet@xxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 18 Dec 2007 16:19:25 +0100
Delivery-date: Tue, 18 Dec 2007 07:20:27 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071218141157.GA15421@xxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4767C937.3040003@xxxxxxxxxxxxxxxxxxxxxx> <20071218141157.GA15421@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
Yes i have but as i wrote it a few lines below, my non-pae xen kernel do a "kernel panic" when using it.

So, again, what can i do?

- Upgrade to Xen 3.1?
- Compile FreeBSD kernel with Pae enabled? (i'm searching for it but 
haven't found one yet, is it a working option for FreeBSD?)
- Any other way?...


Igor Chubin a écrit :
On Di, Dez 18, 2007 at 02:20:55 +0100, Julien Reveillet wrote:
  
Hello everybody,

I'm having troubles creating a FreeBSD DomU.
    



I suppose that you use PAE-enabled kernel in the domain 0.
As for the present it is impossible to run
PV FreeBSD domain on a PAE host.

  
Here are the logs from Xen :

[2007-12-17 10:29:26 xend.XendDomainInfo 25559] DEBUG (__init__:1072) 
XendDomainInfo.create(['vm', ['name', 'FreeBSD'], ['memory', 256], 
['on_crash', 'preserve'], ['vcpus', 1], ['image', ['linux', ['kernel', 
'/boot/xen3_domU'], ['args', 
'boot_verbose,boot_single,vfs.root.mountfrom=ufs:/dev/md0a,kern.hz=100']]], 
['device', ['vbd', ['uname', 'file:/disk/freebsd_racine.img'], ['dev', 
'wd0a'], ['mode', 'w']]], ['device', ['vif']]])
[2007-12-17 10:29:26 xend.XendDomainInfo 25559] DEBUG (__init__:1072) 
parseConfig: config is ['vm', ['name', 'FreeBSD'], ['memory', 256], 
['on_crash', 'preserve'], ['vcpus', 1], ['image', ['linux', ['kernel', 
'/boot/xen3_domU'], ['args', 
'boot_verbose,boot_single,vfs.root.mountfrom=ufs:/dev/md0a,kern.hz=100']]], 
['device', ['vbd', ['uname', 'file:/disk/freebsd_racine.img'], ['dev', 
'wd0a'], ['mode', 'w']]], ['device', ['vif']]]
[2007-12-17 10:29:26 xend.XendDomainInfo 25559] DEBUG (__init__:1072) 
parseConfig: result is {'shadow_memory': None, 'uuid': None, 'on_crash': 
'preserve', 'on_reboot': None, 'localtime': None, 'image': ['linux', 
['kernel', '/boot/xen3_domU'], ['args', 
'boot_verbose,boot_single,vfs.root.mountfrom=ufs:/dev/md0a,kern.hz=100']], 
'on_poweroff': None, 'bootloader_args': None, 'cpus': None, 'name': 
'FreeBSD', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None, 
'vcpu_avail': None, 'memory': 256, 'device': [('vbd', ['vbd', ['uname', 
'file:/disk/freebsd_racine.img'], ['dev', 'wd0a'], ['mode', 'w']]), ('vif', 
['vif'])], 'bootloader': None, 'cpu': None, 'maxmem': None}
[2007-12-17 10:29:26 xend.XendDomainInfo 25559] DEBUG (__init__:1072) 
XendDomainInfo.construct: None
[2007-12-17 10:29:26 xend.XendDomainInfo 25559] DEBUG (__init__:1072) 
XendDomainInfo.initDomain: 35 1.0
[2007-12-17 10:29:26 xend 25559] DEBUG (__init__:1072) Balloon: 1008 KiB 
free; 0 to scrub; need 262144; retries: 20.
[2007-12-17 10:29:26 xend 25559] DEBUG (__init__:1072) Balloon: setting 
dom0 target to 1497 MiB.
[2007-12-17 10:29:26 xend.XendDomainInfo 25559] DEBUG (__init__:1072) 
Setting memory target of domain Domain-0 (0) to 1497 MiB.
[2007-12-17 10:29:27 xend 25559] DEBUG (__init__:1072) Balloon: 263152 KiB 
free; need 262144; done.
[2007-12-17 10:29:27 xend 25559] INFO (__init__:1072) buildDomain os=linux 
dom=35 vcpus=1
[2007-12-17 10:29:27 xend 25559] DEBUG (__init__:1072) dom            = 35
[2007-12-17 10:29:27 xend 25559] DEBUG (__init__:1072) image          = 
/boot/xen3_domU
[2007-12-17 10:29:27 xend 25559] DEBUG (__init__:1072) store_evtchn   = 1
[2007-12-17 10:29:27 xend 25559] DEBUG (__init__:1072) console_evtchn = 2
[2007-12-17 10:29:27 xend 25559] DEBUG (__init__:1072) cmdline        =  
boot_verbose,boot_single,vfs.root.mountfrom=ufs:/dev/md0a,kern.hz=100
[2007-12-17 10:29:27 xend 25559] DEBUG (__init__:1072) ramdisk        =
[2007-12-17 10:29:27 xend 25559] DEBUG (__init__:1072) vcpus          = 1
[2007-12-17 10:29:27 xend 25559] DEBUG (__init__:1072) features       =
[2007-12-17 10:29:27 xend.XendDomainInfo 25559] ERROR (__init__:1072) 
Domain construction failed
Traceback (most recent call last):
File "/usr/lib/xen-3.0.3-1/lib/python/xen/xend/XendDomainInfo.py", line 
195, in create
  vm.initDomain()
File "/usr/lib/xen-3.0.3-1/lib/python/xen/xend/XendDomainInfo.py", line 
1363, in initDomain
  raise VmError(str(exn))
VmError: (22, 'Invalid argument')



Here is my config file :



kernel = "/boot/xen3_domU"

# Optional ramdisk.
#ramdisk = "/boot/initrd.gz"

# The domain build function. Default is 'linux'.
#builder='linux'

# Initial memory allocation (in megabytes) for the new domain.
memory = 256

# A name for your domain. All domains must have different names.
name = "FreeBSD"

vif = [ '' ]

#disk = [ 'phy:hda1,hda1,w' ]
disk = [ 'file:/disk/freebsd_racine.img,wd0a,w' ]

# Set root device.
root = "/dev/sdb1 ro"

#1 Sets runlevel 4.
extra = "4"


extra = "boot_verbose"
extra += ",boot_single"
extra += ",vfs.root.mountfrom=ufs:/dev/md0a"
#extra += ",vfs.root.mountfrom=ufs:/dev/xbd769a"
extra += ",kern.hz=100"


Is there an other builder option for Bsd systems?


I saw many post about people having the same problem but some told them to 
use différent kernel for install or using different way like non pae 
kernel.

As my Xen kernel do a "kernel panic" with non pae (Quad Core with 4Gb) i 
can't try FreeBSD on my system.

What do you suggest to me?

- Upgrade to Xen 3.1?
- Compile FreeBSD kernel with Pae enabled? (i'm searching for it but 
haven't found one yet, is it a working option for FreeBSD?)
- Any other way?...

Thanks in advance.

Julien.

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

  


--

____________________________________

Julien Reveillet
j.reveillet@xxxxxxxxxxxxxxxxxxxxxx


Graphique
Alliance
Solution pré-presse et gestion de documents

Centre Emeraude Cidex 3
61/69 Rue Camille Pelletan 33150 CENON 
Tél. 05 56 67 55 78
Fax. 05 57 54 12 77
www.graphique-alliance.com

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