Hi, Creating a HVM guest for netbsd 3.1 on snv_101b with the command: virt-install -n nbsd31 --hvm -r 512 --vnc \ -f /export/home/admin/domains/nbsd31.img -s 10 \ --cdrom /export/home/admin/domains/i386cd-3.1.iso \ --no-graphics results in xend-debug.log messages at domain creation: Failed allocation for dom 7: 1 extents of order 9 ERROR Internal error: Cannot allocate more 2M pages for HVM guest. (16 = Device busy) The hvm boots from the cdrom image, and the installation begins with a disk format. The kernel crashes as disk write initates. Adding the --livecd option did not help either. Same problem occurs if zpool is used. This was tried with the 64 and 32 bit Xvm hypervisor. Installation of opensolaris i86pc as a hvm fails in a similar way too. any ideas ? Thanks, --anup
Anup Patil wrote:> Failed allocation for dom 7: 1 extents of order 9 > ERROR Internal error: Cannot allocate more 2M pages for HVM guest. > (16 = Device busy)I don''t think these are relevant.> The hvm boots from the cdrom image, and the installation begins with a > disk format. The kernel crashes as disk write initates. > > Adding the --livecd option did not help either. > > Same problem occurs if zpool is used. This was tried with the 64 and 32 > bit Xvm hypervisor.Did you mean you tried it on a zvol, or on a zfs-backed raw file?> Installation of opensolaris i86pc as a hvm fails in a similar way too. > > any ideas ?Try using a vmdk disk. Use name.vmdk for the disk name and virt-install will create a vmdk (it uses the filename extension to determine disk type). - R
Dave E pointed out that you may also be hitting this bug: 6782943 HVM PIO instruction emulation does not deal with a zero REP count Which seems likely, as your domain is crashing at its first I/O to disk. Russ Blaine wrote:> Anup Patil wrote: >> Failed allocation for dom 7: 1 extents of order 9 >> ERROR Internal error: Cannot allocate more 2M pages for HVM guest. >> (16 = Device busy) > > I don''t think these are relevant. > >> The hvm boots from the cdrom image, and the installation begins with a >> disk format. The kernel crashes as disk write initates. >> >> Adding the --livecd option did not help either. >> >> Same problem occurs if zpool is used. This was tried with the 64 and 32 >> bit Xvm hypervisor. > > Did you mean you tried it on a zvol, or on a zfs-backed raw file? > >> Installation of opensolaris i86pc as a hvm fails in a similar way too. >> >> any ideas ? > > Try using a vmdk disk. Use name.vmdk for the disk name and virt-install > will create a vmdk (it uses the filename extension to determine disk type). > > - R > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Anup Patil wrote:> Hi, > > Creating a HVM guest for netbsd 3.1 on snv_101b with the command: > virt-install -n nbsd31 --hvm -r 512 --vnc \ > -f /export/home/admin/domains/nbsd31.img -s 10 \ > --cdrom /export/home/admin/domains/i386cd-3.1.iso \ > --no-graphicsI''ve done some tests with NetBSD 5.0_BETA as a HVM domain. There are some issues: * NetBSD after 3.x patches some kernel functions to contain more optimal code for the architecture. That''s nothing particularly special (Solaris does that too), but it uses the WP bit in cr0 to disable write protection while doing it. Xen doesn''t like that, and it fails. I have a patch for that which I''ll get into the NetBSD tree. * With slightly older qemu versions, NetBSD hangs during the floppy probe. You might have to use boot -c and "disable fdc0" to get around that. * There''s a problem with Xen 3.1.x not correctly emulating repeated I/O instructions when the repeat count is 0. Not a problem for most operating systems, but it can happen under NetBSD. * Lastly, there seems to be some other issue, causing bad pagefaults during install. Again, this is specific to NetBSD (and possibly the other BSDs), but not triggered at all by Windows, Solaris or Linux HVM domains. I tried it under Xen 3.3, and the problem went away; I successfully installed both 32 and 64bit NetBSD 5.0 HVM domains. If you want to run NetBSD under xVM, for now I''d suggest using a PV NetBSD kernel (NetBSD 5.0_BETA is probably the best option here). - Frank