![]() is this the insider preview build of windows 10? Their are known issues with hyper-v and some builds of windows 10. Upgrading to the RC branch (6.33rc4) causes the reboot loop. 'Upgrading' to 6.30.4 causes no interfaces in Hyper-V and also gives me the 24hour limit like I have installed it from the x86 iso image. Upgrading to this version causes continuous reboots. Via the system -> packages I checked for updates and update 6.32.1 is available. Picked the 6.31 IMG file, converted it for Hyper-V. I don't know what is wrong, but in my case it just keeps rebooting on Hyper-V (Running on Windows 10) # INTERFACE USE-PEER-DNS ADD-DEFAULT-ROUTE STATUS ADDRESSĠ bridge1 yes yes bound > sy hardware print My CHR VM is now booting in full SCSI paravirtual mode on ESXI 5.5u2Ĭode: Select all > sy resource pci printĠ 00:03.0 Cirrus Logic GD 5446 (rev: 0) 0ġ 00:02.0 XenSource, Inc. ![]() Vmkfstools -i /vmfs/volumes/Datastore_local_x3300/CHR2/chr-6.31.vmdk /vmfs/volumes/Datastore_local_x3300/CHR2/ I created a new virtual machine with the template "Other Linux 3.x 64bit" and the machine is now created with VMware paravirtual controller and VMXnet3 network adapters.īut I was still unable to boot the VM with disk in SCSI mode (works fine with IDE), I had to "import" the vmdk with the following command executed on the ESXi console : Scsi0.sasWWID = "50 05 05 6e f4 ee b7 a0"Īlso, add scsi drives in order (starting with 0) jumping over may yield strange results.įor my first attempt, I used the template "Other Linux 64bit" and it defaulted with LSI Logic SCSI controller and E1000 network adapter. ![]() Code: Select all scsi0.virtualDev = "pvscsi"
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |