[PVE-User] NFSv4.1 multipath available?

[Gerald Brandt]

Hi,

I'm mount my NFS server (images and backup) as vers=4.1. It works quite 
well. I currently use balance-rr across 2 GigE links to talk to my NFS 
server.


Is there a way to set up multipath with NFS instead?

Gerald


___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [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  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,  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@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-use



___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user


___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Windows Server 2003

[Mark Adams]

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  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,  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@pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-use
> 
>
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] NFS Storage issue

[Mark Schouten]

Might also be the number of nfsd started on your Synology.

--

Mark Schouten 

Tuxis, Ede, https://www.tuxis.nl

T: +31 318 200208 
 



- Originele bericht -


Van: Gerald Brandt (g...@majentis.com)
Datum: 25-04-2019 14:51
Naar: pve-user@pve.proxmox.com
Onderwerp: Re: [PVE-User] NFS Storage issue


On 2019-04-25 7:34 a.m., Gianni Milo wrote:
> Hello
>
> I have a Synology with High Availability serving NFS storage to Proxmox.
>> A couple of months ago, this started happening:
>>
>> Apr 24 12:32:51 proxmox-1 pvestatd[3298]: unable to activate storage
>> 'NAS' - directory '/mnt/pve/NAS' does not exist or is unreachable
>> Apr 24 13:08:00 proxmox-1 pvestatd[3298]: unable to activate storage
>> 'NAS' - directory '/mnt/pve/NAS' does not exist or is unreachable
>>
>>
> It appears that the NFS storage target was unreachable during that time...
>
>
>> It affecting backups and VM speeds. Any idea what is causing this?
>
> I would guess that the network link used for accessing the NFS target is
> getting saturated. This sometimes can be caused by running backup jobs,
> and/or other tasks like VMs demanding high i/o to that destination.
>
> There are no errors in the Synology logs, and the storage stays mounted and
>> accessible.
>>
> You mean that it stays accessible after the backups are finished (or
> failed) and after the i/o operations return to the normal levels ?
> Do you recall if there was any of the above happening during that time ?
>
>
>> Any ideas what's going on?
>>
> I would set bandwidth limits either on the storage target or on the backup
> jobs. See documentation for details on how to achieve this.
> Even better, separate VMs from the backups if that's possible (i.e use
> different storage/network links).
>
> G.
> ___


Thanks for the reply. Although it does happen during backups, causing
serious issues that require Proxmox server restart, it also happens
during the day. I don't see any saturation issues during the day, but
I'll start monitoring that.

So you're saying to set network bandwidth limits on the storage network
(I do keep a separate network for storage). I guess upgrading the
synology's with something that has 10GE would help as well.

Thanks,

Gerald


___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user



___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] NFS Storage issue

[Gerald Brandt]

On 2019-04-25 7:34 a.m., Gianni Milo wrote:

Hello

I have a Synology with High Availability serving NFS storage to Proxmox.

A couple of months ago, this started happening:

Apr 24 12:32:51 proxmox-1 pvestatd[3298]: unable to activate storage
'NAS' - directory '/mnt/pve/NAS' does not exist or is unreachable
Apr 24 13:08:00 proxmox-1 pvestatd[3298]: unable to activate storage
'NAS' - directory '/mnt/pve/NAS' does not exist or is unreachable



It appears that the NFS storage target was unreachable during that time...



It affecting backups and VM speeds. Any idea what is causing this?


I would guess that the network link used for accessing the NFS target is
getting saturated. This sometimes can be caused by running backup jobs,
and/or other tasks like VMs demanding high i/o to that destination.

There are no errors in the Synology logs, and the storage stays mounted and

accessible.


You mean that it stays accessible after the backups are finished (or
failed) and after the i/o operations return to the normal levels ?
Do you recall if there was any of the above happening during that time ?



Any ideas what's going on?


I would set bandwidth limits either on the storage target or on the backup
jobs. See documentation for details on how to achieve this.
Even better, separate VMs from the backups if that's possible (i.e use
different storage/network links).

G.
___



Thanks for the reply. Although it does happen during backups, causing 
serious issues that require Proxmox server restart, it also happens 
during the day. I don't see any saturation issues during the day, but 
I'll start monitoring that.


So you're saying to set network bandwidth limits on the storage network 
(I do keep a separate network for storage). I guess upgrading the 
synology's with something that has 10GE would help as well.


Thanks,

Gerald


___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] NFS Storage issue

[Gianni Milo]

Hello

I have a Synology with High Availability serving NFS storage to Proxmox.
> A couple of months ago, this started happening:
>
> Apr 24 12:32:51 proxmox-1 pvestatd[3298]: unable to activate storage
> 'NAS' - directory '/mnt/pve/NAS' does not exist or is unreachable
> Apr 24 13:08:00 proxmox-1 pvestatd[3298]: unable to activate storage
> 'NAS' - directory '/mnt/pve/NAS' does not exist or is unreachable
>
>
It appears that the NFS storage target was unreachable during that time...


> It affecting backups and VM speeds. Any idea what is causing this?


I would guess that the network link used for accessing the NFS target is
getting saturated. This sometimes can be caused by running backup jobs,
and/or other tasks like VMs demanding high i/o to that destination.

There are no errors in the Synology logs, and the storage stays mounted and
> accessible.
>

You mean that it stays accessible after the backups are finished (or
failed) and after the i/o operations return to the normal levels ?
Do you recall if there was any of the above happening during that time ?


> Any ideas what's going on?
>

I would set bandwidth limits either on the storage target or on the backup
jobs. See documentation for details on how to achieve this.
Even better, separate VMs from the backups if that's possible (i.e use
different storage/network links).

G.
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] proxmox does not support Ubuntu 18.04 desktop installation

[Alain Péan]

Le 25/04/2019 à 12:47, Friedrich Ramberger a écrit :

Try to change "Hardware" "Display" from "Default" to "VMware compatible"


I would say better use Spice. For Hard disk and Network, use VirtIO 
drivers. They are supported by default by the linux kernel.


I installed several Ubuntu 18.04 VMs (server version), without problem 
(it was Proxmox 5.2, now upgraded to 5.4).


Alain

--
Administrateur Système/Réseau
C2N Centre de Nanosciences et Nanotechnologies (UMR 9001)
Boulevard Thomas Gobert (ex Avenue de La Vauve), 91920 Palaiseau
Tel : 01-70-27-06-88 Bureau A255

___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] proxmox does not support Ubuntu 18.04 desktop installation

[Barve Sunita]

Oh thank you that worked.

I also wish to know if I upgrade my server to latest version of proxmox will it 
work properly? Should I upgrade or continue as it is.

reg

Sunita Barve

On 04/25/19 04:18 PM, Friedrich Ramberger   wrote: 
> 
> Try to change "Hardware" "Display" from "Default" to "VMware compatible" 
> 
> > On April 25, 2019 at 11:23 AM Barve Sunita  wrote:
> > 
> > 
> > Dear all
> > 
> > We have installed proxmox 5.0.030 on our server . We could create virtual 
> > machine of Ubuntu 16.04 and two of our vm's are running on our server but 
> > if ubuntu 18.04 is installed the screen gets locked with following
> > 
> > /dev/sda1: clean, 137668/6553600 files, 2086595/26213888 blocks
> > 
> > 
> > 
> > Can someone help to sort out this issue so that we can use ubuntu 18.04 
> > without any errors. 
> > 
> > 
> > -- 
> > with reg
> > 
> > Dr. Sunita Barve/ डॉ. सुनीता बर्वे 
> > Senior Technical Officer/वरिष्ट तकनिकी अधिकारी 
> > KRC/Library/पुस्तकालय 
> > CSIR-National Chemical Laboratory/CSIR - नेशनल केमिकल लेबोरेटरी, पुणे 
> > Dr. Homi Bhabha Road/डॉ. होमी भाभा रोड 
> > Pune 411 008/पुणे ४११००८ 
> > Phone: 020-25902039/दूरभाष : ०२०-२५९०२०३९ 
> > Email : sa.ba...@ncl.res.in /इमेल : sa.ba...@ncl.res.in
> > ___
> > pve-user mailing list
> > pve-user@pve.proxmox.com
> > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> 
> 
-- 
with reg

Dr. Sunita Barve/ डॉ. सुनीता बर्वे 
Senior Technical Officer/वरिष्ट तकनिकी अधिकारी 
KRC/Library/पुस्तकालय 
CSIR-National Chemical Laboratory/CSIR - नेशनल केमिकल लेबोरेटरी, पुणे 
Dr. Homi Bhabha Road/डॉ. होमी भाभा रोड 
Pune 411 008/पुणे ४११००८ 
Phone: 020-25902039/दूरभाष : ०२०-२५९०२०३९ 
Email : sa.ba...@ncl.res.in /इमेल : sa.ba...@ncl.res.in
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] proxmox does not support Ubuntu 18.04 desktop installation

[Friedrich Ramberger]

Try to change "Hardware" "Display" from "Default" to "VMware compatible" 

> On April 25, 2019 at 11:23 AM Barve Sunita  wrote:
> 
> 
> Dear all
> 
> We have installed proxmox 5.0.030 on our server . We could create virtual 
> machine of Ubuntu 16.04 and two of our vm's are running on our server but if 
> ubuntu 18.04 is installed the screen gets locked with following
> 
> /dev/sda1: clean, 137668/6553600 files, 2086595/26213888 blocks
> 
> 
> 
> Can someone help to sort out this issue so that we can use ubuntu 18.04 
> without any errors. 
> 
> 
> -- 
> with reg
> 
> Dr. Sunita Barve/ डॉ. सुनीता बर्वे 
> Senior Technical Officer/वरिष्ट तकनिकी अधिकारी 
> KRC/Library/पुस्तकालय 
> CSIR-National Chemical Laboratory/CSIR - नेशनल केमिकल लेबोरेटरी, पुणे 
> Dr. Homi Bhabha Road/डॉ. होमी भाभा रोड 
> Pune 411 008/पुणे ४११००८ 
> Phone: 020-25902039/दूरभाष : ०२०-२५९०२०३९ 
> Email : sa.ba...@ncl.res.in /इमेल : sa.ba...@ncl.res.in
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Windows Server 2003

[David Lawley]

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,  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@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

[PVE-User] proxmox does not support Ubuntu 18.04 desktop installation

[Barve Sunita]

Dear all

We have installed proxmox 5.0.030 on our server . We could create virtual 
machine of Ubuntu 16.04 and two of our vm's are running on our server but if 
ubuntu 18.04 is installed the screen gets locked with following

/dev/sda1: clean, 137668/6553600 files, 2086595/26213888 blocks



Can someone help to sort out this issue so that we can use ubuntu 18.04 without 
any errors. 


-- 
with reg

Dr. Sunita Barve/ डॉ. सुनीता बर्वे 
Senior Technical Officer/वरिष्ट तकनिकी अधिकारी 
KRC/Library/पुस्तकालय 
CSIR-National Chemical Laboratory/CSIR - नेशनल केमिकल लेबोरेटरी, पुणे 
Dr. Homi Bhabha Road/डॉ. होमी भाभा रोड 
Pune 411 008/पुणे ४११००८ 
Phone: 020-25902039/दूरभाष : ०२०-२५९०२०३९ 
Email : sa.ba...@ncl.res.in /इमेल : sa.ba...@ncl.res.in
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Windows Server 2003

[Thomas Lamprecht]

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,  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@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user