Mark Johnson wrote:
Darren Reed wrote:
On 07/07/09 06:10, Mark Johnson wrote:
What I've come up with so far is:
virt-install --paravirt --name dom1 --ram 6144 --nographics \
--os-type=solaris \
--network bridge=e1000g0,capped-bandwidth=200M \
--disk path=/dev/dsk/c0t1d0s4,driver=phy
--location /isos/osol-200906.iso
... what I'm not happy about:
location - I want to use a DVD disc in my DVD drive, not an ISO image
disk path - how do I tell it to use an entire disk (or fdisk partition),
not just a slice?
cpu - I want to set the limit to 2 CPUs.
I assume your using stock bits? What you have above contains
params which are part of a newer virt-install which is being
putback shortly.
virt-install --help
For the disk and cdrom path, you should use p0.
e.g. here's using a cdrom, with 2 vcpus which I
just tested on stock b118 bits (don't have an extra
disk I can install onto on this machine)
-bash-3.2# virt-install -p -n dom --vcpus=2 -r 800 --nographics
--noautoconsole -f /export/disk0 -s 8 -l /dev/dsk/c1t0d0p0
so a -f /dev/dsk/c0t1d0p0 should do it for the disk. Just don't
specify the wrong
disk ;-)
And that's all working as I expected.
The only part that was a bit weird was starting it up the first time
to see what it would do, stopping it and wanting to recreate the
vm. There doesn't seem to be a virt-destroy and "xm destroy"
didn't undo everything that virt-install did the first time, so I had
to use virt-manager to clean up the old vm.
Looking in virt-manager I can see that I can manage RAM and
CPU... what about disk? Or do I need to wait until it's shutdown
before I can do disk?
Darren
_______________________________________________
xen-discuss mailing list
xen-discuss@opensolaris.org
