FC6, xen installed, latest updates as of five minutes ago. ASUS
P5LD2-R2.0 board, Intel 6600 CPU, 2GB RAM, 1.5TB disk.
PAE on, virtualization on. xend running, "xm list" works, shows one
domain.
Install of any fully virtualized o/s fails. Sample output:
Would you like a fully virtualized guest (yes or no)? This will allow
you to run unmodified operating systems. yes
How much RAM should be allocated (in megabytes)? 256
Would you like to enable graphics support? (yes or no) no
Starting install...
libvir: Xen Daemon error : GET operation failed: No such domain OpenBSD-4.0
libvir: Xen Daemon error : POST operation failed: (xend.err ''Error
creating domain: Disk image does not exist:
/home/davidsen/Virtual_Machines/OpenBSD-4.0a'')
Failed to create domain OpenBSD-4.0
Traceback (most recent call last):
File "/usr/sbin/xenguest-install", line 396, in ?
main()
File "/usr/sbin/xenguest-install", line 360, in main
dom = guest.start_install(conscb)
File "/usr/lib/python2.4/site-packages/virtinst/XenGuest.py", line
355, in start_install
self.domain = self.conn.createLinux(cxml, 0)
File "/usr/lib/python2.4/site-packages/libvirt.py", line 249, in
createLinux
if ret is None:raise libvirtError(''virDomainCreateLinux()
failed'')
libvirt.libvirtError: virDomainCreateLinux() failed
Tried from CD, same error. Tried from xenguest-install and virt-manager,
same error.
VMware under Windows installs everything, but that''s not where I need
it
installed.
Any thoughts?
Bill Davidsen wrote:> FC6, xen installed, latest updates as of five minutes ago. ASUS > P5LD2-R2.0 board, Intel 6600 CPU, 2GB RAM, 1.5TB disk. > PAE on, virtualization on. xend running, "xm list" works, shows one domain. > > > Install of any fully virtualized o/s fails. Sample output: > Would you like a fully virtualized guest (yes or no)? This will allow > you to run unmodified operating systems. yes > How much RAM should be allocated (in megabytes)? 256 > Would you like to enable graphics support? (yes or no) no > > > Starting install... > libvir: Xen Daemon error : GET operation failed: No such domain OpenBSD-4.0 > libvir: Xen Daemon error : POST operation failed: (xend.err ''Error > creating domain: Disk image does not exist: > /home/davidsen/Virtual_Machines/OpenBSD-4.0a'')NOTE: yes it does...> Failed to create domain OpenBSD-4.0 > Traceback (most recent call last): > File "/usr/sbin/xenguest-install", line 396, in ? > main() > File "/usr/sbin/xenguest-install", line 360, in main > dom = guest.start_install(conscb) > File "/usr/lib/python2.4/site-packages/virtinst/XenGuest.py", line 355, > in start_install > self.domain = self.conn.createLinux(cxml, 0) > File "/usr/lib/python2.4/site-packages/libvirt.py", line 249, in > createLinux > if ret is None:raise libvirtError(''virDomainCreateLinux() failed'') > libvirt.libvirtError: virDomainCreateLinux() failed > > Tried from CD, same error. Tried from xenguest-install and virt-manager, > same error. > VMware under Windows installs everything, but that''s not where I need it > installed. > > Any thoughts? >Seems to work with qemu, for what that''s worth. -- Bill Davidsen <davidsen@tmr.com> Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a normal user and is setuid root, with the "vi" line edit mode selected, and the character set is "big5," an off-by-one errors occurs during wildcard (glob) expansion.
Paul Wouters wrote:> On Fri, 17 Nov 2006, Bill Davidsen wrote: > > >> FC6, xen installed, latest updates as of five minutes ago. ASUS P5LD2-R2.0 >> board, Intel 6600 CPU, 2GB RAM, 1.5TB disk. >> PAE on, virtualization on. xend running, "xm list" works, shows one domain. >> > > does not mention "selinux disabled" >If that''s needed it somewhat conflicts with the idea for running things in virtual machines for added security :-( I thought that was a non-issue with 2.6.18, but I may be wrong.> >> libvir: Xen Daemon error : POST operation failed: (xend.err ''Error creating >> domain: Disk image does not exist: >> /home/davidsen/Virtual_Machines/OpenBSD-4.0a'') >> > > And that''s not in /xen/ >Hopefully doesn''t have to be. Having all projects in a single place just begs for name clash and visibility exposure issues. The browse didn''t have any trouble finding the file, at minimum probably a bug if it allows me to select a file I can''t use.> I think that used to be an issue with selinux. not sure if it still is. >Thanks for the ideas, I was hoping to use xen instead of VMware, but when I did a project a few years ago I don''t recall it being particularly inflexible. I''ll try just moving the disk image file and running with that. Again, many thanks. -- bill davidsen <davidsen@tmr.com> CTO TMR Associates, Inc Doing interesting things with small computers since 1979
On Fri, Nov 17, 2006 at 05:51:24PM -0500, Bill Davidsen wrote:> FC6, xen installed, latest updates as of five minutes ago. ASUS > P5LD2-R2.0 board, Intel 6600 CPU, 2GB RAM, 1.5TB disk. > PAE on, virtualization on. xend running, "xm list" works, shows one domain. > > > Install of any fully virtualized o/s fails. Sample output: > Would you like a fully virtualized guest (yes or no)? This will allow > you to run unmodified operating systems. yes > How much RAM should be allocated (in megabytes)? 256 > Would you like to enable graphics support? (yes or no) no > > > Starting install... > libvir: Xen Daemon error : GET operation failed: No such domain OpenBSD-4.0 > libvir: Xen Daemon error : POST operation failed: (xend.err ''Error > creating domain: Disk image does not exist: > /home/davidsen/Virtual_Machines/OpenBSD-4.0a'')In FC6 GA you have to make sure the file for the disk was under /xen to be labelled correctly. In rawhide (and the latest FC6 policy) we''re moving to /var/lib/xen/images. This is consistent with the directory used on Suse, and what the next version of XenD will enforce. To double check what directory is setup for the SELinux policy you can run semanage fcontext -l | grep xen_image_t If you don''t have space under /var/lib/xen/images, then either mount a new volume there, or bind that dir to a location which has extra space, eg mount --bind /some/dir/with/big/disk /var/lib/xen/images If you really really don''t want to use /var/lib/xen/images at all, then you can define a new location in the SELinux policy using: semanage fcontext -a -f "" -t xen_image_t ''/some/directory(/.*)?'' Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
Daniel P. Berrange wrote:> On Fri, Nov 17, 2006 at 05:51:24PM -0500, Bill Davidsen wrote: >> FC6, xen installed, latest updates as of five minutes ago. ASUS >> P5LD2-R2.0 board, Intel 6600 CPU, 2GB RAM, 1.5TB disk. >> PAE on, virtualization on. xend running, "xm list" works, shows one domain. >> >> >> Install of any fully virtualized o/s fails. Sample output: >> Would you like a fully virtualized guest (yes or no)? This will allow >> you to run unmodified operating systems. yes >> How much RAM should be allocated (in megabytes)? 256 >> Would you like to enable graphics support? (yes or no) no >> >> >> Starting install... >> libvir: Xen Daemon error : GET operation failed: No such domain OpenBSD-4.0 >> libvir: Xen Daemon error : POST operation failed: (xend.err ''Error >> creating domain: Disk image does not exist: >> /home/davidsen/Virtual_Machines/OpenBSD-4.0a'') > > In FC6 GA you have to make sure the file for the disk was under /xen > to be labelled correctly. In rawhide (and the latest FC6 policy) > we''re moving to /var/lib/xen/images. This is consistent with the > directory used on Suse, and what the next version of XenD will > enforce. To double check what directory is setup for the SELinux > policy you can run > > semanage fcontext -l | grep xen_image_t > > If you don''t have space under /var/lib/xen/images, then either > mount a new volume there, or bind that dir to a location which > has extra space, eg > > mount --bind /some/dir/with/big/disk /var/lib/xen/images > > If you really really don''t want to use /var/lib/xen/images at all, > then you can define a new location in the SELinux policy using: > > semanage fcontext -a -f "" -t xen_image_t ''/some/directory(/.*)?'' >This sounds like the missing piece, I can check where the current install wants it, and then get it there in one way or another. I''ll try it some time over the long weekend and report back. Thanks much, I suspect this was the hint I needed. -- bill davidsen <davidsen@tmr.com> CTO TMR Associates, Inc Doing interesting things with small computers since 1979
Bill Davidsen wrote:> Daniel P. Berrange wrote: >> On Fri, Nov 17, 2006 at 05:51:24PM -0500, Bill Davidsen wrote: >>> FC6, xen installed, latest updates as of five minutes ago. ASUS >>> P5LD2-R2.0 board, Intel 6600 CPU, 2GB RAM, 1.5TB disk. >>> PAE on, virtualization on. xend running, "xm list" works, shows one >>> domain. >>> >>> >>> Install of any fully virtualized o/s fails. Sample output: >>> Would you like a fully virtualized guest (yes or no)? This will >>> allow you to run unmodified operating systems. yes >>> How much RAM should be allocated (in megabytes)? 256 >>> Would you like to enable graphics support? (yes or no) no >>> >>> >>> Starting install... >>> libvir: Xen Daemon error : GET operation failed: No such domain >>> OpenBSD-4.0 >>> libvir: Xen Daemon error : POST operation failed: (xend.err ''Error >>> creating domain: Disk image does not exist: >>> /home/davidsen/Virtual_Machines/OpenBSD-4.0a'') >> >> In FC6 GA you have to make sure the file for the disk was under /xen >> to be labelled correctly. In rawhide (and the latest FC6 policy) >> we''re moving to /var/lib/xen/images. This is consistent with the >> directory used on Suse, and what the next version of XenD will >> enforce. To double check what directory is setup for the SELinux >> policy you can run >> >> semanage fcontext -l | grep xen_image_t >> >> If you don''t have space under /var/lib/xen/images, then either >> mount a new volume there, or bind that dir to a location which >> has extra space, eg >> >> mount --bind /some/dir/with/big/disk /var/lib/xen/images >> >> If you really really don''t want to use /var/lib/xen/images at all, >> then you can define a new location in the SELinux policy using: >> >> semanage fcontext -a -f "" -t xen_image_t ''/some/directory(/.*)?'' >> > This sounds like the missing piece, I can check where the current > install wants it, and then get it there in one way or another. I''ll try > it some time over the long weekend and report back. > > Thanks much, I suspect this was the hint I needed. >Wasn''t, unfortunately. I still get told both the ISO and the file don''t exist, even though they clearly do. And after attempting a create the system eats the root filesystem so I have to reinstall. Makes for slow testing. - works with Windows and VMware, I think that lets hardware out - runs memtest86+ for hours (and fails every time I do an install). - checked with semanage, /xen and /var/lib/xen/images are listed. Can I safely resize the Dom0 down to get room to do an install? Is it related to running LVM (don''t usually). I have a ton of captured logs and such, didn''t want to post or load for www unless someone wants to see them. Same error as subject, log shows "file does not exist" even though the install process created the image file. -- Bill Davidsen He was a full-time professional cat, not some moonlighting ferret or weasel. He knew about these things.