[PVE-User] Windows Server 2003

[David Lawley]

yep, finally.  Had to shove the new driver into place,  but did not help 
with the restart problem

can start and stop via PVE.   Have a few other quirks too, like 
configuring page file for crash dump, another topic for another vendor.

But it still runs.  Maybe time just to pamper this old creature till 
they decide to  to move its purpose to another resource (not soon enough 
if you ask me)

so get-osinfo shows

  "id" : "mswindows",
    "kernel-release" : "3790",
    "kernel-version" : "5.2",
    "machine" : "x86",
    "name" : "Microsoft Windows",
    "pretty-name" : "Microsoft Windows Server 2003 R2",
    "variant" : "server",
    "variant-id" : "server",
    "version" : "Microsoft Windows Server 2003",
    "version-id" : "2003"

and config shows

agent: 1
boot: c
bootdisk: virtio0
cores: 12
cpu: kvm32
ide2: ISOStore:iso/virtio-win-0.1.164.iso,media=cdrom,size=362130K
localtime: 1
memory: 3072
name: Intranet2
net0: virtio=8E:BB:62:16:15:76,bridge=vmbr0
numa: 0
onboot: 1
ostype: wxp
sockets: 2
startup: up=30
virtio0: netappstore:vm-133-disk-0,size=80G


On 4/25/2019 10:30 AM, Mark Adams wrote:
> AFAIK you need the serial driver for the guest agent to work correctly, so
> make sure that device is up to date. If its not showing as with a missing
> driver in device manager it must already be installed and might just need
> updating?
>
> https://pve.proxmox.com/wiki/Qemu-guest-agent#Windows
>
>
> On Thu, 25 Apr 2019 at 11:41, David Lawley <davel at upilab.com> wrote:
>
>> something up with the guest agent, have to look further.
>>
>> These things have been pounded on for the past few years, something is
>> lingering around.  Agent its running but no communication between guest
>> and PVE
>>
>> On 4/25/2019 2:01 AM, Thomas Lamprecht wrote:
>>> Am 4/24/19 um 8:13 PM schrieb David Lawley:
>>>> I did that as part of the migration
>>>>
>>> and the guest agent works? i.e., things like
>>> # qm guest cmd VMID get-osinfo
>>>
>>> also the guest config could be interesting:
>>> # qm config VMID
>>>
>>>
>>>> Serial driver?  Don't have have any odd devices showing up in the
>> device list
>>>>
>>>>
>>>> On 4/24/2019 2:02 PM, Mark Adams wrote:
>>>>> Haven't tried this myself, but have you updated the qemu-agent and
>> serial
>>>>> driver to check it's not that?
>>>>>
>>>>> On Wed, 24 Apr 2019, 18:59 David Lawley, <davel at upilab.com> wrote:
>>>>>
>>>>>> I know, its an oldie, but.. Windows Server 2003
>>>>>>
>>>>>> But since moving it to PVE 5.4 (from3.4) its does not reboot/restart
>> on
>>>>>> its own.  You can select a restart, but it does not. You have to start
>>>>>> it manually.
>>>>>>
>>>>>> Migration from 3.4 was done via backup then restore into 5.4
>>>>>>
>>>>>> Poking around, but if someone has crossed this path before me I would
>>>>>> appreciate a nudge in the right direction
>>>>>>
>>>>>> Thanks a bunch
>>>
>> _______________________________________________
>> pve-user mailing list
>> pve-user at pve.proxmox.com
>> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-use
>> <https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user>
>>
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user