Am 02.10.2012 11:42, schrieb Fabio Fantoni:> Dom0 is wheezy 64 bit, kernel 3.2.23-1 from debian repository, xen > 4.2.0 compiled from source > > When I try to install Precise domU PV with this xl configuration file: > -------------------------------------------- > PRECISE.cfg > ---------------- > name=''PRECISE'' > memory=1024 > vcpus=2 > disk=[''/mnt/vm/disks/PRECISE.disk1.xm,raw,xvda1,rw'', > ''/mnt/vm/disks/PRECISE.disk2.xm,raw,xvda2,rw''] > #disk=[''/mnt/vm/disks/PRECISE.disk1.xm,raw,xvda,rw''] > vif=[''bridge=xenbr0''] > vfb=[''vnc=1,vncunused=1,vnclisten=0.0.0.0,keymap=it''] > xen_platform_pci=1 > #bootloader=''pygrub'' > #kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz" > #extra = "(hd0,0)/grub/grub.cfg" > # Only for installation > kernel="/boot/domu/precise/vmlinuz" > ramdisk="/boot/domu/precise/initrd.gz" > extra = "debian-installer/exit/always_halt=true -- quiet console=hvc0" > -------------------------------------------- > > The vmlinux and initrd take from here: > http://archive.ubuntu.com/ubuntu/dists/precise-updates/main/installer-amd64/current/images/netboot/xen/ > > > xl create /etc/xen/PRECISE.cfg > Parsing config from /etc/xen/PRECISE.cfg > libxl: error: libxl_device.c:858:device_backend_callback: unable to > disconnect device with path /local/domain/0/backend/vbd/2/51713 > libxl: error: libxl_device.c:858:device_backend_callback: unable to > disconnect device with path /local/domain/0/backend/vbd/2/51714 > libxl: error: libxl_create.c:933:domcreate_launch_dm: unable to add > disk devices > libxl: error: libxl_device.c:858:device_backend_callback: unable to > disconnect device with path /local/domain/0/backend/vbd/2/51713 > libxl: error: libxl_blktap2.c:73:libxl__device_destroy_tapdisk: Unable > to find type aio disk /mnt/vm/disks/PRECISE.disk1.xm: No such file or > directory > libxl: error: libxl_device.c:858:device_backend_callback: unable to > disconnect device with path /local/domain/0/backend/vbd/2/51714 > libxl: error: libxl.c:1465:devices_destroy_cb: libxl__devices_destroy > failed for 2 > > /mnt/vm/disks/PRECISE.disk1.xm exist, domU hvm with raw disks works > > Is xen bug, kernel bug or my error? > Thanks for any reply > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-develHello, I think that the raw parameter isn''t needed and is the reason for the device connecting error. Another way to install the guest would be to use debootstrap. This definitly works. Best Regards _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Am 02.10.2012 12:06, schrieb Fabio Fantoni:> Il 02/10/2012 11:58, Lukas Laukamp ha scritto: >> Am 02.10.2012 11:42, schrieb Fabio Fantoni: >>> Dom0 is wheezy 64 bit, kernel 3.2.23-1 from debian repository, xen >>> 4.2.0 compiled from source >>> >>> When I try to install Precise domU PV with this xl configuration file: >>> -------------------------------------------- >>> PRECISE.cfg >>> ---------------- >>> name=''PRECISE'' >>> memory=1024 >>> vcpus=2 >>> disk=[''/mnt/vm/disks/PRECISE.disk1.xm,raw,xvda1,rw'', >>> ''/mnt/vm/disks/PRECISE.disk2.xm,raw,xvda2,rw''] >>> #disk=[''/mnt/vm/disks/PRECISE.disk1.xm,raw,xvda,rw''] >>> vif=[''bridge=xenbr0''] >>> vfb=[''vnc=1,vncunused=1,vnclisten=0.0.0.0,keymap=it''] >>> xen_platform_pci=1 >>> #bootloader=''pygrub'' >>> #kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz" >>> #extra = "(hd0,0)/grub/grub.cfg" >>> # Only for installation >>> kernel="/boot/domu/precise/vmlinuz" >>> ramdisk="/boot/domu/precise/initrd.gz" >>> extra = "debian-installer/exit/always_halt=true -- quiet console=hvc0" >>> -------------------------------------------- >>> >>> The vmlinux and initrd take from here: >>> http://archive.ubuntu.com/ubuntu/dists/precise-updates/main/installer-amd64/current/images/netboot/xen/ >>> >>> >>> xl create /etc/xen/PRECISE.cfg >>> Parsing config from /etc/xen/PRECISE.cfg >>> libxl: error: libxl_device.c:858:device_backend_callback: unable to >>> disconnect device with path /local/domain/0/backend/vbd/2/51713 >>> libxl: error: libxl_device.c:858:device_backend_callback: unable to >>> disconnect device with path /local/domain/0/backend/vbd/2/51714 >>> libxl: error: libxl_create.c:933:domcreate_launch_dm: unable to add >>> disk devices >>> libxl: error: libxl_device.c:858:device_backend_callback: unable to >>> disconnect device with path /local/domain/0/backend/vbd/2/51713 >>> libxl: error: libxl_blktap2.c:73:libxl__device_destroy_tapdisk: >>> Unable to find type aio disk /mnt/vm/disks/PRECISE.disk1.xm: No such >>> file or directory >>> libxl: error: libxl_device.c:858:device_backend_callback: unable to >>> disconnect device with path /local/domain/0/backend/vbd/2/51714 >>> libxl: error: libxl.c:1465:devices_destroy_cb: >>> libxl__devices_destroy failed for 2 >>> >>> /mnt/vm/disks/PRECISE.disk1.xm exist, domU hvm with raw disks works >>> >>> Is xen bug, kernel bug or my error? >>> Thanks for any reply >>> >>> >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xen.org >>> http://lists.xen.org/xen-devel >> >> Hello, >> >> I think that the raw parameter isn''t needed and is the reason for the >> device connecting error. Another way to install the guest would be to >> use debootstrap. This definitly works. >> >> Best Regards >> >> Nessun virus nel messaggio. >> Controllato da AVG - www.avg.com <http://www.avg.com> >> Versione: 2012.0.2221 / Database dei virus: 2441/5303 - Data di >> rilascio: 01/10/2012 >> > Format seem necessary or give this error: > /etc/xen/PRECISE.cfg: config parsing error in disk specification: > unknown value for format: near `xvda1'' in > `/mnt/vm/disks/PRECISE.disk1.xm,xvda1,rw'' > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-develHello, do you also have tried to install the guest with debootstrap? Best Regards _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Wed, Oct 3, 2012 at 9:26 AM, Fabio Fantoni <fantonifabio@tiscali.it> wrote:> ----------------------------------------------------------------------------------------------- > /var/log/xen/bootloader.9.log > ----------------------------------------------------------------------------------------------- > Traceback (most recent call last): > File "/usr/lib/xen/bin/pygrub", line 20, in <module> > import xen.lowlevel.xc > ImportError: No module named xen.lowlevel.xc > -----------------------------------------------------------------------------------------------I haven''t looked at the rest of this thread in detail; but this kind of error is typically because of a bug with how debian''s python installer places binaries if it''s given a "--prefix" argument. But it seems like if the bootloader was failing, it should have a different set of error messages. Can you try the attached patch to see if it changes anything? -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel