From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 9C71F9DD33 for ; Sat, 28 Oct 2023 23:05:34 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 75F1A355F for ; Sat, 28 Oct 2023 23:05:34 +0200 (CEST) Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Sat, 28 Oct 2023 23:05:33 +0200 (CEST) Received: by mail-lf1-x134.google.com with SMTP id 2adb3069b0e04-5082a874098so2467749e87.3 for ; Sat, 28 Oct 2023 14:05:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698527126; x=1699131926; darn=lists.proxmox.com; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:reply-to:user-agent:mime-version:date :message-id:from:to:cc:subject:date:message-id:reply-to; bh=CSXfqLHfI4OMxHOWHOzqHBXOjWQ0DzT+52a+rGUKMpE=; b=ScJ9QlOQiHy9xPpObDvVou4J7VEI63kESx3gJVxvyt/GBS54fYIlmLpCKWCYngSUZs pg2qvjfGleWmL3I+L7fmK3UlHNsU3WvjzLGuuJl0HhCSWKnsQKr4++sHEDBrtGUMfxe7 hua5zKEzCMGQVgAl7/JC1TXYmp29EO89kkt2ogEE1XRdPjq2BDgQDchhaIOdFLqS/K3t coTiSaVELjUboVknBF2PbanWsQFW53slkEBfm0ka2cTecC8CApjwK1eJApqxwZKatZyJ CoAfgDOSz2Pz45rwNxSVqBYKp8/DyblPYfxhmFgzL5jSajMSMd7gZQMdB8UwrvafiNM/ fOoQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698527126; x=1699131926; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:reply-to:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=CSXfqLHfI4OMxHOWHOzqHBXOjWQ0DzT+52a+rGUKMpE=; b=Z2P/5kXfEcvrndSIJovAXCtxnO4D0PcPxKJD9SDQ8QBKUMgze1ixMbrcW8IEu4qZFe KjVPDIL97WKL4i/NuchBq/kx9bJB6fJA/9hK2KsPACtTirSXXKBJ6HI2gD0M0Vts/Rlw jpqpkJZHO8nmVUnNFv4rAcYCqG8MubfzgY9Zcjxeroe32AgUbafFgW5Oc82B8xZTjqNM cc0eo6ggtzj3jQEmYKVJKpv017Djk1JAZjDVL8h/JKypLH9CsEBQ/nMs7dwHRWNvSRW5 wFxYU+MYDYhqdeHmBSAhxOXfsZDbwC6jN4mHwN4ddacryOVVhI5e0bNuD7pjK+zJhzhu 8ftg== X-Gm-Message-State: AOJu0YzXf1ExX+8xQRxCF5qGsivCswYh3P6+r0dbzMvC7KygmvliwsH7 PjdAhRtn5eOBRqvNR1N98bI= X-Google-Smtp-Source: AGHT+IH96EhjSPoadHDK1W1tdfL3bvfoCW+PpWwQ9Xo759IhKX00V1g4xMpEERKtdNIsn+9ZKlyMbQ== X-Received: by 2002:a05:6512:3995:b0:509:fbf:f235 with SMTP id j21-20020a056512399500b005090fbff235mr1778343lfu.6.1698527126139; Sat, 28 Oct 2023 14:05:26 -0700 (PDT) Received: from ?IPV6:2a02:8070:a280:2d80:d5dc:1045:9cf8:2aa6? ([2a02:8070:a280:2d80:d5dc:1045:9cf8:2aa6]) by smtp.gmail.com with ESMTPSA id t5-20020a5d4605000000b0032f7fab0711sm1104049wrq.93.2023.10.28.14.05.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 28 Oct 2023 14:05:25 -0700 (PDT) Message-ID: <132cac12-2a65-44d3-8159-e2e8940cecae@gmail.com> Date: Sat, 28 Oct 2023 23:05:24 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Reply-To: uwe.sauter.de@gmail.com Content-Language: de-DE To: Oboe Lova , Proxmox VE user list References: <6af33ece-a8e7-41a5-91a0-d8d546deaba0@gmail.com> From: Uwe Sauter In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.130 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider KAM_NUMSUBJECT 0.5 Subject ends in numbers excluding current years RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [virtxxx.man, proxmox.com] Subject: Re: [PVE-User] Adding VEs and containers to 7.4 X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Oct 2023 21:05:34 -0000 Am 28.10.23 um 22:15 schrieb Oboe Lova: > Thanks Ewe, > > I am glad but surprised to hear from anyone on the list because my post was rejected by an auto-email from gitlab saying > it could not handle my message because "We could not tell what it was for.  Please use the web interface or post an > issue.  Do you know precisely what that might mean?  I could not sign up for the forum without a subscription. I think someone subscribed to this list with an email address that points to his/her Gitlab instance. When the list then tried to deliver my answer to said address it caused the error message. >  Anyway, I did know about 8.0-2 in the repository, which I burnt to a DVD  and tried first. Depending on your hardware you will have more fun using a USB stick where you put the ISO onto using the "dd" command. But that but quickly got me > out into the weeds. So I have not yet gone  back to 8.x to see if what I have learned so far will give me better > results.  Are you saying that I will have a chance to start the zfs install from the initial proxmox install with 8.x? > If so does zfs configuration include the 3 come later with the GUI or command line?  Does zfs raid come later with the > GUI or command line? Can I add a third disk formatted with zfs later as the wiki says, and what are the steps? In all of my installations of PVE (I started with PVE 6.x) I had no trouble selecting ZFS during installation. This picture (https://pve.proxmox.com/pve-docs/images/screenshot/pve-select-target-disk.png) shows how the installer should look. If this is not the case then your hardware might lack something… Are all disks recognized in the BIOS or when booting a Debian live system? If so, wipe them clean from all former filesystem and partition signatures using the "wipefs" tool. > I was trying to follow Andreas Spiess's (aka the guy with the Swiss accent) youtube video on setting up a home lab. He > was using 7.2 and the vid was recent. Most of my issues went away when I tried 7.4.  What I did not know at the time is > that either version requires UEFI boot or HHD icons are not shown on the web gui.; only the 3 working partitions show up > on the boot HDD.  I examined and deleted them on the /dev/sda  HDD to start over on a clean system may times. Just > yesterday I found some documentation that said GRUB boots give rise to disk mounting problems.  That made sense so I > tried UEFI boot and the HDD icons showed up on the server view. > I did navigate to the HELP page but only simple instructions were given and I could not establish a running VM by simply > following those HELP steps.  Through experimentation I got two 500 HDDs to show up as icons (pool candidates?) in the > gui.  I also got an iso image of bookworm to upload to VM storage from my laptop DVD drive to somewhere on pve.home. > What I don't understand now is how to get the image to completely install after launching with START command.  I did not > enable start on boot so I could reboot the node and crash out of the VM.  I did so because VM hangs do not respond to > STOP, HARD STOP, etc. With the VM stopped on node reboot I could at least remove it and start over. Given the age of you hardware (a quick search revealed that the notebook you are using has an Ivy Bridge generation Intel CPU which is now 11 years old) I suspect that your troubles come from the CPU that is selected for your VM. The Ivy Bridge chip probably does not have all features that the default emulated CPU ("x86-64-v2-AES") will propagate to the VM. When creating the VM configuration try to select CPU type "host" at the bottom of the list. > One question I have is why QEMU is optional. I'm not quite certain what you mean. QEMU started as a project that emulated certain CPUs in software. When hardware began to support virtualization out of the box the kernel-based virtual machine (KVM) allowed better performance and QEMU adopted the usage of KVM where possible. So when you nowerdays run a x86-64 VM on a x86-64 CPU you will use all the hardware virtualization if these features are not disabled in the BIOS. But if you run an ARM VM on a x86-64 CPU QEMU will still emulate the VM's CPU architecture in software. Do you actually mean libvirt? Libvirt is a project on top of different virtualization technologies and container runtimes that allows you to save a VMs configuration to a file. Libvirt will use QEMU and KVM under the hood. But in PVE libvirt is not used because the devs from Proxmox decided to talk directly to QEMU using their own framework. Isn't it needed for KVM or does the other gui method take over?  I am > referring to virtXXX.man which I previously tried on a direct to Debian QEMU-KVM install try.  When trying to prep for > Home Assistant direct to Debian Bookworm (as direct QEMU-KVM install) I downloaded the the QCOW2 file and tried QEMU to > prepare it for upload to my pve.   QEMU converted it to an img file which was not recognized by Debian or Proxmox. I > tried to do an import to disk from the node DVD drive but the gui would not recognize it; maybe from issues with grub boot. If you download VM images in the qcow2 format you will need to convert these images into the raw image file format. See "man qemu-img". The raw image then can be used as virtual HDD for the VM. >  Are you saying that I will have a chance to start the zfs (instead of ext 4?) install to boot disk from the initial > proxmox install with 8.x?  If so does zfs configuration come later with the GUI or command line?  Does zfs raid come > later with the GUI or command line? Do I add an optional third or fourth  third disk to zfs pool later as the wiki says, > or install the HDD before the initial node installation? Before going down further the debugging road I need you to familiarize yourself with the concepts of ZFS. Even if you succeed lateron to get more disks recognized you will be limited in your possibilities compared to when all disks are recognized during installation. (E.g. you cannot convert a ZFS RAID 1 pool into a ZFS RAIDZ2 pool.) My recommendation is: before trying out to install VMs make sure that your host system is running the way you want it to run. Regards, Uwe > Maybe one more try with 8.0-2 will be more straight forward?  Which log files will reveal problems, and where will they > be stored? > > Armed with the above info I ought to make better progress.  Your help is much appreciated. > > Vielen Danke, > > Chuck in Libby, MT USA > > > > On Sat, Oct 28, 2023 at 12:49 PM Uwe Sauter > wrote: > > Hi, > > don't know if you are aware that PVE 8.0 was released back in June? > > Also, there generally is a help button in the various menus and a documenation button left to the "create vm" and > "create ct" buttons. > > Regarding when to create a ZFS pool: usually you can do that during installation of PVE. You need to change the > filesystem and the disks used by the installer. If that is not the case with your setup there seems to be something > going wrong. > If you'd like to create a ZFS pool on an installed system go to "datacenter -> your server", then select "disks -> > ZFS". > You should be able to create a new pool **if** you have unused disks in your system. > > > Regards, > >         Uwe > > Am 28.10.23 um 18:13 schrieb Oboe Lova: > > Greetings to listers, > > > > I have installed 7.4 VE and am finding no success in installing guest > > images to what looks like a valid install, using the web gui at port 8006. > > Specifically, the best I can do is create a vm using  a windows 7 dvd in > > the node dvd drive and start an install session.  That runs for a while > > then stalls while I watch in a console.  After that using console and othere > > ways to stop, reset, etc the vm so I can remove it are  ignored, though the > > gui is still up and not frozen. Similar symptoms trying various Linux > > distro dvds, from either iso image or burned install disks.  I also fumbled > > around until I managed to upload an iso from laptop to a second internal > > hdd disk but I can’t find a way to load it to a new vm. > > > > Goal is homelab and a separate bookworm as VMs.   So what I obviously need > > is docs on definitions and caveats for each gui option in the web gui. > > Examples: how to create a vm from qcow2 image. Functionally what does  QEMU > > checkbox do since I get console either way?  I expect command line > > maneuvers will be required. > > > > I have read the current wiki and tried help screens but haven’t found > > anything that gives me a detailed recipe.    I would also like to use a > > three x 500 GB disk zfs raid but can’t find when  or where I do the zfs > > setup.  No install option on install except ext 4 partitons.   Dell XPS > >   8500 i7 16 GB ram 4 physical / 8 threads.   Allocating 2 cores with > > default lvms 2048 memory per vm. > > > > Tnx in advance > > _______________________________________________ > > pve-user mailing list > > pve-user@lists.proxmox.com > > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > >