Search results

thx a lot

Let me try this if the next node is available... just a few days far away

I just do see a difference between docu and gui process.... And my support engineer told me he created all manually and never via GUI. So may be nobody knows... this seems to be a working setup: auto vmbr250 allow-ovs vmbr250 iface vmbr250 inet manual ovs_type OVSBridge ovs_ports...

If this can be ignored why this is shown. ? Or should this be better asked at qemu forum ?

Which role should I assign or create for a user who is only allowed to use the get functions from the rest interface ? https://$APINODE:8006/api2/json/cluster/resources?type=node https://$APINODE:8006/api2/json/cluster/resources?type=vm would be enough. But he must see ALL VMs and ALL Nodes

so serial is working with qm terminal but how to use args to modify the chardev part proxmox creates -chardev 'socket,id=serial0,path=/var/run/qemu-server/384.serial0,server,nowait' do I have to configure the whole serial part as args lines ?

sorry wiki page found https://pve.proxmox.com/wiki/Serial_Terminal

[476392.185799] kvm [20583]: vcpu1 unhandled rdmsr: 0x60d [476392.185857] kvm [20583]: vcpu1 unhandled rdmsr: 0x3f8 [476392.185908] kvm [20583]: vcpu1 unhandled rdmsr: 0x3f9 [476392.185947] kvm [20583]: vcpu1 unhandled rdmsr: 0x3fa [476392.185992] kvm [20583]: vcpu1 unhandled rdmsr: 0x630...

It has nothing to do with vxlan. We just seperate a couple of testbeds containing real hw devices and vms over a company wide vlan network. We just got two vlans for our task. Therefore we use the outer vlan as VMAN and the inner one per testbed.

is there a waz to permanently connect a serial port to a vm? If possible can I create also some provide a telnet or ssh access to this serial line ? As result we like to have a telnet to see the linux vm upcoming on the serial interface via telnet from a different host.

HI, I use proxmox 4.4 if I create a ovs bridge the gui creates the interfaces part automatically and I can see the is just +auto vmbr251 +iface vmbr251 inet manual + ovs_type OVSBridge + ovs_ports eth1 but your documentation says https://pve.proxmox.com/wiki/Open_vSwitch#Bridges ...

openvswitch seems to be the solution for issue 1 and 2

I do have just kvm64 as CPU type and these messages too on proxmox 4.4

but I guess this will not change the behavior on the same host. cos proxmox create the vmbr250v1001 automatically and add eth3.250 to this bridge as soon as I set the vlan in the networking part of the vm network add bridge part

Me too ;-) Expectation would be that if a host which is connected to a vlan sub interface of an Ethernet if which is shared with a second vm would see all broadcast frames for this vlan. if host A connected to vmbr250v1001 send s a untagged frame, the frame will be tagged with 1001 as soon as...

HI, it took a while to get some idea about the issue.. Setup: Proxmox 4.4 a VM "router" with 2 network ifs. if1 - vmbr250 if2 - vmbr208 second vm "hostA" with single if if1 - vmbr250v1001 third vm "hostB" with single if if1 - vmbr250v1001 The router vm use internally vlans 1001 and 1002 and...

3526 IOPS on promox host if I use NFSv4 on the server

and it doesnt seem to be a kvm issue. Cos the proxHost measureresult is: 4663 IOPS (Random Seeks)

The recommendation from oracle is nfs v3 cos this lightweight nfs. this is also shown in benchmarks too. AND VMware also runs with nfsv3

So I did some bonnie++ compare. so vmware has much more random iops than kvm (random seeks and less CPU load) and vmware isnt touched at all just straight forward. both run with 4GB RAM and VirtIO Disk driver proxmox vm runs with harddrive writeback unsafe setting