Koan virt install hanging

Hey,

Happy New Years!

 I am having an issue with doing a koan virt install.  I am trying to
build a Centos5.1 Xen VM and during the initial boot it hangs at the
same spot every time.  I am using Cobbler version 0.6.4-2 and Koan
version 0.6.3-3.  Below is the output from the install during the boot
where it hangs.  Can some one help direct me on what might be my
problem?

Regards,
Jason Hartley

Output:
[root <at> hydra cobbler]# koan --virt --system=sirrush --server=hydra
--virt-type=xenpv
- using kickstart from cobbler:
http://hydra.troy.3dogs.us/cblr/kickstarts_sys/sirrush/ks.cfg
libvirt_qemud (pid 3551) is running...
downloading initrd initrd.img to /var/lib/xen/initrd.img
url=http://hydra/cobbler/images/centos5.1-xen-i386/initrd.img
- using kickstart from cobbler:
http://hydra/cobbler/images/centos5.1-xen-i386/initrd.img
downloading kernel vmlinuz to /var/lib/xen/vmlinuz
url=http://hydra/cobbler/images/centos5.1-xen-i386/vmlinuz
- using kickstart from cobbler:
http://hydra/cobbler/images/centos5.1-xen-i386/vmlinuz
use virt-manager or reconnect with virsh console sirrush
[root <at> hydra cobbler]#  xm console sirrush

Re: cobbler: import of x86_64 repo creates i386 distro

Eugene Ventimiglia wrote:
> I'm running:
>
> cobbler import
> --path=/mnt/os-install/exported/media/Linux/RH-4.0-ES-U4-AMD64/
> --name=rhel4
>
> and cobbler list reports:
>
> ...
> distro rhel4-i386
>    profile rhel4-i386
>
> _______________________________________________
> et-mgmt-tools mailing list
> et-mgmt-tools@...
> https://www.redhat.com/mailman/listinfo/et-mgmt-tools
>   
It sort of looks like a bug, but it isn't.  Cobbler determines the 
"arch" bits based on the paths you import.    As the standard 
rsync/build trees (well, RHEL really doesn't have them -- Fedora and 
RHEL derivatives do), typically say x86_64 or i386 in them, it uses the 
presense of these tokens in the part to ID the distro.

If you are importing from a DVD, this shouldn't happen.

Basically the names don't mean anything, so you can just do the 
following and will be fine:

cobbler profile rename --name=rhel4-i386 --newname=rhel4-x86_64 --arch=x86

Re: Koan virt install hanging

Jason Hartley wrote:
> Hey,
>
> Happy New Years!
>
>  I am having an issue with doing a koan virt install.  I am trying to
> build a Centos5.1 Xen VM and during the initial boot it hangs at the
> same spot every time.  I am using Cobbler version 0.6.4-2 and Koan
> version 0.6.3-3.  Below is the output from the install during the boot
> where it hangs.  Can some one help direct me on what might be my
> problem?
>
>   
I think I know what is going on.

It's not hanging, what is happening is that the virtualized console no 
longer becomes useful once the VNC graphics mode engages -- in other 
words, you should be able to watch the rest of the install with 
virt-manager.

Older versions of koan had a flag to disable VNC support, but this was 
missing in recent versions (because I was not aware of the virt console 
issue).  In newer versions of koan (such as the test builds... 
http://cobbler.et.redhat.com/download/testing) there is once again a 
--nogfx flag.

When this flag is used, the installation will happen entirely in the 
virt console (and is watchable in text mode), though you will not be 
able to get VNC graphics at the same time.

Re: Koan virt install hanging

On 1/1/08, Michael DeHaan <mdehaan@...> wrote:
> Jason Hartley wrote:
> > Hey,
> >
> > Happy New Years!
> >
> >  I am having an issue with doing a koan virt install.  I am trying to
> > build a Centos5.1 Xen VM and during the initial boot it hangs at the
> > same spot every time.  I am using Cobbler version 0.6.4-2 and Koan
> > version 0.6.3-3.  Below is the output from the install during the boot
> > where it hangs.  Can some one help direct me on what might be my
> > problem?
> >
> >
> I think I know what is going on.
>
> It's not hanging, what is happening is that the virtualized console no
> longer becomes useful once the VNC graphics mode engages -- in other
> words, you should be able to watch the rest of the install with
> virt-manager.
>
> Older versions of koan had a flag to disable VNC support, but this was
> missing in recent versions (because I was not aware of the virt console
> issue).  In newer versions of koan (such as the test builds...
> http://cobbler.et.redhat.com/download/testing) there is once again a
> --nogfx flag.
>
> When this flag is used, the installation will happen entirely in the
> virt console (and is watchable in text mode), though you will not be
> able to get VNC graphics at the same time.

What component use to bug report?

Hi,

There is a bug I want to report on Bugzilla but I don't know for what
component I assign the ticket. The problem is with the / (slash) key
which don't works when using pt-br VNC keymap to view Qemu and Xen
(and probably KVM too) guests. There is no problem in Xen console
windows.

Thanks,

Davidson Paulo
http://fedoraproject.org/wiki/DavidsonPaulo

Re: What component use to bug report?

On Wed, Jan 02, 2008 at 09:24:13AM -0200, Davidson Rodrigues Paulo wrote:
> Hi,
> 
> There is a bug I want to report on Bugzilla but I don't know for what
> component I assign the ticket. The problem is with the / (slash) key
> which don't works when using pt-br VNC keymap to view Qemu and Xen
> (and probably KVM too) guests. There is no problem in Xen console
> windows.

If you're installing with virt-manager then use that as the component,
otherwise use 'qemu' or 'kvm'. If need be, the maintainer can easily
re-assign the bug to a different component later, so don't worry too
much.

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  -=| 

Re: [PATCH] BZ#251643: Allow to set the cpu pinning for creating domain with virt-manager.

On Tue, Dec 25, 2007 at 03:37:58PM +0900, Nobuhiro Itou wrote:
> Hi
> 
> As well as virt-install, I want to set the cpu pinning 
> at the time of creating domain with virt-manager.
> And, because virtinst changeset 320 was committed, 
> I add the allocation setting of pCPU to virt-manager.
> 
> some notes are follows:
>  - This feature works with changeset of virtinst is 320 or later.
>  - The specification about the CPU pin parameter follows that of virt-install.
>  - This function can be used only for xen hypervisor.
>  - When 1 pCPU in xen hypervisor, this function is disabled.

I appreciate your work on this patch, however, IMHO this is not something
we should add to the new VM wizard. The need to pin CPUs at install time
has a tiny niche scenario of usefullness. For most people pinning CPUs is
a bad idea as they will make worse decisions that the hypervisor/OS
schedular. The more features we add to the 'new VM wizard', the more
complex the user interaction becomes. Our goal for virt-manager is to
provide UI which targets the most commonly used features only and explicitly
leave out features only used in a niche use cases, thus keeping the app
simple to use. IMHO, pinning CPUs at install time is just not a feature
which is critical enough to justify in the new VM wizard.

I *would* however welcome a patch to the 'Virtual Machine Details' dialog
where you can currently adjust the  number of vCPUs. It would make sense
to be able to have UI for pinning vCPUs of an existing domain in this part
of the UI.

Reminder: FUDCon (the Fedora conference) is January 11-13 in Raleigh, and FREE

Details here:

    http://barcamp.org/FUDConRaleigh2008

Everyone is welcome.  

The actual conference talks are going to be on Saturday, with hack 
sessions Friday and Sunday.

--Michael

Re: [PATCH] BZ#251643: Allow to set the cpu pinning for creating domain with virt-manager.

Nobuhiro Itou wrote:
> Hi
> 
> As well as virt-install, I want to set the cpu pinning 
> at the time of creating domain with virt-manager.
> And, because virtinst changeset 320 was committed, 
> I add the allocation setting of pCPU to virt-manager.
> 
> some notes are follows:
>  - This feature works with changeset of virtinst is 320 or later.
>  - The specification about the CPU pin parameter follows that of virt-install.
>  - This function can be used only for xen hypervisor.
>  - When 1 pCPU in xen hypervisor, this function is disabled.

Nobuhiro, Did you have any comments on my proposal here?

https://www.redhat.com/archives/libvir-list/2007-December/msg00327.html

Rich.

--

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903

_______________________________________________
et-mgmt-tools mailing list

FYI: virt-manager re-instate new & delete buttons

After the mild disaster of including the new & delete buttons inline in the
list of VMs / connections, I've reverted the UI back to the old style with
new & delete buttons at the bottom of the window.  Anyone interested in 
checking this out the changes are now in the virt-manager HG repo and I
will do an update release this week with them in...

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  -=|