I think this may be a question about virsh or libvirt, but anyway ..
When I do a command like:
virt-install \
--name=$tmpname \
--ram=1024 \
--os-type=linux --os-variant=$osvariant \
--arch ppc64le --machine pseries \
--initrd-inject=$(pwd)/preseed.cfg \
--extra-args="auto console=tty0 console=hvc0" \
--disk=$(pwd)/$output,size=4,format=raw \
--serial pty \
--location=http://ports.ubuntu.com/ubuntu-ports/dists/$dist/main/installer-ppc64el \
--nographics \
--noreboot
It later fails with the instructions:
Additional details may be available in /var/log/syslog or on virtual
console 4.
which is great, but I can find no way to get to "virtual console 4",
and that's a problem because there's no further way to diagnose this
bug.
What element of the stack is implementing the serial console and what
keys might be used to switch between virtual consoles?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
_______________________________________________
virt-tools-list mailing list
virt-tools-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/virt-tools-list
