On 6/17/07, Daniel P. Berrange <
berrange@xxxxxxxxxx> wrote:
On Sat, Jun 16, 2007 at 05:57:09PM -0700, Adam Monsen wrote:
> First of all, the improved virt-manager that comes with Fedora 7 is
> awesome! By simply clicking through the UI and exploring a bit I was
> able to learn how to create a functional bridged network to the LAN my
> host is on. I know naught about networking and this has traditionally
> been the most painful aspect for me when I was playing with
> virtualization some time ago.
Great - glad its working well for you !
> 1. Should virsh work with KVM in Fedora 7? When I run virsh I get only
> "virsh: error: failed to connect to the hypervisor"
You need to explicitly tell virsh to connect to QEMU/KVM since it
defaults to Xen.
virsh --connect qemu:///system
Or
export VIRSH_DEFAULT_CONNECT_URI=qemu:///system
virsh
> 2. What is the canonical/"out of the box" way to start a KVM-based
> guest when the host system boots? I'm fine with "just use
> /etc/rc.local" or whatever if the infrastructure isn't in place yet
> (if so, what command should I run?). But it would be nice to be able
> to manage the guest from virt-manager after starting it up from a
> script somehow.
We've not hooked up autostart to the virt-manager UI yet, in the meantime
you can use virsh like this:
virsh autostart [vm name]
Th VM will be started by the libvirt daemon at boot time.
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 -=|
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
