NetBSD-Users archive

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

Re: CentOS DomU under NetBSD51 Dom0 XEN 41

On Wed, 18 Jan 2012 15:49:56 +0100, Roger Pau Monné wrote:
2012/1/18 Bruno Gruel <>:
On Wed, 18 Jan 2012 10:48:10 +0100, Roger Pau Monné wrote:

2012/1/18 Bruno Gruel <>:

Can you describe the problems you are having?
Can you post the DomU configuration file?


Here is a sample config file. I try a lot of combinaison (with or witout
kickstar file ..)

import os, re
arch = os.uname()[4]
kernel = "/etc/xen/vmlinuz"
ramdisk = "/etc/xen/initrd.img"
memory = 512
shadow_memory = 8
name = "NUXEO57"
vif = [ 'type=ioemu, bridge=bridge0, model=ne2k_pci' ]
disk = [ 'file:/VM/linux.img,xvda,w',
'file:/VM/centos57.iso,xvdc:cdrom,r' ]
device_model = '/usr/pkg/libexec/qemu-dm'
vfb = ["type=vnc, keymap=fr"]

Whow, this is quite strange, what I usually use (haven't tried it on NetBSD with CentOS because I use Debian most of the time, but I think
it should work).

Download files from

Sample config file:

kernel = "/path/to/vmlinuz"
ramdisk = "/path/to/initrd.img"

name = "my_centos_domu"
memory = 512
vcpus = 1

vif = ['bridge=my_bridge']
disk = ['file:/path/to/my/img,xvda,w']

After that:

xm create -c /path/to/config

Once the system is installed, remove kernel and ramdisk options and add:

bootloader = "pygrub"

That should do it (I think). Your config file looked like a mess
between a HVM and a PV domain.

Regards, Roger.


It's better but not completly full (i would be more patient after a few
seconds the boot process begin).
The install process begin
The retreive of the install.img file it's OK.

But i always have  error on the storage file (linux.img created with DD),

How did you create it? If you created a spare file (with seek), it
will not work, what I use to create virtual disk images/partitions:

dd if=/dev/zero of=virtualdisk.img bs=1024 count=2000

(this will create a 2GB file)

So this command create a 2MB file. But i steel have to initialize the DD (i do some test with a 2Go file)

during the install process i have somme message tha tell me to initialise
the DD because there is somme error.

And after the initialisation i have this message :

Input/Output error during read on /dev/xvda ?

When you get this error, can you switch to the Dom0 and paste the
output of running "xenstore-ls -fp"?

Now there is no more message with Input/Output error during read on /dev/xvda but i still can't install the systeme... When i selecte "Use entire disk" or other options i have the following message "Impossible to allocate asking paition not enought space for LVM requests.

And the xenstore-ls -fp :

/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/image/ostype = "linux"   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/image/kernel = "/etc/xen/centos/vmlinuz" (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/image/cmdline = ""   (n0,r49)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/image/ramdisk = "/etc/xen/centos/initrd.img" (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device = ""   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/vbd = ""   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/vbd/51712 = ""   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/vbd/51712/frontend = "/local/domain/49/device/vbd/51712" (n0) /vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/vbd/51712/frontend-id = "49" (n0) /vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/vbd/51712/backend-id = "0" (n0) /vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/vbd/51712/backend = "/local/domain/0/backend/vbd/49/51712" (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/vif = ""   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/vif/0 = ""   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/vif/0/frontend = "/local/domain/49/device/vif/0" (n0) /vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/vif/0/frontend-id = "49" (n0) /vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/vif/0/backend-id = "0" (n0) /vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/vif/0/backend = "/local/domain/0/backend/vif/49/0" (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/console = ""   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/console/0 = ""   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/console/0/frontend = "/local/domain/49/device/console/0" (n0) /vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/console/0/frontend-id = "49" (n0) /vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/console/0/backend-id = "0" (n0) /vm/7c239e06-1e76-1452-34c3-914ffc306aa3/device/console/0/backend = "/local/domain/0/backend/console/49/0" (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/on_xend_stop = "ignore"   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/pool_name = "Pool-0"   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/shadow_memory = "0"   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/uuid = "7c239e06-1e76-1452-34c3-914ffc306aa3" (n0,r49)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/on_reboot = "restart"   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/start_time = "1326907193.96" (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/on_poweroff = "destroy"   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/bootloader_args = ""   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/on_xend_start = "ignore" (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/on_crash = "restart"   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/xend = ""   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/xend/restart_count = "0" (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/vcpus = "1"   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/vcpu_avail = "1"   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/bootloader = ""   (n0)
/vm/7c239e06-1e76-1452-34c3-914ffc306aa3/name = "centos"   (n0)



Sallanches Data Network (SDN)
Pour l'Internet des Internautes

Home | Main Index | Thread Index | Old Index