Hi Joerg,
Sure, the KVM command is :
/usr/bin/kvm -enable-nesting -no-kvm-irqchip -S -M pc-0.14 -enable-kvm
-m 2048 -smp 2,sockets=2,cores=1,threads=1 -name hyperv1 -uuid
8c5d8f1f-5767-b388-d408-1b53a1b66e72 -nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/hyperv1.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=readline -rtc base=localtime
-no-reboot -boot d -drive
file=/srv/hyperv/hyperv1.vmimg,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
-drive
file=/srv/virtual-machines/fromiscsi/iso/W2K8ENTR2SP1.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw
-device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0
-drive
file=/srv/virtual-machines/fromiscsi/iso/virtio-win-1.1.16.iso,if=none,media=cdrom,id=drive-ide0-1-1,readonly=on,format=raw
-device ide-drive,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1
-netdev tap,fd=17,id=hostnet0 -device
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:2a:be:2f,bus=pci.0,addr=0x3
-chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0 -usb -device
usb-tablet,id=input0 -vnc 127.0.0.1:0 -vga std -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
This is started via virsh.
Jim
On 18/10/2011 17:34, Joerg Roedel wrote:
Hi Jim,
On Tue, Oct 18, 2011 at 12:34:23PM +0100, Jim wrote:
I've worked with KVM for quite a while now but have come across a
problem when trying to run some W2K8R2 VMs where I want to also run
Hyper-V on those VMs - nested virtualization.
I've researched and checked the obvious AMD processor with the enable
nested flag, running a kvm guest with the nesting support enabled etc.
which did allow me to add the Hyper-V role to the VM but when it
reboots, the machine hardware lists a problem with the VM machine bus
and no hyper-v VMs can be created.
Can you share the qemu command line you used to start the VM?
From what I've read through from lurking on the list and reading the
archives, I'm not sure whether the problem is that KVM is not ready to
support Hyper-V yet or if I'm doing it wrong.
I'd be very thankful if someone could say if I'm hoping for too much
right now or point me where to go to find some details on what I'm
doing wrong and how to do it right.
I also had issues with Hyper-V. But at least the root-domain should boot
up without problems. I also started a Linux guest inside but that got
stuck at some point in the kernel boot process. I havn't debugged that
further yet, though.
Joerg
----------------------------------------------------------------------
All e-mail and telephone communications are subject to Suresafe Terms
And Conditions and may be monitored, recorded and processed for the
purposes contained therein and adherence to regulatory and legal
requirements.
Your further communication or reply to this e-mail indicates your
acceptance of this.
Any views or opinions expressed are the responsibility of the author
and may not reflect those of Suresafe Protection Limited.
Suresafe Protection Limited is registered in Scotland, number SC132827
The registered office is at 8 Kelvin Road, Cumbernauld, G67 2BA.
Telephone: 01236 727792 Fax: 01236 723301 VAT Number: 556 6950 02
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
