Thanks for replying. Good info so far. After I start the VM, I’m going to need to see the boot console, and I’ll need to ssh into it with a hostname or IP. What are some required steps for those needs? This VM is going to need to access a few associated networks. I can see that the “—networks”
option is part of the interface for configuring this. What are some things I’ll have to do for this? From: Jeff Tchang [mailto:jeff.tchang@xxxxxxxxx]
I actually find I do almost all my VM management inside the virsh command. If the VM appears to exist inside virsh but is in a shut off state then you should try to start it. VNC can also be SSH port forwarded (which I have done before). Not sure if this will help but this is the command I use to create VMs: virt-install \ --name example \ --vcpus=4 \ --disk /data/example,size=80 \ --ram 2048 \ --graphics vnc,password=**********,listen=0.0.0.0,port=15916 \ --accelerate \ --cdrom /var/kvm/ubuntu-14.04.1-server-amd64-autoinstall.iso \ --os-type=linux \ --noautoconsole \ --network network=default \ --boot cdrom,fd,hd,network,menu=off I also edit the XML file sometimes. Notice I have the autoinstall iso. Basically I went through and created a ks.cfg file after extracting the ISO file to a directory. Then I ran a command like this: mkisofs -D -r -V "auto install" -cache-inodes -J -l -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table
-o /var/kvm/ubuntu-14.04.1-server-amd64-autoinstall.iso /root/serveriso On Thu, Jul 9, 2015 at 10:57 AM, KARR, DAVID <dk068x@xxxxxxx> wrote:
|
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users