A QubesVM always has an empty DomainPool
- A DomainPool is initialized by QubesVM after Storage initialization on a `domain-load` event
This commit is contained in:
		
							parent
							
								
									ddf040ae64
								
							
						
					
					
						commit
						3f5a92772a
					
				| @ -51,6 +51,8 @@ import qubes.vm | ||||
| import qubes.vm.mix.net | ||||
| import qubes.tools.qvm_ls | ||||
| 
 | ||||
| from qubes.storage.domain import DomainPool | ||||
| 
 | ||||
| qmemman_present = False | ||||
| try: | ||||
|     import qubes.qmemman.client | ||||
| @ -516,6 +518,8 @@ class QubesVM(qubes.vm.mix.net.NetVMMixin, qubes.vm.BaseVM): | ||||
| 
 | ||||
|         # Initialize VM image storage class | ||||
|         self.storage = qubes.storage.Storage(self) | ||||
|         vm_pool = DomainPool(self) | ||||
|         self.app.pools[vm_pool.name] = vm_pool | ||||
| 
 | ||||
| 
 | ||||
|     @qubes.events.handler('property-set:label') | ||||
|  | ||||
		Loading…
	
		Reference in New Issue
	
	Block a user
	 Bahtiar `kalkin-` Gadimov
						Bahtiar `kalkin-` Gadimov