Using virt-manager to perform an install, select new to create a new vm. Select the first option, local install media. Then just select next, the second screen offers use cdrom or dvd or use ISO image. Selecting the first option, it then stops. Ensuring the dvd drive is properly mounted, it still doesn't proceed. Selecting next or forward, just triggers the error screen message An install media selection is required. It has been selected, but clearly not been registered. Happens every time, happens on my two instances of gentoo, one i386, and amd _64. The expected result ofcourse is to proceed to the next screen. genny ~ # emerge --info --- Invalid atom in /etc/portage/package.unmask: media-gfx/iscan x86 Portage 2.1.7.16 (default/linux/x86/10.0/desktop, gcc-4.3.4, glibc-2.11-r1, 2.6.31-gentoo-r6 i686) ================================================================= System uname: Linux-2.6.31-gentoo-r6-i686-Intel-R-_Core-TM-2_Duo_CPU_E6550_@_2.33GHz-with-gentoo-2.0.1 Timestamp of tree: Wed, 20 Jan 2010 00:15:02 +0000 app-shells/bash: 4.0_p35 dev-java/java-config: 2.1.10 dev-lang/python: 2.6.4, 3.1.1-r1 dev-util/cmake: 2.8.0 sys-apps/baselayout: 2.0.1 sys-apps/openrc: 0.6.0 sys-apps/sandbox: 2.2 sys-devel/autoconf: 2.13, 2.65 sys-devel/automake: 1.8.5-r4, 1.9.6-r2, 1.10.3, 1.11.1 sys-devel/binutils: 2.20 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.6b virtual/os-headers: 2.6.30-r1 ACCEPT_KEYWORDS="x86 ~x86" ACCEPT_LICENSE="* -@EULA dlj-1.1" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=core2 -fomit-frame-pointer -pipe -O2 -mno-tls-direct-seg-refs -ggdb" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/sandbox.d /etc/splash /etc/terminfo" CXXFLAGS="-march=core2 -fomit-frame-pointer -pipe -O2 -mno-tls-direct-seg-refs -ggdb" DISTDIR="/mnt/images/genny/distfiles" FEATURES="assume-digests buildpkg distlocks fixpackages news parallel-fetch protect-owned sandbox sfperms strict unmerge-logs unmerge-orphans userfetch" GENTOO_MIRRORS="ftp://ftp.swin.edu.au/gentoo/ ftp://mirror.pacific.net.au/linux/Gentoo ftp://mirror.isp.net.au/pub/gentoo/ http://mirror.isp.net.au/pub/gentoo/ http://mirror.averse.net/pub/gentoo/" LDFLAGS="-Wl,-O1" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.au.gentoo.org/gentoo-portage" USE="(-altivec) (-aqua) (-fixed-point) (-gallium) (-hardened) (-kdeprefix) (-libffi) (-multilib) (-n32) (-n64) (-ps3) (-selinux) (wide-unicode) X a52 aac acl acpi aio alsa apm armeb arts audiofile avi bash-completion berkdb bluetooth bmp bzip2 cairo cdparanoia cdr cli client%* consolekit corefonts cracklib cris crypt ctype cups cxx dba dbmaker dbus dga dri dts dv dvd dvdr dvdread eds emboss encode esd ethereal evo extras fam fbcon ffmpeg fftw fftw* firefox flac fortran ftp gdbm gif gnome gnutls gphoto gpm gstreamer gtk gtk%* gtk2 hal handbook i386 iconv imagemagick inifile java jpeg kde ladcca ldap libg++ libvirtd lm_sensors lxc mad mbox microblaze mikmod mime mips64 mips64el mipsel mmap mng modules mono mozilla mp3 mp4 mpeg msn mudflap mysql ncurses netapi network nls nptl nptlonly ogg openal opengl openmp oss pam pcre pdf perl png png%* pnp posix ppc64abi32 ppcemb ppds pppd python qdbm qt qt3support qt4 quicktime readline reflection ruby samba scanner sdl semantic-desktop server%* session sh4 sh4eb shared slp smbclient sndfile sockets source sparc32plus sparc64 spell spl sse sse2 ssl startup-notification svg svga sysfs tcpd theora threads thunar tiff truetype udev udev%* urandom usb v4l videos vorbis websockets wifi win32codecs x264 x86 x86_64 xcb* xine xinerama xml xml2 xorg xulrunner xv xvid zlib" ALSA_CARDS="snd_hda_intel" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" RUBY_TARGETS="ruby18" USERLAND="GNU" VIDEO_CARDS="fbdev i810 nv nvidia tdfx trident vesa vga" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
(In reply to comment #0) > Using virt-manager to perform an install, select new to create a new vm. > Select the first option, local install media. Then just select next, the > second screen offers > use cdrom or dvd or use ISO image. > > Selecting the first option, it then stops. > Ensuring the dvd drive is properly mounted, it still doesn't proceed. > Selecting next or forward, just triggers the error screen message > > An install media selection is required. > > It has been selected, but clearly not been registered. > > Happens every time, happens on my two instances of gentoo, one i386, and amd > _64. > > The expected result ofcourse is to proceed to the next screen. > > genny ~ # emerge --info > --- Invalid atom in /etc/portage/package.unmask: media-gfx/iscan x86 > Portage 2.1.7.16 (default/linux/x86/10.0/desktop, gcc-4.3.4, glibc-2.11-r1, > 2.6.31-gentoo-r6 i686) > ================================================================= > System uname: > Linux-2.6.31-gentoo-r6-i686-Intel-R-_Core-TM-2_Duo_CPU_E6550_@_2.33GHz-with-gentoo-2.0.1 > Timestamp of tree: Wed, 20 Jan 2010 00:15:02 +0000 > app-shells/bash: 4.0_p35 > dev-java/java-config: 2.1.10 > dev-lang/python: 2.6.4, 3.1.1-r1 > dev-util/cmake: 2.8.0 > sys-apps/baselayout: 2.0.1 > sys-apps/openrc: 0.6.0 > sys-apps/sandbox: 2.2 > sys-devel/autoconf: 2.13, 2.65 > sys-devel/automake: 1.8.5-r4, 1.9.6-r2, 1.10.3, 1.11.1 > sys-devel/binutils: 2.20 > sys-devel/gcc-config: 1.4.1 > sys-devel/libtool: 2.2.6b > virtual/os-headers: 2.6.30-r1 > ACCEPT_KEYWORDS="x86 ~x86" > ACCEPT_LICENSE="* -@EULA dlj-1.1" > CBUILD="i686-pc-linux-gnu" > CFLAGS="-march=core2 -fomit-frame-pointer -pipe -O2 -mno-tls-direct-seg-refs > -ggdb" > CHOST="i686-pc-linux-gnu" > CONFIG_PROTECT="/etc /usr/share/X11/xkb /usr/share/config" > CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ > /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/sandbox.d /etc/splash > /etc/terminfo" > CXXFLAGS="-march=core2 -fomit-frame-pointer -pipe -O2 -mno-tls-direct-seg-refs > -ggdb" > DISTDIR="/mnt/images/genny/distfiles" > FEATURES="assume-digests buildpkg distlocks fixpackages news parallel-fetch > protect-owned sandbox sfperms strict unmerge-logs unmerge-orphans userfetch" > GENTOO_MIRRORS="ftp://ftp.swin.edu.au/gentoo/ > ftp://mirror.pacific.net.au/linux/Gentoo ftp://mirror.isp.net.au/pub/gentoo/ > http://mirror.isp.net.au/pub/gentoo/ http://mirror.averse.net/pub/gentoo/" > LDFLAGS="-Wl,-O1" > MAKEOPTS="-j2" > PKGDIR="/usr/portage/packages" > PORTAGE_CONFIGROOT="/" > PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress > --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles > --exclude=/local --exclude=/packages" > PORTAGE_TMPDIR="/var/tmp" > PORTDIR="/usr/portage" > SYNC="rsync://rsync.au.gentoo.org/gentoo-portage" > USE="(-altivec) (-aqua) (-fixed-point) (-gallium) (-hardened) (-kdeprefix) > (-libffi) (-multilib) (-n32) (-n64) (-ps3) (-selinux) (wide-unicode) X a52 aac > acl acpi aio alsa apm armeb arts audiofile avi bash-completion berkdb bluetooth > bmp bzip2 cairo cdparanoia cdr cli client%* consolekit corefonts cracklib cris > crypt ctype cups cxx dba dbmaker dbus dga dri dts dv dvd dvdr dvdread eds > emboss encode esd ethereal evo extras fam fbcon ffmpeg fftw fftw* firefox flac > fortran ftp gdbm gif gnome gnutls gphoto gpm gstreamer gtk gtk%* gtk2 hal > handbook i386 iconv imagemagick inifile java jpeg kde ladcca ldap libg++ > libvirtd lm_sensors lxc mad mbox microblaze mikmod mime mips64 mips64el mipsel > mmap mng modules mono mozilla mp3 mp4 mpeg msn mudflap mysql ncurses netapi > network nls nptl nptlonly ogg openal opengl openmp oss pam pcre pdf perl png > png%* pnp posix ppc64abi32 ppcemb ppds pppd python qdbm qt qt3support qt4 > quicktime readline reflection ruby samba scanner sdl semantic-desktop server%* > session sh4 sh4eb shared slp smbclient sndfile sockets source sparc32plus > sparc64 spell spl sse sse2 ssl startup-notification svg svga sysfs tcpd theora > threads thunar tiff truetype udev udev%* urandom usb v4l videos vorbis > websockets wifi win32codecs x264 x86 x86_64 xcb* xine xinerama xml xml2 xorg > xulrunner xv xvid zlib" ALSA_CARDS="snd_hda_intel" ALSA_PCM_PLUGINS="adpcm alaw > asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa > lfloat linear meter mmap_emul mulaw multi null plug rate route share shm > softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon > authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile > authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate > dir disk_cache env expires ext_filter file_cache filter headers include info > log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling > status unique_id userdir usertrack vhost_alias" ELIBC="glibc" > INPUT_DEVICES="evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk > hd44780 lb216 lcdm001 mtxorb ncurses text" RUBY_TARGETS="ruby18" USERLAND="GNU" > VIDEO_CARDS="fbdev i810 nv nvidia tdfx trident vesa vga" > Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LANG, > LC_ALL, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, > PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY > On my gentoo 32, it has got past this point, so it occurs sometimes. Once past that point, at the last wizzard screen, under Advanced options, it fails to include a selection of paravirt or full virt. i.e. These options for Virt type are both greyed out. If the selection is made to finish, it creates the disk image, then presents the error message failed to install, (xend.err "Error creating domain: (22, 'Invalid argument')") Cannot make a selection of CD DVD drive to do an install As an adjunct, if the selection is made at the first screen of network install, I cannot find any way of nominating the cd / dvd drive as a network device despite following some suggested methods using ftp. How is it done to make the dvd a network device?
I hope this DOESN'T inconvenience, but I'm new at this. I had hoped to not make these repeat entries, but! The bug seems to be missing from searching, I'd think because it has status RESOLVED, which I didn't select. It hasn't been looked at yet. It seems I can change it, so I have, to re-open, which is the only one to sensibly pick. This virtinst just keeps missing. Being new I don't know if it warrants separate entries for each misfire, but it has too many. I'd like to get a response to this before making any more (possibly unwanted) entries, so I'll briefly add this. virtinst can't install via virt-manager. more examples,: -- selecting any type of install for qemu, it can't find the network, error bridge virbr0 doesn't exist package not installed when it is installed and the bridge does exist. Create new virtual networks and it can't find them, and selecting xen to do a network install, it actually succeeds in beginning a pxe network install, then falls over with ......... File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1097, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: Domain not found: xenUnifiedDomainLookupByName' I tried it a couple of times. virtinst just keeps missing. It works in SUSE, to a reasonable level. Let's get gentoo in the same league, please.
Oh, what the heck. Just a few more words. virtinst managed to succeed in an install of a fedora 12 with qemu, using entry to virtinst by the command line sudo virt-install --connect=qemu:///system -n fedora12 ..... -l http://ga14.files.bigpond.com:4040/fedora/linux/releases/12/Fedora/i386/os/ ... succeeded. equivalent entry for xen, option -v for paravirt, resulted in -connecting to net site, -downloading 2-3 items, -bailing out, claiming it couldn't find an image. It's clearly there in the tree, and qemu-kvm managed to find it ok. So, xen could be to blame, maybe.
ok, I have to back pedal. Cancel the comment re qemu-kvm not being able to have networking. Sure enough it was my setup, kernel was lacking. virtinst is ok if qemu kvm is selected via virt-manager. I didn't have a proper networking setup. I found a guide and fixed it. Deficits are only in place for xen related attempts as described. Can't find anything lacking in that area.
I'm not sure what goes on here. I've changed this again from resolved to which it was reset a few days ago, which it isn't, to re-opened again. I'm sure you're busy, awaiting a reply.
eeeh, did I say something wrong? Hello. I don't want to add if no-one reads.
(In reply to comment #5) > I'm not sure what goes on here. I've changed this again from resolved to which > it was reset a few days ago, which it isn't, to re-opened again. I'm sure > you're busy, awaiting a reply. > Just to clear your confusion. You resolved the bug yourself two times. https://bugs.gentoo.org/show_activity.cgi?id=305821
Can you distill this down into a specific test case to trigger the issue? Since the problem appears to be on the Xen side of things, bringing them on the ticket.
(In reply to comment #8) > Can you distill this down into a specific test case to trigger the issue? Since > the problem appears to be on the Xen side of things, bringing them on the > ticket. Yes, I'm afraid I've confused the issue by so many entries. Using virt-manager to install a new xen vm, select the first option, local install media. This is the first wizzard screen. Then move to the second wizzard screen, select the first check box, use CDROM OR DVD. (Initially this was my bug, but it resolved, leading to the other entries.) This resolved, but it then faulted in a different way - Progress to the last wizzard screen, under Advanced options, it fails to offer a selection of paravirt or full virt. i.e. There is a drop box or list box for Virt type. The entries paravirt and full virt are both greyed out. If the selection is made to finish, it creates the disk image, then presents the error message failed to install, (xend.err "Error creating domain: (22, 'Invalid argument')") The expected result is to be able to select paravirt or full virt to install. Generally under xen the full virt option need be made, but both are greyed out. So this is the essence of the bug. As my previous comments indicate, I had other faults occur, which I felt inclined to add. Overall I could not install a new vm at all with virtinst in xen, but they should each be different bugs. Should I create them? The problems occur only xen, so the fault(s) may come from xen??!
> > Generally under xen the full virt option need be made, but both are greyed out. > So this is the essence of the bug. > > As my previous comments indicate, I had other faults occur, which I felt > inclined to add. Overall I could not install a new vm at all with virtinst in > xen, but they should each be different bugs. Should I create them? > > The problems occur only xen, so the fault(s) may come from xen??! > I was hoping for a reply to this well before now. I've found the likely source is not virtinst, but virt-manager. app-emulation/virt-manager Latest version available: 0.8.2 Latest version installed: 0.8.2 I tried out the similar packages in debian, squeeze amd lenny. I found the SAME BUG in all of squeeze and gentoo and fedora12. I submitted it to debian and just made a find. If interested, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579146 for the whole thing. I basically made a similar description to this, sort of. Working on different versions between them I found the following; I'll just cite snippets of the description from the debian submission. I'm not going through it all again having already mapped it out. ............................ I've likely solved this by accident. The culprit is not libvirt, it is virt-manager. I sparked up the xen live cd for the purpose of resolving the first one I submitted, losing contact with the console. My intention was to upgrade the libvirt package in the live cdrom to prove a point re consoles. I installed, used virt-manager, expecting to get the console issue attempting to prove that the cause of that is the 64 arch. The issue is i.e. There is a drop box or list box for Virt type. The entries paravirt and full virt are both greyed out. So, the versions in the squeeze are (were) libvirt 0.8.0-1 also for libvirt-bin. I took the package directly from my lenny 64 and installed into this 64 squeeze, version 0.6.0-6. After a reboot, could connect to xen, and use it. It DOESN'T produce the issue. It can BEGIN the install. In typical fashion, it faultered again anyway So i simply downgraded virt-manager to 0.6.0-6. The cdrom install was made possible. The next fault is separate again. My libvirt is * app-emulation/virt-manager Latest version available: 0.8.2 Latest version installed: 0.8.2 and virtinst is already stated. So it looks as if virt-manager is the source. I don't know how to find and fix it.
(In reply to comment #11) > > > > Generally under xen the full virt option need be made, but both are greyed out. > > So this is the essence of the bug. > > > > As my previous comments indicate, I had other faults occur, which I felt > > inclined to add. Overall I could not install a new vm at all with virtinst in > > xen, but they should each be different bugs. Should I create them? > > > > The problems occur only xen, so the fault(s) may come from xen??! > > > > I was hoping for a reply to this well before now. I've found the likely source > is not virtinst, but virt-manager. > > app-emulation/virt-manager > Latest version available: 0.8.2 > Latest version installed: 0.8.2 > virt-manager-0.8.3 has been available in the tree since Feb 9th and virt-manager-0.8.4 has been available in the tree since April 28th. The former was available long before you posted this, I would make sure you're testing against the latest versions as your bug may have been solved by upstream. Unfortunately I've got no XEN setups or any knowledge about XEN as I've never used it. So we're going to have to wait for either upstream to magically fix it, or the XEN herd to wake up and help.
> > virt-manager-0.8.3 has been available in the tree since Feb 9th and > virt-manager-0.8.4 has been available in the tree since April 28th. The former > was available long before you posted this, I would make sure you're testing > against the latest versions as your bug may have been solved by upstream. > > Unfortunately I've got no XEN setups or any knowledge about XEN as I've never > used it. So we're going to have to wait for either upstream to magically fix > it, or the XEN herd to wake up and help. > Thanks for answering, but this is bleak news. The issue is not with xen, it's with libvirt and virtinst and virt-manager, all python packages. I'm new to this bug submission, so I don't know much about your structure and such. I can report that the newest versions are equally broken. Note that the problem is also in place with the pxe choice at the first stage. These later versions really seem to have taken a real backward step or three. The choice of a network install yields my other bug report, one of two others. Between the two, virt-manager is totally crippled re installing vms, explicit to xen. It seems it can manage established ones, but fails in all these ways to install, all those options just go to waste and don't work. kvm qemu fair much better. well they miss on network installs, but I think they may not be compatible. I found this rectified by revering to the cited version. Can I acquire the now outdated version 0.6 to test and confirm this? Portage ofcourse just removed prior versions. Is it still around and procurable? These newer versions you cite clearly miss it, There is one possibility, the first screen of a new vm offers a warning, Host does not appear to support hardware virtualisation. Install options may be limited. It must be looking at the kernel. My impression is the warning is unfounded. The kernel manages qemu ok, remembering a xen kernel supports qemu but shuns kvm. I can only test kvm in a regular kernel environment. The same kernel config is in place running xen in two other distros, and fairs ok, including the one where I discovered the problem was with virt-manager. Anyway, considering your limitations you cited, is it worth giving you more descriptions? I've procured a python debugger to attack these issues, I first have to figure how to use it. I shall attack it for may own interest anyway. Will it be any benefit submitting findings from it? You can always pass them on. Can you inform me just what upstream is please?
(In reply to comment #13) > > Can you inform me just what upstream is please? > I have some info. This is the first bug that I submitted and the last to get a handle on. It's still a bug and it still needs fixing, but I found more about it and I have a work around. It's very easy to implement, and gives gentoo virt-manager I think full functioning. The problem is that the options at the very last step are greyed out.This gave me the impression that the options were with-held, shouldn't be so, and made the choice of a cdrom dvd install unworkable. If you click return and let it attempt, it does return an erroneous error and stops from installing. I ran virt-manager through a console debugger and also cross-referenced the cdrom install with a direct install to virt-install and pinpointed the error it produces. Now it may perhaps be specific to my hardware but the same mistake occured in squeeze and fedora. I acquired xml dumps from libvirt of the faulty virt-manager install and did a direct comparison with the xml dump of an effective cdrom install from libvirt directly. combined with the debug output, I narrowed it down to a simple virtual hardware selection made by the virt-manager / virt-install duo. No need to include the dumps, but it came down to this line <sound model='es1370'/> I transposed every other element of the healthy into the faulty xml definition of the vm, and this was the cause of it. The sound choice didn't work, got hald associated errors everywhere pointing the finger at a virtual hardware device. Remove the sound hardware selection, compromise and do without it, and it becomes an effective install. So, at the last step, check the checkbox to check and finalise the content of the proposed install. This is a wise inclusion, a back door for virt-manager. It brings up the virt-manager vnc console that virt-manager creates. You can select the Details tab of the console which lists all the essential elements to define the vm. Remove the sound choice, apply and select install. So for the sake of a sound card selection, the whole choice of a cdrom dvd install was hijacked. It's quite likely not everyone else has this occur, otherwise someone should have made a bug of it already. I don't have other machines to test it on. virt-install has one associated glitch. It reports that you can't do a para install on the cdrom, which is rubbish. Fedora, centos and Suse are setup to do so, debian not. This is something that should be rectified, both virt-manager's status and also debian's setup. Using virt-manager as described, despite the selection being greyed out, virt-manager actually makes a default choice of hvm type, concurring with the wrong standing in virt-install. Perhaps the most common choice is full virt, but that is no cause to block the paravirt choice. Pass this on if you will. This is readily testable, if someone could do it. Help polish this and see if it can be confirmed or not.
I would strongly suggest you report these as bugs to the virtinst and virt-manager maintainers then. http://www.virt-manager.org/page/BugReporting
(In reply to comment #15) > I would strongly suggest you report these as bugs to the virtinst and > virt-manager maintainers then. > > http://www.virt-manager.org/page/BugReporting > I already have, and I haven't heard from them either. https://bugzilla.redhat.com/show_bug.cgi?id=585460 in which I reference this entry. Since you clearly declare it a bug, I'll re-open it, but I am new. Reclassify if you will
According to Cole, he worked with you and fixed these issues in 0.500.4 and gave them some polish for the 0.500.5 release which I just added to the tree. Closing this issue out.
(In reply to comment #17) > According to Cole, he worked with you and fixed these issues in 0.500.4 and > gave them some polish for the 0.500.5 release which I just added to the tree. > Closing this issue out. > well that didn't take long, 8 months! Could you tell me what is up with xen. Where do you procure the latest sources? It was once xenbits but I get no response to the xnebits xensource site. Is it citrix now? Just what has happened to xen development and releases???
(In reply to comment #18) > (In reply to comment #17) > > According to Cole, he worked with you and fixed these issues in 0.500.4 and > > gave them some polish for the 0.500.5 release which I just added to the tree. > > Closing this issue out. > > > > well that didn't take long, 8 months! Could you tell me what is up with xen. > Where do you procure the latest sources? It was once xenbits but I get no > response to the xnebits xensource site. Is it citrix now? Just what has > happened to xen development and releases??? > According to Cole, he resolved this with you a long time ago. I was just delayed in closing the ticket out. I've never used Xen and no one on the Gentoo team that maintains these sets of packages uses it. We provide support for Xen since the package provides it and we rely on user feedback to fix potential issues. So I couldn't tell you how to get Xen or configure it or anything about it.
> get Xen or configure it or anything about it. > ok, that's fine, let me worry about running and configuring. As a developer in gentoo, what you do do is acquire xen source. When I was using it extensively, I also acquired the latest xen source from xenbits/xensource using mercurial. Retrying, it all seems to have been withdrawn. What I was asking is who and where is xen now developed and released. i.e. where & what is upstream. I find citrix has "acquired" xen and the sites that supported xen now seem half shutdown. I tried unmerging xen then some other system packages wanted to use xen modules so I tried emerging it, and it kept faultering. Actually xen-tools emerged but xen (hypervisor) couldn't. I'm not breaking my neck to submit bugs like I was months ago but I can if it's warranted. I can give you the output of the line that it fails. The unpacked xen source is fairly different in structure to the xensource I last acquired via mercurial. Have you had xen build failures?
