On 10/06/12 06:28 PM, Michael Tokarev wrote:
On 11.06.2012 00:15, Gary Dale wrote:
How do I get a command line from virt-mgr?
It should be available in the log, and shown by ps.
Secondly, whether or not I can create a new virtual machine is a different
issue. I shouldn't have to create new virtual machines every time I upgrade my
system. One virtual machine should be able to run on different processors,
especially when they are as similar as Phenom II and Bulldozer. According to
what I've read, I should even be able to migrate a VM from AMD to Intel.
That's exactly how it is here: no matter which CPU I run it on, it works.
It is possible however to make a (physical) winXP confused by upgrading
physical CPU.
/mjt
Here's the qemu/ghoswheel64.log entries for the startup of the local copy:
2012-06-10 23:38:23.205+0000: starting up
LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin HOME=/
QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-1.0 -enable-kvm -m 2048 -smp
2,sockets=2,cores=1,threads=1 -name ghostwheel64 -uuid
68bbcceb-f8c4-6a58-9a79-c50e177f8641 -nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/ghostwheel64.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime
-no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
file=/var/lib/libvirt/images/ghostwheel64.img,if=none,id=drive-ide0-0-0,format=raw
-device
ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1
-netdev tap,fd=20,id=hostnet0 -device
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:74:2f:af,bus=pci.0,addr=0x3
-chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0
-vnc 127.0.0.1:1 -vga std -device intel-hda,id=sound0,bus=pci.0,addr=0x4
-device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
char device redirected to /dev/pts/4
I'm confused by your statement about the physical WInXP. Granted, I
can't upgrade the mainboard and processor on a physical Windows computer
without Windows complaining but that's mainly a licensing issue. Once
the proper drivers are installed, it should work.
With a virtual machine, I thought the machine pretty much stayed the
same despite differences in the host architecture.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
