search for: virtualdev

A colleague found some VMX files which omit the deviceType field. This allows -i vmx mode to parse them. Rich.

https://bugzilla.redhat.com/show_bug.cgi?id=1441197

>First, I was looking for the actual values.? >For a VM with (among other values): > config.version = "8" > virtualHW.version = "10" > ethernet0.virtualDev = "e1000" > guestOS = "rhel6-64" > firmware = "efi" > I see: > option-93 = 0x07 > option-60 ="PXEClient:Arch:00007:UNDI:003016" OK I take binaries (w/o recompiling) from https://www.kernel.org/pub/linux/utils/boot/syslinux/syslinux-6.03.z...

Just curious but how long has ESX support been in libvirt? Also I noticed this error when accessing one of my windows vms: error: internal error Expecting VMX entry 'scsi0.virtualDev' to be 'buslogic' or 'lsilogic' but found 'lsisas1068' Not sure whether this is an enhancement, defect, or not supported at this time. Thanks. -Jon

...otmgfw.efi then the Microsoft boot manager > perfectly boots it retrieves the BCD etc. etc that tells me > it is not a VMware problem. First, I was looking for the actual values. For a VM with (among other values): config.version = "8" virtualHW.version = "10" ethernet0.virtualDev = "e1000" guestOS = "rhel6-64" firmware = "efi" I see: option-93 = 0x07 option-60 = "PXEClient:Arch:00007:UNDI:003016" and present it efi64/efi/syslinux.efi and it boots. I also only have 1 NIC in this VM. This level of detail is what it takes for someon...

> I use Syslinux 6.03 EFI64 on a VMware Workstation 10 VM on > 10.0.2 on Linux. > w/o any problem? >> correctly sends back w/o error the "corresponding" syslinux.efi >> "EFI BC" -> EFI64\syslinux.efi >> "EFI IA32"-> EFI32\syslinux.efi >I only send back 1 filename. > Me too, I just send the

On Sun, Jan 11, 2015 at 10:32 AM, Patrick Masotta <masottaus at yahoo.com> wrote: > >>First, I was looking for the actual values. >>For a VM with (among other values): > >> config.version = "8" >> virtualHW.version = "10" >> ethernet0.virtualDev = "e1000" >> guestOS = "rhel6-64" >> firmware = "efi" > >> I see: > >> option-93 = 0x07 >> option-60 ="PXEClient:Arch:00007:UNDI:003016" > > OK I take binaries (w/o recompiling) from > https://www.kernel.org/pub/li...

...> I see it has two cores per socket. Is it one socket? What exact make/model >> is the CPU in the host? You might be choking the VM. Have you considered >> just 1 socket and 1 core per socket? 1) My assumption would be that the VMware virtualized AMD 79C970A (PCNet32 driver; vlance virtualDev) lacks proper EFI64 support. 2) I have 0 speed issues using your VMX. If you only have two real cores for this 2vCPU VM, you're choking it as the host needs time to run. If you choke it, you mess with timers. If you mess with timers, interface polling and a HUGE slew of items (including a g...

On Mar 8, 2014 10:08 AM, "Gene Cumm" <gene.cumm at gmail.com> wrote: > > On Mar 8, 2014 9:27 AM, "Steven Shiau" <steven at nchc.org.tw> wrote: > > > > > > > > On 03/08/2014 10:06 PM, Gene Cumm wrote: > > >> Hi Gene, > > >> > Thanks. As you suggested, I did a test about 6.03-pre6, and I still got > >

I tried using it in a template: <%= memory %> and it put "0" in my file when i switched the variable name to the_memory, it worked Eugene Ventimiglia Director of Systems GridApp Systems e: eventi@gridapp.com o: 646 452 4081 _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com

...= "normal" ide0:0.present = "true" ide0:0.deviceType = "ata-hardDisk" ide0:0.fileName = "/vmfs/volumes/349969f9-070dee8d/./windows2008.vmdk" floppy0.present = "false" floppy1.present = "false" ethernet0.present = "true" ethernet0.virtualDev = "e1000" ethernet0.networkName = "VM Network" ethernet0.connectionType = "bridged" ethernet0.addressType = "vpx" ethernet0.generatedAddress = "00:50:56:91:00:07" svga.vramSize = "8388608" zhanggp -------------------------------------...

On 2014/3/10 ?? 05:48, Gene Cumm wrote: > 1) My assumption would be that the VMware virtualized AMD 79C970A > (PCNet32 driver; vlance virtualDev) lacks proper EFI64 support. > > 2) I have 0 speed issues using your VMX. If you only have two real > cores for this 2vCPU VM, you're choking it as the host needs time to > run. If you choke it, you mess with timers. If you mess with timers, > interface polling and a HUGE slew...