<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>All Fusion Feature Requests posts</title>
    <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/idb-p/fusion-ideas</link>
    <description>All Fusion Feature Requests posts</description>
    <pubDate>Fri, 10 Nov 2023 20:50:39 GMT</pubDate>
    <dc:creator>fusion-ideas</dc:creator>
    <dc:date>2023-11-10T20:50:39Z</dc:date>
    <item>
      <title>Few feature requests for the future version</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Few-feature-requests-for-the-future-version/idi-p/2977588</link>
      <description>&lt;P&gt;(1) Per-VM setting for mouse/game optimization - At this moment it is a single global setting&lt;/P&gt;&lt;P&gt;(2) Higher refresh rate - This is possible. Parallels' windows guest are running at 120hz refresh rate&lt;/P&gt;&lt;P&gt;(3) Not sure if this is already supported - Headless guest?&lt;/P&gt;&lt;P&gt;(4) More customizable vmnet settings. i.e. routing settings, DHCP options , etc.&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Sun, 16 Jul 2023 08:21:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Few-feature-requests-for-the-future-version/idi-p/2977588</guid>
      <dc:creator>Clemond</dc:creator>
      <dc:date>2023-07-16T08:21:57Z</dc:date>
    </item>
    <item>
      <title>Re: Return multiple monitor support</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Return-multiple-monitor-support/idc-p/2964331#M20</link>
      <description>&lt;P&gt;there doesn't seem to be put much effort into development - any news regarding multi-monitor?&lt;/P&gt;</description>
      <pubDate>Tue, 18 Apr 2023 06:50:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Return-multiple-monitor-support/idc-p/2964331#M20</guid>
      <dc:creator>za4</dc:creator>
      <dc:date>2023-04-18T06:50:31Z</dc:date>
    </item>
    <item>
      <title>Re: Return multiple monitor support</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Return-multiple-monitor-support/idc-p/2955231#M19</link>
      <description>&lt;P&gt;I switched my users to Fusion from Parallels over a decade ago, but the lag in full support for Windows guest on Apple silicon has gotten beyond frustrating and is causing serious reconsideration.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please return this functionality!&lt;/P&gt;</description>
      <pubDate>Fri, 17 Feb 2023 17:57:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Return-multiple-monitor-support/idc-p/2955231#M19</guid>
      <dc:creator>scsiboy71</dc:creator>
      <dc:date>2023-02-17T17:57:40Z</dc:date>
    </item>
    <item>
      <title>Re: Support Booting native (Asahi) Linux Installations on Apple Silicon</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2953689#M18</link>
      <description>&lt;P&gt;Thank you very much&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/136376"&gt;@ColoradoMarmot&lt;/a&gt;. That is a reasonable explanation. I still hope VMWare will address the issue as it basically seems to be broken functionality, that raw vmdk do not work on apple silicon even though they work on Intel Macs (since 13.0.1). If the Fusion team considers to implement support via the GUI it would be even better of course, but I'm fine dealing with the CLI as long as it works. Let's hope for the best.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2023 10:21:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2953689#M18</guid>
      <dc:creator>Rastafabisch</dc:creator>
      <dc:date>2023-02-10T10:21:26Z</dc:date>
    </item>
    <item>
      <title>Re: Support Booting native (Asahi) Linux Installations on Apple Silicon</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2953312#M17</link>
      <description>&lt;P&gt;Remember that Fusion is a commercial product. &amp;nbsp; I seriously doubt there are incremental sales at sufficient level to justify building support in fusion for a project that Apple doesn't support.&lt;/P&gt;&lt;P&gt;Windows is a different story, because there absolutely is commercial demand for it - in fact, I'd argue that without Windows support, Fusion would likely go EOL. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Put it another way - absolutely fair to make the request. &amp;nbsp;Just understand that it'll be queued and prioritized based on revenue potential....and the Fusion team is clearly struggling to deliver things that have much higher business value.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Feb 2023 16:04:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2953312#M17</guid>
      <dc:creator>ColoradoMarmot</dc:creator>
      <dc:date>2023-02-08T16:04:49Z</dc:date>
    </item>
    <item>
      <title>Re: Support Booting native (Asahi) Linux Installations on Apple Silicon</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2953265#M16</link>
      <description>&lt;P&gt;I totally get where the sepsis is coming from. However I feel like you misjudge the situation. Thought that might be true or me as well.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Asahi is less of a bistro, but more of an upstreaming project, thus enabling any up to date linux distro to support Apple silicon hardware. As a matter of fact freeBSD already supports Apple Silicon due to this and Fedora developers are on their way, too.&lt;/LI&gt;&lt;LI&gt;Running alternative kernels and thus OS is a supported scenario by Apple. They even developed an environment to set this up (kmutil) and even introduced further updates to ease the development by deliberately enabling non mach kernels to be booted natively.&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;The Asahi Linux project&amp;nbsp;provides&amp;nbsp;the&amp;nbsp;boot loader&amp;nbsp;(combination - m1n1 + uBoot). to enable UEFI booting (including external media). While this is needed for any distro with current upstream kernel (which already is&amp;nbsp;enough to boot on Apple Silicon) it is not unlike BOOTCAMP back when Windows used to&amp;nbsp;require BIOS&amp;nbsp;mode to boot (As in having a custom Boot environment.) However kernels could be booted without this and it is only to facilitate the process. The difference still is, of&amp;nbsp;course, that BOOTCAMP was (is) a first party implementation, while m1n1+uBoot is only an apple-sanctioned&amp;nbsp;implementation.&lt;/LI&gt;&lt;LI&gt;Like&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/453305"&gt;@Technogeezer&lt;/a&gt;&amp;nbsp;said: It's mostly for convenience. But how does that differ to booting BOOTCAMP as a vm?&lt;/LI&gt;&lt;LI&gt;The low level boot process is totally irrelevant as in the end the kernel is booted by a stock Grub aa64 environment. - Just as stock linux vm use them.&amp;nbsp;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;I do very well understand how this makes it different from supporting BOOTCAMP in the past, however being officially unsupported&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/136376"&gt;@ColoradoMarmot&lt;/a&gt;&amp;nbsp;does not seem to be a valid argument, as Windows VMs are officially unsupported by Microsoft either, and Fusion still supports Windows nonetheless.&lt;/P&gt;&lt;P&gt;Also we are not talking about some niche distro, but Linux in general. Asahi is just the project enabling any Linux to be Apple Silicon compatible.&lt;/P&gt;&lt;P&gt;So the issue currently boils down to: Why do raw vmdks to not work on apple silicon. They sure seem to be a supported scenario in general, aren't they?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Feb 2023 12:08:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2953265#M16</guid>
      <dc:creator>Rastafabisch</dc:creator>
      <dc:date>2023-02-08T12:08:06Z</dc:date>
    </item>
    <item>
      <title>Re: Support Booting native (Asahi) Linux Installations on Apple Silicon</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2953155#M15</link>
      <description>&lt;P&gt;Great summary of the hardware limitations (which are pretty severe), and all on a niche distribution without much real software support. &amp;nbsp;It's much more a science project than anything else, and only one apple OS update from rendering the whole machine unbootable.&lt;/P&gt;&lt;P&gt;Until Microsoft licenses Windows on Mac, and Apple builds bootcamp for it, Fusion isn't going to pay any attention to it. &amp;nbsp;Even then, I'd seriously doubt that Apple enables bootcamp for Asahi (if they do it for anything, it'll be a mainstream distro).&lt;/P&gt;</description>
      <pubDate>Tue, 07 Feb 2023 21:42:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2953155#M15</guid>
      <dc:creator>ColoradoMarmot</dc:creator>
      <dc:date>2023-02-07T21:42:16Z</dc:date>
    </item>
    <item>
      <title>Re: Support Booting native (Asahi) Linux Installations on Apple Silicon</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2953147#M14</link>
      <description>&lt;P&gt;You are correct that Fusion isn't up to the task currently. The lack of an Apple Silicon LLB boot loader in a Fusion VM is a big hurdle in my mind, as that's what Asahi expects the initial boot to come from. Perhaps you can hack the Asahi boot process to stop the chain boot to uboot and go directly to grub - using the UEFI environment already provided by Fusion.&amp;nbsp;&lt;/P&gt;&lt;P&gt;That leads to other questions in my mind.&lt;/P&gt;&lt;P&gt;I question whether running Asahi in a Fusion VM would have any benefits over a natively booted Asahi operating system other than convenience. It certainly would have no benefit over the numerous arm64 Linux distros that already run in a VM. Consider that an Asahi Linux VM would not have direct access to the hardware features of the M1/M2 SOCs - it would be dealing with a virtualized vmwgfx display adapter, an e1000e or vmxnet3 virtual network adapter, and virtualized hard drives (even though it would be direct access to a hard disk partition rather than a VMware formatted VMDK).&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Feb 2023 21:13:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2953147#M14</guid>
      <dc:creator>Technogeezer</dc:creator>
      <dc:date>2023-02-07T21:13:46Z</dc:date>
    </item>
    <item>
      <title>Re: Support Booting native (Asahi) Linux Installations on Apple Silicon</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2953139#M13</link>
      <description>&lt;P&gt;It is unsupported by Apple. &amp;nbsp;As such Fusion will not support it.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Feb 2023 20:53:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2953139#M13</guid>
      <dc:creator>ColoradoMarmot</dc:creator>
      <dc:date>2023-02-07T20:53:16Z</dc:date>
    </item>
    <item>
      <title>Re: Support Booting native (Asahi) Linux Installations on Apple Silicon</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2953126#M12</link>
      <description>&lt;P&gt;I think you are missing the&amp;nbsp;&lt;A title="Asahi Linux" href="https://asahilinux.org" target="_blank" rel="noopener"&gt;fact that Asahi Linux is already working on Apple Silicon natively&lt;/A&gt; and nicely. Including graphics acceleration. So there no issue on that side. Booting is handled via a custom boot loader which runs on apple silicon and chain loads uboot to provide a UEFI environment. From there on it's just grub booting a custom linux kernel. So it is kinda like BOOTCAMP, but for Linux rather than Windows. As it is basically just a linux on a current kernel it thus should be possible to boot it as a virtual machine, if VMWare Fusion was up to the task, which it apparently isn't according to my testing.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Feb 2023 19:46:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2953126#M12</guid>
      <dc:creator>Rastafabisch</dc:creator>
      <dc:date>2023-02-07T19:46:41Z</dc:date>
    </item>
    <item>
      <title>Re: Support Booting native (Asahi) Linux Installations on Apple Silicon</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2952905#M11</link>
      <description>&lt;P&gt;The real problem is that Apple Silicon does not use a "standard" UEFI boot loader, it uses Apple specific Low Level Bootloader (LLB) firmware.&lt;/P&gt;&lt;P&gt;Fusion implements UEFI firmware (as required by the ARM SystemReady specifications) for its virtual machines, not Apple's LLB firmware. That's probably why Asahi won't recognize any devices since it's expecting Apple's LLB firmware.&lt;/P&gt;&lt;P&gt;It's not going to be easy to boot anything Apple Silicon native until Fusion can provide an LLB firmware implementation. Or implements Apple's high level virtualization framework which I don't see happening any time soon because it's too far away from their ESXi roots.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Feb 2023 19:40:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2952905#M11</guid>
      <dc:creator>Technogeezer</dc:creator>
      <dc:date>2023-02-06T19:40:38Z</dc:date>
    </item>
    <item>
      <title>Re: Support Booting native (Asahi) Linux Installations on Apple Silicon</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2952901#M10</link>
      <description>&lt;P&gt;Bootcamp isn't supported on M1 macs, so there's nothing for Fusion to support.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Feb 2023 18:54:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2952901#M10</guid>
      <dc:creator>ColoradoMarmot</dc:creator>
      <dc:date>2023-02-06T18:54:17Z</dc:date>
    </item>
    <item>
      <title>Re: Return multiple monitor support</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Return-multiple-monitor-support/idc-p/2952764#M9</link>
      <description>&lt;P&gt;the new version of fusion (13.0.1) still does not allow multi-monitor support.&lt;/P&gt;&lt;P&gt;well, I am trying to get Parallels already. it will be great to have multi-monitor support again &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@7651DD0E8772B3B5D93ADA9ABA2E067C/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Feb 2023 07:13:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Return-multiple-monitor-support/idc-p/2952764#M9</guid>
      <dc:creator>za4</dc:creator>
      <dc:date>2023-02-06T07:13:41Z</dc:date>
    </item>
    <item>
      <title>Re: Support Booting native (Asahi) Linux Installations on Apple Silicon</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2952741#M8</link>
      <description>&lt;P&gt;Since the VMware Fusion 13.01 Update raw drives should work again (as does BOOTCAMP support on Intel Macs), creating the raw disk works fine now. On a default Apple Silicon system with a default Asahi Linux installation the appropriate Linux related partition numbers are 4 (EFI, including Grub) and 5 (Linux home, ext4 partition) on the internal NVMe SSD (disk0).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;vmware-rawdiskCreator create /dev/disk0 4,5 ~/Asahi nvme&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Editing the .vmx file of a default Linux Kernel 5 virtual machine to refer to the just created (and moved into the vm) vmdk files (Asahi.vmdk &amp;amp; Asahi-pt.vmdk) works and the resulting vm tried to boot but gets stuck searching for a bootable network instance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;nvme0.present = "TRUE"
nvme0:0.fileName = "Asahi.vmdk"
nvme0:0.present = "TRUE"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-SPOILER&gt;Does not work using other interfaces either. Tested with SATA, IDE &amp;amp; SCSI. (Reflecting those changes on the previous cli command, too.)&lt;/LI-SPOILER&gt;&lt;P&gt;Checking the EFI environment (pressing F10 on vm boot) reveals that the vm cannot actually see the assigned partitions.&lt;/P&gt;&lt;LI-SPOILER&gt;&lt;BR /&gt;Only network boot paths available in the boot from file menu.&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="Bildschirm­foto 2023-02-06 um 01.46.50.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/99796i451A499C46D3B023/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="Bildschirm­foto 2023-02-06 um 01.46.50.png" alt="Bildschirm­foto 2023-02-06 um 01.46.50.png" /&gt;&lt;/span&gt;&lt;/LI-SPOILER&gt;&lt;P&gt;Thus I suspect Fusion needs to be updated to support this BOOTCAMP support alike functionality on Apple Silicon.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Feb 2023 00:59:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idc-p/2952741#M8</guid>
      <dc:creator>Rastafabisch</dc:creator>
      <dc:date>2023-02-06T00:59:01Z</dc:date>
    </item>
    <item>
      <title>Re: Return multiple monitor support</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Return-multiple-monitor-support/idc-p/2952703#M7</link>
      <description>&lt;P&gt;The issue impacts users of both Intel and Apple Silicon Macs, and has been present since at least Fusion 12.&lt;/P&gt;</description>
      <pubDate>Sun, 05 Feb 2023 18:13:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Return-multiple-monitor-support/idc-p/2952703#M7</guid>
      <dc:creator>Technogeezer</dc:creator>
      <dc:date>2023-02-05T18:13:58Z</dc:date>
    </item>
    <item>
      <title>Re: Return multiple monitor support</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Return-multiple-monitor-support/idc-p/2952702#M6</link>
      <description>&lt;P&gt;I've been a Fusion user for a very very long time.&amp;nbsp; I don't mind being a little on the bleeding edge with my Win11 ARM64 installation, but without multiple monitor support this product is virtually useless to me.&amp;nbsp; I don't understand the technical issues making this so difficult to implement, but without it my support for the Fusion product will ultimately come to an end.&lt;/P&gt;</description>
      <pubDate>Sun, 05 Feb 2023 18:11:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Return-multiple-monitor-support/idc-p/2952702#M6</guid>
      <dc:creator>Paxsoga</dc:creator>
      <dc:date>2023-02-05T18:11:53Z</dc:date>
    </item>
    <item>
      <title>Support Booting native (Asahi) Linux Installations on Apple Silicon</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idi-p/2952629</link>
      <description>&lt;P&gt;The title is pretty self explanatory. It would be very useful if it were possible to boot residing native Linux installations from within macOS, just like we used to have support for booting BOOTCAMP installs on Intel Macs.&lt;/P&gt;&lt;P&gt;I already tried to archive this, using the cli raw disk creator, but this did not work.&lt;/P&gt;</description>
      <pubDate>Sat, 04 Feb 2023 23:28:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Support-Booting-native-Asahi-Linux-Installations-on-Apple/idi-p/2952629</guid>
      <dc:creator>Rastafabisch</dc:creator>
      <dc:date>2023-02-04T23:28:35Z</dc:date>
    </item>
    <item>
      <title>Re: Configure VMs to prevent host from sleeping</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Configure-VMs-to-prevent-host-from-sleeping/idc-p/2946502#M4</link>
      <description>&lt;P&gt;Interesting idea, but an idling Mac Pro is safely in the double digits in terms of power draw. That’s not something I am willing to invest 24/7.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 17:33:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Configure-VMs-to-prevent-host-from-sleeping/idc-p/2946502#M4</guid>
      <dc:creator>amalthea</dc:creator>
      <dc:date>2023-01-03T17:33:16Z</dc:date>
    </item>
    <item>
      <title>Re: Configure VMs to prevent host from sleeping</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Configure-VMs-to-prevent-host-from-sleeping/idc-p/2946500#M3</link>
      <description>&lt;P&gt;Why not just disable sleep on the host when on AC power? &amp;nbsp;With modern computers, there's so little power draw when idle, that sleeping isn't really necessary (apple's gotten massively aggressive with sleeping - and is screws up a lot of things).&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 17:27:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Configure-VMs-to-prevent-host-from-sleeping/idc-p/2946500#M3</guid>
      <dc:creator>ColoradoMarmot</dc:creator>
      <dc:date>2023-01-03T17:27:56Z</dc:date>
    </item>
    <item>
      <title>Configure VMs to prevent host from sleeping</title>
      <link>https://communities.vmware.com/t5/Fusion-Feature-Requests/Configure-VMs-to-prevent-host-from-sleeping/idi-p/2946449</link>
      <description>&lt;P&gt;When VMs are performing a long-running activity, the Mac will still go to sleep when nothing is happening on the host. This obviously prevents progress of any activity within the VM. It can also crash VM guest OSes because the host CPU is being yanked away.&lt;/P&gt;&lt;P&gt;I would like to have a per-VM or global Fusion configuration option to prevent the Mac from sleeping as long as a VM is running. This enables activities in VMs to continue without activity on the host.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 13:24:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-Feature-Requests/Configure-VMs-to-prevent-host-from-sleeping/idi-p/2946449</guid>
      <dc:creator>amalthea</dc:creator>
      <dc:date>2023-01-03T13:24:36Z</dc:date>
    </item>
  </channel>
</rss>

