Add more vpcus to Xpenology vm instance in Proxmox #408
Comments
|
Hello, I don't know what may be happening, but you can test with the CPU in "host". |
|
Some success? |
|
No; it's weird. When I have 2 vcpus, it seems to work fine but when I set it to 4, there is an endless boot. Here is the console output: [ 1.585690] <redpill/virtual_pci.c:420> Attempting to add vPCI device [printed below] @ bus=0c dev=00 fn=00 [ 63.174031] <redpill/bios_shim.c:215> Symbol #54 in mfgBIOS "broadwellnk_synobios" {synobios_event_ecc_notification} |
|
this issue should be fixed with latest patches and lkm "prod" |
|
Hi, I have updated to v1.0-beta13 but still no joy I'm afraid. Booting with 2 vcpus works fine but if I set it 4 it all goes horribly wrong. Here is dmesg excerpt: :: Loading module xhci-hcd ... [ OK ] |
do you use numa in proxmox? if yes disable it, don't know how but some of my guys are able to use it with 12 cores. CPU settig has to be "host" if not, nothing will work. do you use only 1 cpu? if yes all is fine, if not you have to set all the cores manually to 1 cpu. please look in bios for numa and memory remap. both should be disabled. and report back. one last thing, use the img as virtual usb stick in proxmox, this can solve the most problems. do not use it as sata disk. |
|
On this vm, I am not using numa. cpu setting is always 'host'. The host machine has only 1 cpu (i7-4770). I haven't heard of the 'memory remap' but a couple of other vm's are running no problem on the same machine. It breaks when I change 'cores' from 2 to 4. Here is my vm config: cat /etc/pve/qemu-server/2200.conf |
|
I removed the vgenid, smbios and mac address for the above config |
mount the loader disk as usb device and not on sata |
|
Hi. Is this a simple config change? Can you remind me how to let my disk image be seen as a usb device? Thanks for your help in trying to solve this. |
no can't tell you. you have to create an usb device and mount the img as this device. is working with the ui. but don't know the steps. |
|
No dice. I have changed my config to boot from a usb image but it changes nothing. Here is my new config: args: -drive 'if=none,id=synoboot,format=raw,file=/var/lib/vz/images/2200/arpl-current.img' -device 'qemu-xhci,addr=0x18' -device 'usb-storage,drive=synoboot,bootindex=5' It would be better to be able to use my original setup as this allows my to backup my config easily but I will keep it like this until I find a solution. |
please wait. i asked in my community for proxmox users. i hope someone can send me his config. |
|
I think I made some progress here. After that, it started working. On the left is the broken one with 4 cores added and the right is the working one with 4 cores Here are the logs This seems to be where things really go south. I hope this helps the devs get things working properly. |
So I am running a ds3622 (version 7.1.1-42962 Update 2) as a Proxmox VM and it works well.
Originally I gave it 2 vpcus but now I would like to increase that to something more (i.e. 6 like the original ds3622). However, when I set this in Proxmox, the vm fails fails to boot. I can see lots repeating segfaults in the serial terminal but it never finishes.
Do I need to rebuild the loader or something else? Most vm's are happy to accept a config change like this. I also would like to change from using the default kvm64 cpu model to 'host' (I am on an Intel i7-4770) Would that be ok to do as well?
Thanks very much for all the hard work!
The text was updated successfully, but these errors were encountered: