thr3ads.net - Xen users - [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1) [Dec 2007]

If this information is useful, please help other people find it:
Share via:

Julien Reveillet

2007-Dec-18 09:50 UTC

[Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

Hello everybody,

I''m having troubles creating a FreeBSD DomU.

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"

on_crash    = ''preserve''

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 Reveillet

j.reveillet@graphique-alliance.com

GraphiqueAlliance

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@lists.xensource.com
http://lists.xensource.com/xen-users

Julien Reveillet

2007-Dec-18 11:52 UTC

head link

[Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

Hello everybody,

I''m having troubles creating a FreeBSD DomU.

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"

on_crash    = ''preserve''
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@lists.xensource.com
http://lists.xensource.com/xen-users

Julien Reveillet

2007-Dec-18 13:20 UTC

head link

[Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

Hello everybody,

I''m having troubles creating a FreeBSD DomU.

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"

on_crash    = ''preserve''
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@lists.xensource.com
http://lists.xensource.com/xen-users

Igor Chubin

2007-Dec-18 14:11 UTC

head link

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

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"
>
> on_crash    = ''preserve''
> 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@lists.xensource.com
> http://lists.xensource.com/xen-users
-- 
WBR, i.m.chubin


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

Julien Reveillet

2007-Dec-18 15:19 UTC

head link

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

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"

on_crash    = ''preserve''
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@lists.xensource.com
http://lists.xensource.com/xen-users

-- 

____________________________________

Julien Reveillet

j.reveillet@graphique-alliance.com

GraphiqueAlliance

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@lists.xensource.com
http://lists.xensource.com/xen-users

Igor Chubin

2007-Dec-18 15:53 UTC

head link

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

...> 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.
You have kernel panic in the domain 0?
Right?

Can you provide more details on that?


I''m sorry I haven''t seen these lines.
>
> 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?)

I think it would be great option, 
bat as far as I know this is impossible for the present.
> - Any other way?...
>
> Thanks in advance.
>
> Julien.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
-- 
WBR, i.m.chubin


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

Julien Reveillet

2007-Dec-18 18:24 UTC

head link

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

Nop!

I''ve found that my grub conf use Dom0 kernel with pae enabled when
using Xen 3 kernel pae disabled.

Here are the logs i''ve catched : 

PAE mode mismatch in Xen (xen=no Dom0=yes)

What i''ve see while googling is that on Debian, they only give us
Pae kernels.

I have to compile my own kernels for Dom0 in a way to use FreeBSD as a
DomU.

Just for my knowledge, how can you get logs of your Xen 3 kernel when
it is rebooting because of a kernel panic?

Is it possible?

Thanks.

Julien.

Igor Chubin a écrit :

...

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.

You have kernel panic in the domain 0?
Right?

Can you provide more details on that?

I''m sorry I haven''t seen these lines.

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?)

I think it would be great option, 
bat as far as I know this is impossible for the present.

- Any other way?...

Thanks in advance.

Julien.

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

-- 

____________________________________

Julien Reveillet

j.reveillet@graphique-alliance.com

GraphiqueAlliance

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@lists.xensource.com
http://lists.xensource.com/xen-users

Kip Macy

2007-Dec-19 02:39 UTC

head link

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

PAE is currently the default option for Xen. After a 2 year hiatus I
very recently started working on FreeBSD support for Xen again. I''m
currently fixing issues related to PAE in FreeBSD Xen support on
-current in a P4 branch. I hope to have more to say very soon.

-Kip

On Dec 18, 2007 10:24 AM, Julien Reveillet
<j.reveillet@graphique-alliance.com> wrote:>
>  Nop!
>
>  I''ve found that my grub conf use Dom0 kernel with pae enabled
when using
> Xen 3 kernel pae disabled.
>  Here are the logs i''ve catched :
>
>  PAE mode mismatch in Xen (xen=no Dom0=yes)
>
>  What i''ve see while googling is that on Debian, they only give us
Pae
> kernels.
>
>  I have to compile my own kernels for Dom0 in a way to use FreeBSD as a
> DomU.
>
>  Just for my knowledge, how can you get logs of your Xen 3 kernel when it
is
> rebooting because of a kernel panic?
>
>  Is it possible?
>
>  Thanks.
>  Julien.
>
>  Igor Chubin a écrit :
>  ...
>
>
>  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.
>
>  You have kernel panic in the domain 0?
> Right?
>
> Can you provide more details on that?
>
>
> I''m sorry I haven''t seen these lines.
>
>
>
>  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?)
>
>
> I think it would be great option,
> bat as far as I know this is impossible for the present.
>
>
>
>  - Any other way?...
>
> Thanks in advance.
>
> Julien.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>
>
>
>
> --
>
>
>
> ____________________________________
>
>  Julien Reveillet
>  j.reveillet@graphique-alliance.com
>
>  GraphiqueAlliance
>  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@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Mark Williamson

2007-Dec-19 05:10 UTC

head link

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

> PAE is currently the default option for Xen. After a 2 year hiatus I
> very recently started working on FreeBSD support for Xen again.
I''m
> currently fixing issues related to PAE in FreeBSD Xen support on
> -current in a P4 branch. I hope to have more to say very soon.
Yay!

Cheers,
Mark
> -Kip
>
> On Dec 18, 2007 10:24 AM, Julien Reveillet
>
> <j.reveillet@graphique-alliance.com> wrote:
> >  Nop!
> >
> >  I''ve found that my grub conf use Dom0 kernel with pae
enabled when using
> > Xen 3 kernel pae disabled.
> >  Here are the logs i''ve catched :
> >
> >  PAE mode mismatch in Xen (xen=no Dom0=yes)
> >
> >  What i''ve see while googling is that on Debian, they only
give us Pae
> > kernels.
> >
> >  I have to compile my own kernels for Dom0 in a way to use FreeBSD as
a
> > DomU.
> >
> >  Just for my knowledge, how can you get logs of your Xen 3 kernel when
it
> > is rebooting because of a kernel panic?
> >
> >  Is it possible?
> >
> >  Thanks.
> >  Julien.
> >
> >  Igor Chubin a écrit :
> >  ...
> >
> >
> >  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.
> >
> >  You have kernel panic in the domain 0?
> > Right?
> >
> > Can you provide more details on that?
> >
> >
> > I''m sorry I haven''t seen these lines.
> >
> >
> >
> >  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?)
> >
> >
> > I think it would be great option,
> > bat as far as I know this is impossible for the present.
> >
> >
> >
> >  - Any other way?...
> >
> > Thanks in advance.
> >
> > Julien.
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
> >
> >
> >
> >
> > --
> >
> >
> >
> > ____________________________________
> >
> >  Julien Reveillet
> >  j.reveillet@graphique-alliance.com
> >
> >  GraphiqueAlliance
> >  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@lists.xensource.com
> > http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users


-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

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

Julien Reveillet

2007-Dec-19 08:49 UTC

head link

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

We hope too!...

Thanks for your effort.

Regards.

Julien.

Kip Macy a écrit :

PAE is currently the default option for Xen. After a 2 year hiatus I
very recently started working on FreeBSD support for Xen again. I''m
currently fixing issues related to PAE in FreeBSD Xen support on
-current in a P4 branch. I hope to have more to say very soon.

-Kip

On Dec 18, 2007 10:24 AM, Julien Reveillet
 wrote:

 Nop!

 I''ve found that my grub conf use Dom0 kernel with pae enabled when
using
Xen 3 kernel pae disabled.
 Here are the logs i''ve catched :

 PAE mode mismatch in Xen (xen=no Dom0=yes)

 What i''ve see while googling is that on Debian, they only give us Pae
kernels.

 I have to compile my own kernels for Dom0 in a way to use FreeBSD as a
DomU.

 Just for my knowledge, how can you get logs of your Xen 3 kernel when it is
rebooting because of a kernel panic?

 Is it possible?

 Thanks.
 Julien.

 Igor Chubin a écrit :
 ...

 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.

 You have kernel panic in the domain 0?
Right?

Can you provide more details on that?

I''m sorry I haven''t seen these lines.

 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?)

I think it would be great option,
bat as far as I know this is impossible for the present.

 - Any other way?...

Thanks in advance.

Julien.

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

--

____________________________________

 Julien Reveillet
 j.reveillet@graphique-alliance.com

 GraphiqueAlliance
 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@lists.xensource.com
http://lists.xensource.com/xen-users

-- 

____________________________________

Julien Reveillet

j.reveillet@graphique-alliance.com

GraphiqueAlliance

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@lists.xensource.com
http://lists.xensource.com/xen-users

Igor Chubin

2007-Dec-19 13:13 UTC

head link

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

On Di, Dez 18, 2007 at 06:39:56 -0800, Kip Macy wrote:> PAE is currently the default option for Xen. After a 2 year hiatus I
> very recently started working on FreeBSD support for Xen again.
I''m
> currently fixing issues related to PAE in FreeBSD Xen support on
> -current in a P4 branch. I hope to have more to say very soon.

Hello, Kip,
thank you for your answer,
and thank you for your work at all!

Please, say, 
is it possible to build FreeBSD domU kernel 
from source (even without PAE support)
with GCC >= 4.1 at the moment?

Thank you for your great work once again!

> 
> -Kip
> 
> On Dec 18, 2007 10:24 AM, Julien Reveillet
> <j.reveillet@graphique-alliance.com> wrote:
> >
> >  Nop!
> >
> >  I''ve found that my grub conf use Dom0 kernel with pae
enabled when using
> > Xen 3 kernel pae disabled.
> >  Here are the logs i''ve catched :
> >
> >  PAE mode mismatch in Xen (xen=no Dom0=yes)
> >
> >  What i''ve see while googling is that on Debian, they only
give us Pae
> > kernels.
> >
> >  I have to compile my own kernels for Dom0 in a way to use FreeBSD as
a
> > DomU.
> >
> >  Just for my knowledge, how can you get logs of your Xen 3 kernel when
it is
> > rebooting because of a kernel panic?
> >
> >  Is it possible?
> >
> >  Thanks.
> >  Julien.
> >
> >  Igor Chubin a écrit :
> >  ...
> >
> >
> >  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.
> >
> >  You have kernel panic in the domain 0?
> > Right?
> >
> > Can you provide more details on that?
> >
> >
> > I''m sorry I haven''t seen these lines.
> >
> >
> >
> >  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?)
> >
> >
> > I think it would be great option,
> > bat as far as I know this is impossible for the present.
> >
> >
> >
> >  - Any other way?...
> >
> > Thanks in advance.
> >
> > Julien.
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
> >
> >
> >
> >
> > --
> >
> >
> >
> > ____________________________________
> >
> >  Julien Reveillet
> >  j.reveillet@graphique-alliance.com
> >
> >  GraphiqueAlliance
> >  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@lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
-- 
WBR, i.m.chubin


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

Kip Macy

2007-Dec-20 04:50 UTC

head link

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

On Dec 19, 2007 5:13 AM, Igor Chubin <igor@chub.in>
wrote:> On Di, Dez 18, 2007 at 06:39:56 -0800, Kip Macy wrote:
> > PAE is currently the default option for Xen. After a 2 year hiatus I
> > very recently started working on FreeBSD support for Xen again.
I''m
> > currently fixing issues related to PAE in FreeBSD Xen support on
> > -current in a P4 branch. I hope to have more to say very soon.
>
>
> Hello, Kip,
> thank you for your answer,
> and thank you for your work at all!
>
> Please, say,
> is it possible to build FreeBSD domU kernel
> from source (even without PAE support)
> with GCC >= 4.1 at the moment?
I believe so. However, I don''t think what I have out there now will
work with anything newer than Xen 3.0.2.

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

Kip Macy

2008-Jan-18 03:10 UTC

head link

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

You can get a copy of my perforce branch via a cvsup mirror using
cvsup10.freebsd.org or cvsup18.freebsd.org.

There is more information at:
http://wiki.freebsd.org/FreeBSD/Xen

I still need to track down a bug in Xen. As far as I can tell writable
pagetables don''t always preserve the OS-reserved bits.

 -Kip


On Dec 18, 2007 5:20 AM, Julien Reveillet
<j.reveillet@graphique-alliance.com> wrote:> Hello everybody,
>
> I''m having troubles creating a FreeBSD DomU.
>
> 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"
>
> on_crash    = ''preserve''
> 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@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Kip Macy

2008-Jan-18 20:46 UTC

head link

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

It currently only supports 3.0.4 or later.

 -Kip

On Dec 18, 2007 1:50 AM, Julien Reveillet <julien.reveillet@gmail.com>
wrote:>
>  Hello everybody,
>
>  I''m having troubles creating a FreeBSD DomU.
>
>  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"
>
>  on_crash    = ''preserve''
>  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 Reveillet
>  j.reveillet@graphique-alliance.com
>
>  GraphiqueAlliance
>  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@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Xen users - Dec 2007 - FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

[Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

[Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

[Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)

Re: [Xen-users] FreeBSD DomU under Debian Etch Dom0 (Xen 3.0.3-1)