Re: [PVE-User] sbin/unconfigured.sh
I tried proxdebug. No extra messages are generated after the network has initialised. There is no log in /tmp folder ? Has the log moved? How do I run xinit? Where is it? Do you mean init? If I run this it says must be run as PID 1 - how can I fix this (sorry, I am not a linux guru!) On 19 May 2017 at 09:12, Fabian Grünbichler <f.gruenbich...@proxmox.com> wrote: > On Fri, May 19, 2017 at 08:28:17AM +0100, Steve wrote: > > Thanks > > I tried that. > > I made a new .sh from the portion of the initrd that mounts all the > > squashfs files and runs unconfigured.sh. > > It seems to almost work, but it gets to Detecting network settings... > done > > and then says > > \nInstallation aborted - unable to continue > > > > any ideas why? > > > > boot it with "proxdebug" as part of the kernel cmdline and examine the > logs. you can also manually run "xinit" in the debug shell to restart > the installer from the debug shell. > > ___ > 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] sbin/unconfigured.sh
I just found a way to get it to work by modifying the grub menu and add lvm2root=/dev/sdX4 where sdX4 is a partition on the USB drive which points directly to the ISO file. So I am booting from the ISO (mapped to the BIOS device (0xff) in grub4dos) which boots to the grub2 menu and then I add the lvm2root parameter. The strange thing is that if I boot from a FAT32 flat-file system and have the ISO mapped to a partition in exactly the same way, the init script fails. On 19 May 2017 at 12:46, Fabian Grünbichler <f.gruenbich...@proxmox.com> wrote: > On Fri, May 19, 2017 at 10:27:20AM +0100, Steve wrote: > > If I type xinit it says /bin/sh: xinit: not found > > > > I am the author of easy2boot which is a USB multiboot tool to allow > people > > to boot from 100's of different ISOs (or images) all from one USB stick. > > I have been asked by a user to get proxmox 4 working. > > 3.2 works because I can run the unconfigured.sh from the command line > > > > http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos- > to-easy2boot.html > > http://www.easy2boot.com > > > > I tried setting proxdebug and root=/dev/sdb1 or lvm2root=/dev/sdb1 to > get > > it to mount the FAT32 partition to /mnt. I do not need to manually use > any > > mount commands, it just automatically runs init but this causes an early > > error message of > > mount: mounting /dev/sdb1 on /mnt failed: Invalid argument > > but if I use the mount command I can see that /mnt is present as a vfat > > /dev/sdb1 > > If I press CTRL+D to continue, it fails in the exact same place with > > Installation aborted - unable to continue. > > Note that this is not using my script at all, just the original init > script > > - I have not broken into the boot process because it picks up the > lvm2root > > parameter. > > > > I am so *near*, yet I just cannot get the unconfigured.sh script to run > in > > this way... > > > > thanks for your help. > > Steve > > I just did a quick test run using Grub: > > loopback test PATHTOISO > linux (test)/boot/linux26 proxdebug ramdisk_size=16777216 rw > initrd (test)/boot/initrd.img > boot > > drops me into the initrd debug shell > > if I do the following (major/minor depend on your disk configuration, > check /sys/class/block/XXX/dev where XXX is your usb partition where > the iso is) > > mknod /tmp/usbdev b MAJOR MINOR > mkdir /tmp/usbmnt > mount /tmp/usbdev /tmp/usbmnt > mount /tmp/usbmnt/PATHTOISO /mnt > > followed by lines 294ff of the init script launch the graphical > installer (although the resolution is messed up - probably because I did > not bother to change any of the graphic stuff in Grub), and I am able to > complete the installation.. > > so I think it must be something in your environment / setup. > > (note that there are TWO debug shells, one in the initrd with very > limited commands, and one in the installer environment with access to a > lot more tools - a quick test is to run something like "lsblk", since > that only exists in the latter environment ;). maybe your switch to the > installer environment did not work, and you are still in the initrd > shell? that would explain why you can't execute "xinit") > > ___ > 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] sbin/unconfigured.sh
See the blog post (end of page) http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos-to-easy2boot.html On 19 May 2017 at 12:51, Steve <st...@easy2boot.com> wrote: > I just found a way to get it to work by modifying the grub menu and add > lvm2root=/dev/sdX4 > > where sdX4 is a partition on the USB drive which points directly to the > ISO file. > So I am booting from the ISO (mapped to the BIOS device (0xff) in > grub4dos) which boots to the grub2 menu and then I add the lvm2root > parameter. > > The strange thing is that if I boot from a FAT32 flat-file system and have > the ISO mapped to a partition in exactly the same way, the init script > fails. > > > > On 19 May 2017 at 12:46, Fabian Grünbichler <f.gruenbich...@proxmox.com> > wrote: > >> On Fri, May 19, 2017 at 10:27:20AM +0100, Steve wrote: >> > If I type xinit it says /bin/sh: xinit: not found >> > >> > I am the author of easy2boot which is a USB multiboot tool to allow >> people >> > to boot from 100's of different ISOs (or images) all from one USB stick. >> > I have been asked by a user to get proxmox 4 working. >> > 3.2 works because I can run the unconfigured.sh from the command line >> > >> > http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos-to- >> easy2boot.html >> > http://www.easy2boot.com >> > >> > I tried setting proxdebug and root=/dev/sdb1 or lvm2root=/dev/sdb1 to >> get >> > it to mount the FAT32 partition to /mnt. I do not need to manually use >> any >> > mount commands, it just automatically runs init but this causes an early >> > error message of >> > mount: mounting /dev/sdb1 on /mnt failed: Invalid argument >> > but if I use the mount command I can see that /mnt is present as a vfat >> > /dev/sdb1 >> > If I press CTRL+D to continue, it fails in the exact same place with >> > Installation aborted - unable to continue. >> > Note that this is not using my script at all, just the original init >> script >> > - I have not broken into the boot process because it picks up the >> lvm2root >> > parameter. >> > >> > I am so *near*, yet I just cannot get the unconfigured.sh script to run >> in >> > this way... >> > >> > thanks for your help. >> > Steve >> >> I just did a quick test run using Grub: >> >> loopback test PATHTOISO >> linux (test)/boot/linux26 proxdebug ramdisk_size=16777216 rw >> initrd (test)/boot/initrd.img >> boot >> >> drops me into the initrd debug shell >> >> if I do the following (major/minor depend on your disk configuration, >> check /sys/class/block/XXX/dev where XXX is your usb partition where >> the iso is) >> >> mknod /tmp/usbdev b MAJOR MINOR >> mkdir /tmp/usbmnt >> mount /tmp/usbdev /tmp/usbmnt >> mount /tmp/usbmnt/PATHTOISO /mnt >> >> followed by lines 294ff of the init script launch the graphical >> installer (although the resolution is messed up - probably because I did >> not bother to change any of the graphic stuff in Grub), and I am able to >> complete the installation.. >> >> so I think it must be something in your environment / setup. >> >> (note that there are TWO debug shells, one in the initrd with very >> limited commands, and one in the installer environment with access to a >> lot more tools - a quick test is to run something like "lsblk", since >> that only exists in the latter environment ;). maybe your switch to the >> installer environment did not work, and you are still in the initrd >> shell? that would explain why you can't execute "xinit") >> >> ___ >> 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] sbin/unconfigured.sh
If I type xinit it says /bin/sh: xinit: not found I am the author of easy2boot which is a USB multiboot tool to allow people to boot from 100's of different ISOs (or images) all from one USB stick. I have been asked by a user to get proxmox 4 working. 3.2 works because I can run the unconfigured.sh from the command line http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos-to-easy2boot.html http://www.easy2boot.com I tried setting proxdebug and root=/dev/sdb1 or lvm2root=/dev/sdb1 to get it to mount the FAT32 partition to /mnt. I do not need to manually use any mount commands, it just automatically runs init but this causes an early error message of mount: mounting /dev/sdb1 on /mnt failed: Invalid argument but if I use the mount command I can see that /mnt is present as a vfat /dev/sdb1 If I press CTRL+D to continue, it fails in the exact same place with Installation aborted - unable to continue. Note that this is not using my script at all, just the original init script - I have not broken into the boot process because it picks up the lvm2root parameter. I am so *near*, yet I just cannot get the unconfigured.sh script to run in this way... thanks for your help. Steve On 19 May 2017 at 10:04, Fabian Grünbichler <f.gruenbich...@proxmox.com> wrote: > On Fri, May 19, 2017 at 09:40:54AM +0100, Steve wrote: > > I tried proxdebug. No extra messages are generated after the network has > > initialised. > > There is no log in /tmp folder ? Has the log moved? > > > > How do I run xinit? Where is it? > > Do you mean init? If I run this it says must be run as PID 1 - how can I > > fix this (sorry, I am not a linux guru!) > > > > just type "xinit" in the debug shell. but if you are not comfortable > with this kind of debugging, you might be better off just (temporarily) > "sacrificing" a thumb drive for the PVE installer instead of trying to > get this non-standard way to boot it to work ;) > > I hope to fix the initrd during the 5.x release cycleto to allow booting > in some kind of loopback mode, but it's a low priority item on my todo > list.. > > ___ > 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
[PVE-User] sbin/unconfigured.sh
In version 3.2 ISO there was this script to start an install. This file is not in recent versions. Is there an equivalent way to start an install with v4.4 or any other recent version? Thanks Steve ___ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Re: [PVE-User] sbin/unconfigured.sh
One last hurdle! instead of /dev/sda1 I want to use /dev/disk/by-uuid/XXX because I don't know how many disks there are in the system but it does not work - I presume that /dev/disk/by-uuid does not yet exist at the time the init script is running? Is there any other way to reference the partition? I am guessing that by-label will not work either?... Steve On 19 May 2017 at 10:04, Fabian Grünbichler <f.gruenbich...@proxmox.com> wrote: > On Fri, May 19, 2017 at 09:40:54AM +0100, Steve wrote: > > I tried proxdebug. No extra messages are generated after the network has > > initialised. > > There is no log in /tmp folder ? Has the log moved? > > > > How do I run xinit? Where is it? > > Do you mean init? If I run this it says must be run as PID 1 - how can I > > fix this (sorry, I am not a linux guru!) > > > > just type "xinit" in the debug shell. but if you are not comfortable > with this kind of debugging, you might be better off just (temporarily) > "sacrificing" a thumb drive for the PVE installer instead of trying to > get this non-standard way to boot it to work ;) > > I hope to fix the initrd during the 5.x release cycleto to allow booting > in some kind of loopback mode, but it's a low priority item on my todo > list.. > > ___ > 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] sbin/unconfigured.sh
I think the problem is with grub4dos.
If I use this menu from a FAT32 USB drive
title ProxMox lvm2root=sda1
kernel /boot/linux26 ro ramdisk_size=16777216 lvm2root=/dev/sda1 rw quiet
splash=silent
initrd /boot/initrd.img
then it does not work and I get the Installation aborted message
but if I use the same menu in grub2 from the same drive,
menuentry 'Install Proxmox VE sda1' --class debian --class gnu-linux
--class gnu --class os {
linux /boot/linux26 ro ramdisk_size=16777216 lvm2root=/dev/sda1 rw quiet
splash=silent
initrd /boot/initrd.img
}
then it works and loads the installer GUI.
I also note that it does not change to 1024x768 when booting via grub4dos,
so I added
vga=791
and now it works!!!
On 19 May 2017 at 12:46, Fabian Grünbichler <f.gruenbich...@proxmox.com>
wrote:
> On Fri, May 19, 2017 at 10:27:20AM +0100, Steve wrote:
> > If I type xinit it says /bin/sh: xinit: not found
> >
> > I am the author of easy2boot which is a USB multiboot tool to allow
> people
> > to boot from 100's of different ISOs (or images) all from one USB stick.
> > I have been asked by a user to get proxmox 4 working.
> > 3.2 works because I can run the unconfigured.sh from the command line
> >
> > http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos-
> to-easy2boot.html
> > http://www.easy2boot.com
> >
> > I tried setting proxdebug and root=/dev/sdb1 or lvm2root=/dev/sdb1 to
> get
> > it to mount the FAT32 partition to /mnt. I do not need to manually use
> any
> > mount commands, it just automatically runs init but this causes an early
> > error message of
> > mount: mounting /dev/sdb1 on /mnt failed: Invalid argument
> > but if I use the mount command I can see that /mnt is present as a vfat
> > /dev/sdb1
> > If I press CTRL+D to continue, it fails in the exact same place with
> > Installation aborted - unable to continue.
> > Note that this is not using my script at all, just the original init
> script
> > - I have not broken into the boot process because it picks up the
> lvm2root
> > parameter.
> >
> > I am so *near*, yet I just cannot get the unconfigured.sh script to run
> in
> > this way...
> >
> > thanks for your help.
> > Steve
>
> I just did a quick test run using Grub:
>
> loopback test PATHTOISO
> linux (test)/boot/linux26 proxdebug ramdisk_size=16777216 rw
> initrd (test)/boot/initrd.img
> boot
>
> drops me into the initrd debug shell
>
> if I do the following (major/minor depend on your disk configuration,
> check /sys/class/block/XXX/dev where XXX is your usb partition where
> the iso is)
>
> mknod /tmp/usbdev b MAJOR MINOR
> mkdir /tmp/usbmnt
> mount /tmp/usbdev /tmp/usbmnt
> mount /tmp/usbmnt/PATHTOISO /mnt
>
> followed by lines 294ff of the init script launch the graphical
> installer (although the resolution is messed up - probably because I did
> not bother to change any of the graphic stuff in Grub), and I am able to
> complete the installation..
>
> so I think it must be something in your environment / setup.
>
> (note that there are TWO debug shells, one in the initrd with very
> limited commands, and one in the installer environment with access to a
> lot more tools - a quick test is to run something like "lsblk", since
> that only exists in the latter environment ;). maybe your switch to the
> installer environment did not work, and you are still in the initrd
> shell? that would explain why you can't execute "xinit")
>
> ___
> 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] sbin/unconfigured.sh
Thanks for the quick reply. I am booting from the ISO file itself which is on a multiboot USB drive. In previous versions, you could boot to the shell, mount the ISO as /mnt and then start the install by running unconfigured.sh. So basically, if I boot to the shell, how can I start the install from the contents of the CD/ISO. On 18 May 2017 at 19:04, Uwe Sauter <uwe.sauter...@gmail.com> wrote: > Don't know what your situation is but there is a wiki page [1] that > describes the installation of Proxmox on top of an > existing Debian. > > [1] https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie > > Am 18.05.2017 um 19:55 schrieb Steve: > > In version 3.2 ISO there was this script to start an install. > > This file is not in recent versions. > > Is there an equivalent way to start an install with v4.4 or any other > > recent version? > > Thanks > > Steve > > ___ > > 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 > ___ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Re: [PVE-User] sbin/unconfigured.sh
Thanks I tried that. I made a new .sh from the portion of the initrd that mounts all the squashfs files and runs unconfigured.sh. It seems to almost work, but it gets to Detecting network settings... done and then says \nInstallation aborted - unable to continue any ideas why? On 19 May 2017 at 07:34, Fabian Grünbichler <f.gruenbich...@proxmox.com> wrote: > On Thu, May 18, 2017 at 07:08:36PM +0100, Steve wrote: > > Thanks for the quick reply. > > I am booting from the ISO file itself which is on a multiboot USB drive. > > In previous versions, you could boot to the shell, mount the ISO as /mnt > > and then start the install by running unconfigured.sh. > > > > So basically, if I boot to the shell, how can I start the install from > the > > contents of the CD/ISO. > > > > you need to mount the contained squashfs files in the right order on the > right places, make an overlayfs and then bind mount the iso into that. > then you can chroot and run the unconfigured.sh script. basically do all > the steps that the initrd contained on the iso does ;) > > ___ > 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] sbin/unconfigured.sh
P.S. As an experiment, I even inserted a dd'd flash drive containing the proxmox ISO (which works if I boot to it) and then booted from my multiboot USB drive to the shell and then mounted /mnt as the flash drive mount /dev/sdc /mnt then I ran the modified script. I gave the same fail message. So that seems to indicate that something is wrong with the script or environment when I run the script? The script I run starts with if [ -f /mnt/pve-installer.squashfs ]; then echo this is a Proxmox VE installation CD if ! mount -t squashfs -o ro,loop /mnt/pve-base.squashfs /mnt/.pve-base; then debugsh_err_reboot "mount pve-base.squashfs failed" fi any ideas what is not set up before this? Steve On 19 May 2017 at 07:34, Fabian Grünbichler <f.gruenbich...@proxmox.com> wrote: > On Thu, May 18, 2017 at 07:08:36PM +0100, Steve wrote: > > Thanks for the quick reply. > > I am booting from the ISO file itself which is on a multiboot USB drive. > > In previous versions, you could boot to the shell, mount the ISO as /mnt > > and then start the install by running unconfigured.sh. > > > > So basically, if I boot to the shell, how can I start the install from > the > > contents of the CD/ISO. > > > > you need to mount the contained squashfs files in the right order on the > right places, make an overlayfs and then bind mount the iso into that. > then you can chroot and run the unconfigured.sh script. basically do all > the steps that the initrd contained on the iso does ;) > > ___ > 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] sbin/unconfigured.sh
Here is final grub4dos menu for use with Easy2Boot which works iftitle [if exist $HOME$/proxmox-ve_4.4-eb2d6f1e-2.iso] proxmox 4.4\n You must enter the correct USB name. set ISO=proxmox-ve_4.4-eb2d6f1e-2.iso set ldisk= errorcheck off if not exist ldisk geometry (hd9) > nul && set ldisk=sdj4 if not exist ldisk geometry (hd8) > nul && set ldisk=sdi4 if not exist ldisk geometry (hd7) > nul && set ldisk=sdh4 if not exist ldisk geometry (hd6) > nul && set ldisk=sdg4 if not exist ldisk geometry (hd5) > nul && set ldisk=sdf4 if not exist ldisk geometry (hd4) > nul && set ldisk=sde4 if not exist ldisk geometry (hd3) > nul && set ldisk=sdd4 if not exist ldisk geometry (hd2) > nul && set ldisk=sdc4 if not exist ldisk geometry (hd1) > nul && set ldisk=sdb4 echo echo -e $[0104] I guess partition 4 of the USB drive will be %ldisk% echo set /p ldisk=Enter linux device name for USB drive (ptn4), e.g. sdb4 or sdc4 (ESC=%ldisk%) : echo pause --wait=3 Will use /dev/%ldisk% set NOSUG=1 set redir=> nul /%grub%/QRUN.g4b $HOME$/%ISO% kernel /boot/linux26 ro ramdisk_size=16777216 lvm2root=/dev/%ldisk% vga=791 rw initrd /boot/initrd.img boot Thanks for your help . ___ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
[PVE-User] Problem with vnc and arrow keys
Hello, if we try to configure a virtual machine via vnc-console, the arrow keys and F1 to F8 aren't working. We can not use them on our Linux guests. Our Windows guests are working properly. pve-version: 2.2-31, It is the same for all three nodes. Greetings Steve ___ pve-user mailing list pve-user@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Re: [PVE-User] Problem with vnc and arrow keys
Hello, we are trying to connect to linux containers not kvm's. We found that the variable TERM becomes linux and not xterm. A temporary fix is: * connecting via vnc * and then typing export TERM=xterm How can we fix the cause of this? Greetings Steve ___ pve-user mailing list pve-user@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Re: [PVE-User] Backup retention policy
If it's just the rotation part you need, you could handle that on the backup server side with a short script, copying the dailies into weekly folders, weeklies into monthly folders, etc. I know, rolling a custom script is something some want to avoid, but this particular script would be very straight forward. I've been using this guy's strategy for years... http://www.mikerubel.org/computers/rsync_snapshots/ ...and now that is rolled into a utility called rsnapshot (www.rsnapshot.org). In this case, you would only use to rotate, though, not actually back up. On Fri, May 17, 2013 at 6:33 AM, admin extremeshok.com ad...@extremeshok.com wrote: Yes and delta backups. Ie.. full backup every week, then a delta backup every day. Thanks On 2013-05-16 01:58 PM, Fabrizio Cuseo wrote: Hello people. I am seeing that Proxmox misses a very important features about backup retention. An example could be: - Last week, N backup daily - Last month, N backup weekly - Last year, N backup monthly So, with a total of 9 backups, I could have: - The last 3 daily backups - The last 3 weekly backups - The last 3 montly backups Another nice feature could be a pool selection of VM's to backup, so adding a VM in the pool will insert the VM in the backup schedule. Also the machine name in the backup file will be useful (i have already read about it in the mailing list). Thanks, Fabrizio ___ pve-user mailing list pve-user@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user -- __ Steve Audia w +1(412)268-1438 Director of Information Technology sau...@cmu.edu Carnegie Mellonwww.etc.cmu.edu Entertainment Technology Center@cmuetc __ ___ pve-user mailing list pve-user@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Re: [PVE-User] Pve 4.0
Jérémy Carnus jeremy@... writes:
Hello all,
I tried the new proxmox 4.0 including lxc.
I am 2 questions on it:
- I saw it not possible to resize disk of an lxc container after
creation, is it a restriction ?
- Trying to migrate a vz container to a lxc container using backup
/
restore leads me to a TASK ERROR: Insecure dependency in unlink
while running with -T switch at /usr/share/perl5/PVE/Tools.pm line
187. when restoring the zip archive in the pve4.0
Thanks--
Jérémy Carnus
body {font-family: Calibri;color:#17365E;}
div
Hello all,brbr
I tried the new proxmox 4.0 including lxc.br
I am 2 questions on it:br
- I saw it not possible to resize disk of an lxc container after
creation, is it a restriction ?br
- Trying to migrate a vz container to a lxc container using backup
/
restore leads me to a TASK ERROR: Insecure dependency in unlink
while running with -T switch at /usr/share/perl5/PVE/Tools.pm line
187. when restoring the zip archive in the pve4.0brbr
Thanksbrbrbrdiv class=moz-signature-- br
Jérémy Carnus
body {font-family: Calibri;color:#17365E;} /div
/div
Hey Jérémy,
Did you have any luck in migrating openvz to lxc ? I'm going from a
host running 3.4 to 4.0 and get the same issue:
TASK ERROR: Insecure dependency in unlink while running with -T switch
at /usr/share/perl5/PVE/Tools.pm line 187.
Cheers and good luck I've been searching around for a fix :)
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
