why do you need OMV2? what is you final goal for the setup?
and it is not as simple to install webvirtmanager on OMV as it seams.
I have tried and it is quiet a quest.
and even though IOMMU may not be needed, you still need virtualization extensions supported by the CPU for KVM to work.
But what I don't understand from the guide here in this forum: How can I access the webwirtmgr GUI? Just tipping on my laptops browser: ip-of-server:port-of-webvirtmgr ?
yes that is the proper way, however you might need to enable ports on OMV firewall to make it work.
I do not remember exactly port numbers but I had open ports 8000-9000 and 16000-17000
webvirtmanager GUI uses port 8000 or 8080 and also port 16509 I think for noVNC console
so to get to the GUI you would use http://<your server ip>:8000 or 8080
Opening Ports are only needed if I want to acess from over the internet i thougt?
yes it but true but we are not opening ports on your firewall/router , we are opening port on OMV firewall.
systemd is secure by default, so all ports other than most common one like 80,443.. are blocked.
in order for webvirtmanager to work you need to open them on OMV.
if you would configuring access from outside you would need to do the same on OMV AND on your router/firewall box
systemd is secure by default, so all ports other than most common one like 80,443.. are blocked.
Um no. systemd doesn't block ports (iptables does) and no ports are blocked on a default OMV install.
well in that case I do not know why I had to create ACCEPT rules for port range 8000-8500 and 16000-16800 when I tried to setup KVM + webvirtmanager on OMV3.0 last time I tested that.
until I did that I could not get to to virtmanager GUI and open noVNC console from the GUI once I done that.
we service was running but webpage said connection refused. on the GUI part
and on console it said access denied to the node or something like that.
once I added the rules in OMV firewall tab all worked as expected.
I do not remember now but I think I had to reboot the server after adding rule, but I might be wrong on that one.
Not sure. Did you have any firewall rules before that? I setup webvirtmanager following luxflow's guide and didn't have to create any firewall rules. I never use firewall rules on my OMV boxes. I let my router do that work.
nope, fresh omv 3.0 install.
run all updates etc.
install backport kernel but not boot into it.
well, here are the ports open on essentially fresh omv install.
the only ports opened in addition to normal are "10000" for webmin and "18083" for virtualbox
and
there are not ports in 8000-8500 range or 16000-16800 range.
Frankly I might do the setup a new some time next week and see if it was just a glitch the last time.
but I think run all under proxmox is a good option. so not sure if I want to go this rout myself now.
netstat -lntup | egrep 'Proto|LISTEN'
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:53551 0.0.0.0:* LISTEN 1245/rpc.mountd
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1029/rpcbind
tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN 1428/perl
tcp 0 0 0.0.0.0:44561 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1057/sshd
tcp 0 0 0.0.0.0:855 0.0.0.0:* LISTEN 1138/rpc.rquotad
tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN 2069/0
tcp 0 0 0.0.0.0:46107 0.0.0.0:* LISTEN 1245/rpc.mountd
tcp 0 0 0.0.0.0:45019 0.0.0.0:* LISTEN 1038/rpc.statd
tcp 0 0 127.0.0.1:2812 0.0.0.0:* LISTEN 1251/monit
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 1420/smbd
tcp 0 0 0.0.0.0:45245 0.0.0.0:* LISTEN 1245/rpc.mountd
tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:18083 0.0.0.0:* LISTEN 1252/vboxwebsrv
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 1420/smbd
tcp6 0 0 :::39887 :::* LISTEN 1038/rpc.statd
tcp6 0 0 :::111 :::* LISTEN 1029/rpcbind
tcp6 0 0 :::80 :::* LISTEN 1293/nginx -g daemo
tcp6 0 0 :::21 :::* LISTEN 1393/proftpd: (acce
tcp6 0 0 :::22 :::* LISTEN 1057/sshd
tcp6 0 0 ::1:6010 :::* LISTEN 2069/0
tcp6 0 0 :::46811 :::* LISTEN -
tcp6 0 0 :::445 :::* LISTEN 1420/smbd
tcp6 0 0 :::37793 :::* LISTEN 1245/rpc.mountd
tcp6 0 0 :::2049 :::* LISTEN -
tcp6 0 0 :::51491 :::* LISTEN 1245/rpc.mountd
tcp6 0 0 :::45771 :::* LISTEN 1245/rpc.mountd
tcp6 0 0 :::139 :::* LISTEN 1420/smbdA service won't listen on every port in the range it uses. Most services listen on one port and transfer you to another port once you make the connection. So, unless there are connections to one of those ports, netstat won't show them. That doesn't mean it is blocked.
what can I say, it worked last time for me.
if I have some time I will run the setup again and see.
Not at the moment. I do testing in VM running on my win10 hyper-v. I had re installed the whole thing after testing.
As on how, I just created a rule in firewall tab to accept on ports I want.
Sorry do not have time right now. Might get some free time next week so will re-do the set-up again
Sent from my SGH-T889 using Tapatalk
ok everybody,
I had 40 min free today so I did a full test run on this one following the original guide.
FIY :I remember that yes if you run locally you do not need any firewall rules. you just setup a localhost connection to use with webvirtmanager...
here are my steps :
Step 1. install Debian 8 and run all updates
Step 2. install OMV using
echo "deb http://packages.openmediavault.org/public erasmus main" > /etc/apt/sources.list.d/openmediavault.list
apt-get update
apt-get install openmediavault-keyring postfix
apt-get update
apt-get install openmediavault
omv-initsystemStep 3 . on WebGUI update all info as needed, Admin password, Network settings, repo selection etc.
run updates
Step 4 install omv-extras
Step 5. do KVM-webvirtmanager setup as per how-to
Step 6 DO NOT FORGET TO change "/var/www/webvirtmgr/conf/gunicorn.conf.py" to fix the port
I could not figure out the SSH setup yet. so I change the port
Step 7 reboot
you should be able to login to WebVirtManager using <serveriIP>:8000
I think that what was OP issue. local port setting.
I think with proxmox you would see it as part oh host hardware, but I am not sure what would happen if you try to mount it on host. Either it will moint and drop it from VM or tell you that device not available.
Not really sure about how to adding second drive to host but I am sure it possible. My guess would be mount the drive on host and add it to the local storage. Repoint the image store to the new drive. Should be able to do all from ui.
Sent from my SGH-T889 using Tapatalk
To which part of my post belongs your first part? I'm a lil bit confused, maybe it is too late and I should go to bed..
Sorry I was responding from my phone and it is not very easy to quote properly there.
the first part of my response where relating to this :
If i passtrough the HDD to the guest, i still see it in blkid on host. Should I install HD-idle on the host?
the second part was about adding more drives for data storage.
What I mean with the second HDD: if I create a VM, it would be nice to give them some more space like virtual HDD container. Or does everyone stores their data on the bootdrive?
I haven't used Proxmox for a while so I am not sure how to do this. but I know it is possible.
no, not every one uses the boot drive to store vm data.
but I am not sure if data storage is a whole or nothing deal with Proxmox.
meaning can you have both locations or have to choose one and stick with it.
i.e. can you keep the default data store locations as is AND add another locations and us it as well.
the core location by default is in "/var/lib/vz/" that is on your boot drive obviously.
or you can add new data-store location and move all there.
Backups - /var/lib/vz/dump
ISOs - /var/lib/vz/template/iso
Images - /var/lib/vz/images
Templates - /var/lib/vz/template/cachehere some links I found for proxmox storage info
Proxmox Storage Model
Mastering Proxmox Book
it will work if you use LVM as file system, default case when you chose EXT4 or lower during install,
if you use ZFS on install you will need different process.
but essentially it would work.
all you really need is to add the disk to hardware, mount it and create a file system on it.
than just point the data store to the mount location.
i.e. basic process step by step as I see it based on all the how-to I read.
Step 1: install the drive or drives on host
Step 2: create file system on the drive(s). you can do this individually drive per drive
or use LVM, or ZFS to create a single pool.
FYI: if using ZFS, plan ahead for the size of the pool. as far as I know ZFS pools are not
expandable, or at least no easily. LVM or BTRFS is better in that regards.
Step 3: mount the drive/FS pool you created in Step 2 in fstab so it is mounted on reboot.
Step 4: using webUI add the new mount to data store indication what type of data it will store.
should work from there on.
again if you are using LVM (you choose anything other than ZFS during Proxmox install)
and assuming the Proxmox install, or you during install, have partitioned the boot drive into separate partition/Volume groups to begin to,
than you can(again based on many things I have found on google) setup specific Volume Group/Logival volumes per use and put the data stores on them
for example:
we have 4 basic locations used for storing data in Proxmox
0. VM config files - /etc/pve/qemu-server/
so, assuming we split the SSD onto 20GB - OS partition and 220GB data partition
and we also adding a 1TB data drive
PS>> you can not resize install partition on live system if you not using LVM and even that is
questionable. there might be ways to resize ZFS volume but I do not know.
here something that might be helpful.
we could create a LV(say VMDATA) to hold locations 0 and 1 on SSD
than we can create additional LV for backups, ISO, Templates. on the 1TB.
now we can maybe move all files from original folders in /var/lib/vz to this new LV locations and use simlinks to re-point the original folders to the LV.
or simply mount all of this LV in fstab and ad them as appropriate data store options in WebUI.
you might need to do some research on that one.
same would apply for ZFS and other FS but maybe with some extra steps here and there.
it will work if you use LVM as file system, default case when you chose EXT4 or lower during install,
if you use ZFS on install you will need different process.
but essentially it would work.
all you really need is to add the disk to hardware, mount it and create a file system on it.
than just point the data store to the mount location.
i.e. basic process step by step as I see it based on all the how-to I read.
Step 1: install the drive or drives on host
Step 2: create file system on the drive(s). you can do this individually drive per drive
or use LVM, or ZFS to create a single pool.
FYI: if using ZFS, plan ahead for the size of the pool. as far as I know ZFS pools are not
expandable, or at least no easily. LVM or BTRFS is better in that regards.
Step 3: mount the drive/FS pool you created in Step 2 in fstab so it is mounted on reboot.
Step 4: using webUI add the new mount to data store indication what type of data it will store.
should work from there on.
again if you are using LVM (you choose anything other than ZFS during Proxmox install)
and assuming the Proxmox install, or you during install, have partitioned the boot drive into separate partition/Volume groups to begin to,
than you can(again based on many things I have found on google) setup specific Volume Group/Logival volumes per use and put the data stores on them
for example:
we have 4 basic locations used for storing data in Proxmox
0. VM config files - /etc/pve/qemu-server/
so, assuming we split the SSD onto 20GB - OS partition and 220GB data partition
and we also adding a 1TB data drive
PS>> you can not resize install partition on live system if you not using LVM and even that is
questionable. there might be ways to resize ZFS volume but I do not know.
here something that might be helpful.
we could create a LV(say VMDATA) to hold locations 0 and 1 on SSD
than we can create additional LV for backups, ISO, Templates. on the 1TB.
now we can maybe move all files from original folders in /var/lib/vz to this new LV locations and use simlinks to re-point the original folders to the LV.
or simply mount all of this LV in fstab and ad them as appropriate data store options in WebUI.
you might need to do some research on that one.
same would apply for ZFS and other FS but maybe with some extra steps here and there.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!